Page History

...

• No Oracle Client installation is used, however, you might need an Oracle Client to set up and to configure the Oracle Wallet®.
  • Typical commands to create a wallet include e.g.:
    • # create wallet in a directory that is accessible to the JobScheduler run-time account assumed to be "jobscheduler"
mkstore -wrl /home/jobscheduler/wallet -create
# add credentials to wallet; specify entry key, database account and password
mkstore -wrl /home/jobscheduler/wallet/ -createCredential jobscheduler some_account some_password
  • Consider that the mkstore command will might add the location of the wallet to your sqlnet.ora configuration file.
    • This file is used e.g. by SQLPlus SQL*Plus and therefore allows e.g. to execute: sqlplus /@jobscheduler by specifying the entry key for tnsnames.ora and sqlnet.ora
    • This file is not considered when using the Oracle JDBC Driver, therefore the above Java define -Doracle.net.wallet_location has to be used.
• JobScheduler makes use of the Oracle JDBC Driver:
  • Check the Oracle JDBC Driver version that ships with the JobScheduler release, see Which Database Management Systems are supported by JobScheduler? A newer Oracle JDBC Driver might be available for download as the Open Source JobScheduler might not be bundled with the latest Oracle JDBC Driver.
  • Oracle JDBC Drivers that ship for release 18c of the DBMS are reported to work. Previous JDBC Driver releases as e.g. 12c are reported not to work with Oracle Wallet® when used by JobScheduler.
• The following Oracle Java libraries are required that should match the version of the Oracle JDBC Driver.
  • The .jar files are available from an Oracle Client installation and that are offered by Oracle for download:
    • $ORACLE_HOME/jlib/oraclepki.jar
    • $ORACLE_HOME/jlib/osdt_cert.jar
    • $ORACLE_HOME/jlib/osdt_core.jar
  • Store the libraries in the ./lib/user_lib directory of our JobScheduler Master and JOC Cockpit installation path respectively.

Using Oracle Wallet® for Jobs

Usage

Once Oracle Wallet® is configured for the account that will trigger the jobs, the account is able to See How to make JITL Jobs connect to an Oracle database without password specification, e.g. by using sqlplus /@db11g

Prerequisites

Prerequisites to execute SQL*Plus with Oracle Wallet® on Linux:

1. Oracle client installed
2. Environment variables being set: ORACLE_HOME, LD_LIBRARY_PATH=$ORACLE_HOME/lib, TNS_ADMIN

Prerequisites to execute shell scripts from JobScheduler Master that call SQL*Plus with Oracle Wallet®:

1. Copy declaration and initialization with export of the environment variables to the script ./user_bin/jobscheduler_environment_variables.sh
   • ORACLE_HOME=/some_location
LD_LIBRARY_PATH=$ORACLE_HOME/lib
TNS_ADMIN=/some_location
export ORACLE_HOME LD_LIBRARY_PATH TNS_ADMIN
   • This script is executed on JobScheduler start in the context of the user account that JobScheduler is operated for. The environment variables are forwarded to subsequent jobs.
2. Restart JobScheduler

Hints

...

using Wallet®