The FNCM operator includes a single version of Db2 (db2jcc4.jar), Oracle (ojdbc8.jar),
Microsoft SQL Server (mssql-jdbc.jre11.jar), and PostgreSQL (postgresql-42.6.0.jar) JDBC drivers to
use in your production deployments. If you need to use other versions, then you must package these
files into a compressed file and use the sc_drivers_url configuration parameter
to download them from an accessible web server. If you need IBM Content Collector for SAP
Applications libraries, you must also put them inside the compressed file.
Before you begin
Note: Before you package the files into a compressed file, you must make sure that the custom JDBC
driver that you want to use is compatible with Java 17.
Procedure
- Prepare your JDBC files and organize them into the following folder structure:
The following JAR files are the default versions:
/jdbc/db2/db2jcc4.jar
/jdbc/oracle/ojdbc8.jar
/jdbc/sqlserver/mssql-jdbc.jre11.jar
/jdbc/postgresql/postgresql-42.6.0.jar
The Db2 license file (db2jcc_license_cu.jar) is included in all Db2 server editions and you must
take the license file from the Db2 Activation CD or download it from Passport Advantage. For more
information, see Db2 license files.
For Oracle, you must download the required JDBC JAR and other companion JAR files such as
orai18n.jar, oraclepki.jar, osdt_core.jar, osdt_cert.jar from the Oracle Technology Network JDBC Download Page.
If you want to deploy Application Engine or playback server and use the customized JDBC driver
for Oracle, besides the available JDBC driver files, you need ODPI-C applications with Oracle
Instant Client to connect to the database. Download Oracle Instant Client Zip from
Oracle Instant Client Download Page. Download the Oracle Instant Client file
required for your operating system. Unzip the file and copy the extracted files to the
/oracle_node
directory as shown in the following
example:
/jdbc/oracle_node/<extracted files>
-
Download the SAP Netweaver SDK 7.50 library from the SAP Service Marketplace or SAP NW RFC SDK 7.50. Ensure that the library includes the
following files: libicudata.so.50, libicudecnumber.so, libicui18n.so.50, libicuuc.so.50,
libsapnwrfc.so, and libsapucum.so
Note that you need an SAP Support user (S-user) ID to access the SAP Service
Marketplace.
-
Download the SAP Cryptographic Library version 8 from the SAP Service Marketplace or COMMONCRYPTOLIB 8. Ensure that the library includes the
following file: libsapcrypto.so
Note that you need an SAP Support user (S-user) ID to access the SAP Service
Marketplace.
-
Download the SAP Java Connector Release 3.1 from the SAP Service Marketplace or SAP JCO 3.1. Ensure that the library includes the following
file: sapjco3
Note that you need an SAP Support user (S-user) ID to access the SAP Service
Marketplace.
- Extract all of the content of the packages to a saplibs directory
and give read and write permissions to the directory by running the chmod
command.
/saplibs/libicudata.so.50
/saplibs/libicudecnumber.so
/saplibs/libicui18n.so.50
/saplibs/libicuuc.so.50
/saplibs/libsapcrypto.so
/saplibs/libsapjco3.so
/saplibs/libsapnwrfc.so
/saplibs/libsapucum.so
/saplibs/sapjco3.jar
- Compress them into a file (.zip, .tar, .tar.gz, .tar.bz2, .tar.xz) by running the
following command:
zip -r $localpath_to_zip/jdbc.zip jdbc saplibs
The command generates the path and file name:
$localpath_to_zip/jdbc.zip.
- Use the HTTPd docker image to start a container with the name
http
.
docker run -dit --name http -p 8888:80 httpd
- Open the container by using the URL
http://hostname:8888.
The hostname is where you run the HTTPd docker
image. It displays the following message:
"it works!"
- Copy the compressed file to the docker container by running the following command:
docker cp $localpath_to_zip/jdbc.zip http:/usr/local/apache2/htdocs
- The operator downloads the compressed file when you set the value of the
sc_drivers_url parameter in the custom resource (CR) to the URL of the file in
the HTTPd container: http://hostname:8888/jdbc.zip. The hostname is where you
run the HTTPd docker image.
You set the values of the CR when you create an instance of the production deployment.
shared_configuration:
sc_drivers_url: http://hostname:8888/jdbc.zip