Configuring a Database Connector Using DADriver (Release 9.2.7)

Starting with Tools Release 9.2.7, you can configure a database connector in the Orchestrator Studio that uses the JD Edwards EnterpriseOne Data Access Driver (DADriver). The DADriver is a read-only type 4 JDBC driver and it enables read-only connectivity to the EnterpriseOne database. Using this connector, you can read data from the EnterpriseOne database by using complex SQL statements and joined tables.

For more information about the DADriver and the supported SQL grammar, see:

Using the JDBC Driver

For information about the settings for JDBj.ini, see:

Create an Application Interface Services (AIS) Server as a New Managed Instance

Note: You must have knowledge of the Groovy, JRuby, or Jython scripting language to create a database connector to read data from the EnterpriseOne database. The Connector design page provides a template for the selected scripting language that you can use as a basis for creating a script for a database connector.

1. Click the Connectors icon on the Orchestrator Studio Home page.

2. On the Connectors side panel, click the New drop-down menu and select Database.

3. Create and name the connector service request as described in Creating a Component.

4. On the Connectors design page, click the Database field and select the EnterpriseOne Database (Read-only) connection. Selecting this option enables you to connect to the DADriver that provides a built-in, preconfigured, and read-only connection to the EnterpriseOne database.

   Note: The system uses the same login credentials used for the Orchestrator Studio to connect to the DADriver. For executions outside of the Orchestrator Studio, the credentials used to run the orchestration are also used for the DAD driver.

   The Orchestrator Studio displays an edit area that contains a script template corresponding to the selected scripting language (Groovy, JRuby, or Jython). Click the Show Shortcut Command icon (?) to view the commands to work with the script.

   In the edit area, you can add advanced database operations like complex queries and table joins.

5. In the Input grid, enter the inputs that you want to pass to the database connector.

6. In the Output column, list the fields added to the returnMap in the Groovy script to make those outputs available to the orchestration. Optionally, enter a variable name in the Variable column if you want to make the values available for mapping to a subsequent step in an orchestration.

7. If you intend to return a set of records, enter a name for the data set in the Data Set Variable Name field.

   You must then define the column names (fields) for the records you want to return (such as name, location, and so on).

   Member Names - Variable Name grid is applicable only used if you enter a value in the Data Set Variable Name field.

8. The Member Name column correspond to the field in the table in the database. The Variable Name column is the name that you would use to refer to the corresponding field when passing it to the other orchestration steps.

9. Click Save.

> quick tour: Click here to view a recording of this feature.