Change RMI port on Websphere 6 using Maximo

Question

The set up

I have websphere 6.1 running two application servers. Each running the same application (Maximo). Each application point to a different database.

There is a third party app that connects VIA an RMI port of 13400.

Both Maximo applications have this in the proprieties file.

mxe.registry.port=13400

The issue

When the third party program makes a call to the RMI port the wrong application processes gets the call.

What I have tried

I can't find anything in the WebSphere console that would let me change the port.

Changing the RMI port in the Maximo properties file to 13400 and redeploying the ear. Then changed the port on the third party software. No dice. In fact I get a Error 500 System not bound on when accessing Maximo.

ServletWrappe E   SRVE0100E: Did not realize  init() exception thrown by servlet ReportBridgeServlet: java.lang.NoClassDefFoundError: com.ibm.tivoli.maximo.report.birt.logging.ReportLoggerFactory
at com.ibm.tivoli.maximo.report.birt.bridge.launcher.FrameworkLauncher.<init>(FrameworkLauncher.java:83)
at com.ibm.tivoli.maximo.report.birt.servlet.MXWebAppOSGiFrameworkLauncher.<init>(MXWebAppOSGiFrameworkLauncher.java:33)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1328)
    ...... 12000++ lines of errors like this one.

As ring bearer pointed out this error doesn't correlate with changing the RMI port. Yet when I change the proprieties file back to 13400 there are no error what so ever.

The Question

How do I change the RMI port for each application server?

Hypothesis

I'm hoping it's somewhere in the application server.

Answer 1

Finally found what I was looking for:

In the maximo.properties file add this...

// Port used by RMI for communication, if left at 0, RMI will use any available
// port on the system. To use a specific port, set this parameter to an available  
// port number.
mxe.rmi.port=0

I set it to 12222 rebuilt the ear and redeployed. Port 12222 never opened up.

The real issue was the mxe.name all there applications had the same name in the proprieties file. Changing the names resolved the issue.

// Name to bind the MXServer server object to in the RMI registry
mxe.name=MXServer

https://www-304.ibm.com/support/docview.wss?uid=swg21262022

Answer 2

Logon to admin console and follow this selection path - Application_servers > server1 > Ports > BOOTSTRAP_ADDRESS

Note that once you are on the "Server1" selection page, the ports link will appear on the right hand side, under "Communications" section

Assuming your default server name is server1 You will have a screen where you can edit port number for BOOTSTRAP_ADDRESS- which is the WebSphere Application Server name Service or RMI Connector Port.

Answer 3

Make a copy of your weblogic folder and rename it something else. You can change the settings on the second instance.