Creating the Data Source Name

This section describes how to edit the DSN configuration and then authenticate and connect to JD Edwards APIs.

DSN Configuration

You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the installation process creates a both a user DSN and a system DSN, as described in Installing the Connector.

Note: The connector stores connection information in the Windows registry. To ensure that the connector can write to the registry, either run Power BI as an administrator or use a User DSN for your connection instead of a System DSN.

User DSN

Complete the following steps to edit the DSN configuration:

Select Start > Search, and enter ODBC Data Sources in the Search box.
Choose the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).
Select the system data source and click Configure.
Edit the information on the Connection tab and click OK.

System DSN

Configure the system DSN the same way as the user DSN, except you will need to switch to the System DSN tab before performing Step 3.

If you're using Power BI's On-Premises Data Gateway with Standard mode, you must use the system DSN.

You must also specify a valid location for CredentialsLocation (a path where the MFA credentials file is locally stored).

This is because the Standard mode runs on service mode and can only access permitted locations, such as C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway.

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.