Deploying the remote method invocation registry file for WebLogic Server

When you build the remote method invocation (RMI) registry file, the file must be deployed each physical server. Deployment includes creating an RMI registry service and, creating a batch file to start RMI. To run the process correctly, you must update the start sequence for all servers so that all product ervers start after the RMI server starts.

  1. Java remote method invocation
    Remote method invocation (RMI) is an application programming interface that provides a way for objects in separate memory areas to interact. Separate memory areas can be part of the same physical system or can be on different systems connected by a network.
  2. Creating remote method invocation registry services for WebLogic Server
    You can deploy a remote method invocation (RMI) registry file to create a registry that is independent of the product servers. A server that contains an RMI registry continues to run even if another server in the cluster fails. This registry starts on the server before any of the cluster members starts.
  3. Creating a batch file to start remote method invocation on WebLogic Server
    After you create the remote method invocation (RMI) registry service, you must create a batch file to start RMI on the application server.
Parent topic: Creating and deploying clusters in WebLogic Server
Next topic: Creating clusters in WebLogic Server
Related concepts:
Java remote method invocation

Feedback