Release 8.12 resides on an Intel Pentium-based Deployment Server running Microsoft Windows. The software install and upgrade programs enable you to create and maintain installation plans and deploy Release 8.12 to the Enterprise Servers and workstations. The installation program loads the software on the Deployment Server, in- stalls the MSDE database, and then loads Planner and Workbench tables into the MSDE database on the Deploy- ment Server.
Note
Alternatively, you can choose to replace MSDE with SQL Server as your repository on the Deployment Server. In that case, refer toAccessing Minimum Technical Requirementsfor specific versions of SQL Server and other requisite software, especially the SQL Native Client which is a unique requirement for SQL Server 2005. If you choose to use SQL Server, you must meet the MTRs prior to running the De- ployment Server installer.
Tip
The InstallShield process creates temporary files during the install. By default these are placed on the c: drive of your Windows-based Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. Alternately, you can redirect these temporary files to a different drive with more space by using this procedure to change the Environment Variables for the logged in user:
1. Create a new empty folder on the drive that has more room. For example, the drive and folder might bed:\ISMPTemp.
2. Right click on My Computer then choose Properties | Advanced | Environment Variables. 3. Scroll through the variables in the top pane (User) and find TEMP and TMP.
Mandatory PATH Environment Variable Change
If you do not have MSDE, or SQL Server, or SQL Server 2005 currently installed on the Deployment Server, the Deployment Server install will install MSDE. During the Deployment Server install, it in- stalls MSDE then immediately attempts to use it to attach the shipped MSDE databases. This will only work if the path to the MSDE code is defined before the Deployment Server install is run. Note that the MSDE install has the location hard coded:
C:\Program Files\Microsoft SQL Server To modify the PATH environment variable:
1. On the Deployment Server, right click on My Computer. 2. Click on Properties | Advanced | Environment Variables.
3. Click on PATH in the bottom pane and add to the end of the existing value:
;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
This table lists the mandatory and optional components of the Deployment Server installation.
Server Mandatory Component Optional Components
Deployment Server JD Edwards EnterpriseOne files Production environment Prototype environment Development environment Pristine environment
The installation process for the Deployment Server performs these functions:
• Installs the objects from the CDs.
• Creates the path code directory structures (such as PS812 and PD812) based on your selections. • Updates the Microsoft Windows Registry.
Note
You can run the Deployment Server and the Platform Pack installation concurrently (assuming the in- stallation programs are run on different machines).
After verifying the support structure, you can install the Deployment Server. This process installs the Deploy- ment Server from CDs.
Note
Prerequisites
Before you run the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). You can restart these programs after you finish installing the Deployment Server.
The diagram below illustrates the process flow and the various installation paths.
To install the Deployment Server:
1. Log on to the Deployment Server as a user with Administrator rights.
Warning
Ensure that the Administrator account name that you use does not contain any special characters. 2. Insert the first Deployment Server CD into the CD drive.
The setup starts automatically.
If the setup does not begin automatically or if you wish to start the installation manually, you can execute theRunInstall.exefile which is located at the root of the installation disk. TheRunInstall.exe (which is called by theautorun.inf) enables the JD Edwards EnterpriseOne Deployment Server In- staller to detect the drive with the most available space and to use it as the default drive for the installation. If you directly execute the Deployment Server installation program (setupwin32.exe) then the JD Ed- wards EnterpriseOne Deployment Server Installer will not scan available drives for disk space and you must have adequate space on your c: drive which will be the assumed default drive.
Note
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards En- terpriseOne Deployment Server Installer. Although this may take a few minutes to completely ini- tialize, you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne De- ployment Server Installer window is displayed.
3. On JD Edwards | EnterpriseOne Deployment Server Installer, Welcome, click Next.
4. On JD Edwards | EnterpriseOne Deployment Server Installer, License Validation Panel, complete these fields:
Expiration Date Enter the date on which Release 8.12 software expires.
This date should default into the SPC generator program as 1/1/2899. For a discussion on obtaining and using the license key generator program, refer toRevalidating the Deployment Serverin the chapter of this guide en- titled:Installation Utilities.
Number of Licenses Enter the number of licenses.
Note
This number should be less than 5000 in order to avoid potential per- formance impact. For additional details, refer toRevalidating the Deployment Serverin the chapter of this guide entitled:Installation Utilities.
Authorization Code Enter the codes that were generated by the SPC generator program. For a discussion on obtaining and using the license key generator program, rRefer toRevalidating the Deployment Serverin the chapter of this guide en- titled:Installation Utilities.
Caution
Each time the setup program is run, the serial number changes, which requires a new JD Edwards EnterpriseOne authorization code. Avoid stopping and rerunning the installation program after ob- taining an authorization code.
6. On JD Edwards | EnterpriseOne Deployment Server Installer, directory selection panel, complete this field: Directory Name Enter the drive and directory where you want the files installed on your Deploy-
ment Server. The JD Edwards EnterpriseOne Deployment Server Installer auto- matically scans all drives for available space and by default chooses the drive that contains the most available space. For example:z:\JDEdwards\E812
7. Click Next.
8. On JD Edwards | EnterpriseOne Deployment Server Installer, setup type panel, choose your installation type:
Typical Recommended for most users, choose this setup type if you wish to complete the De- ployment Server installation with no further specifications. This installation option in- cludes the required JD Edwards EnterpriseOne files for the Prototype and Pristine envir- onments.
Tip
If you choose Typical installation, you can skip directly to step11located later in this task to complete the Deployment Server installation.
Custom Recommended for experienced users, choose this setup type if you wish to complete the Deployment Server installation by specifying the installation of a subset of pre-defined environments.
9. If you chose Custom Mode on the previous panel, on JD Edwards |EnterpriseOne Deployment Server In- staller, feature selection panel, select the features you want to install:
• JD Edwards EnterpriseOne Files
Note
This selection includes mandatory system files. If you do not select this box and the JD Ed- wards EnterpriseOne Deployment Server Installer can not detect the required system files, it se- lects them automatically and displays a warning message. On the warning message, you must either select OK to acknowledge that the selection of the mandatory system files, or click Back and change your selections manually. Likewise, if you re-run the JD Edwards EnterpriseOne Deployment Server Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne files. • Production Environment • Prototype Environment • Development Environment • Pristine Environment 10. Click Next.
11. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information panel, verify that the appropriate components are selected.
If there is insufficient disk space to complete the installation is available on the Deployment Server target machine, an error message is displayed.
12. Click Next to begin the Installation.
The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation.
On JD Edwards | EnterpriseOne Deployment Server Installer, after the installation is complete, a message appears stating that the installation was successful.
13. Click Finish to complete the installation and exit the JD Edwards | EnterpriseOne Deployment Server In- staller.
Note
After the JD Edwards EnterpriseOne Deployment Server Installer is complete, a panel may appear directing you to reboot the machine to complete the installation. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Therefore, in such cases the installation cannot be completed until the machine is rebooted.
You should review the log file created by the Deployment Server Installer. The file is named log.txt and is located in the Deployment Server installation directory. For example:
x:\JDEdwards\E812\log.txt