Page History

...

• The wallet does not necessarily have to be created on the machine where JOC Cockpit is located. The wallet preferably consists of a number of keystore and truststore files that can be copied from a remote machine to the server that hosts JOC Cockpit.

• Typical commands to create a wallet include for example:
  
  

  Code Block
  title Example how to set up a wallet linenumbers true
  # 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

...

Anchor
pki pki

Oracle PKI Libraries

• The following Oracle Java PKI libraries are required that and 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 For on premises installations store the libraries to the JETTY_HOME/lib/user_lib directory of the JOC Cockpit installation directory respectively.
• When running JOC Cockpit containers for Docker® consider to store the JDBC Driver and libraries in the JETTY_BASE/resources/joc/lib directory.

...

• The Hibernate configuration file can look like this:
  
  

  Code Block
  title Example of a Hibernate configuration file linenumbers true collapse true
  <?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 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 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 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.

Anchor
tnsnames_ora tnsnames_ora

Oracle tnsnames.ora Configuration File

...