Do you have the arsys.xml in <tomcat>/conf/Catalina/localhost ?
Have you reviewed the tomcat logs eg. the catalina.out log for errors during deployment of /arsys context?
Thanks for taking the time to respond Andreas,
I moved a copy of the original arsys.xml from Tomcat 7 and placed in <Tomcat 8.5>\conf\Catalina\localhost
in the Catalina (and stderr log) I've the following severe messages
05-Nov-2019 16:11:38.323 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
05-Nov-2019 16:11:38.323 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/arsys] startup failed due to previous errors
I've been looking for information around these errors but haven't found anything yet
Make sure that the old tomcat 7 is shut down otherwise the new tomcat will be unable to open the port (in case you configured it on the same port as the old one).
Review the connector settings in server.xml in new tomcat for port settings and make sure that all ports are not in use (http/https/ajp/shutdown) by any other software.
If you have checked that and it still not working, attach the server.xml + error.logs
3 of 3 people found this helpful
According to the logs it seems the /arsys context gets deployed properly.. However there seem to be a problem accessing config file:
java.io.FileNotFoundException: E:\Program Files\BMC Software\ARSystem\midtier\WEB-INF\classes\config.properties (Access is denied)
Try giving tomcat 8.5 service full access to E:\Program Files\BMC Software\ARSystem\midtier folder.
Are you able to access MT config page?
I've amended folder access and no longer see the 'access is denied' error in the logs, but I am still getting a error when trying to launch Remedy. Logs attached, thanks for your help so far its really appreciated
apologies for the slow response.
as you've pointed out there was an issue with the specified cookie and BMC recommended that we add the following line into the context.xml file
that alongside your other suggestions have helped resolve the issue so thank you very much