APSecure does not work after installing only the xMatters web server component

Due to an incorrectly set class path, APSecure does not work after installing only the xMatters web server component.

Resolution

To resolve this issue:

  1. Navigate to <xMHOME>/common/APSecure.conf on Windows or <xMHOME>/APSecure.sh on Unix and open the file in a text editor.
  2. Add the following to the beginning of the -classpath (replace <xMHOME> with the name of the installation directory):

Windows

"<xMHOME>\webserver\webapps\cocoon\WEB-INF\lib\com.invoqsystems.foundation.jar;{installation-directory}\webserver\webapps\cocoon\WEB-INF\lib\aspectjrt.jar;"

Unix

"<xMHOME>/webserver/webapps/cocoon/WEB-INF/lib/com.invoqsystems.foundation.jar:{installation-directory}/webserver/webapps/cocoon/WEB-INF/lib/aspectjrt.jar:"

  1. Save the file.

UPDATE for xMatters 4.1

This article was originally created for xMatters 3.2.1 and 4.0; to make it work for xMatters 4.1, you need one more jar because of the code changes introduced in 4.1. That is, add the following to the beginning of the -classpath (within double quotes):

  • in the APSecure.sh (Posix):

<xMHOME>/webserver/webapps/cocoon/WEB-INF/lib/spring.jar:

or

  • in the APSecure.conf (Windows):

<xMHOME>\webserver\webapps\cocoon\WEB-INF\lib\spring.jar;

xMatters Reference

DTN-1792, SUP-7776, JDN-1214

Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk