Well, this has been posted frequently in our forums. Customers using two or more ManageEngine products should have definitely come across this.
Why does this happen, at the first place?
All ManageEngine products have been built on the same carrier platform and all use Tomcat / JBOSS server for serving the webpages. The cookie set in the browser by these products have the same name(JSESSION_ID) and the context path. So, when you access one ManageEngine product ( say for example, OpManager ), the cookie is first set on your browser. When you access Applications Manager or ServiceDesk Plus, you will be prompted to login to the web client. The value of the cookie is now set (ie., updated) to what Applications Manager or ServiceDesk Plus server offers. However, when you try to access the OpManager pages, the value of the session cookie will now be different from what was set earlier through OpManager and hence, you are forced to relogin with a session timeout message.
You will now be interested to know how to overcome this. It is easy, though the individual products are now working to change the cookie name.
1. Access OpManager through the hostname of the server and access Applications Manager or ServiceDesk Plus through the ipaddress.
2. Install these products on different physical server or VMWare instances.
3. You can think of setting up different hostnames ( CNAME entries ) for the applications in your DNS.
I will keep you all posted when this is getting addressed.
Kevin
