{ "mode": "man", "parameter": "orbd", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/orbd/1/json", "generated": "2026-10-22T12:01:34Z", "synopsis": "orbd [ options ]\noptions\nCommand-line options. See Options.", "sections": { "NAME": { "content": "orbd - Enables clients to locate and call persistent objects on servers in the CORBA\nenvironment.\n", "subsections": [] }, "SYNOPSIS": { "content": "orbd [ options ]\n\n\noptions\nCommand-line options. See Options.\n", "subsections": [] }, "DESCRIPTION": { "content": "The orbd command enables clients to transparently locate and call persistent objects on\nservers in the CORBA environment. The Server Manager included with the orbd tool is used to\nenable clients to transparently locate and call persistent objects on servers in the CORBA\nenvironment. The persistent servers, while publishing the persistent object references in the\nnaming service, include the port number of the ORBD in the object reference instead of the\nport number of the server. The inclusion of an ORBD port number in the object reference for\npersistent object references has the following advantages:\n\n• The object reference in the naming service remains independent of the server life cycle.\nFor example, the object reference could be published by the server in the Naming Service\nwhen it is first installed, and then, independent of how many times the server is started\nor shut down, the ORBD returns the correct object reference to the calling client.\n\n• The client needs to look up the object reference in the naming service only once, and can\nkeep reusing this reference independent of the changes introduced due to server life cycle.\n\nTo access the ORBD Server Manager, the server must be started using servertool, which is a\ncommand-line interface for application programmers to register, unregister, start up, and\nshut down a persistent server. For more information on the Server Manager, see Server\nManager.\n\nWhen orbd starts, it also starts a naming service. For more information about the naming\nservice. See Start and Stop the Naming Service.\n", "subsections": [] }, "OPTIONS": { "content": "-ORBInitialPort nameserverport\nRequired. Specifies the port on which the name server should be started. After it is\nstarted, orbd listens for incoming requests on this port. On Oracle Solaris software,\nyou must become the root user to start a process on a port below 1024. For this\nreason, Oracle recommends that you use a port number above or equal to 1024.\n\nNONREQUIRED OPTIONS\n-port port\nSpecifies the activation port where ORBD should be started, and where ORBD will be\naccepting requests for persistent objects. The default value for this port is 1049.\nThis port number is added to the port field of the persistent Interoperable Object\nReferences (IOR).\n\n-defaultdb directory\nSpecifies the base where the ORBD persistent storage directory, orb.db, is created. If\nthis option is not specified, then the default value is ./orb.db.\n\n-serverPollingTime milliseconds\nSpecifies how often ORBD checks for the health of persistent servers registered\nthrough servertool. The default value is 1000 ms. The value specified for milliseconds\nmust be a valid positive integer.\n\n-serverStartupDelay milliseconds\nSpecifies how long ORBD waits before sending a location forward exception after a\npersistent server that is registered through servertool is restarted. The default\nvalue is 1000 ms. The value specified for milliseconds must be a valid positive\ninteger.\n", "subsections": [ { "name": "-J_option_", "content": "Passes option to the Java Virtual Machine, where option is one of the options\ndescribed on the reference page for the Java application launcher. For example, -J-\nXms48m sets the startup memory to 48 MB. See java(1).\n\nSTART AND STOP THE NAMING SERVICE\nA naming service is a CORBA service that allows CORBA objects to be named by means of binding\na name to an object reference. The name binding can be stored in the naming service, and a\nclient can supply the name to obtain the desired object reference.\n\nBefore running a client or a server, you will start ORBD. ORBD includes a persistent naming\nservice and a transient naming service, both of which are an implementation of the COS Naming\nService.\n\nThe Persistent Naming Service provides persistence for naming contexts. This means that this\ninformation is persistent across service shutdowns and startups, and is recoverable in the\nevent of a service failure. If ORBD is restarted, then the Persistent Naming Service restores\nthe naming context graph, so that the binding of all clients' and servers' names remains\nintact (persistent).\n\nFor backward compatibility, tnameserv, a Transient Naming Service that shipped with earlier\nreleases of the JDK, is also included in this release of Java SE. A transient naming service\nretains naming contexts as long as it is running. If there is a service interruption, then\nthe naming context graph is lost.\n\nThe -ORBInitialPort argument is a required command-line argument for orbd, and is used to set\nthe port number on which the naming service runs. The following instructions assume you can\nuse port 1050 for the Java IDL Object Request Broker Daemon. When using Oracle Solaris\nsoftware, you must become a root user to start a process on a port lower than 1024. For this\nreason, it is recommended that you use a port number above or equal to 1024. You can\nsubstitute a different port when necessary.\n\nTo start orbd from a UNIX command shell, enter:\n" }, { "name": "orbd -ORBInitialPort 1050&", "content": "From an MS-DOS system prompt (Windows), enter:\n" }, { "name": "start orbd -ORBInitialPort 1050", "content": "Now that ORBD is running, you can run your server and client applications. When running the\nclient and server applications, they must be made aware of the port number (and machine name,\nwhen applicable) where the Naming Service is running. One way to do this is to add the\nfollowing code to your application:\n" }, { "name": "Properties props = new Properties();", "content": "" }, { "name": "props.put(\"org.omg.CORBA.ORBInitialPort\", \"1050\");", "content": "" }, { "name": "props.put(\"org.omg.CORBA.ORBInitialHost\", \"MyHost\");", "content": "" }, { "name": "ORB orb = ORB.init(args, props);", "content": "In this example, the naming service is running on port 1050 on host MyHost. Another way is to\nspecify the port number and/or machine name when running the server or client application\nfrom the command line. For example, you would start your HelloApplication with the following\ncommand line:\n" }, { "name": "java HelloApplication -ORBInitialPort 1050 -ORBInitialHost MyHost", "content": "To stop the naming service, use the relevant operating system command, such as pkillorbd on\nOracle Solaris, or Ctrl+C in the DOS window in which orbd is running. Note that names\nregistered with the naming service can disappear when the service is terminated because of a\ntransient naming service. The Java IDL naming service will run until it is explicitly\nstopped.\n\nFor more information about the naming service included with ORBD, see Naming Service at\nhttp://docs.oracle.com/javase/8/docs/technotes/guides/idl/jidlNaming.html\n" } ] }, "SERVER MANAGER": { "content": "To access the ORBD Server Manager and run a persistent server, the server must be started\nwith servertool, which is a command-line interface for application programmers to register,\nunregister, start up, and shut down a persistent server. When a server is started using\nservertool, it must be started on the same host and port on which orbd is executing. If the\nserver is run on a different port, then the information stored in the database for local\ncontexts will be invalid and the service will not work properly.\n\nSee Java IDL: The \"Hello World\" Example at\nhttp://docs.oracle.com/javase/8/docs/technotes/guides/idl/jidlExample.html\n\nIn this example, you run the idlj compiler and javac compiler as shown in the tutorial. To\nrun the ORBD Server Manager, follow these steps for running the application:\n\nStart orbd.\n\nUNIX command shell, enter: orbd -ORBInitialPort 1050.\n\nMS-DOS system prompt (Windows), enter: start orbd -ORBInitialPort 1050.\n\nPort 1050 is the port on which you want the name server to run. The -ORBInitialPort option is\na required command-line argument. When using Oracle Solaris software, you must become a root\nuser to start a process on a port below 1024. For this reason, it is recommended that you use\na port number above or equal to 1024.\n\nStart the servertool: servertool -ORBInitialPort 1050.\n\nMake sure the name server (orbd) port is the same as in the previous step, for example,", "subsections": [ { "name": "-ORBInitialPort 1050.", "content": "In the servertool command line interface, start the Hello server from the servertool prompt:\n" }, { "name": "servertool > register -server HelloServer -classpath . -applicationName", "content": "HelloServerApName\n\nThe servertool registers the server, assigns it the name HelloServerApName, and displays its\nserver ID with a listing of all registered servers.Run the client application from another\nterminal window or prompt:\n" }, { "name": "java HelloClient -ORBInitialPort 1050 -ORBInitialHost localhost", "content": "For this example, you can omit -ORBInitialHost localhost because the name server is running\non the same host as the Hello client. If the name server is running on a different host, then\nuse the -ORBInitialHost nameserverhost option to specify the host on which the IDL name\nserver is running.Specify the name server (orbd) port as done in the previous step, for\nexample, -ORBInitialPort 1050. When you finish experimenting with the ORBD Server Manager, be\nsure to shut down or terminate the name server (orbd) and servertool. To shut down orbd from\nam MS-DOS prompt, select the window that is running the server and enter Ctrl+C to shut it\ndown.\n\nTo shut down orbd from an Oracle Solaris shell, find the process, and terminate with the kill\ncommand. The server continues to wait for invocations until it is explicitly stopped. To shut\ndown the servertool, type quit and press the Enter key.\n" } ] }, "SEE ALSO": { "content": "• servertool(1)\n\n• Naming Service at http://docs.oracle.com/javase/8/docs/technotes/guides/idl/jidlNaming.html\n\nJDK 8 21 November 2013 orbd(1)", "subsections": [] } }, "summary": "orbd - Enables clients to locate and call persistent objects on servers in the CORBA environment.", "flags": [ { "flag": "", "long": null, "arg": null, "description": "Passes 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 MB. See java(1). START AND STOP THE NAMING SERVICE A naming service is a CORBA service that allows CORBA objects to be named by means of binding a name to an object reference. The name binding can be stored in the naming service, and a client can supply the name to obtain the desired object reference. Before 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, then the Persistent Naming Service restores 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 that shipped with earlier releases of the JDK, is also included in this release of Java SE. A transient naming service retains naming contexts as long as it is running. If there is a service interruption, then 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 runs. The following instructions assume you can use port 1050 for the Java IDL Object Request Broker Daemon. When using Oracle Solaris software, you must become a root user to start a process on a port lower than 1024. For this reason, it is recommended that you use a port number above or equal to 1024. You can substitute a different port when necessary. To start orbd from a UNIX command shell, enter:" } ], "examples": [], "see_also": [ { "name": "servertool", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/servertool/1/json" } ] }