This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Maximo 6.2.3
Oracle 10x
WebSphere 6.1.0.43
We have Maximo MEA and three clusters in our Websphere environment.
Over the weekend, we moved Maximo to a new server that already had WebSphere installed. Unfortunately, now we are having a number of Maximo issues and have discovered that in maxsession table, Maximo is connecting users to server name 'MXServerMEA' when it should be connecting users to server name, MXServerCLS' which is the cluster.
We believe that, how Maximo chooses the SERVERNAME, is inside Maximo program since WebSphere has not changed.
Has anyone experienced this in Maximo before ?? If so, any suggestions for resolution would be greatly appreciated.
Thanks,
TP
In a typical setup (and by typical I mean following IBM recommended setup), the cluster and the MEA/MIF instance don't listen on the same port. I would look at the application servers defined in WebSphere to make sure that the ports for each are defined the same as they are on the original server. Also look at the port that the http server is listening on. The cluster is usually accessed through that port and not directly through the port(s) of its application servers. One other thing, make sure your MEA server is not set as a member of the cluster.
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of tpw5511
Sent: Monday, April 30, 2012 11:23 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] In maxsession table, session connects to server MXServerMEA instead of Cluster
Maximo 6.2.3
Oracle 10x
WebSphere 6.1.0.43
We have Maximo MEA and three clusters in our Websphere environment.
Over the weekend, we moved Maximo to a new server that already had WebSphere installed. Unfortunately, now we are having a number of Maximo issues and have discovered that in maxsession table, Maximo is connecting users to server name 'MXServerMEA' when it should be connecting users to server name, MXServerCLS' which is the cluster.
We believe that, how Maximo chooses the SERVERNAME, is inside Maximo program since WebSphere has not changed.
Has anyone experienced this in Maximo before ?? If so, any suggestions for resolution would be greatly appreciated.
Thanks,
TP