Custom Third-party Libraries
The customization init image can be used to configure custom third-party libraries including jars, database driver jars, properties and shared or native libraries.
ibm
b2bi
customization
thirdparty
jars
dbjars
properties
shared
pre-dynamicclasspath.cfg.in
pre-dynamicclasspathAC.cfg
All custom third-party jars, dbjars, properties or shared libraries that are to be applied to the product are required to be placed in the above structure as per the third party type. Also each third-party file needs to be enclosed in its vendor name and version sub folders so that the appropriate vendor name and version could be added to its path in dynamic classpath. All files not placed under the appropriate structure including the vendor name and version sub folders will be ignored while adding dynamic classpath entries. The pre-dynamicclasspath.cfg.in, applicable for asi containers, and pre-dynamiclasspathAC.cfg, applicable for ac containers, can be used to place any third-party jars, dbjars, properties at the top of the application dynamic classpath in case there of any conflicts with the product libraries.
ibm
b2bi
customization
thirdparty
jars
seas-sso
1.0
seas-sso-1.0.jar
awssdk
1.12.779
aws-java-sdk-1.12.779.jar
dbjars
mssql
21.0
sqljdbc4.jar
properties
seas-sso
1.0
seas-sso.properties
seas-auth.properties
shared
sap
3.2
sap-jco.so