Connect to JD Edwards from a Connection Pool in WebLogic

The CData JDBC Driver for JD Edwards enables you to follow standard procedures to integrate JD Edwards data into Java Web applications. This article shows how to deploy the CData JDBC Driver for JD Edwards in WebLogic Server.

Deploy the JDBC Driver in WebLogic Server

To deploy the driver, add the driver JAR to your classpath. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory.

If you want to add the driver to all domains, prepend the path to the JAR to the WEBLOGIC_CLASSPATH environment variable in WL_HOME\common\bin\commEnv.cmd/sh. This script is located in WL_HOME\common\bin\. For example:

set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.jdedwards.jar;%WEBLOGIC_CLASSPATH%

In WebLogic 12.2.1 if you want to add the driver to a specific domain, you can simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.

Earlier versions require that you manually add the driver to the classpath: Prepend the following to the PRE_CLASSPATH environment variable in setDomainEnv.cmd/sh. This script is located in the bin subfolder of the folder for that domain.

set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.jdedwards.jar;%PRE_CLASSPATH%

After making these changes, restart the server.

Create a JDBC Data Source for JD Edwards

After deploying the driver, log into the WebLogic Administration Console and create the connection.

1. In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
2. On the JDBC Data Source Properties page, enter the following information:
   • Name: Enter a user-friendly name; for example, jdedwardsjdbc.
   • JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/JDEdwards.

   • Database Type: Select Other.

   

3. Click Next to use the default options. On the last page, enter the following information and click Test Configuration:

   • Driver Class Name: Enter the driver class, cdata.jdbc.jdedwards.JDEdwardsDriver.

   • URL: Enter the JDBC URL. A typical JDBC URL is below:

     jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;

     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.

     
   • Database User Name: Enter the username, if not specified in the JDBC URL.
   • Password: Enter the password, if not specified in the JDBC URL.
   

After selecting the server where you want to deploy the JDBC data source, you can now connect to JD Edwards data.

More WebLogic Integration

The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the WebLogic Data Sources chapter of the Oracle Fusion Middleware documentation.