Introduction

Unity Version 3.0 ODBC Help - Introduction

General

This is Unity Solutions latest Help Manual and relates specifically to jdeDirect ODBC Driver and Gateway Service Release Version 3.0 and above for JDE OneWorld and EnterpriseOne.

However, the manual has been updated also with all the details fully described in version 2.0.  It is not now necessary to have to refer to two versions of the jdeDirect Manual to find the information you require.

(Note however, version 2.0 of the user Guide is still available from the Unity Solutions Web site.  If required it may be downloaded from   http://www.unitysolutions.com/helps/unity_odbcv2/html/ )

Included here are

The new version 3.0 ODBC drivers have now eliminated completely the need for an E1 Fat Client.  However, if a Fat Client is present the option exists to use it or not.

Also the new version 3.0 ODBC Driver for JD Edwards OneWorld and EnterpriseOne now expose E1 Media and Text Objects just like any other table and column.  This is explained in detail in the Media and Text Objects section of this manual.

Introduction to Installation and Set-Up

Before starting your OneWorld jdeDirect ODBC Driver installation it is strongly recommended that you read this introduction fully in conjunction with the two schematics; Gateway Service Set-Up Schematic and jdeDirect ODBC Driver Set-Up Schematic in the following sections.

The most simple driver installation is 'Pass Through'.  This can be installed on your PC and is independent of the JDE OneWorld release in use and whether a Fat Client is installed.  The actual driver installation is no different to that described in the version 2.0 manual but one screen layout varies slightly.  The schematic following describes the screens only.

Next, decide whether the Gateway Service is to be used or not.

The Gateway Services Manager can be installed anywhere and does not now require a Fat Client.  The installation process recognises if a Fat Client is loaded on the PC and will give you the option to use it or not.  You can use the Fat Client route once only.

It is now possible via the Gateway Services to install multiple services, thus allowing Users to have access to different versions of native JDE, Xe through to version 8.12.  Each service is configured to point to the Gateway machine IP address, which you will need for the driver install, and a different port which the system assigns but can be overridden at any time.

The Gateway Services install recognises through the .INI file specified which version of JDE is required for the driver.  If Xe or ERP8 are identified, the install further asks for the .LOG file to  use, this then defines the Service Pack installed.

If a Fat Client is to be used, then the install uses Fat Client APIs for user authentication etc.

If a Fat Client is NOT used or has been used once already then the install uses the Classes files for the information needed (.JAR files) for user authentication. Namely Java Interoperability.

(As a further note for those technically minded the Service manager has been designed to support multiple threads.  Therefore, if a number of Users all sign onto a single service at the same time the sign on process is speeded up).

If the Gateway Service is to be used then note the IP address of the service machine.  It will be needed for the service installation.

Also NOTE: The Gateway Service IP address should be a Fixed Address.

A schematic of the install process is available here.  Full details of the Gateway install are available at Gateway Machine Installation Common.

Having decided if the Gateway service is to be used or not then the jdeDirect ODBC Driver can be installed...

If the Gateway Service is to be used, then select that route and follow the simple installation route using the IP address and required service port etc.

If the Gateway Service is NOT used then installation options are more extensive.

First question is, is a Fat Client (FC) installed on the PC?  The Driver Set-Up checks and;

If it is not then the driver installation behaves as a Gateway Service installation and requires an IP address and Port for the service together with JDE User and Pass Word details.

If now a Fat Client is installed then the installation route will vary depending on the Service pack installed.  Again the Driver install Set-Up checks for service pack.  See the Schematic following for a visual representation of the options.  Full details of the Client install process are available at Client Machine.