This section describes how to set up ODBC connectivity and configure DSNs on several Linux distributions: Debian-based systems, like Ubuntu, and Red Hat Linux platforms, like Red Hat Enterprise Linux (RHEL) and Fedora.

Minimum Linux Versions

Here are the minimum supported versions for Red Hat-based and Debian-based systems:

OS	Min. Version
Ubuntu	18.04
Debian	10
RHEL	8
Fedora	28
SUSE	15

Installing the Driver Dependencies

Run the following commands as root or with sudo to install the necessary dependencies:

• Debian/Ubuntu:
  

  apt-get install libc6 libstdc++6 zlib1g libgcc1

• RHEL/Fedora:
  

  yum install glibc libstdc++ zlib libgcc

Installing the Driver

You can use standard package management systems to install the driver.

On Debian-based systems, like Ubuntu, run the following command with root or sudo:

dpkg -i /path/to/driver/setup/JDEdwardsODBCDriverforUnix.deb 

On systems that support the RPM package format, run the following command with root or sudo:

rpm -ivh /path/to/driver/JDEdwardsODBCDriverforUnix.rpm 

Licensing the Driver

Run the following commands to license the driver. To activate a trial, omit the <key> input.

cd /opt/cdata/cdata-odbc-driver-for-jdedwards/bin/
sudo ./install-license.sh <key>

Connecting through the Driver Manager

The driver manager loads the driver and passes function calls from the application to the driver. You need to register the driver with the driver manager and you define DSNs in the driver manager's configuration files.

The driver installation registers the driver with the unixODBC driver manager and creates a system DSN. The unixODBC driver manager can be used from Python and from many other applications. Your application may embed another driver manager.

Creating the DSN

See Using unixODBC to install unixODBC and configure DSNs. See Using the DataDirect Driver Manager to create a DSN to connect to OBIEE, Informatica, and SAS.

Connecting to JD Edwards

The driver 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 driver 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 driver 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 driver. 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 driver 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 driver 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 driver automatically requests a new token using the stored credentials.

Set the Driver Encoding

The ODBC drivers need to specify which encoding to use with the ODBC Driver Manager. By default, the CData ODBC Drivers for Unix are configured to use UTF-16 which is compatible with unixODBC, but other Driver Managers may require alternative encoding.

Alternatively, if you are using the ODBC driver from an application that uses the ANSI ODBC API it may be necessary to set the ANSI code page. For example, to import Japanese characters in an ANSI application, you can specify the code page in the config file '/opt/cdata/cdata-odbc-driver-for-jdedwards/lib/cdata.odbc.jdedwards.ini':

[Driver]
AnsiCodePage = 932