11-106
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 11 XML Transport and Event Notifications
Cisco CRS-1 Series XML Transport and CORBA IDL
CORBA NameServer
The NameServer is used by client applications to obtain the interface object request (IOR) of the
CORBA XML agent object. In order to make the IOR available to clients, the CORBA XML agent
exports it to the NameServer upon startup.
The CORBA Naming Service stores a name with each object reference and provides a hierarchical
namespace to allow server implementers to logically organize the IORs of the objects that they export.
Naming Contexts are CORBA objects within the Naming Service. There are several operations and
methods defined in the naming context IDL. The most commonly used of these are "bind()" and
"resolve()". Servers export IORs in a particular naming context by using the "bind()" operation,
specifying the name of the object being exported along with the corresponding IOR. Clients then use the
"resolve()" operation to obtain the IOR corresponding to a particular name.
Client Access to the Root Naming Context
The standard mechanism for finding the Naming Service and obtaining the root Naming Context is the
“resolve_initial_references()” API. This API makes use of proprietary mechanisms to contact the
Naming Service and extract the root naming context. Generally, this involves having the environment
previously configured with the host on which the name server is running, the port ID, and so on.
The client application can connect to the Naming Service running on the Cisco CRS-1 Series router
using a Domain Name Server (DNS) configured router name or via the Naming Service IOR as follows:
client -ORBInitRef NameService=iioploc://<router_name>:10001/NameService
client -ORBInitRef NameService=file://<IOR file>
If CORBA is used with SSL, then the IOR method of contacting to the Naming Service must be used
along with a service configurator file:
client -ORBInitRef NameService=file://<IOR file> -ORBSvcConf <config file>
Here the service configurator file would contain the SSL variable definitions, for example:
static SSLIOP_Factory "-SSLAuthenticate NONE -SSLPrivateKey
PEM:server_key.pem -SSLCertificate PEM:server_cert.pem"
static Resource_Factory "-ORBProtocolFactory SSLIOP_Factory"
The Naming Service IOR file can be obtained from the router via HTTP at:
https://<router-name>/cwi/ns_ssl.ior
Note Connection to the Naming Service via an IP address is not supported.
LR Name Server Tree
The name hierarchy for the Cisco CRS-1 Series router is shown in Figure 11-1. The root naming context
identifies the particular logical router (LR) on which the Name Server is running. Within the root context
is the list of object references that components within the LR have exported.