Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • No Oracle Client installation is used, however, you might need an Oracle Client to set up and configure the Oracle Wallet®.
    • Typical commands to create a wallet include e.g.:
      • # create wallet in a directory that is accessible to the JS7 run-time account assumed to be "JS7"
        mkstore -wrl /home/JS7/wallet -create
        # add credentials to wallet; specify entry key, database account and password
        mkstore -wrl /home/JS7/wallet/ -createCredential JS7 some_account some_password
    • Consider that the mkstore the command will add the location of the wallet to your sqlnet.ora configuration file.
      • This file is used e.g. by SQLPlus and therefore allows e.g. to execute: sqlplus /@JS7 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.
  • JS7 makes use of the Oracle JDBC Driver:
    • Check the Oracle JDBC Driver version that ships with the JS7 release, see JS7-Database-DBMSandJDBCDriverVersions. A newer Oracle JDBC Driver might be available for download as the Open Source JS7 might not be bundled with the latest Oracle JDBC Driver.
    • Oracle JDBC Drivers that ship for release 18c of the DBMS are is reported to work. Previous JDBC Driver releases as e.g. 12c are reported not to work with Oracle Wallet® when used by JS7.
  • 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  JOC Cockpit installation path respectively.

...

  1. Copy declaration and initialization with the export of the environment variables to the script ./user_bin/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 Controller start in the context of the user account that Controller is operated for. The environment variables are forwarded to subsequent jobs in a workflow.
  2. Restart Controller


Instead of adding the environment variables to the Controller's environment variable script, it can be added to the Job Resources which then can be assigned to the job which requires access to Oracle environment variables. Job Resources are the name/value pairs that can be assigned to any job or workflow.

Hints

  • The Oracle Wallet® cannot be copied to other servers or to other accounts, it should be configured separately per each environment.
  • The same mechanism is available for JS7 Agent that allows to set and export environment variables from its instance script.

...