When installing the CM server, include the JDBC component to create the Oracle database connection parameters, which are stored in the cm.conf configuration file. The instance name is usually orcl, in Oracle Express it is XE.
After completing the guide and installing the database's certificate and the trusted issuer's certificate on the Oracle database, additional changes are required in the cm.conf file in order for CM and the Oracle JDBC driver to be able to connect to the database. A detailed explanation of relevant parameters of the Oracle JDBC driver can be found here: http://www.oracle.com/technetwork/ database/enterprise-edition/wp-oracle-jdbc-thin-ssl-130128.pdf Follow these steps:
Change the Database.name parameter to provide the whole connection information as defined in the Oracle database file tnsnames.ora. For example:
In order for the Oracle JDBC to trust the Oracle database's certificate, the certificate's issuer has to be trusted. To achieve this, add the issuer's certificate in a keystore with trusted certificates. For example:
Example: Add issuer's certificate in keystore with trusted certificates
If TLS client authentication is also activated on the server, the Oracle JDBC driver needs to be provided with the key and certificate to be used for authenticating to the Oracle database. This certificate has to be signed by an issuer trusted by the Oracle database. For example:
Example: Sign certificate by an issuer trusted by the Oracle database
;If PKCS12 file is used as storage for key and certificate
Database.security.4 = javax.net.ssl.keyStore = <path_to_p12_file>
Database.security.5 = javax.net.ssl.keyStoreType = PKCS12
Database.security.6 = javax.net.ssl.keyStorePassword = <p12_password>
;If JKS keystore file is used
;Database.security.4 = javax.net.ssl.keyStore = <path_to_JKS_file>
;Database.security.5 = javax.net.ssl.keyStoreType = JKS
;Database.security.6 = javax.net.ssl.keyStorePassword = <keystore_password>