How To
Summary
Some customers enable SSL or MTLS in the database. The setup requires any JVM process that connects to the database to supply SSL properties. Some Order Management out of box utilities are ant tasks, for example dbverify.sh. It invokes build files (deployer.xml) which is an outer shell. We need to add the SSL properties in the final forked java call to entity deployer to make the values passed reaching SchemaSynchronizer class. It's entityDeployer.xml in this case.
Steps
Go to entityDeployer.xml, look at the 'schema-synchronizer' target, which invokes the SchemaSynchronizer class, and try passing the properties directly there. For example, <sysproperty key="javax.net.ssl.trustStore" value="/path/to/jkscert/test-roots.jks"/>
<sysproperty key="javax.net.ssl.trustStoreType" value="JKS"/>
<sysproperty key="javax.net.ssl.trustStorePassword" value="XXXXXXXX"/>
<sysproperty key="oracle.net.ssl_server_dn_match" value="false"/>
<sysproperty key="javax.net.ssl.keyStore" value="/path/to/jkscert/test-roots.jks"/>
<sysproperty key="javax.net.ssl.keyStoreType" value="JKS"/>
<sysproperty key="javax.net.ssl.keyStorePassword" value="XXXXXXXXX"/>
Additional Information
A note, entityDeployer.xml needs to be examined to verify if the added properties are still present after a fix pack installation. Add these properties if necessary.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
11 July 2024
UID
ibm17160031