Using the Provisioning Service
The NMC-RX Provisioning Service registers with the CORBA Naming Service by using a configurable name. This is the name that the CORBA client (NMS client) program uses to find the CORBA reference from the CORBA Naming Service. For example:
JUNIPER_NMCRX_TMF814_EMSSESSIONFACTORY_8384
This name comprises three parts:
- JUNIPER_NMCRX—Identifies the EMS of the vendor.
- TMF814_EMSSESSIONFACTORY—Refers to the TMF.814 EMS Session Factory object, which is the entry object for the NMS client to access the EMS.
- 8384—Specifies the port on which the remote method invocation (RMI) server is running.
You can change the first part of the name, JUNIPER_NMCRX, and the port number, 8384, by modifying the provisioningserver.rc file in the <NMC-RX_HOME> directory. The NMS client then retrieves the NMC-RX provisioning server entry reference emsSessionFactory.idl by looking up this name from the CORBA name server.
The standard Interface Definition Language (IDL) emsSessionFactory.idl is the primary class that the NMS communicates with and acts as the focal point for gaining access to managed elements. From the standard IDL emsSession.idl a programmer can get a specific unspRXDeviceMgr.idl to perform inquiries and actions against a specific device. When a particular handle to a device is formed, all operations on that device are achieved by means of the unspRXDeviceMgr.idl when you use the appropriate action and object paths.
The other proprietary IDL, unspRXCustomerMgr.idl, is very similar to unspRXDeviceMgr.idl; however, unspRXCustomerMgr.idl applies to the EMS level and does not apply to devices. For unspRXCustomerMgr.idl, do not set the ManagedElement object when you configure the object path.
Figure 8 illustrates the process of accessing E-series router objects and provides a listing of the objects supported in this release.
