Idea Details

JWP should support LDAP-based Oracle JDBC strings in ucsrv.ini

Last activity 05-18-2018 12:47 AM
Michael Lowry's profile image
04-13-2018 04:35 PM

In the JDBC section of the ucsrv.ini file, one specifies a JDBC connection string (Oracle in our case) that instructs the AE processes (CPs, WPs, and JWPs) how to connect to the database. The Java Work Process does not work correctly if the Oracle JDBC connection string is based on LDAP. It should.

Non-LDAP connection string

SQLDRIVERCONNECT=jdbc:oracle:thin:@//ABX4-SCAN.MYCOMPANY.COM:1521/DB123.CORP.MYCOMPANY.COM

LDAP connection string

SQLDRIVERCONNECT=jdbc:oracle:thin:@ldap://oranamesldap1.mycompany.com:3389/DB123,cn=OracleContext,dc=mycompany,dc=com

The advantage of using a connection string based on LDAP is that we can put a DB name in the string, and not a DB host name. This means if the DB host name changes, it will still work.

The JWP should support LDAP-based connection strings.

Legacy enhancement request ID: PMPER-454, opened March 2015.


Comments

05-18-2018 12:47 AM

This idea should be understood to apply broadly to any Automic component that uses JDBC.

05-18-2018 12:47 AM

Announced in Automic Community discussion thread: