Connect to JD Edwards Data from a Connection Pool in JBoss

CData JDBC drivers can be configured in JBoss by following the standard procedure for connection pooling. This article details how to access JD Edwards data from a connection pool in JBoss applications. This article details how to use the JBoss Management Interface to configure the CData JDBC Driver for JD Edwards. You will then access JD Edwards data from a connection pool.

Create a JDBC Data Source for JD Edwards from the Management Console

Follow the steps below to add the driver JAR and define required connection properties.

1. In the Runtime menu, select the Domain or Server menu, depending on whether you are deploying to a managed domain or to a stand-alone server, and click "Manage deployments" to open the Deployments page.
2. Click Add. In the resulting wizard, add the JAR file and license for the driver, located in the lib subfolder of the installation directory. Finish the wizard with the defaults, select the driver, and click Enable.
3. In the Configuration menu, click Subsystems -> Connector -> Datasources. This opens the JDBC Datasources page.
4. Click Add and, in the resulting wizard, enter a name for the driver and the JNDI name. For example:

   java:jboss/root/jdbc/JDEdwards

5. Select the driver that you added above.

6. Enter the JDBC URL and the username and password. The syntax of the JDBC URL is jdbc:jdedwards: followed by a semicolon-separated list of connection properties.

   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.

   

   A typical connection string is below:

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

7. Test the connection and finish the wizard. Select the JD Edwards data source and click Enable.

More JBoss Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more information, refer to the Data Source Management chapter in the JBoss EAP documentation.