- Out of the box the Oracle PP only supports the use of the Oracle JDBC Thin driver with Thin-style Service Name Syntax (@//host_name:port_number/service_name) when building the DB connection string.
- This document covers how to use the Oracle JDBC OCI driver with TNSNames Alias Syntax (@MyTNSAlias)
- A small change needs to be made to the getConnectionString() method for com.wily.introscope.oracle.util.DBConnectionData contained in the PPOracleDB.jar file.The change simply modifies the Oracle JDBC connection string to just take the hostname part of the hostname-port-db property in the PPOracleDB.properties field and uses that as the TNS alias.
- To avoid a syntax error at PP startup the hostname-port-db property still needs to contain the 3 parameters for "Hostname/Port/Database" e.g. orcl_iscope/1521/orcl where orcl_iscope is the TNS alias from the tnsnames.ora file
- An Oracle Secure External Password Store using a client-side Oracle wallet can be configured to securely store the credentials for the PP Oracle connection (default iscope_orcl/iscope/orcl) e.g. http://docs.oracle.com/cd/E25054_01/network.1111/e16543/authentication.htm#CHDHGAIJ.
So that means the username & password fields can be set to null in the PPOracleDB.properties file for improved security.
- Connection to an Oracle RAC could be achieved via the RAC TNS_ALIAS (usually configured with a VIP for the hostname)
- Modified version of DBConnectionData.java, compiled class DBConnectionData.class and APM 10.1 version of updated PPOracleDB.jar
- Example PPOracleDB.properties file
Please post any questions/problems back to this page
Please note that like any other Field pack this change is not officially supported\tested\certified.