Deploying the RMI registry in a Maximo Clustered Environment, part 2
lanxpham 270003YRBB Visits (10174)
Continuing from Depl
Let's now look at how to prepare the RMI registry file, rmireg.war to build and deploy this to your clustered environment.
1. Prepare and Build the RMI Registry file
The tool used to build the rmireg.war file is <max
TIP: If you wanted, you could make a copy of the original maximo.properties file, rename it to for example maxi
Open the buildrmiregwar.xml (which is used by the buil
a) Edit the maxi
By default, there is no mxe.registry.port property in properties files.
This property must be added if the registry port needs to be controlled or modified to use a port different than the default value of 1099.
Save your changes to the file.
b) Open command prompt and navigate to <max
c) You will see the rmireg_war file is created under the <max
2. Now, let's move on to deploying this RMI registry in the application server.
This file will be deployed as a separate server on it's own independent of the Maximo clusters.
NOTE: I am using Maximo 7.5.x.x with Websphere 7.0.x.x for this demonstration, however, the process is the same for Maximo 7.6 with WebSphere 8.x.x.x.
a) Follow the below in depth guide with screenshots on how to deploy the RMI registry.
Note: It is important to note the RMI registry JVM is always the first one to start, then you can ripple start any Maximo clusters/JVMs afterwards.
3. Once everything is up and running!
Check out the Maximo systemout.log at the time of startup and you will see the RMI registry bound entry, which shows the registry started successfully.
Search for "Bound rmiI" text in the log file.
This is simple blog on how to set up RMI for a clustered environment. I hope you have enjoyed following this blog.