A Maximo installation includes a JVM which runs the Maximo application in the Websphere application server.
When a JVM starts up Websphere performs a number of different operations.
These operations include:
- Connect to network ports to accept connections
- Connect to database resources e.g. for message stores
- Connect to other JVMs
- Setup JMS engines for messages
These operations configure the JVM so it can perform its operations.
Maximo then logs into the database and performs its own setup.
When I teach the log analysis course I’m often asked how to tell if the JVM has started up properly without having to check the Maximo front-end.
An easy way is to check the logs for the following log message:
[5/20/13 22:19:01:062 BST] 0000000a WsServerImpl A WSVR0001I: Server MXServer1 open for e-business
MXServer1 is the name of the JVM as defined in Websphere.
This post refers to entries in the SystemOut.log file described in this article.
So the JVM has started …. So that means Maximo has started ??…. Not necessarily...
This message is generated by Websphere when the JVM has completed its setup. This message isn’t a guarantee that the JVM has started properly. The JVM could fail to connect to ports that it needs to connect to other JVMs.
The Maximo application could fail to start due to other problems.
Startup failures can be caused by problems such as:
- Unable to connect to ports required by Websphere
- Unable to login to the Maximo database
- Maximo services failing to start
- Maxadmin account is blocked - discussed in this article
- Maxsession entry preventing startup – discussed in this article
- Other problems
Tip -> Start a JVM and study the logs so you know what the system looks like when it starts successfully. This will make it easier to identify problems when they appear in the logs.
Tip -> If you are restarting a JVM then always wait a minute after it has shutdown. A short wait before restarting the JVM ensures that the operating system has released the ports the JVM was using.
Vetasi training
Vetasi offers training on analysing log files.
Vetasi offer a course that gives system a technical overview of Websphere and the knowledge to be able to debug common problems and considerations for some of the important design options.
This blog series
This article is one of a series of articles to help system administrators understand the Maximo logs and the underlying architecture.
Articles are normally posted on a Tuesday and Thursday.
No article is planned for Thursday this week as I am working on another exciting Maximo blogging opportunity that will be starting soon. More details about that next week.
If you like this article then please share it so others can benefit from it or like it so I can understand which articles are the most useful.
Disclaimer
The postings on this blog are my own and don't necessarily represent Vetasi's positions, strategies or opinions.
The materials on this site are provided "AS IS" and the author will not be liable for any direct, indirect or incidental damages arising out or relating to any use or distribution of them.
#AssetandFacilitiesManagement#TRIRIGA#InternetofThings-IoT