2 Before You Begin the Installation

You should complete the tasks in this chapter before you begin the actual installation process.

This chapter discusses:

2.1 Verifying Software and Hardware Requirements

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.1, "Accessing Minimum Technical Requirements (Certifications)".

Note:

Make sure that you have taken and installed the latest Planner Update ESU from the Oracle JD Edwards Update Center. Failing to do so may prevent proper installation of the software.

Additionally, a new compiler requirement is added for Release 9.1. Before you run the Deployment Server or Platform Pack installer, you should install a Microsoft Visual C++ compiler on any machine on which the installer will be run. The MTRs list supported C++ compilers on Microsoft Windows-based machines. Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)"

2.2 Verifying the Disk Space Requirements

The amount of disk space you need for Release 9.1 software on the Deployment Server and Enterprise Server depends on many variables according to platform and database. For the Deployment Server, all disk space must be available on one drive except if you use the Remote Share option. With the Remote Share option, there must be enough room on one remote share for all the path codes. For Enterprise Server installation, multiple foundations during the install are not supported. There must be enough space on one disk drive for all logic components.

After you have completed an installation, you can manually relocate some components of the Enterprise Server on different drives, such as printqueue location, build areas, package location, and BI-Publisher storage. Additionally, when using multiple foundations it is possible to use different drives for each set of JD Edwards EnterpriseOne pathcodes. However, it is important to note that for purposes of the initial installation, having the correct amount of space available, but not on a single drive, is not adequate. Up-to-date disk space requirements are listed in the Release 9.1 Minimum Technical Requirements. Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)".

Note:

While the disk space tables accurately represent the disk space requirements, the actual requirements for an installation will be greater due to the requirement for temporary space.

2.3 SQL Server 2012 Requirements for FASTFIRSTROW

Previous to Microsoft SQL Server 2012, the database supported an internal function called FASTFIRSTROW, which by default is used by JD Edwards EnterpriseOne. However, that functionality is no longer supported in SQL Server 2012. Therefore, users running SQL Server 2012 must manually change the jde.ini file settings on their database server to disable this functionality. Otherwise, you cannot delete any object or perform certain database specific operations.

It is recommended that you use Server Manager to change the following setting in the jde.ini file on your Enterprise Server:

[DB SYSTEM SETTINGS]
FASTFIRSTROW = N