blob: 489319bf5eb4f5af9a3c7aea9de7cbde37ceb107 [file] [log] [blame]
J. Duke319a3b92007-12-01 00:00:00 +00001.'" t
2."
3." Copyright 2000-2006 Sun Microsystems, Inc. All Rights Reserved.
4." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
5."
6." This code is free software; you can redistribute it and/or modify it
7." under the terms of the GNU General Public License version 2 only, as
8." published by the Free Software Foundation.
9."
10." This code is distributed in the hope that it will be useful, but WITHOUT
11." ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
12." FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
13." version 2 for more details (a copy is included in the LICENSE file that
14." accompanied this code).
15."
16." You should have received a copy of the GNU General Public License version
17." 2 along with this work; if not, write to the Free Software Foundation,
18." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
19."
20." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
21." CA 95054 USA or visit www.sun.com if you need additional information or
22." have any questions.
23."
24." `
25.TH rmiregistry 1 "05 Aug 2006"
26." Generated by html2roff
27
28.LP
29.SH NAME
30rmiregistry \- The Java Remote Object Registry
31.LP
32
33.LP
34.LP
35The \f3rmiregistry\fP command starts a remote object registry on the specified port on the current host.
36.LP
37.SH "SYNOPSIS"
38.LP
39
40.LP
41.nf
42\f3
43.fl
44rmiregistry [\fP\f4port\fP\f3]
45.fl
46\fP
47.fi
48
49.LP
50.SH "DESCRIPTION"
51.LP
52
53.LP
54.LP
55The \f3rmiregistry\fP command creates and starts a remote object registry on the specified \f2port\fP on the current host. If \f2port\fP is omitted, the registry is started on port 1099. The \f3rmiregistry\fP command produces no output and is typically run in the background. For example:
56.LP
57.LP
58\f2rmiregistry &\fP
59.LP
60.LP
61A remote object registry is a bootstrap naming service that is used by RMI servers on the same host to bind remote objects to names. Clients on local and remote hosts can then look up remote objects and make remote method invocations.
62.LP
63.LP
64The registry is typically used to locate the first remote object on which an application needs to invoke methods. That object in turn will provide application\-specific support for finding other objects.
65.LP
66.LP
67The methods of the \f2java.rmi.registry.LocateRegistry\fP class are used to get a registry operating on the local host or local host and port.
68.LP
69.LP
70The URL\-based methods of the \f2java.rmi.Naming\fP class operate on a registry and can be used to look up a remote object on any host, and on the local host: bind a simple (string) name to a remote object, rebind a new name to a remote object (overriding the old binding), unbind a remote object, and list the URLs bound in the registry.
71.LP
72.SH "OPTIONS"
73.LP
74
75.LP
76.TP 3
77\-J
78Used in conjunction with any \f2java\fP option, it passes the option following the \f2\-J\fP (no spaces between the \-J and the option) on to the \f2java\fP interpreter.
79.LP
80.SH "SEE ALSO"
81.LP
82
83.LP
84.LP
85java,
86.na
87\f2java.rmi.registry.LocateRegistry\fP @
88.fi
89http://java.sun.com/javase/6/docs/api/java/rmi/registry/locateregistry.html and
90.na
91\f2java.rmi.Naming\fP @
92.fi
93http://java.sun.com/javase/6/docs/api/java/rmi/naming.html
94.LP
95
96.LP
97