When launched, each PPM client server registers at the RMI registry server with a unique name. This name enables the PPM command line programs and the other server components to query connection information from the registry and to establish a connection to the PPM client server.
The data exchange via RMI is completely transparent for the Java application. All RMI network connections must be available during the entire PPM software runtime.
The RMI objects themselves are designed for direct network communication. The address information contained in the RMI objects (IP address and port number) cannot be evaluated by the firewalls when transferred across network boundaries.
The following figure and table illustrate the RMI data flow described:
|
Client |
Server |
Process |
---|---|---|---|
1 |
PPM client |
RMI registry |
During startup, the client server registers at the registry server with its name. |
2 |
PPM command line programs |
RMI registry |
Query whether the relevant client server is available (specification of the client name in the login dialog) |
3 |
PPM command line programs |
RMI registry |
The RMI registry returns the RMI object reference of the client server started. |
4 |
PPM command line programs |
PPM client |
The front-end executes methods of the client server using the RMI object reference provided. |
5 |
PPM command line programs |
PPM client |
The client server returns results. |
RMI data transfer modes
You can set different modes for RMI communication between PPM server components, which are described in the following chapters. After you created a client, the Compressed data transfer mode described in chapter Compressed data transfer is set.