Important Notes

Refer to the following important notes regarding the overall installation of a Development Client.

1. For Tools Release 9.2.1.0, refer to MOS Doc ID 2207529.1 for directions on installing the requisite JRE version prior to running the Development Client Installer.

   For Tools Release 9.2.1.2 and later, OUI installs its own Java Runtime Environment (JRE) so one is not required to be present before OUI is run. However, OUI will attempt to use any Java-related Microsoft Windows environment variables that are set before it is run. Examples of some Java environment variables are JAVA_HOME, JAVA_TOOL_OPTIONS, and _JAVA_OPTIONS. If any of these are set to invalid values, OUI may fail to run, or it may fail during the installation. Be sure to either validate these environment variables or delete them before running OUI.

2. Microsoft Visual Studio is not required unless you are building business functions on the Development Client. If you plan to build business functions, you will need the compiler and additional libraries that Visual Studio and Windows Software Development Kit (SDK) provides.
3. Verify that all previous releases of JD Edwards EnterpriseOne (Development and Standalone) Clients have been completely uninstalled or saved via SnapShot before installing a new Development or Standalone Client. For instructions on how to uninstall the Development Client, refer to the section of this guide entitled: Uninstalling the Development Client.
4. The Development Client does not require Software Protection Codes (SPCs) to run so you will not need to perform the steps for applying SPCs that previous EnterpriseOne releases required.
5. The EnterpriseOne Development Client does not use a local database (E1Local, OEE) in Tools Release 9.2.5 and later.
   1. There is no need to install OEE on a workstation on which only 9.2.5.0 or later Tools Releases will be used.
   2. If OEE is already installed:
      • Keep it installed if snapshots from earlier Tools Releases need it.
      • Uninstall it if not being used.
   3. A workstation can have both EnterpriseOne instances that use OEE and instances that do not use OEE.
      • Only one active EnterpriseOne instance at a time is in a runnable state.
      • Inactive EnterpriseOne instances should be saved via Snapshot.
   4. Snapshot supports EnterpriseOne instances that use OEE as well as instances that do not use OEE.
   5. Be sure to use the latest Snapshot.exe available.
6. The Development Client sign on uses this JD Edwards EnterpriseOne application:

   Work with User Spec Objects Eligible for Delete

   1. The Work with User Spec Objects Eligible for Delete application displays objects that are not checked out to the user. You can cancel out of the form and retain your user specs or select records to delete.
   2. If there are user specs, runtime will run off the user specs.
   3. If there are NO user specs, runtime will run off the package specs.
   4. If the object is not checked out to the user, the latest specs for that object are in the package that the user just installed (in the package specs).
   5. If the package specs have the latest specs for the object, there is no need to retain the user specs records for that objects.
   6. If the package name and pathcode does not reside in F98825 you will not be able to log on.
   7. If there is an object that is frequently changed and you have modifications for that object you use for testing, you may want to keep the user spec.