Deploying the remote method invocation registry file in WebSphere Application Server

A server that has a remote method invocation (RMI) registry continues to run even if another server in the cluster fails. When you build the RMI registry file, the file must be deployed in the application server.

About this task

For each physical server or virtual machine that acts as a server in your environment, you must create a JVM to host the RMI registry. The RMI JVM must be created outside of the clusters and must be started before any other JVMs. If you do not have clients that use RMI registry servers, you can remove the RMI registries set up and deployment processes from your configuration process.

The install_home variable represents the installed location of the product folder.


  1. Log in as the administrative user to the Integrated Solutions Console by using the address http://servername:9060/admin
  2. In the navigation pane of the Integrated Solutions Console, select Servers > Server Types > WebSphere Application Servers and then click New to create a JVM for the RMI registry.
  3. Specify RMIRegistry for the server name and use the default settings for the server template and server properties.
  4. Click Finish, and then save the server information.
  5. In the navigation pane of the Integrated Solutions Console, click Applications > Application Types > WebSphere Enterprise Applications.
  6. Click WebSphere enterprise applications, and then click Install.
  7. Click Browse and specify the install_home/deployment/default/rmireg.war file.
  8. In the Context Root field, specify RMI.
  9. Select the Generate Default Bindings check box.
  10. Continue to the next section without changing any selections. Do not change the default application name rmireg_war.
  11. In the Mapping Modules to Servers section, select the RMIRegistry server, select the MBO Web Application check box, and click Apply.
  12. Confirm that the MBO Web Application is mapped to the RMIRegistry.
  13. Click Finish to complete the installation of the file.
  14. Save the rmireg_war file to the master configuration.
  15. Repeat steps 1-14 for every physical server or virtual machine that acts as a server.