Previous | Naming Service Manager | Next |
The Naming Service Manager shows the naming hierarchy as a graphical tree view
The object is labelled with its Id and/or Kind (if specified), in one of the following formats:
An object's IOR can be selected in the properties pane and copied to the clipboard.
Different objects in the Naming Service Manager are identified by different icons in the tree view.
The Naming Service Manager adds new buttons to the tool bar. These buttons are only available when the Naming Service Manager is active.The buttons are disabled if a leaf node or an invalid naming context is selected in the naming hierarchy.
A new naming context must be added as a child of an existing naming context (or the root context) in the naming hierarchy. A naming context cannot be added as a child of a bound CORBA or non-CORBA object.
To add a new naming context to the naming hierarchy:
The new naming context is added to the naming hierarchy as a child of the selected parent naming context.
When a Service is started in the Administration Manager, each of its Singletons will attempt to bind to the Naming Service if it is configured to do so (see below), and if the Naming Service is running when the Service starts.
This occurs each time the Service is started. (Persistent objects remain registered when the Service is stopped, with a Status of Inactive/Persistent.) If the bind is successful, entries for the Singletons are added to the Naming Service Manager hierarchy. To see any newly-started objects, right-click on the root node of the Naming Service Manager and select Refresh Node from the pop-up menu.
OpenFusion Singletons that register themselves in this way are bound directly under the Naming Service root context.
If a Singleton is to register itself with a running Naming Service when it is started, it must be configured to do so, as follows:
An object must be added as a child of an existing naming context (or the root context) in the naming hierarchy. An object cannot be added as a child of a bound CORBA or non-CORBA object (bound objects are always leaf nodes in the hierarchy).
An object's IOR is used to bind the object into the naming hierarchy. The IOR of an existing object must be copied to the clipboard before the object can be bound into the naming context. See The CORBA Object Browser for details of querying objects in the Object Browser and copying the object's IOR to the clipboard.
Once the required object's IOR is copied, follow these steps to bind the object:
The new object is added to the naming hierarchy as a child of the selected parent naming context.
It is possible to bind a naming context object as either an object or a naming context. If it is bound as an object, it becomes a leaf node and will not be used for name resolution.
To delete a naming context or object binding from the naming hierarchy, right-click on the node and select Delete from the pop-up menu. Click the DELETE button in the Warning dialog box.
Deleting an object binding will not remove the underlying object; only its resolution through the Naming Service will be affected.
When a naming context is deleted, all of its children (naming contexts and object bindings) are also removed from the hierarchy.
Any portion of the naming hierarchy can be exported to an XML file.
The XML Export will fail if the tree being exported contains any invalid naming contexts.
The XML export can also be performed from the command line. The command line method is preferred when dealing with very large naming hierarchies (where the export operation may take a considerable time).
An XML file containing a previously-exported section of the naming hierarchy can be re-imported into the naming hierarchy.
The imported branch of the naming hierarchy must be added to an existing naming context node.
As an exported branch of the naming hierarchy can be imported into a completely different location, this is a convenient way to move or replicate large sections of the naming hierarchy
The contents of the imported file are added to the naming hierarchy in the selected location.
The XML import can also be performed from the command line. The command line method is preferred when dealing with very large naming hierarchies (where the import operation may take a considerable time).
Other OpenFusion graphical tools can be launched from the Naming Service Manager.
The right-click menu options of each object in the naming hierarchy include options for launching browsers and managers specific to that object.
For example, a bound NotificationSingleton object has a menu option to launch the Notification Service Manager.
All nodes include an option to launch the CORBA Object Browser. See The CORBA Object Browser for details. The CORBA Object Browser can be used to view naming contexts as well as CORBA objects.
Naming contexts include an option to launch a new instance of the Naming Service Manager. The new instance is rooted at the selected naming context.
This is not a new instance of the Naming Service. The new manager is simply a new view of the selected portion of the Naming Service.
Previous | Naming Service Manager | Next |