Database connection string for Oracle with protocol TCPS

Article Id: 84705
Status: Published
Updated On: 15-04-2018 08:01
Legacy Id: 000014096
Products:
CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction:

Error Message :
N/A

When the Transmission Control Protocol Service (TCPS) protocol is used with the Automation Engine (AE) using an Oracle database (DB), the connection string of [JDBC] must be set:

[JDBC]
ods.setURL(sqlDriverConnect=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=exa33-scan4.swift.corp)(PORT=1501))(CONNECT_DATA=(SERVICE_NAME=autprd_dba.swift.com))));TrustStore=/u01/app/orls/product/12.2.0/client_1/network/admin/wallet/ewallet.p12

Otherwise the Java Worker Process (JWP) cannot  be started.

This is not an issue of AE, since TCPS is not supported.
 

Cause:

Cause type:
By design
Root Cause: TCPS is not supported - by changing the connect string - the JDBC connect is not found and the JWP is doing a fallback to OCI.

Environment:

Release: AUTWAB99000-12.0-Automic Workload Automation-Base Edition
Component:

Resolution:

The TCPS protocol is not supported.  By changing the connect string, the JDBC connect string is not found and the JWP is doing a fallback to OCI.

Set the [JDBC] connection string as follows:
 

[JDBC]
ods.setURL(sqlDriverConnect=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=exa33-scan4.swift.corp)(PORT=1501))(CONNECT_DATA=(SERVICE_NAME=autprd_dba.swift.com))));TrustStore=/u01/app/orls/product/12.2.0/client_1/network/admin/wallet/ewallet.p12


Fix Status: No Fix

Additional Information:

Workaround :
N/A