JavaParty Command Reference
- Quick Tour
- Mailing Lists
- Command Reference
- Object Model
- Transparent Threads
- Distributed Threads
- Remote Monitors
- Object Location
- Object Migration
- Remote Threads
- Replicated Objects
The JavaParty Compiler
The JavaParty compiler is derived from the Generic Java compiler and therefore accepts the same options plus some JavaParty specific options. The JavaParty compiler is invoked with the following command line:
jpc options* source-file.java+
You can specify options as described below followed by a list of Java or JavaParty source files.
Specifies the output directory for compiled class files. You must specify this option when compiling classes that reside inside a package.
Path for loading classes referenced from source files being compiled. Alternatively, you can set the CLASSPATH environment variable.
The JavaParty compiler automatically generates stubs and skeletons for remote classes. If you use KaRMI, the compiler generates debugging code that traces remote method calls via debugging messages.
Prints all supported options.
Unix only: Invite a Java party
jpinvite [-cp|-classpath <application-class-path>] [-D<property-name>=<value>]* [-X<virtual-machine-option>]* [-J <argument-passed-directly-to-Java>]* [-nodenames <comma-separated-list-of-hosts> |-nodefile <PBS-style-node-file>]? [-frontend]? [-purify]? <class-name> <class-arguments>*
JPInvite spawns a Java virtual machine on all specified hosts, invokes your application class and shuts down the environment after the main() method returns.
The Java specific options are passed to each participating virtual machine. The script assumes that either the cluster has a common network file system, or the file system layout of each node is identical to the layout on the invoking machine.
-cp <application-class-path> -classpath <application-class-path>
Sets the class path for the application consistent on all participating virtual machines. Assumes, all computing nodes have a common network file system or have at least the same directory layout.
Set a system property consistent on all participating virtual machines.
Set a non-standard option on the Java virtual machine.
Pass some other option directly to the underlying Java virtual machine.
Use an extra front-end virtual machine for invoking a local main class. This front-end virtual machine does not become part of the dirstributed environment and can be used to start a local GUI.
To get X11 forwarding, for all your nodes, set the JPQ_RSH environment variable accordingly. -purify Purify the console output of the virtual machines spawning the distributed environment. This option prevents that lines of output from different virtual machines are merged. Additionaly, each line of output is prefixed with the number of the virtual machine that printed it. With this option, all output is redirected to standard output.
For the complete list of options please try:
Windows only: The JavaParty Runtime Manager
The runtime manager is the central instance in a JavaParty environment. It keeps track of registered virtual machines and manages information about loaded remote classes.
Starts the JavaParty runtime manager on the current machine.
The JavaParty virtual machines use multi-cast to look up an active JavaParty environment for registration. Each JavaParty environment must use an unique code to make sure that a virtual machine registers at the right manager.
If no code is specified, your user name is used as default value. Therefore, only need to choose another code, if you want to start more than one JavaParty environment.
Chooses an alternate port for exporting the registry (for details consult the RMI specification). You only need to use this option, if you want to start more than one runtime manger on the same host, or if the default port is use from another application.
Note: If you are using JavaParty for KaRMI, you also have to adapt the KaRMI configuration (see the KaRMI).
Show what the runtime manager is doing.
Show information about remote classes loading.
Windows only: The JavaParty Virtual Machine
Start one node of the distributed environment. The execution of a JavaParty program takes place in one ore more virtual machines.
See section runtime manager.
Only register the virtual machine on a runtime manager running on the specified host. By default the runtime manager is looked up using multi-cast. See the runtime manager.
-host runtime-manager-host -port runtime-manager-port
If you specify the -host and -port options, no multi-cast is used.
Windows only: Application startup
Invoke the applications main class. See JavaParty virtual machine for options accepted for choosing the runtime manager. The command returns when the main method of the application is completed.
jp jp-args* class-name arguments*