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

Idea created by Michael_Lowry on Apr 13, 2018
    Under review
    Score4
    • Franz Zalubil
    • Michael_Lowry
    • eric.felker
    • AxelLambrecht

    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.