Why is there some differences between JVMOptions.txt in Siteminder releases ?

Document ID : KB000011825
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

The JVMOptions.txt file contains the settings that the Policy Server uses when creating the Java virtual machine. It can vary depending on version.

Question:

Why is there some differences between JVMOptions.txt in Siteminder releases ?

For example, class path is very small in 12.52SP1 as compare to 12.0

12.0 version:

-Djava.class.path=%SM_INSTALL_DIR%/config/properties;%SM_INSTALL_DIR%/bin/jars/SmJavaApi.jar;%SM_INSTALL_DIR%/bin/jars/SmActiveExpr.jar;%SM_INSTALL_DIR%/bin/jars/variableapi.jar;%SM_INSTALL_DIR%/bin/jars/util.jar;%SM_INSTALL_DIR%/bin/jars/util_sdk.jar;%SM_INSTALL_DIR%/bin/jars/smkeydatabase.jar;%SM_INSTALL_DIR%/bin/thirdparty/jce1_2_1.jar;%SM_INSTALL_DIR%/bin/thirdparty/js.jar;%SM_INSTALL_DIR%/bin/endorsed/xercesImpl.jar;%SM_INSTALL_DIR%/bin/endorsed/xml-apis.jar;%SM_INSTALL_DIR%/bin/endorsed/resolver.jar;%SM_INSTALL_DIR%/bin/endorsed/xmlsec-1.4.3.jar;%SM_INSTALL_DIR%/bin/thirdparty/cryptoj.jar;%SM_INSTALL_DIR%/bin/thirdparty/cryptojFIPS.jar;%SM_INSTALL_DIR%/bin/thirdparty/certj.jar;%SM_INSTALL_DIR%/bin/thirdparty/ldapjdk.jar;%SM_INSTALL_DIR%/bin/thirdparty/openldap.jar;%SM_INSTALL_DIR%/bin/thirdparty/sslj.jar;%SM_INSTALL_DIR%/bin/thirdparty/codebase.jar;%SM_INSTALL_DIR%/bin/thirdparty/soap.jar;%SM_INSTALL_DIR%/bin/thirdparty/javax.jar;%SM_INSTALL_DIR%/bin/endorsed/jaxb-api.jar;%SM_INSTALL_DIR%/bin/endorsed/jaxb-impl.jar;%SM_INSTALL_DIR%/bin/endorsed/jaxb-libs.jar;%SM_INSTALL_DIR%/bin/endorsed/jaxb-xjc.jar;%SM_INSTALL_DIR%/bin/endorsed/jax-qname.jar;%SM_INSTALL_DIR%/bin/endorsed/commons-logging-api-1.1.1.jar;%SM_INSTALL_DIR%/bin/endorsed/commons-logging-1.1.1.jar;%SM_INSTALL_DIR%/bin/thirdparty/namespace.jar;%SM_INSTALL_DIR%/bin/endorsed/relaxngDatatype.jar;%SM_INSTALL_DIR%/bin/endorsed/xsdlib.jar;%SM_INSTALL_DIR%/bin/jars/affwebservices.jar;%SM_INSTALL_DIR%/bin/jars/smerrlog.jar;%SM_INSTALL_DIR%/bin/jars/smfedservercomponent.jar;%SM_INSTALL_DIR%/bin/jars/assertiongenerator.jar;%SM_INSTALL_DIR%/bin/jars/saml.jar;%SM_INSTALL_DIR%/bin/jars/saml2.jar;%SM_INSTALL_DIR%/bin/jars/saml2Gen.jar;%SM_INSTALL_DIR%/bin/jars/ws.jar;%SM_INSTALL_DIR%/bin/jars/wsgen.jar;%SM_INSTALL_DIR%/bin/jars/saml2Security.jar;%SM_INSTALL_DIR%/bin/jars/federationps.jar;%SM_INSTALL_DIR%/bin/jars/smauthsaml.jar;%SM_INSTALL_DIR%/bin/jars/srca.jar;%SM_INSTALL_DIR%/bin/jars/smsamlattributeauthority.jar;%SM_INSTALL_DIR%/bin/jars/SmAuthInfoCard.jar;%SM_INSTALL_DIR%/bin/jars/InfoCardHiggins.jar;%SM_INSTALL_DIR%/bin/thirdparty/commons-lang-2.1.jar;%SM_INSTALL_DIR%/bin/thirdparty/commons-chain-1.1.jar;%SM_INSTALL_DIR%/bin/thirdparty/org.eclipse.higgins.configuration.api.jar;%SM_INSTALL_DIR%/bin/thirdparty/org.eclipse.higgins.sts.api.jar;%SM_INSTALL_DIR%/bin/thirdparty/org.eclipse.higgins.sts.common.jar;%SM_INSTALL_DIR%/bin/thirdparty/org.eclipse.higgins.sts.spi.jar;%SM_INSTALL_DIR%/bin/thirdparty/org.eclipse.higgins.sts.xmlsecurity.apache.jar;%SM_INSTALL_DIR%/bin/jars/SmAuthCert.jar;:%SM_INSTALL_DIR%/bin/thirdparty/commons-codec-1.3.jar

12.52SP1 version:

-Djava.class.path=%SM_INSTALL_DIR%/resources;%SM_INSTALL_DIR%/config/properties;%SM_INSTALL_DIR%/bin/jars/smbootstrap.jar;C:/Program Files (x86)/CA/sdk/MyCustomClasses.jar

Answer:

We always should use the JVMOptions.txt provided with the current release and then report any customization (Addtional Jars).
Starting in R12.51 we have given reference links in smbootstrap.jar file.

Additional Information:

Community thread with details:

https://communities.ca.com/thread/241767354