Out of support This documentation supports the 8.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.Click here to view the documentation for a supported version of Remedy Single Sign-On.

JVM parameter additions for external Tomcat installations

The following initialization parameters must be specified for the JVM that is running an external Tomcat. If Tomcat is controlled via scripts, these JVM parameters can be included in a script file:

  • (Microsoft Windows) setenv.bat
  • (UNIX) setenv.sh

When Tomcat is installed as a Windows Service, include these values in the wrapper. When the wrapper is a supplied Apache wrapper (via Tomcat6w.exe or Tomcat7w.exe), the JVM additions are added to the Java tab.


-Dcom.sun.identity.configuration.directory=<tomcat-dir>\webapps\atriumsso\WEB-INF\config
-XX:PermSize=64m
-XX:MaxPermSize=256m
-Dcom.sun.identity.session.connectionfactory.provider=com.bmc.atrium.sso.opensso.extensions.ha.ConnectionFactoryProviderImpl
-Djava.security.auth.login.config=login.conf
-Djavax.net.ssl.trustStore=<truststore-canonical-name>
-Djavax.net.ssl.trustStorePassword=changeit
-Djavax.net.ssl.trustStoreType=JKS
-Djavax.net.ssl.keyStore=<keystore-canonical-name>
-Djavax.net.ssl.keyStorePassword=changeit
-Djavax.net.ssl.keyStoreType=JKS
-Dopensso.protocol.handler.pkgs=com.bmc.atrium.sso.common
-Djava.protocol.handler.pkgs=com.bmc.atrium.sso.common
-Datsso.in.sso.server=true

 

Note

<truststore-canonical-name> and <keystore-canonical-name> are the full path and name to the truststore and keystore that were created by the user for use by the Tomcat server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*