Name¶

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 @
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html

SYNOPSIS¶

orbd <options>

DESCRIPTION¶

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:

To access ORBD's Server Manager, the server must be started using servertool(1), 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 @
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html.

OPTIONS¶

Starting and Stopping the Naming Service¶

A Naming Service is a CORBA service that allows CORBA objects @
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlGlossary.html#CORBA%20object to be named by means of binding a name to an object reference. The name binding @
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlGlossary.html#name%20binding may be stored in the naming service, and a client may supply the name to obtain the desired object reference.

Prior to running a client or a server, you will start ORBD. ORBD includes a persistent Naming Service and a transient Naming Service, both of which are an implementation of the COS Naming Service.

The Persistent Naming Service provides persistence for naming contexts. This means that this information is persistent across service shutdowns and startups, and is recoverable in the event of a service failure. If ORBD is restarted, the Persistent Naming Service will restore the naming context graph, so that the binding of all clients' and servers' names remains intact (persistent).

For backward compatibility, tnameserv, a Transient Naming Service shipped with older versions of the JDK, is also included in this release of J2SE. A transient naming service retains naming contexts as long as it is running. If there is a service interruption, the naming context graph is lost.

The -ORBInitialPort argument is a required command-line argument for orbd, and is used to set the port number on which the Naming Service will run. The following instructions assume you can use port 1050 for the Java IDL Object Request Broker Daemon. 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. You can substitute a different port if necessary.

To start orbd from a UNIX command shell, enter:

  orbd -ORBInitialPort 1050&

From an MS-DOS system prompt (Windows), enter:

  start orbd -ORBInitialPort 1050

Now that ORBD is running, you can run your server and client applications. When running the client and server applications, they must be made aware of the port number (and machine name, if applicable) where the Naming Service is running. One way to do this is to add the following code to your application:

        Properties props = new Properties();


        props.put("org.omg.CORBA.ORBInitialPort", "1050");


        props.put("org.omg.CORBA.ORBInitialHost", "MyHost");


        ORB orb = ORB.init(args, props);

In this example, the Naming Service is running on port 1050 on host "MyHost". Another way is to specify the port number and/or machine name when running the server or client application from the command line. For example, you would start your "HelloApplication" with the following command line:

     java HelloApplication -ORBInitialPort 1050 -ORBInitialHost MyHost

To stop the naming service, use the relevant operating system command, such as pkill orbd on Solaris, or Ctrl+C in the DOS window in which orbd is running. Note that names registered with the naming service may disappear when the service is terminated if the naming service is transient. The Java IDL naming service will run until it is explicitly stopped.

For more information on the Naming Service included with ORBD, see Naming Service @
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html.

Server Manager¶

To access ORBD's Server Manager and run a persistent server, the server must be started using servertool(1), which is a command-line interface for application programmers to register, unregister, startup, and shutdown a persistent server. When a server is started using servertool, it must be started on the same host and port on which orbd is executing. If the server is run on a different port, the information stored in the database for local contexts will be invalid and the service will not work properly.

  orbd -ORBInitialPort 1050 

  start orbd -ORBInitialPort 1050

  servertool -ORBInitialPort 1050

  servertool  > register -server HelloServer -classpath . -applicationName


                HelloServerApName

  java HelloClient -ORBInitialPort 1050 -ORBInitialHost localhost

See Also¶