IBM Support

Setting up Maximo Application server to use Node Monitoring in WebSphere

Technical Blog Post


Abstract

Setting up Maximo Application server to use Node Monitoring in WebSphere

Body

Previously, it was recommended to setup the Maximo Application Server (default name: MXServer) as a service in Windows. That recommendation has now changed.

Beginning with Maximo Asset Management 7.1  technical support now recommends the usage of WebSphere Node Monitoring.

This setting looks to the NodeAgent Windows service and applies the appropriate state to the MXServer.

 To implement Node Monitoring use the following steps:

1) Log into WebSphere Integrated Solutions Console.

2) From the left navigation select Servers --> Application Servers.

3) Click the appropriate Maximo Application Server (default name MXServer).

4) From the right side under Server Infrastructure select Java and Process Management --> Monitoring Policy.

The Monitoring Policy screen will display.

There is a setting for node restart state, below that there is a drop down with three choices:

STOPPED, RUNNING, PREVIOUS.

To have the MXServer to start when the NodeAgent starts select RUNNING.

5) Once selected, click OK.

6) If prompted click the Save directly to the master configuration link in the Messages box.

The setting is dynamic and does not require a server restart.

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

UID

ibm11134297