Maximo Cluster deployment Assigning names to JVMs as Generic JVM arguments.

In WebSphere you can set the mxe.name property directly on the JVM. This is done in the Generic JVM arguments for each individual JVM. This prevents each cluster from starting up with a random name e.g. mxserverc1. This way we can specify the cron tasks do not run properties at the instance level for each JVM in the database.

1. In your WebSphere Console, expand 'Server Types' and click on 'WebSphere Application Servers'. From here click on maximo_ui01.

2. Under 'Server Infrastructure'  expand 'Java and Process Management' and click on 'Process Definition'. Under 'Additional Properties' click on 'Java Virtual Machine'.

3. There will be a box that says 'Generic JVM arguments' in here we want to enter -Dmxe.name=maximo_ui01 as seen below.

-Dsun.rmi.dgc.ackTimeout=10000 

-Djava.net.preferIPv4Stack=true 

-Dmxe.name=maximo_ui01 

4- Repeat the above steps for your remaining JVM's.  For example Dmxe.name=maximo_ui02,Dmxe.name=maximo_mif01,Dmxe.name=maximo_rep01 and Dmxe.name=maximo_cron01.

 This should be done before deploying Maximo applications on cluster and then start you cluster.