1. Deployment Server Reference Guide for IBM i
  2. Understanding the Local Oracle Database Installer

Understanding the Local Oracle Database Installer

Tools Releases prior to 9.2.5.0 require a database to be installed onto the same machine on which the Development Client is to be installed. This local Oracle database on the Development Client contains local specs and other data. This database is also referred to as E1Local, OEE (which stands for Oracle Enterprise Edition), or JDELocal. With Tools Release 9.2.5.0, the EnterpriseOne object specs were moved from that local database to the Central Objects data source. Because of this, the need for the database on the Development Client was removed. This move saves the time and disk space required to install the local Oracle database. It also saves much time during the installation of the Development Client and the save/restore operations of SnapShot.

You can choose the database based on the Applications Release of EnterpriseOne and "bitness" of the Windows operating system that your users are using. Do not take the following information for granted - you should always check Oracle Certifications for the most current official information.

  • Applications Release 9.0
    • 64-bit Oracle Enterprise Edition 12c (OEE)
    • Microsoft SQL Server 2005 Express Edition SP3 or later
  • Applications Release 9.2
    • 64-bit Oracle Enterprise Edition 19c (OEE) or
    • 64-bit Oracle Enterprise Edition 12c (OEE)

To install a database onto a Development Client machine, the user runs this program:

\\<deployment server name>\<release>\OneWorld Client Install\InstallManager.exe

This program enables the user to install a local database or the JD Edwards EnterpriseOne Development Client. By default, the InstallManager.htm file is shipped from Oracle configured to install OEE.