Versions Compared

Key

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

...

Using Oracle Wallet® for JOC Cockpit

Anchor
prerequisites
prerequisites
Prerequisites

Anchor
wallet
wallet
Oracle Wallet®

No Oracle Client installation is required

...

at run-time for use of a wallet with JS7 components. However, users need an Oracle Client to set up and to configure the wallet.

  • The wallet does not necessarily have to be created on the machine where JS7 components such as JOC Cockpit is or Agents are located. Technically the wallet preferably consists of a number of keystores and truststores that can be copied from a remote machine to the server that hosts JOC Cockpitthe JS7 component.
  • Typical commands to create a wallet include for example:
    • # create the wallet in an arbitrary location
      mkstore -wrl /home/js7/wallet -create
      # add credentials to the wallet; specify key, user account and password for database access
      mkstore -wrl /home/js7/wallet/ -createCredential js7 some_account some_password
    JOC Cockpit makes use of the

Anchor
jdbc
jdbc
Oracle JDBC Driver

...

  • Check the Oracle JDBC Driver version that ships with the JS7 release, see JS7 - Database, chapter: Individual JDBC Driver Versions. A newer Oracle JDBC Driver might be available for download as included with the JS7 release.
  • Oracle JDBC Drivers that ship for release 18c of the DBMS are reported to work. Previous JDBC Driver releases, for example 12c, are reported not to work with Oracle Wallet® when used by JS7. If in doubt use the JDBC Driver version that matches the version of the DBMS.

Anchor
pki
pki
Oracle PKI Libraries

  • The following Oracle Java libraries are required that have to match the version of the Oracle DBMS and Oracle JDBC Driver.
  • The .jar files are available from an Oracle Client installation and are offered by Oracle for download:
    • $ORACLEORACLE_HOME/jlib/oraclepki.jar
    • $ORACLEORACLE_HOME/jlib/osdt_cert.jar
    • $ORACLEORACLE_HOME/jlib/osdt_core.jar

Using Oracle Wallet® for JOC Cockpit

Prerequisites

  • The Oracle Wallet® is required, see Prerequisites: Oracle Wallet
  • The JDBC Driver is required, see Prerequisites: Oracle JDBC Driver
  • The Oracle PKI Libraries are requires, see Prerequisites: Oracle PKI Libraries
    • Store the libraries to the JETTY_HOME/lib/user_lib directory of the JOC Cockpit installation directory respectively. When running JOC Cockpit for Store the libraries in the JETTY_HOME/lib/user_lib directory of the JOC Cockpit installation directory respectively. When running JOC Cockpit for Docker® consider to store the JDBC Driver and libraries in the JETTY_BASE/resources/joc/lib directory.

...

  • The hibernate configuration should look like this:

    Code Block
    titleHibernate configuration file for Oracle® database
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <hibernate-configuration>
     <session-factory>
      <property name="hibernate.connection.driver_class">oracle.jdbc.OracleDriver</property>
      <property name="hibernate.connection.password"></property>
      <property name="hibernate.connection.url">jdbc:oracle:thin:@/js7?tns_admin=/home/js7/wallet</property>
      <property name="hibernate.connection.username"></property>
      <property name="hibernate.dialect">org.hibernate.dialect.Oracle12cDialect</property>
      <property name="hibernate.show_sql">false</property>
      <property name="hibernate.connection.autocommit">false</property>
      <property name="hibernate.format_sql">true</property>
      <property name="hibernate.temp.use_jdbc_metadata_defaults">false</property>
      <property name="hibernate.connection.provider_class">org.hibernate.hikaricp.internal.HikariCPConnectionProvider</property>
      <property name="hibernate.hikari.maximumPoolSize">10</property>
     </session-factory>
    </hibernate-configuration>
  • 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 would 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 not required 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 for of a JDBC connection.

Anchor
tnsnames_ora
tnsnames_ora
Oracle tnsnames.ora Configuration File

...

The JS7 offers the following job templates for use with a Oracle Wallet®:

Both template jobs are running with Agents, therefore the wallet configuration is applied to the respective Agent.

Prerequisites

  • The Oracle Wallet® is required, see Prerequisites: Oracle Wallet
  • The JDBC Driver is required, see Prerequisites: Oracle JDBC Driver
  • The Oracle PKI Libraries are requires, see Prerequisites: Oracle PKI Libraries prerequisites for setting up the wallet and use of the Oracle JDBC Driver are the same as explained above with chapter Prerequisites.The following Oracle Java libraries are required that have to match the version of the Oracle DBMS and Oracle JDBC Driver.
      The .jar files are available from an Oracle Client installation and 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 JS7_AGENT_HOME/lib/user_lib directory of the Agent installation directory. When running Agents for Docker® consider to store the JDBC Driver and libraries in the JS7_AGENT_CONFIG_DIR/lib directory.

...

JS7 offers the following job templates for use with a Oracle Wallet®:

The template job is running with Agents and makes use of the sqlplus Command Line Client, therefore the wallet configuration is applied to the respective Agent.

Prerequisites

Prerequisites to execute SQL*Plus with Oracle Wallet® include that

...