1. Deployment Server Reference Guide for Microsoft Windows
  2. Remove the Local Oracle Database Installer for the Development Client

Remove the Local Oracle Database Installer for the Development Client

In Tools Release 9.2.5.0, the requirement for a local Oracle database on the Development Client was removed. This database is also referred to as E1Local, OEE (which stands for Oracle Enterprise Edition), or JDELocal. The EnterpriseOne object specs were moved from that local database to the Central Objects datasource. 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.

Important: Although the need for E1Local was removed from the Development Clients, it is still required on the Deployment Server.

E1Local can remain installed on Development Client machines, or it may be removed following the steps in the Development Client Installation Guide.

These steps to remove the E1Local installer from the Deployment Server are optional:

  • Edit this file:

    <E1_dep_svr_install_directory>\OneWorld Client Install\InstallManager.htm

  • Either comment out or remove the line on which OEE12Setup.exe exists.
  • Save the file.
  • Delete this directory:

    <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\ORACLE

Important: In order to avoid incompatibilities between versions of OUI on the Development Client, you can use Snapshot or uninstall the existing Development Client before attempting to install a full package using the new installers.

Note: The SnapShot program that comes with the Tools Release 9.2.5.0 and higher is backwards compatible and can save/restore EnterpriseOne Development Clients from previous Tools Releases that include E1Local and also save/restore clients from Tools Releases up to the Tools Release of Snapshot.exe.

Important: When installing the Web Client (WLSH4A or WASH4A) using installers prior to Tools Release 9.2.5.0, the JDBj-SPEC DATA SOURCE section in the jdbj.ini file is populated with information that points to the E1Local database as the location of the Serialized Objects tables (F989998 and F989999). Because E1Local is no longer supported with Tools Release 9.2.5.0, the Web Client installers comment out this entire section in the jdbj.ini file. This causes the Web Client to use OCM to determine the location of the Serialized Objects tables.