Maximo comes with a utility named CheckMXServer which can be used to output a report showing all of the Maximo and Java property values, the RMI port usage, and test the creation and deletion of a test workorder. Note this is an internal tool and is not supported.
Resolving The Problem
This utility is named CHECKMXSERVER.BAT on Windows, and checkmxserver.sh on Unix systems. It is located in the Maximo 5 root directory and in MAXIMO_ROOT\tools\maximo\internal under Maximo 6 and 7.
CheckMXServer utility is used to check mxserver start status and to collect useful diagnostic information from the server. By using this utility you are assured of collecting the server settings from the server itself rather than accidentally getting wrong information from an unimplemented properties file.
The following information is collected:
RMI registry list
Server names in the RMI registry
Server's Java properties, including classpath and version
Server's MXServer.properties file properties
Results of an attempt to create, update, and delete, a simple workorder.
The collected information can be seen on the screen or can be written to a log file. The log filename is passed as a parameter to the checkmxserver utility.
checkmxserver -? shows the command line help (checkmxserver.sh -? on Unix).
Usage : checkmxserver -h<hostname> -s<servername> -u<username> -p<password> -f<logfile> -?
hostname / ip address of the machine running maximo application server For example: localhost, myhost.mycompany.com, 127.0.0.1
Note : By default the RMI registry is run on 1099, for any reason if RMI registry is not running on 1099, then the hostname should be qualified with RMI registry port, e.g. myhost.mycompany.com:1200
Maximo 7 and higher use 13400 as the default RMI port.
The name of the maximo application server to connect.
Maximo application server administrative account to use, by default
checkmxserver uses WILSON.
Maximo application server administrative account password
The log file to collect the information.
NOTE: The output from checkmxserver will contain the passwords that are listed in the MXServer.properties file. You should edit the output file and remove the values for any 'password' properties if the passwords in the properties file are not encrypted.
NOTE: This is an internal tool and is not supported.
This utility does not work when LDAP authentication is enabled. It will fail with error
"UNABLE TO CONNECT TO MAXIMO SERVER....
17 June 2018