Setting up ODI to Integrate with JD Edwards

  To set up ODI to integrate with JD Edwards:

1. Download the JD Edwards EnterpriseOne Data Access Driver (DAD) driver:

   1. Select the Patches and Updates tab, and then select JD Edwards Patches.

   2. From JDEdwards, enter: EnterpriseOne Tools Releases.

   3. In Release, select All Releases.

   4. In Platform, select Multiplatform.

   5. In Description (*text*), select *Data Access Driver*.

   6. Select the License Agreement check box.

   7. Click Search.

   8. Click the plus sign (+) to add Tools 9.1 Data Access Driver to the Download Basket.

   9. Click the Item(s) hyperlink and download the tools release specific item.

2. To copy the DAD Drive:

   1. Unzip the archive file to a temporary directory.

   2. Extract the JAR file DADriver_EAR.jar file.

   3. Copy the extracted contents of DADriver_EAR.jar to the following directory: EPM_MIDDLEWARE_HOME\odi\odi_misc.

      Typically, EPM_MIDDLEWARE_HOME is C:\Oracle\Middleware

3. Request that the JD Edwards system administrator to provide you with the following files:

   • jdbj.ini

   • jas.ini

   • jdelog.properties

   The three files above can be generated when you register the JD Edwards EnterpriseOne Data Access Driver using the JD Edwards Server Manager.

4. Copy the jas.ini file, jdbj.ini file, and jdelog.properties file from the JDE Application Server to:

   EPM_MIDDLEWARE_HOME\odi\odi_misc directory.

   Typically, EPM_MIDDLEWARE_HOME is C:\Oracle\Middleware

5. Ensure that the security server of the jas.ini file is set correctly.

6. Review and edit the jdbj.ini file as follows:

   1. If the JD Edwards application database is Oracle, update the location to the tnsnames.ora file.

   2. Encrypt the [JDBj-BOOTSTRAP SESSION] stanza, and then the password value.

   3. Modifications to the .INI file password encryption can only be accomplished through the use of Server Manager.

   4. Set the value of following parameters under [JDBj-RUNTIME PROPERTIES] stanza to:

      resultSetTimeout=-1
      transactionTimeout=-1
      usageExecutionThreshold=20000
      usageResultSetOpenThreshold=120000
      usageTracking=false
      msSQLQueryTimeout=1800000

7. Edit the jdelog.properties file and set the log level as needed.

   In a production environment, set the log level to SEVERE so that only severe errors are reported in the log file.

8. Ensure you can access the server specified in the jdbj.ini file from the ODI Server.

9. Run the script updateODIEAR.bat / sh from the following directory: EPM_ORACLE_HOME\products\FinancialDataQuality\bin

   Before running the script, make sure that environment variables JAVA_HOME and TEMP are set correctly.

   Typically the EPM_ORACLE_HOME directory is C:\Oracle\Middleware\EPMSystem11R1

10. If you are using JDE Tools 9.1.2 or 9.1.3, then run the script copyfilesJDE912.bat / sh from the following directory:

    EPM_ORACLE_HOME \products\FinancialDataQuality\bin

    If you are using JDE Tools 9.1.4 or higher, then run the script copyfilesJDE914.bat / sh from the following directory:

    EPM_ORACLE_HOME \products\FinancialDataQuality\bin

11. If JD Edwards is using Microsoft SQL Server or IBM databases, then download the JDBC driver and copy it to the: <DOMAIN HOME>/lib directory.

    Typically this is the C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib directory.

    Refer to the JD Edwards Tools documentation for the supported versions of the JDBC driver for the database platform.