Page History

...

• Check the Oracle JDBC Driver version that ships with the JS7 release, see JS7 - Database, chapter: Individual JDBC Driver Versions. A newer JDBC Driver might be available for download from Oracle.
• Oracle JDBC Drivers that ship for release 18c of the DBMS are reported to work. Previous Oracle JDBC Driver releases, for example 12c, are reported not to work with Oracle Wallet® when used by JS7. If in doubt use the Oracle JDBC Driver version that matches the version of the DBMS.
• Users who want to use a specific version of the Oracle JDBC Driver can apply the following steps:
  • For on premises installations store the Oracle JDBC Driver's .jar file in the JS7_AGENT_HOME/lib/user_lib directory of the Agent installation directory.
  • When running JS7 Agent containers for Docker® consider to store the Oracle JDBC Driver's .jar file in the JS7_AGENT_CONFIG_DIR/lib directory.

...

The JS7 - JITL SQLExecutorJob and JS7 - JITL PLSQLJob make use of the Oracle PKI Libraries.

• The Oracle PKI libraries are required that and have to match the version of the Oracle DBMS and Oracle JDBC Driver.
• The .jar files are offered by Oracle for download and are available from an Oracle Client installation and are offered by Oracle for downloadfor example from:
  • ORACLE_HOME/jlib/oraclepki.jar
  • ORACLE_HOME/jlib/osdt_cert.jar
  • ORACLE_HOME/jlib/osdt_core.jar
• For on premises installations store the Oracle PKI libraries in to the JS7_AGENT_HOME/lib/user_lib directory of the JS7 Agent installation directory.
• When running JS7 Agent containers for Docker® consider to store the Oracle PKI libraries in the JS7_AGENT_CONFIG_DIR/lib directory.

...

• The below explanations about use of a URL such as jdbc:oracle:thin:@/js7?tns_admin=/home/js7/wallet similarly apply.
• For use with Oracle Wallet® the job arguments db_user and db_password are omitted.

The A Hibernate configuration file by default is located looked up in JETTY_BASE/resources/joc/hibernate.cfg.xml, see JS7 - Database. The Hibernate configuration can look like this:

...

• Consider the empty elements that are used for the account and password. Do not delete the respective elements from the Hibernate configuration file.
• The connection URL specifies js7 as the key to an entry in the wallet.
• The URL parameter tns_admin is used to specify the directory of the tnsnames.ora configuration file. JDBC Connections usually do not need this configuration file as connection details (Listener, Service Name, Service ID) are specified with the URL. However, due to use of the js7 key to the wallet in the URL it is preferable to manage connection details from a tnsnames.ora configuration file.
• In the above example this file is located in the /home/js7/wallet directory that in fact is the directory where the wallet is located. This location is not required authoritative as the file can reside in any directory that is accessible to JOC Cockpit.
• Consider that an sqlnet.ora configuration file is not used with the above setup of a JDBC connection.

...