Versions Compared

Key

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

...

No Oracle Client installation is required at run-time for use of a wallet with JS7 componentsJOC Cockpit. 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 or Agents are is located. Technically the The wallet preferably consists of a number of keystores keystore and truststores truststore files that can be copied from a remote machine to the server that hosts the JS7 componentJOC Cockpit.
  • 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

...

  • 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.
  • To apply a version of the JDBC Driver that is different from the version that ships with JS7, see JS7 - Database, chapter: Individual JDBC Driver Versions.

...

JOC Cockpit is configured to connect to an Oracle database by use of Hibernate. In addition the Oracle database without specifying a user account and password, instead, at run-time JOC Cockpit makes use of a walletlocation of Oracle configuration files and of the wallet has to be specified.

Anchor
hibernate_cfg_xml
hibernate_cfg_xml
Hibernate hibernate.cfg.xml Configuration File

  • Location: JETTY_BASE/resources/joc/hibernate.cfg.xml, see JS7 - Database.
  • The hibernate Hibernate configuration should file can 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 of a JDBC connection.

...