5 Installing the Oracle Local Database

Complete this chapter to install the local Oracle Enterprise Edition (OEE) database that the Development Client will use.

If you encounter errors during the installation process, refer to these troubleshooting chapters:

Caution:

It is very important that no files exist in the E1Local subdirectory when you attempt to install the OEE database. If any files do exist, the OEE installation will probably fail.

Caution:

Be sure to follow the guidelines in the preceding sections of this guide entitled:

If you have not already installed the database engine and a database called E1Local does not exist on your Development Client, use the procedures in this section to install these requisite components before installing the JD Edwards EnterpriseOne Development Client. If the local database engine is already installed and an E1Local database exists, you can skip this chapter.

Caution:

You can run the JD Edwards EnterpriseOne program InstallManager to install the local database into any location. However it is strongly recommended that you not choose a directory that contains space characters in the directory name. Avoiding such directory names will avoid the possibility of issues arising later due to known issues with such directory names.

Note:

For instructions on launching InstallManager to install the local Oracle database with default parameters, refer to the section entitled: Section 5.2, "Using InstallManager to Install a Local Database".

For instructions on manually launching the OEE12Setup.exe program to install the local Oracle database with optional parameters, refer to the appendix of this guide entitled: Appendix A, "Running OEE12Setup.exe from the Command Line".

This section discusses these topics:

5.1 Oracle Database 12c Considerations

Starting with Oracle Database 12c, Oracle supports the use of an Oracle Home User who will own the install of the database. This user must not have Microsoft Windows Administrator (admin) rights. Note that in this context, the user is the local Microsoft Windows user, not a database user.

Caution:

Do not install the Oracle Database 12c into an existing Oracle Base directory. For example, do not install into this directory if it already exists:

C:\Oracle

If you attempt to install to an existing Oracle directory, the OEE12Setup.exe installer will likely fail. Later releases of this installer may be able to programmatically resolve this issue.

This section discusses these topics:

5.1.1 Prerequisites to Running the OEE12Setup.exe Program

Tools Release 9.2.2 Considerations. The OUI installer delivered by Tools Release 9.2.2 is upgraded to a newer version of OUI itself. You may encounter issues if you use a newer version installer to install a package on an existing Development Client installation that used the older version installer. Although not required, Oracle highly recommends that the older Development Client installation either be uninstalled or saved using Snapshot before running a new installer. Furthermore the new installer for 9.2.2 requires an uplift to the latest JRE/JDK as listed in the Oracle Certifications for the Development Client.

The OEE12Setup.exe program is used to install the local Oracle 12c database. This program is called from the InstallManager program when you click on this link:

EnterpriseOne Database Engine

Optionally you can also manually launch the OEE12Setup.exe program to perform optional functions. In either case (InstallManager or manually), prior to running the OEE12Setup.exe program, ensure that this Microsoft Windows system variable either does not exist, or if it does that it points to a valid JDK:

JAVA_HOME

Otherwise, the OEE12Setup.exe program will fail to execute and return an error stating the JDK is invalid.

Note:

For instructions on launching InstallManager to install the local Oracle database with default parameters, refer to the section entitled: Section 5.2, "Using InstallManager to Install a Local Database".

For instructions on manually launching the OEE12Setup.exe program to install the local Oracle database with optional parameters, refer to the appendix of this guide entitled: Appendix A, "Running OEE12Setup.exe from the Command Line".

5.1.2 Specifying the Oracle Home User and Oracle Base Directory

When you launch the OEE12Setup.exe program with no switches (this is the default operation when launched from the link on InstallManager) an OEE12Setup GUI is displayed prompting for Oracle Home User login and Oracle Base Directory information. This data entry GUI is also displayed when OEE12Setup.exe is run with certain combinations of command line switches as described in the appendix of this guide entitled: Appendix A, "Running OEE12Setup.exe from the Command Line".

5.1.3 Manually Creating Oracle Home User

If you cannot use the OEE12Setup.exe program to create the Oracle Home User, you can create the user manually using the steps described in this section.

To create a Microsoft Windows user, launch Local Users and Groups management console using this navigation:

Control Panel > Administrative Tools > Computer Management > System Tools > Local Users and Groups

Surrounding text describes create_oracle_user_1.gif.
  1. On Local Users and Groups (Local)\Users, in the left pane, select Users.

  2. Right click and select New User.

    Surrounding text describes new_user.gif.
  3. On New User, complete these fields:

    • User name:

      Enter a name for the user. For example, e1dbuser.

    • Password and Confirm Password

      Enter and confirm the password for the user.

    • Ensure this checkbox is not checked:

      User must change password at next logon

  4. Click the Create button.

5.2 Using InstallManager to Install a Local Database

In most cases, your JD Edwards EnterpriseOne administrator will have already downloaded and prepared the local database installer for you to install on your Development Client. If so, the administrator should be able to provide you with the location of InstallManager.exe. In that case, in the following procedure you can skip to Step 4. If not, start with Step 1.

  1. Obtain the appropriate disk images from Oracle Software Delivery Cloud for the local database you wish to install on your Development Client.

  2. Log on to the Development Client as a user with Administrator rights.

    Caution:

    Ensure that the Administrator account name that you use does not contain any special characters.
  3. If you have not already done so, expand all disk images to be under a common directory called Disk1 on your Development Client.

  4. Right-click on the InstallManager.exe program (either in Disk1 or on your Deployment Server) and select Run as Administrator.

    Caution:

    For Microsoft Windows, you must right-click on the executable and select Run as Administrator from the drop-down. Likewise, if you have a shortcut assigned to InstallManager.exe, you must either configure the shortcut to always run as administrator or right click the shortcut and choose Run as Administrator.
    Surrounding text describes install_manager.gif.
  5. On JD Edwards Install Manager, select this link to install the local OEE database:

    EnterpriseOne Database Engine

    Surrounding text describes oee12setup_inst_man.gif.
  6. On User Account Control, click the Yes button to launch the OEE12Setup.exe installer.

    Surrounding text describes install_man_security_warn.gif.
  7. If you receive an Install Manager - Security warning dialog with the message "The publisher could not be verified", click the Run button to continue the execution of the OEE12Setup.exe program to install the local Oracle database.

    Surrounding text describes oee_setup_ora_user.gif.
  8. On OEE12Setup, in the Oracle Home User section, you must select an Oracle Home User. For security purposes, Oracle recommends that you specify a standard Windows user account (that is, an account that is not in the Administrator group of the computer). The OEE12Setup.exe program will not allow you to specify an account that has Administrator privileges. Valid choices are:

    • Use existing Windows User

      Choose this option if you want to use an existing account for a Windows user. This user must not have Administrator privileges. You must specify a valid User Name and associated Password for the user.

      For instructions on how to manually create an Oracle Home User, refer to the section entitled: Section 5.1.3, "Manually Creating Oracle Home User".

    • Create New Windows User

      Choose this option if you want OEE12Setup.exe to create an account for a Windows user without Administrator privileges. You must specify a valid User Name and associated Password and Confirm Password for the user. Be sure to record and remember this password.

      Note:

      OEE12Setup Fails to Create the User. If the OEE12Setup.exe program fails to create the user it might be because the password does not meet the password complexity policy requirements of your computer. You can try again with a more complex password, or exit. If you are unable to create the user using the OEE12Setup.exe interface, you should try to create it manually and rerun OEE12Setup.exe. Refer to the next section entitled: Section 5.1.3, "Manually Creating Oracle Home User".

      Tip:

      Password Complexity Policy. The Administrator user of the Microsoft Windows machine determines the password complexity policy for each machine. Additionally, such policies vary according to the server or client version of Microsoft Windows. The OEE12Setup.exe program cannot programmatically determine and return these policy requirements. Therefore it is beyond the scope of this documentation to guide the end user to determine the exact policy requirements for user names and their associated passwords.
    • Use Windows Built-in Account

      This selection is equivalent to legacy JD Edwards EnterpriseOne functionality for releases prior to Tools Release 9.2.

      Caution:

      For strongest security, Oracle recommends that you do not use the Windows built-in user account. To provide optimal security, you should install and configure with a Windows User Account with limited privileges. For additional details on the Oracle policy regarding Supporting Oracle Home User on Windows, refer to this link:

      http://docs.oracle.com/database/121/NTQRF/oh_usr.htm

      If you choose this selection, you are presented with the following dialog where you must confirm that you understand the security impact of this selection.

      Surrounding text describes oee_setup_builtin_confirm.gif.

      Click the Yes button to confirm and continue, or the No button to exit the OEE12Setup.exe program.

  9. On OEESetup, in the Oracle Base Directory section, enter the path where you want to install the local Oracle database. It is recommended that you install the Oracle database into its own root directory and not into any other Oracle base directory used by another Oracle product, such as c:\ORACLE. If you accept the default location (which is c:\Oracle), some auxiliary files are installed in that location while the local Oracle database itself will be installed in the location you specified, such as:

    C:\E1Local

    Caution:

    Do not install the Oracle Database 12c into an existing Oracle Base directory. For example, do not install into this directory if it already exists:

    C:\Oracle

    If you attempt to install to an existing Oracle directory, the OEE12Setup.exe installer will likely fail. Later releases of this installer may be able to programmatically resolve this issue.

    Caution:

    Do not include the string E1Local in the path. For example, if you specified C:\Oracle\E1Local as the base install path, the local Oracle database will be installed in this location:

    C:\Oracle\E1Local\E1Local

  10. On OEE12Setup, click the OK button to accept the selected values. If the values are valid the OEE12Setup.exe program proceeds to install the local Oracle database.

Caution:

You must reboot your machine before continuing with the installation of the JD Edwards EnterpriseOne Development Client as described in the section in this guide entitled: Chapter 7, "Installing the Development Client and Web Client Features (WLSH4A and WASH4A)".