ELM support for LDAP-based Oracle JDBC connection (support WAS Liberty managed server.xml data sources)

Customer using Oracle JDBC URL connections in Traditional WAS with ELM cannot use them after migrating to Liberty. Below is some background.

The behavioral difference between traditional WAS and Liberty is due to differences in JNDI context handling.

In traditional WAS, JNDI resources are container-managed and available to all application threads, including async/background threads. Since Oracle LDAP-based JDBC URLs require JNDI lookups for LDAP resolution, the Oracle driver is able to successfully resolve the LDAP URL in all threads.

In Liberty, ELM does not use Liberty-managed datasources defined in server.xml. Instead, ELM establishes database connections directly using the JDBC URL configured in teamserver.properties. When async/background threads create new connections, the Oracle JDBC driver attempts to perform LDAP resolution through JNDI. However, these threads do not have the required JNDI/OSGi context available, which results in the observed NoInitialContextException ("The calling code's BundleContext could not be determined").

Although defining a datasource in server.xml would allow Liberty to manage the datasource lifecycle, JNDI binding, and connection pooling, ELM currently does not use Liberty-managed datasources for JDBC connections.

However, other ELM applications use Liberty datasource defintions, for example Jazz Authorization Server and PUB Document Builder.