You should complete the tasks in this chapter before you begin the actual installation process. This chapter contains the following topics:
Certain minimum hardware and software requirements must be met to run Release 9.1 on various operating systems and servers. Verify that the Deployment Server, Enterprise Servers, and workstations meet the hardware and software requirements.
Because the software and hardware requirements change rapidly as manufacturers constantly update their products, requirements are not provided in this documentation. Refer to Section 1.3, "Certifications (Formerly Known as Minimum Technical Requirements)" in this guide.
Note:Make sure that you have taken and installed the latest Planner ESU from the Update Center on My Oracle Support. Failing to do so may prevent proper installation of the software.
Additionally, a new compiler requirement is added for Release 9.1. Before installing the Deployment Server, you should install a Microsoft Visual C++ compiler on it. The MTRs list supported C++ compilers on Microsoft Windows-based machines. Refer to Certifications (Formerly Known as Minimum Technical Requirements) in this guide.
The amount of disk space you need for Release 9.1 software on the Deployment Server and OVS Host depends on many variables. In general, this release of OVM requires three times the base space requirement for each EnterpriseOne component. Configuring disk space is covered in this guide. Up-to-date disk space requirements for JD Edwards EnterpriseOne components are listed in the Release 9.1 Minimum Technical Requirements. Refer to Certifications (Formerly Known as Minimum Technical Requirements).
Note:While the disk space tables accurately represent the disk space requirements, the actual requirements for an installation will be three times greater due to the requirement for temporary space.
The Oracle JD Edwards EnterpriseOne Application requires that Virtual Machine hostnames are not fully qualified with domain names. With the exception of the Enterprise Server, a maximum of 15 character mixed case alphanumeric name is allowed for names of these JD Edwards EnterpriseOne Servers:
Enterprise Server (exception maximum of 13 characters)
BI Publisher Server
These names should correctly resolve using the local DNS. The configuration of these items is the responsibility of the local network and system administrators.
The Oracle database users created for your JD Edwards EnterpriseOne Database Server have been set up with the default passwords (for example, JDE user has JDE for the password). You should change the passwords for the Oracle database users within the Oracle DBMS.
A minimal JD Edwards EnterpriseOne security definition has been shipped with your Database Server. Follow the instructions in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix to change the passwords within EnterpriseOne for JDE, DV910, PS910, and PY910 so they match any changes you make to the passwords for the Oracle Database users.
One of the purposes of the following flow chart is to help you determine which processes can be done in parallel. Because the Deployment Server installation is the most time consuming installation in the entire process, the reason for having the Change Assistant and Server Manager installations at the beginning of the flow is so that after they installed you could be using those tools while the Deployment Server installation is running. That is, if applicable to your implementation, you could be using Change Assistant to download ESUs and software components and you could be deploying software components (such as Tools Releases) using Server Manager while the Deployment Server installer is running.
While there is no dependency between the steps shown in flow chart, you cannot run more than one installation (Change Assistant, Server Manager, and Deployment Server) at the same time on the same machine.
The following diagram (which spans two pages) illustrates the overall process flow for the entire JD Edwards EnterpriseOne installation process using Oracle VM templates.
Process Flow - Deployment Server and Foundation Servers (Part 1 of 2)
Process Flow - Optional Servers (Part 2 of 2)