Configuring a Connection

After Installing the Connector you can connect and create a Data Source for data in JD Edwards.

Setting Up a Data Source

Complete the following steps to connect to the data:

Under Connect | To a Server, click More....
Select the data source called JD Edwards by CData.
Enter the information required for the connection.
Click Sign In.
If necessary, select a Database and Schema to discover what tables and views are available.

Using the Connection Builder

The connector makes the most common connection properties available directly in Tableau. However, it can be difficult to use if you need to use more advanced settings or need to troubleshoot connection issues. The connector includes a separate connection builder that allows you to create and test connections outside of Tableau.

There are two ways to access the connection builder:

On Windows, use a shortcut called Connection Builder in the Start menu, under the CData Tableau Connector for JD Edwards folder.
You can also start the connection builder by going to the driver install directory and running the .jar file in the lib directory.

In the connection builder, you can set values for connection properties and click Test Connection to validate that they work. You can also use the Copy to Clipboard button to save the connection string. This connection string can be given to the Connection String option included in the connector connection window in Tableau.

Connecting to JD Edwards

The connector connects to JD Edwards through your JD Edwards Application Interface Services (AIS) Server.

Set the following connection properties to connect:

URL: The base HTTPS URL of your AIS Server. For example: https://jde-ais.example.com:8300
User: Your JD Edwards username.
Password: Your JD Edwards password.
Environment (optional): The JD Edwards environment to use (for example, PD920 for production or DV920 for development). The environment determines which database and configuration settings the provider uses during the session. If not specified, the AIS Server's default environment is used.
Role (optional): The JD Edwards role for the session. Roles in JD Edwards determine the permissions and data access 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. If not specified, the IP address of the device the connector is running on is used as the identifier.
Jasserver (optional): The specific JAS (Java Application Server) instance to route requests through. This connection property is useful for associating requests with a particular node in a clustered environment. If not specified, the connector uses the default HTML Server configured for the AIS Server.

To control what exact JD Edwards data is exposed, set these properties:

DataModel: A module (or a comma-separated list of modules) whose system codes you want to expose as schemas in the connector. Supported values include All, FinancialManagement, HumanCapitalManagement, Logistics, Manufacturing, OrderManagement, RealEstateManagement, and others. Defaults to FinancialManagement.
SystemCodes: A comma-separated list of additional JD Edwards system codes to expose as schemas alongside those of the selected DataModel(s). For example, SystemCodes=42,43.

Token Caching

The connector uses your credentials to obtain a session token, which is necessary to request your JD Edwards data from the API, from the AIS Server and caches it for subsequent requests.

On the first connection, the connector sends your credentials to the AIS Server to obtain a session token. You can use the CredentialsLocation property to change the token storage location.

When the session token approaches expiry — after approximately 90% of the AIS Server's configured session timeout — the connector automatically requests a new token using the stored credentials.

Next Step