This chapter contains the following topics:
Installation of the Development Client involves the following steps, each of which are described in the following sections and chapters:
Understanding Oracle Homes
Understanding important notes
Meeting the Minimum Technical Requirements
Installing WebSphere Express 7.0 or WebSphere Developer 7.0 (H4A7 only)
Running Install Manager
Installing a local database
Installing a local database client
Installing the Development Client (this uses the Oracle Universal Installer (OUI)).
Troubleshooting any installation errors.
Running the Development Client.
As of Tools Release 9.1, the Development Client is installed using the Oracle Universal Installer (OUI). In addition, the Web Client is installed as a package feature using OUI.
Each Oracle product that is installed on a machine is installed into an Oracle Home directory or path. This is a directory that contains most of the files associated with the product. This path has a name as well. You can specify a name that is intuitive so you do not have to remember the path.
When you install the Oracle Enterprise Edition (OEE) database engine on the Development Client, by default the Oracle Home path will be:
c:\Oracle\E1Local
The value E1Local cannot be changed, but you may specify another drive and/or directory instead of c:\Oracle. The Oracle Home name for the OEE database is E1Local. SSE does not install into an Oracle Home path.
When you install the Development Client, you specify an Oracle Home and name for that installation as well. For example, you may enter C:\E910 as the Oracle Home path and JDE_E910_Client as the Oracle Home name.
If you are using OEE and, following the above examples, you would now have two Oracle Homes:
The first Oracle Home is the Oracle Home of the OEE database; it has these properties:
Oracle Home Path
C:\Oracle\E1Local
Oracle Home Name
E1Local
The second Oracle Home is the Oracle Home of the Development Client; it has these properties:
Oracle Home Path
C:\E910
Oracle Home Name
JDE_E910_Client
During the installation of a Development Client installation package, OUI will copy the files from the package to subdirectories under the Oracle Home path and then perform the necessary configurations. In addition, it places a copy of OUI into the Oracle Home Path.
OUI also creates a submenu of items in the Start / All Programs menu. This submenu is named "Oracle - <Oracle_Home_Name>" where <Oracle_Home_Name> is the name that the user specified during the installation. This submenu will include a link to the EnterpriseOne Solution Explorer and another submenu for Oracle Installation Products. Oracle Installation Products includes a link to the copy of OUI that is in the Oracle Home Path. Although you can run other copies of OUI to deinstall (remove) the EnterpriseOne Development Client, it is safest to deinstall using the link in Start / All Programs / Oracle - <Oracle_Home_Name> / Oracle Installation Products / Universal Installer.
Refer to the following important notes regarding the overall installation of a Development Client.
Caution:
Please verify all JD Edwards EnterpriseOne Minimum Technical Requirements (MTRs) for supported versions of third party software. See the section Accessing Minimum Technical Requirements.OUI uses the term "deinstall" to mean removal of an Oracle product. This document will do the same.
JDK 1.6 is supplied with the installation for the Development Client to run. Do not replace this with another version of the JDK because higher versions of the JDK have not been validated with EnterpriseOne Tools Release 9.1. Also, do not replace this JDK with a 64-bit version because EnterpriseOne is a 32-bit program which requires a 32-bit version of the JDK even when running on a 64-bit version of Microsoft Windows.
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.
Microsoft Visual Studio is not required unless you are building business functions on the Development Client. The installation of the Development Client installs the Microsoft libraries that are necessary to run EnterpriseOne, but if you plan to build business functions, you will need the compiler and additional libraries that Visual Studio provides.
Verify that all previous releases of JD Edwards EnterpriseOne (Development and Standalone) Clients have been completely deinstalled or saved via Snapshot before installing a new Development or Standalone Client. For instructions on how to deinstall the Development Client, refer to the section of this guide entitled: Chapter 7, "Deinstalling the Development Client."
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.
Applications Release 9.1 supports only the Oracle Enterprise Edition (OEE) as the local database. It does not support Microsoft SQL Server 2005 Express Edition (SSE); however, Applications Release 9.0 supports both OEE and SSE.
If you previously had installed a local Oracle 11gR2 database for the Development Client and you are reinstalling the Development Client, you do not have to deinstall the database first. However, if you need to reinstall the OEE or SSE database for some reason, follow the instructions in the appropriate section of this guide entitled: Chapter 4, "Installing the Local Database."
If you need to install the OEE database and the Microsoft Windows environment variable ORACLE_HOME exists, the OEE installer will delete it during the installation.