source: arduino-1-6-7/trunk/fuentes/arduino-ide-amd64/java/man/man1/orbd.1 @ 4837

Last change on this file since 4837 was 4837, checked in by daduve, 2 years ago

Adding new version

File size: 11.9 KB
Line 
1'\" t
2.\"  Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved.
3.\"     Arch: generic
4.\"     Software: JDK 8
5.\"     Date: 21 November 2013
6.\"     SectDesc: Java IDL and RMI-IIOP Tools
7.\"     Title: orbd.1
8.\"
9.if n .pl 99999
10.TH orbd 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools"
11.\" -----------------------------------------------------------------
12.\" * Define some portability stuff
13.\" -----------------------------------------------------------------
14.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15.\" http://bugs.debian.org/507673
16.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18.ie \n(.g .ds Aq \(aq
19.el       .ds Aq '
20.\" -----------------------------------------------------------------
21.\" * set default formatting
22.\" -----------------------------------------------------------------
23.\" disable hyphenation
24.nh
25.\" disable justification (adjust text to left margin only)
26.ad l
27.\" -----------------------------------------------------------------
28.\" * MAIN CONTENT STARTS HERE *
29.\" -----------------------------------------------------------------
30
31.SH NAME   
32orbd \- Enables clients to locate and call persistent objects on servers in the CORBA environment\&.
33.SH SYNOPSIS   
34.sp     
35.nf     
36
37\fBorbd\fR [ \fIoptions\fR ]
38.fi     
39.sp     
40.TP     
41\fIoptions\fR
42Command-line options\&. See Options\&.
43.SH DESCRIPTION   
44The \f3orbd\fR command enables clients to transparently locate and call persistent objects on servers in the CORBA environment\&. The Server Manager included with the orbd tool is used to enable clients to transparently locate and call 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:
45.TP 0.2i   
46\(bu
47The 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 shut down, the ORBD returns the correct object reference to the calling client\&.
48.TP 0.2i   
49\(bu
50The client needs to look up the object reference in the naming service only once, and can keep reusing this reference independent of the changes introduced due to server life cycle\&.
51.PP
52To access the ORBD Server Manager, the server must be started using \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. For more information on the Server Manager, see Server Manager\&.
53.PP
54When \f3orbd\fR starts, it also starts a naming service\&. For more information about the naming service\&. See Start and Stop the Naming Service\&.
55.SH OPTIONS   
56.TP
57-ORBInitialPort \fInameserverport\fR
58.br
59Required\&. Specifies the port on which the name server should be started\&. After it is started, \f3orbd\fR listens for incoming requests on this port\&. On Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, Oracle recommends that you use a port number above or equal to 1024\&.
60.SS NONREQUIRED\ OPTIONS   
61.TP
62-port \fIport\fR
63.br
64Specifies 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)\&.
65.TP
66-defaultdb \fIdirectory\fR
67.br
68Specifies the base where the ORBD persistent storage directory, \f3orb\&.db\fR, is created\&. If this option is not specified, then the default value is \f3\&./orb\&.db\fR\&.
69.TP
70-serverPollingTime \fImilliseconds\fR
71.br
72Specifies how often ORBD checks for the health of persistent servers registered through \f3servertool\fR\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&.
73.TP
74-serverStartupDelay milliseconds
75.br
76Specifies how long ORBD waits before sending a location forward exception after a persistent server that is registered through \f3servertool\fR is restarted\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&.
77.TP
78-J\fIoption\fR
79.br
80Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
81.SS START\ AND\ STOP\ THE\ NAMING\ SERVICE   
82A 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\&.
83.PP
84Before 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\&.
85.PP
86The 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)\&.
87.PP
88For backward compatibility, \f3tnameserv\fR, 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\&.
89.PP
90The \f3-ORBInitialPort\fR argument is a required command-line argument for \f3orbd\fR, 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\&.
91.PP
92To start \f3orbd\fR from a UNIX command shell, enter:
93.sp     
94.nf     
95\f3orbd \-ORBInitialPort 1050&\fP
96.fi     
97.nf     
98\f3\fP
99.fi     
100.sp     
101From an MS-DOS system prompt (Windows), enter:
102.sp     
103.nf     
104\f3start orbd \-ORBInitialPort 1050\fP
105.fi     
106.nf     
107\f3\fP
108.fi     
109.sp     
110Now 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, when applicable) where the Naming Service is running\&. One way to do this is to add the following code to your application:
111.sp     
112.nf     
113\f3Properties props = new Properties();\fP
114.fi     
115.nf     
116\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
117.fi     
118.nf     
119\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialHost", "MyHost");\fP
120.fi     
121.nf     
122\f3ORB orb = ORB\&.init(args, props);\fP
123.fi     
124.nf     
125\f3\fP
126.fi     
127.sp     
128In this example, the naming service is running on port 1050 on host \f3MyHost\fR\&. 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 \f3HelloApplication\fR with the following command line:
129.sp     
130.nf     
131\f3java HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost\fP
132.fi     
133.nf     
134\f3\fP
135.fi     
136.sp     
137To stop the naming service, use the relevant operating system command, such as \f3pkill\fR\f3orbd\fR on Oracle Solaris, or \fICtrl+C\fR in the DOS window in which \f3orbd\fR is running\&. Note that names registered with the naming service can disappear when the service is terminated because of a transient naming service\&. The Java IDL naming service will run until it is explicitly stopped\&.
138.PP
139For more information about the naming service included with ORBD, see Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
140.SH SERVER\ MANAGER   
141To access the ORBD Server Manager and run a persistent server, the server must be started with \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. When a server is started using \f3servertool\fR, it must be started on the same host and port on which \f3orbd\fR is executing\&. If the server is run on a different port, then the information stored in the database for local contexts will be invalid and the service will not work properly\&.
142.PP
143See Java IDL: The "Hello World" Example at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlExample\&.html
144.PP
145In this example, you run the \f3idlj\fR compiler and \f3javac\fR compiler as shown in the tutorial\&. To run the ORBD Server Manager, follow these steps for running the application:
146.PP
147Start \f3orbd\fR\&.
148.PP
149UNIX command shell, enter: \f3orbd -ORBInitialPort 1050\fR\&.
150.PP
151MS-DOS system prompt (Windows), enter: \f3s\fR\f3tart orbd -ORBInitialPort 105\fR\f30\fR\&.
152.PP
153Port 1050 is the port on which you want the name server to run\&. The \f3-ORBInitialPort\fR option is a required command-line argument\&. When using Oracle Solaris software, you must become a root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number above or equal to 1024\&.
154.PP
155Start the \f3servertool\fR: \f3servertool -ORBInitialPort 1050\fR\&.
156.PP
157Make sure the name server (\f3orbd\fR) port is the same as in the previous step, for example, \f3-ORBInitialPort 1050\&.\fR The \f3servertool\fR must be started on the same port as the name server\&.
158.PP
159In the \f3servertool\fR command line interface, start the \f3Hello\fR server from the \f3servertool\fR prompt:
160.sp     
161.nf     
162\f3servertool  > register \-server HelloServer \-classpath \&. \-applicationName\fP
163.fi     
164.nf     
165\f3                HelloServerApName\fP
166.fi     
167.nf     
168\f3\fP
169.fi     
170.sp     
171The \f3servertool\fR registers the server, assigns it the name \f3HelloServerApName\fR, and displays its server ID with a listing of all registered servers\&.Run the client application from another terminal window or prompt:
172.sp     
173.nf     
174\f3java HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost\fP
175.fi     
176.nf     
177\f3\fP
178.fi     
179.sp     
180For this example, you can omit \f3-ORBInitialHost localhost\fR because the name server is running on the same host as the \f3Hello\fR client\&. If the name server is running on a different host, then use the -\f3ORBInitialHost nameserverhost\fR option to specify the host on which the IDL name server is running\&.Specify the name server (\f3orbd\fR) port as done in the previous step, for example, \f3-ORBInitialPort 1050\fR\&. When you finish experimenting with the ORBD Server Manager, be sure to shut down or terminate the name server (\f3orbd\fR) and \f3servertool\fR\&. To shut down \f3orbd\fR from am MS-DOS prompt, select the window that is running the server and enter \fICtrl+C\fR to shut it down\&.
181.PP
182To shut down \f3orbd\fR from an Oracle Solaris shell, find the process, and terminate with the \f3kill\fR command\&. The server continues to wait for invocations until it is explicitly stopped\&. To shut down the \f3servertool\fR, type \fIquit\fR and press the \fIEnter\fR key\&.
183.SH SEE\ ALSO   
184.TP 0.2i   
185\(bu
186servertool(1)
187.TP 0.2i   
188\(bu
189Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
190.RE
191.br
192'pl 8.5i
193'bp
Note: See TracBrowser for help on using the repository browser.