How can I configure OpenFusion CORBA services?

Product: OpenFusion CORBA Services

Version: ALL 

Description:

How can I configure OpenFusion CORBA services?

Resolution:

The OpenFusion services can be configured using the Administration Manager. The following command will bring up the Administration Manager as a pure configuration tool allowing the changing of configuration properties only, without the ability to start and stop the services:

manager -noorb

The adminMgrTool utility, available in the bin directory of the installation, can be used for configuration from the command line. The tool is started using the following command:

adminMgrTool

The following parameters can be used with the tool to provide different functionality:

-p Causes the tool to fully populate the XML configuration files.

-r <restore_name> Restores a named object in the Object Hierarchy. <restore_name> is a hierarchical name (using dots to separate the name components) which identifies the object to be restored. For example, to restore the NotificationService from the localhost node of the OpenFusion domain:

adminMgrTool -r OpenFusion.localhost.NotificationService

-d <node_name> Deletes a named object in the Object Hierarchy. <node_name> is a hierarchical name (using dots to separate the name components) which identifies the object to be deleted. For example, to delete the NotificationService from the localhost node of the OpenFusion domain:

adminMgrTool -d OpenFusion.localhost.NotificationService

-aDom <domain_name> Adds a Domain to the Object Hierarchy. For example the following adds a node to a domain, where <domain_name> is the name of the domain that the node will be added to:

adminMgrTool -aDom OpenFusion -aNode <domain_name> <node_name>

For example, the following adds the localhost node to the Openfusion domain:

adminMgrTool -aNode Openfusion localhost

-aServ <node_name> <service_name> Adds a Service to a node in the Object Hierarchy. <node_name> is a hierarchical name (using dots to separate the name components) which identifies the node that the Service will be added to. For example, the following adds NamingService to the localhost node of the OpenFusion domain:

adminMgrTool -aServ OpenFusion.localhost NameService

-aSing <service_name> <singleton_name> Adds a Singleton to a Service. <singleton_name> is a hierarchical name (using dots to separate the name components) which identifies the Service that the Singleton will be added to. For example, the following adds the NameSingleton to the NameService:

adminMgrTool -aSing OpenFusion.localhost.NameService NameSingleton

-aJO <service_name> <java_object_name> Adds a Java Object to a Service. <service_name> is a hierarchical name (using dots to separate the name components) which identifies the Service that the object will be added to. For example, the following adds the SNMPAgentObject to the NameService:

adminMgrTool -aJO OpenFusion,localhost.NameService SNMPAgentObject

-ap <object_name> <property_name> <new_property_value> Changes a property value for an object in the Object Hierarchy. <object_name> is a hierarchical name (using dots to separate the name components) which identifies the object. For example, the following changes the value of the Naming Service log4j.rootLogger property to "Debug":

adminMgrTool -ap OpenFusion.localhost.NameService log4j.rootLogger Debug

-dpv <object_name> <property_name> Displays a property value for an object in the Object Hierarchy. <object_name> is a hierarchical name (using dots to separate the name components) which identifies the object. <property_name> is the name of the property to be displayed. For example, the following displays the value of the Naming Service logging level property:

adminMgrTool -dpv OpenFusion.localhost.NameService log4j.rootLogger

-h -? -help These options are equivalent and print usage information for the tool.

A single command line can only include one parameter. So for example in order to add a domain, a node, and two Services to the Object Hierarchy, the Administration Manager tool must be invoked four times with a different object added in each invocation.

The Administration Manager tool must be invoked with the -p option before any Services can be started from the command line using the server - start script.