'\" t
.\" @(#)rmid.1 1.2 97/06/21 SMI;
.\" Copyright 1999 Sun Microsystems, Inc. All rights reserved.
.\" Copyright 1999 Sun Microsystems, Inc. Tous droits réservés.
.\" 
.TH rmid 1 "18 Feb 1999"
.SH NAME
rmid \- RMI activation system daemon
.SH SYNOPSIS
.B rmid 
[
.BI \-C " command-line-option"
]
[
.BI \-log  " dir" 
] [
.BI \-port " port" 
] 
.if n .ti 10
[
.B \-stop
]
.SH DESCRIPTION
.IX "RMI activation system daemon" "" "RMI activation system daemon \(em \fLrmid\fP"
.IX "rmid" "" "\fLrmid\fP \(em RMI activation system daemon"
The
.B rmid 
tool starts the activation system daemon. Before
activatable objects can be either registered with the activation
system or activated in a Java VM, the activation system daemon
must be started. See the RMI Specification for details on how to
write programs that use activatable remote objects. The daemon can
be started by executing the rmid command with no options, as
follows:
.LP
.ft 3
.nf
example% rmid
.fi
.ft 1
.LP
starts the Activator and an internal registry on the default port
of 1098, and binds an 
.B ActivationSystem 
with the name
.B java.rmi.activation.ActivationSystem 
in this internal registry. To
specify an alternate port for the registry, you must specify the
.B -port 
option when starting up
.BR rmid , 
for example:
.LP
.ft 3
.nf
example% rmid -port 1099
.fi
.ft 1
.LP
starts the activation system daemon and a registry on the
registry's default port of 1099.
.LP
.SH OPTIONS
.TP
.BI \-C " command-line-option"
Specifies an option that is passed as a command line option
to each child process (activation group) of 
.B rmid 
when that
process is created. 
The 
.I command-line-option 
is any option that the "command" will accept when 
.B rmid
starts up
the group using the "command".  By default the command to start up the
group
is 
.BR javac (1), so any 
.BR javac (1)
option is okay.  The application can specify
that the
command can be other than 
.BR javac (1)
by specifying a
.B ActivationGroup.CommandEnvironment 
when registering an activation
group.
.LP
To pass a property to
each Java Virtual Machine spawned by the activation system
daemon:
.LP
.RS
.ft 3
.nf
example% rmid -C-Dsome.property=value
.fi
.ft 1
This ability to pass command line options to child
processes can be useful for debugging. For example, the
following command:
.LP
.ft 3
.nf
example% rmid -C-Djava.rmi.server.logCalls=true
.fi
.ft 1
will enable server-call logging in all child Java Virtual
Machines.
.RE
.TP
.BI \-log  " dir"
Specifies the name of the directory the activation system
daemon uses to write its database and associated information.
The log directory defaults to creating a directory, log, in
the directory in which the 
.B rmid 
command was executed.
.TP
.BI \-port " port" 
Specifies the 
.I port 
the registry of rmid uses. The activation
system daemon binds the 
.BR ActivationSystem , 
with the name
.BR java.rmi.activation.ActivationSystem , 
in this registry. Thus,
the 
.B ActivationSystem 
on the local machine can be obtained
using the following 
.B Naming.lookup 
method call:
.LP
.RS 
.ft 3
.nf
import java.rmi.*;
import java.rmi.activation.*;

ActivationSystem system;
system = (ActivationSystem)
Naming.lookup("//:port/java.rmi.activation.ActivationSystem");
.fi
.ft 1
.RE
.TP
.B \-stop
Stops the current invocation of
.BR rmid , 
for a port specified by
the 
.B -port 
option. If no 
.I port 
is specified, it will stop the
rmid running on port 1098.
.SH ENVIRONMENT VARIABLES
.TP 20
.SB CLASSPATH
Used to provide the system a path to user-defined classes.
Directories are separated by colons. For example,
.RS
.LP
.ft 3
.nf
example% .:/usr/local/java/classes
.fi
.ft 1
.RE
.SH ATTRIBUTES
See
.BR attributes (5)
for a description of the following attributes:
.sp
.TS
box;
cbp-1 | cbp-1
l | l .
ATTRIBUTE TYPE	ATTRIBUTE VALUE
=
Availability	SUNWjvrt, SUNWjvdev
.TE
.SH SEE ALSO
.BR rmic (1)
.LP
See (or search java.sun.com) for the following:
.TP 10
Setting the Classpath @
http://java.sun.com/products/jdk/1.2/docs/tooldocs/solaris/classpath.html
.TP 10
RMI Specification @
http://java.sun.com/products/jdk/1.2/docs/guide/rmi/spec/rmiTOC.doc.html