orbd − The Object Request Broker Daemon |
orbd is used to enable clients to transparently locate and invoke persistent objects on servers in the CORBA environment. See also: Naming Service |
orbd <options> |
The Server Manager included with the orbd tool is used to enable clients to transparently locate and invoke persistent objects on servers in the CORBA environment. The persistent servers, while publishing the persistent object references in the Naming Service, include the port number of the ORBD in the object reference instead of the port number of the Server. The inclusion of an ORBD port number in the object reference for persistent object references has the following advantages: |
o |
The object reference in the Naming Service remains independent of the server life cycle. For example, the object reference could be published by the server in the Naming Service when it is first installed, and then, independent of how many times the server is started or shutdown, the ORBD will always return the correct object reference to the invoking client. |
||
o |
The client needs to lookup the object reference in the Naming Service only once, and can keep re−using this reference independent of the changes introduced due to server life cycle. |
To access ORBD’s Server Manager, the server must be started using servertool, which is a command−line interface for application programmers to register, unregister, startup, and shutdown a persistent server. For more information on the Server Manager, see the section in this document titled Server Manager. When orbd starts up, it also starts a naming service. For more information on the naming service, link to Naming Service. |
Required Options |
−ORBInitialPort nameserverport |
Specifies the port on which the name server should be started. Once started, orbd will listen for incoming requests on this port. Note that when using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024. (required) |
OTHER OPTIONS |
−port port |
Specifies the activation port where ORBD should be started, and where ORBD will be accepting requests for persistent objects. The default value for this port is 1049. This port number is added to the port field of the persistent Interoperable Object References (IOR). (optional) |
−defaultdb directory |
Specifies the base where the ORBD persistent storage directory orb.db is created. If this option is not specified, the default value is "./orb.db". (optional) |
−serverPollingTime milliseconds |
Specifies how often ORBD checks for the health of persistent servers registered via servertool. The default value is 1,000 ms. The value specified for milliseconds must be a valid positive integer. (optional) |
−serverStartupDelay milliseconds |
Specifies how long ORBD waits before sending a location forward exception after a persistent server that is registered via servertool is restarted. The default value is 1,000 ms. The value specified for milliseconds must be a valid positive integer. (optional) |
−Joption |
Pass option to the Java virtual machine, where option is one of the options described on the reference page for the java application launcher. For example, −J−Xms48m sets the startup memory to 48 megabytes. It is a common convention for −J to pass options to the underlying virtual machine. |