Configure the CData JDBC Driver for JD Edwards in a Connection Pool in Tomcat

The CData JDBC Drivers support standard JDBC interfaces to integrate with Web applications running on the JVM. This article details how to connect to JD Edwards data from a connection pool in Tomcat.

Connect to JD Edwards Data through a Connection Pool in Tomcat

1. Copy the CData JAR and CData .lic file to $CATALINA_HOME/lib. The CData JAR is located in the lib subfolder of the installation directory.
2. Add a definition of the resource to the context. Specify the JDBC URL here.

   The driver connects to JD Edwards through your Application Interface Services (AIS) Server. Set the following connection properties:

   • URL: The base HTTPS URL of your AIS Server (e.g., https://jde-ais.example.com:8300).
   • User: Your JD Edwards username.
   • Password: Your JD Edwards password.
   • Environment (optional): The JD Edwards environment to use (e.g., PD920 for production or DV920 for development). If not specified, the AIS Server's default environment is used.
   • Role (optional): The JD Edwards role for the session. If not specified, the AIS Server's default role is used.
   • DeviceName (optional): An identifier for the connecting device or application, used for auditing and logging on the AIS Server.
   • Jasserver (optional): The specific Java Application Server (JAS) instance to route requests through, useful in clustered environments.

   Choosing Which Data Is Exposed

   JD Edwards organizes tables and business views by System Code, and the driver exposes each System Code as its own schema. Use these properties to control which schemas are available:

   • DataModel: One or more ERP modules (comma-separated) whose System Codes are exposed as schemas, or All to expose every System Code in the connected instance. Defaults to FinancialManagement.
   • SystemCodes: A comma-separated list of additional System Codes to expose alongside those from DataModel (e.g., 42,43).

   When you connect, the driver sends your credentials to the AIS Server to obtain a session token and caches it. The driver requests a new token automatically before the session expires.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the JD Edwards JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   
   java -jar cdata.jdbc.jdedwards.jar
   

   Fill in the connection properties and copy the connection string to the clipboard.

   

   You can see the JDBC URL specified in the resource definition below.

   
   
   <Resource name="jdbc/jdedwards"   auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.jdedwards.JDEdwardsDriver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;" maxActive="20" maxIdle="10" maxWait="-1" />
   

   To allow a single application to access JD Edwards data, add the code above to the context.xml in the application's META-INF directory.

   For a shared resource configuration, add the code above to the context.xml located in $CATALINA_BASE/conf. A shared resource configuration provides connectivity to JD Edwards for all applications.

3. Add a reference to the resource to the web.xml for the application.

   
   
     JD Edwards data JSP
     jdbc/JDEdwards
     javax.sql.DataSource
     Container
   
   

4. Initialize connections from the connection pool:

   
   Context initContext = new InitialContext();
   Context envContext  = (Context)initContext.lookup("java:/comp/env");
   DataSource ds = (DataSource)envContext.lookup("jdbc/JDEdwards");
   Connection conn = ds.getConnection();
     

More Tomcat Integration

The steps above show how to connect to JD Edwards data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.