JD Edwards EnterpriseOne

Express Installation Guide

Applications Release 9.0 Update with Tools Release 8.98.4.1 for IBM i on Power Systems

E21612-01

March 2012

JD Edwards EnterpriseOne Express Installation Guide, Applications Release 9.0 Update with Tools Release 8.98.4.1 for IBM i on Power Systems

E21612-01

Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Understanding JD Edwards EnterpriseOne and IBM i

- 1.1 Understanding This Guide

- 1.2 Understanding the Installation Process

- 1.2.1 Understanding the Deployment Server Installation

- 1.2.2 Understanding the installation of the Enterprise, Database and HTML Web Server on IBM i

- 1.2.3 Understanding the Development Client Installation

- 1.3 Accessing Minimum Technical Requirements

- 1.4 Working With the Customer Checklist

- 1.5 Working With the Pre-Install Worksheet

- 1.6 Environments Overview

2 Before Beginning the Installation

- 2.1 Verifying Software and Hardware Requirements

- 2.2 Verifying the Disk Space Requirements

- 2.3 Security Considerations

- 2.4 Overall Process Flow

3 Working with the Deployment Server

- 3.1 Understanding the Deployment Server

- 3.1.1 Local Oracle Enterprise Edition (OEE) Considerations

- 3.2 Before Installing the Deployment Server

- 3.3 Installing the Deployment Server

- 3.4 Downloading and Installing the Latest Software Updates (optional)

- 3.4.1 Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server

- 3.4.2 Installing the Latest Planner Update

- 3.5 tnsnames.ora File Location

- 3.6 Rebooting the Deployment Server

- 3.7 Configuring the Planner Databases

4 Working with Express Installation for IBM i for JD Edwards EnterpriseOne

- 4.1 Completing the Pre-Install Worksheet

- 4.2 Adding an Entry to the Remote Database Directory

- 4.3 IBM i Express Installation Image System Changes

- 4.4 Update the IBM i TCP/IP Host Table with Deployment Server Information

- 4.5 Testing Long File Names on the IBM i

- 4.6 Rebuilding Cross Reference Tables on the IBM i

- 4.7 Adding a New Entry to the QAQQINI File

- 4.8 Setting Up a Network Share for iSeries Root

- 4.9 Obtaining and Preparing the IBM i Express Installation Image

- 4.10 Copying IBM i Java Utilities into the Express Installation Image

- 4.11 Installing Microsoft Windows Visual Studio

- 4.12 Running the Express Installation for IBM i

- 4.13 Understanding the IBM i HTTP, HTML, and Server Manager Agent Components Installation

- 4.14 Reinvoking the IBM i HTTP, HTML, and Server Manager Agent Components Installation Process

- 4.15 Troubleshooting Express Installation for IBM i

- 4.16 Post Installation Step

- 4.17 Starting the Server Manager Agent

- 4.18 Optional Steps - Enterprise Server

5 Working With the Enterprise Server

- 5.1 Starting and Shutting Down Network Services on the Enterprise Server

- 5.2 Verifying the Release 9.0 Enterprise Server Installation Using PORTTEST

6 Starting the HTML Server

7 Testing the JD Edwards HTML Web Server Connection

8 Installing the Workstations for Developers and System Administrators

- 8.1 Overview of Workstation Installation

- 8.2 Preparing for Workstation Installation

- 8.3 Copying the Configured tnsnames.ora File

- 8.4 Copying the JDBC drivers to the Client Install Directory

- 8.5 Copying the JDK to the Deployment Server

- 8.6 Working With Workstation Installation

- 8.6.1 Creating a Desktop Shortcut

- 8.6.2 Using a Shared Drive

- 8.6.3 Understanding Third-Party Products

- 8.7 Understanding Third-Party Products

- 8.8 Working with the Workstation JDE.INI on the Deployment Server

- 8.8.1 Understanding the Workstation JDE.INI on the Deployment Server

- 8.8.2 Modifying the Workstation JDE.INI on the Deployment Server

9 Next Steps

10 Uninstalling the Software

- 10.1 Understanding the Uninstallation Process

- 10.2 Uninstalling the Software from the Workstations

- 10.3 Uninstalling the Deployment Server

- 10.4 Deinstalling the IBM i Server

- 10.5 Uninstalling the IBM i Delivered HTTP, HTML, and Server Manager Agent Components

Preface

Welcome to the JD Edwards EnterpriseOne Express Installation Guide.

Audience

This document is intended for implementers and administrators who are responsible for performing an express JD Edwards EnterpriseOne installation.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the Server Manager Guide.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Understanding JD Edwards EnterpriseOne and IBM i

This chapter contains the following topics:

- Section 1.1, "Understanding This Guide"

- Section 1.2, "Understanding the Installation Process"

- Section 1.3, "Accessing Minimum Technical Requirements"

- Section 1.4, "Working With the Customer Checklist"

- Section 1.5, "Working With the Pre-Install Worksheet"

- Section 1.6, "Environments Overview"

1.1 Understanding This Guide

This guide is designed to direct you through a basic JD Edwards EnterpriseOne installation using the Oracle JD Edwards Express Installation disk images and a special Platform Pack installer for IBM i on POWER System (hereafter in this guide referred to as IBM i) which delivers the Platform Pack, Server Manager Agent and HTML Server.

Note:
Always check My Oracle Support (MOS) for updates to this document. Generally, this document is republished in its entirety only for the next major applications release of JD Edwards EnterpriseOne. This Express Installation document can be located on MOS by using the link provided in this Documentation Overview document: IBM i Express Installation for JD Edwards EnterpriseOne Documentation Overview (Doc ID 1288002.1) https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1288002.1

Important:
The JD Edwards EnterpriseOne Express Installation solution for IBM i must be installed on a POWER System or POWER System LPAR (logical partition) which does not already have JD Edwards EnterpriseOne components. Common JD Edwards EnterpriseOne components include but are not limited to JD Edwards EnterpriseOne libraries, IFS folders, and OW Journals.

This guide contains only the procedures required for a standard installation with all standard environments and databases. Additional components may be added after the Express Installation by following procedures in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries, which is available in this document on My Oracle Support (MOS):

JD Edwards EnterpriseOne Applications Release 9.0 Installation Guides, Update (Doc ID 705463.1)

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=705463.1

In the above MOS document, locate and download this attachment:

9.0_install_as400.pdf

Important:
The instructions in the JD Edwards EnterpriseOne installation guide for IBM assume that the IBM i host has IBM WebSphere 7.0 Express Edition installed using the default installation path along with other relevant MTRs. See Section 4.8, "Setting Up a Network Share for iSeries Root" in this document for instructions regarding sharing the root folder. This is a requirement if following the IBM i host IBM WebSphere 7.0 installation guide to the letter.

For instructions on using IBM WebSphere 7.0 with JD Edwards EnterpriseOne, refer to the MOS document entitled:

JD Edwards EnterpriseOne Tools 8.98 Update 3 IBM WebSphere Application Server 7.0 Certification (Doc ID 1086578.1)

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1086578.1

In the above MOS document, locate and download this attachment:

8.98.3_HTML_Web_Server_Reference_Guide_WAS70_IBMi.pdf

Review the Oracle JD Edwards EnterpriseOne Express Installation Minimum Technical Requirements (MTRs) for specific details. Then follow the HTML Web Server guide to install IBM WebSphere 7.0 Express with the currently supported Fixpack and/or iFixes as specified in the MTRs.

When installing IBM WebSphere 7.0, this default install path must be used or the installation and configuration will fail:

/QIBM/ProdData/WebSphere/AppServer/V7/Express

This guide is designed for management information system (MIS) managers and installers. It outlines the procedures for installing Release 9.0. To successfully install Release 9.0, a rudimentary understanding of the following is required:

- Hardware and software requirements

- Database setup and management

- Enterprise platforms and operating systems

At a minimum, review these guides before beginning:

- JD Edwards EnterpriseOne Tools Foundation Guide

- JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide

- JD Edwards EnterpriseOne Tools System Administration Guide

- JD Edwards EnterpriseOne Tools Package Management Guide

- JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide

- JD Edwards EnterpriseOne Tools Security Administration Guide

In addition, it is recommended to complete the IBM i database product courses provided by IBM.

1.2 Understanding the Installation Process

This documentation explains how to install Release 9.0 software using this five (5) step installation process:

- Install Change Assistant

Note:
The Change Assistant install download is available on My Oracle Support on the Electronic Software Updates page at this link:
https://jde.oracle.com/softwaredownloads/home/content/documents/ChangeAssistant.html

- Install the Deployment Server (see below for concurrent operations)

- Install the Enterprise, Database and HTML Server on a single IBM i machine.

Note:
For Release 9.0, the current terminology and that used in this guide is to refer to the Java Application Server (JAS) machine running the JD Edwards EnterpriseOne HTML Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.

- Install Server Manager.

Note:
Download Server Manager from http://edelivery.oracle.com/ and follow the installation instructions in the JD Edwards EnterpriseOne Server Manager Guide. This installation process assumes that Server Manager has been installed on the Deployment Server. The control files for the IBM i Server Manager Agents are updated to reference the Deployment Server.

- Install the workstations for developers and system administrators

Note:
The installer for IBM i runs on a Windows machine. It is strongly recommended that this installer executes on the Deployment Server as the Oracle Universal Installer (OUI) inventory will be stored on the Windows machine used to perform the install.

Both the Express Installation Deployment Server and the IBM i Express Installation contain a complete install of the four standard environments (PS900, PY900, PD900 and DV900) - with ESUs applied. This greatly reduces the overall install time for the server.

See Also:

- "Understanding Typical Customer Configurations" in the JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide for more information about the typical customer configuration provided with Release 9.0.

1.2.1 Understanding the Deployment Server Installation

The Deployment Server is the focus of the Release 9.0 installation process. The installation program for the Deployment Server copies the Release 9.0 software and a language, if applicable, from the disk images to the Deployment Server. From the Deployment Server, the Release 9.0 software is distributed to one or more workstations. When running the Installer for the IBM i Platform Pack on the Deployment Server, these two installs need to be run sequentially. They cannot be run concurrently.

The Deployment Server installation program updates the Microsoft Windows registry with information about the Release 9.0 installation and languages, if applicable.

For more information on Language support, see the "Language Process Overview" section in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries.

1.2.2 Understanding the installation of the Enterprise, Database and HTML Web Server on IBM i

The Express Installation for IBM i completely installs of these four standard environments:

- PS900

- PY900

- PD900

- DV900

The Express Installation for IBM i also completely installs the HTML Web Server with four standard environments. The installer for the IBM i updates the database tables and control files on the server with your IBM i machine name.

1.2.3 Understanding the Development Client Installation

The Development Client is installed on the workstations from the Deployment Server. The Development Client is installed on workstations using the Workstation Installation program. During the installation, a stand-alone Microsoft Windows application reads the deployment preferences information from the JD Edwards EnterpriseOne system tables to drive the workstation installation process.

1.3 Accessing Minimum Technical Requirements

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Minimum Technical Requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.http://www.oracle.com/corporate/contracts/index.htmlAccess the current Minimum Technical Requirements (MTR) for the JD Edwards EnterpriseOne products from My Oracle Support:

JD Edwards EnterpriseOne Current MTR Index (Doc ID 747323.1)

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=747323.1

1.4 Working With the Customer Checklist

The Release 9.0 support structure consists of components such as databases, operating systems, and hardware. To install Release 9.0 successfully, set up the support structure before starting the installation process.

The tasks in this section are designed to prepare the customer's system for the installation process. Some of the tasks, such as checking that the appropriate hardware and software are available, can take some time to complete. Other tasks are quick and easy.

This checklist helps to organize the required upgrade preparation:

- Review the Section called Environments Overview.

- Assess the network.

- Verify that the Deployment Server hardware and software meet minimum technical requirements.

- Verify that the IBM i hardware and software meet minimum technical requirements.

- Verify that the workstation hardware and software meet minimum technical requirements.

- Verify that the Deployment Server disk space meets minimum technical requirements.

- Verify that the host disk space meets minimum technical requirements.

1.5 Working With the Pre-Install Worksheet

A Pre-Install Worksheet is provided in Section 4.1, "Completing the Pre-Install Worksheet" to gather information about your planned installation prior to running the IBM i Express Installation. Using this worksheet decreases the chances for data entry errors and makes for a documented and repeatable process. Since the scripts used to update the database and control files on the IBM i host are designed to execute only once, incorrect deployment will necessitate deinstalling and reinstalling the IBM i Express Installation.

1.6 Environments Overview

The HTML Web Server (J) environments have the same mappings as the regular environments with the exception of logic, all of which is mapped to run on the Enterprise Server.

Each environment shipped with Release 9.0 has a specific use. For more detail, refer to these sections in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries:

- Understanding Environments

- Planner Environment (JDEPLAN)

- Pristine Environment (PS900)

- Deployment Environment (DEP900)

- Prototype Environment (PY900)

- Production Environment (PD900)

- Development Environment (DV900)

- Additional Considerations

See Also:
JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries, which is available in this document on My Oracle Support:
JD Edwards EnterpriseOne Applications Release 9.0 Installation Guides, Update (Doc ID 705463.1)

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocID=705463.1&from=BOOKMARK&bmDocDsrc=KB&viewingMode=1143))

2 Before Beginning the Installation

Complete the tasks in this chapter before beginning the actual installation.

This chapter contains the following topics:

- Section 2.1, "Verifying Software and Hardware Requirements"

- Section 2.2, "Verifying the Disk Space Requirements"

- Section 2.3, "Security Considerations"

- Section 2.4, "Overall Process Flow"

2.1 Verifying Software and Hardware Requirements

Certain minimum hardware and software requirements must be met to run Release 9.0 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, "Accessing Minimum Technical Requirements" in this guide.

Note:
The Oracle Universal Installer (OUI) for IBM i uses Visual Studio/2008 RunTime. Install VS2008SP1 Run Time before running the Installer. Refer to the section of this guide entitled: Section 4.11, "Installing Microsoft Windows Visual Studio".

Additionally, a new compiler requirement is added for Release 9.0. Before installing the Deployment Server, a Microsoft Visual Studio C++ compiler must be installed. The MTRs list supported C++ compilers on Microsoft Windows-based machines. Refer to Section 1.3, "Accessing Minimum Technical Requirements" in this guide.

2.2 Verifying the Disk Space Requirements

The amount of disk space required for Release 9.0 software on the Deployment Server and IBM i server depends on many variables. Up-to-date disk space requirements are listed in the Release 9.0 Minimum Technical Requirements. Refer to Section 1.3, "Accessing Minimum Technical Requirements".

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

2.3 Security Considerations

The IBM i users created for the JD Edwards EnterpriseOne IBM i Express Installation have been set up with the default passwords (for example, JDE user has JDE for the password). It is recommended that change the passwords for the system users are changed and the corresponding changes are performed in EnterpriseOne security setup.

A minimal JD Edwards EnterpriseOne security definition has been shipped with the IBM i server. Follow the instructions in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries to change the passwords within EnterpriseOne for JDE, DV900, PD900, PS900 and PY900 so they match the passwords for the system users.

2.4 Overall Process Flow

This diagram illustrates the overall process flow for the entire JD Edwards EnterpriseOne installation process using Express Installation for IBM i.

3 Working with the Deployment Server

This chapter contains the following topics:

- Section 3.1, "Understanding the Deployment Server"

- Section 3.2, "Before Installing the Deployment Server"

- Section 3.3, "Installing the Deployment Server"

- Section 3.4, "Downloading and Installing the Latest Software Updates (optional)"

- Section 3.6, "Rebooting the Deployment Server"

- Section 3.7, "Configuring the Planner Databases"

Important:
If all four standard environments are not installed as recommended, the Tools Accelerator will fail for each environment not installed. However, this does not prevent it from running correctly for each standard environment that was installed.

3.1 Understanding the Deployment Server

Release 9.0 resides on an x86-based Deployment Server running Microsoft Windows. The software install and upgrade programs help create and maintain installation plans and deploy Release 9.0 to the workstations. The installation program loads the software on the Deployment Server, installs a local database, and then loads Planner and Workbench tables into the local database on the Deployment Server.

The local database for the Oracle for JD Edwards EnterpriseOne Express Installation is Oracle Enterprise Edition (OEE). Order and use only the Deployment Server disk images intended for use with the Oracle JD Edwards EnterpriseOne Express Installation.

Note:
There is no migration path between local databases on the Deployment Server. The Deployment Server disk images install a Local Oracle database. The planner databases cannot be migrated to a different local database. No separate end-user licensing is required for installation of the database by the Deployment Server installer. It should be noted, however, that the local OEE database is not a fully functional commercial version of Oracle Enterprise Edition database.

3.1.1 Local Oracle Enterprise Edition (OEE) Considerations

The Deployment Server installation includes the OEE database (version 10.2.0.3) for local use by the Deployment Server. The installation does not include any GUI tools for database administration. By default, the local database can only be accessed through command line entries. However, a free and fully support GUI tool, Oracle SQL Developer, can be used. It is available at this link:

http://www.oracle.com/technology/products/database/sql_developer/index.html

JD Edwards EnterpriseOne Application P96717

Best practices in JD Edwards EnterpriseOne environments are to never directly modify an EnterpriseOne database outside of EnterpriseOne. Therefore a new application, P96717, is provided to perform the following Oracle database actions:

- Import Tablespace

- Export Tablespace

- Create Tablespace

- Drop Tablespace

Best Practices for OEE Performance

Always verify that the Deployment Server machine meets the MTRs (refer to Accessing Minimum Technical Requirements). The local Oracle database performs best on hard drives that are not fragmented or full. Additionally, the following table lists some guidelines for minimum configurations.

Specification

Recommendation

RAM

2 GB minimum

Page File Size

Minimum setting should be two times the amount of memory

Disk Space Usage

When fully loaded, best performance is obtained if the hard drive on the Deployment Server machine has at least 20% free space.

Local Database Name

Ensure that any reference in data sources and .ini files refer to the local database name in the exact mixed case, which is:
E1Local

Failure to use the exact mixed case will lead to decreased performance of JD Edwards EnterpriseOne on the Deployment Server and on Administrative Clients (also called "fat" or Development Clients).

3.2 Before Installing the Deployment Server

The Deployment Server installer process creates temporary files during the install. By default these are placed on the c: drive of the Windows-based Deployment Server. A sizable amount of free space may be required on the c: drive to complete the installation successfully. Alternately, these temporary files can be directed 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 be:

d:\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.

4. Change both of these to point to the folder created on the larger drive in Step 1.

5. This table lists the mandatory and optional components of the Deployment Server installation.

Server

Mandatory Component

Optional Components

Deployment Server

JD Edwards EnterpriseOne files

Prototype environment
Pristine environment

Production environment

Development environment

The installation process for the Deployment Server performs these functions:

- Installs the objects from the disk images.

- Creates the path code directory structures (PS900, PY900, PD900, and DV900) based on the selections made.

- Updates the Microsoft Windows Registry.

After verifying the support structure, install the Deployment Server. This process installs the Deployment Server from disk images.

Note:
The Deployment Server must be installed locally; the Deployment Server cannot be installed from a remote machine.

3.3 Installing the Deployment Server

Note:
Before running the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (e.g., Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). These programs can be restarted after installing the Deployment Server.

The diagram below illustrates the process flow and the various installation paths.

To install the Deployment Server:

1. Install the Deployment Server from images obtained from the Oracle Software Delivery Cloud site.

Note:
Ensure the Administrator account name used does not contain any special characters.

2. To install from images downloaded from the Oracle Software Delivery Cloud site, create a parent download directory on a disk with at least seven (7) GB free space. For example:
c:\DepSvr

3. Download the source disk images for the JD Edwards EnterpriseOne Deployment Server for Oracle VM into the above directory.

4. Create a sub directory for each disk image. For example:

c:\DepSvr\disk1
c:\DepSvr\disk2
c:\DepSvr\disk3

5. Move the disk images into each sub directory as appropriate. Unzip each disk image in place within the sub directory. It is important to preserve the above directory names - disk1, disk2, and so on.
For example:

- Download the first JD Edwards EnterpriseOne Deployment Server for Oracle VM zip file (for example, V21290-01.zip).

- Move the downloaded .zip file into the \disk1 sub directory.

- Extract the .zip file in place.
In this example, the unzip process creates the contents of the \disk1 subdirectory within the parent download directory, as shown below:

c:\DepSvr\disk1

Make sure you do not have this structure:

c:\DepSvr\disk1\disk1

Continue with disk2 and disk3. When all disk images are downloaded and extracted, the directory structure should look similar to:

c:\DepSvr\disk1 c:\DepSvr\disk2

c:\DepSvr\disk3

Locate the RunInstall.exe within the \disk1 subdirectory and double click on this executable to begin the Deployment Server or Enterprise Server installer.

Note:
Windows 2008. If running the installer on a Microsoft Windows Server 2008 machine, right-click on RunInstall.exe and choose the Run As Administrator option. Failing to do this will cause intermittent failures in many EnterpriseOne processes on the Deployment Server, as Microsoft Windows Server 2008 will block some necessary updates to the registry. Choosing Run As Administrator must be done for every JD Edwards EnterpriseOne process run on this machine, including: Starting Change Assistant, Installing Planner Updates, Starting EnterpriseOne, and Running SpecialInstrs.bat in the Planner Update.

As the installer executes, it automatically moves through the directories within the parent download directory until the installation is complete. If the delivered directory names are not found with the expected names and within the same parent download directory, Java exception error messages will be generated and the installation will stop. Therefore it is very important that the download directory matches the above structure.

Note:
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Deployment Server Installer. This may take a few minutes to completely initialize. The progress can be viewed on the InstallShield Wizard dialog that appears on the screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne Deployment Server Installer window is displayed.

6. On the Welcome screen, click the Next button.

7. On the directory selection panel, complete this field:

Field

Description

Directory Name

Enter the drive and directory to install the files on the Deployment Server. The JD Edwards EnterpriseOne Deployment Server Installer automatically scans all drives for available space and by default chooses the drive that contains the most available space. For example:
d:\JDEdwards\E900

8. Click the Next button.

9. On the information advisory screen, review the content and click the Next button.

10. On JD Edwards EnterpriseOne Deployment Server Installer, setup type panel, choose the installation type:

Value

Description

Custom

Choose Custom and select all environments.
Important: The selection of all environments is required to ensure the environments on the Deployment Server exactly matches those that are installed with the Express Installation for IBM i.

Typical

The Typical install only installs the PS900 and PY900 environments.
Important: The Typical install is not recommended because the control data delivered with the IBM i Express Installation references the four standard environments.

11. Click the Next button.

12. On Edwards EnterpriseOne Deployment Server Installer, Select features screen, select EnterpriseOne Files and all environments.

Important:
Select the check boxes for all environments to ensure the environments on your Deployment Server exactly match those that are installed on the IBM i.

13. Click the Next button.

14. On the machine names screen, complete these fields:

Important:
Record the names entered on this screen on the Pre-Install Worksheet, located in Section 4.1, "Completing the Pre-Install Worksheet".

Important:
The Deployment Server Express Installation installer is used for multiple platforms, which is why the comment on the machine names screen above reads '… Usually lower case". For the IBM i platform the server host name is typically UPPER CASE. Use command CFGTCP option 12 to validate the host name of your server.

Field

Description

Location Name

Enter the location to which this Deployment Server applies. The location could be a city, company headquarters, or a division of a company. For example:
Corporate

Important: When running the OUI installer to install the IBM i Platform Pack, you must supply the same values you enter here.

Important: The Location Name value is case-sensitive and a maximum of 15 alphanumeric characters.

Deployment Server

Verify the machine name for your Deployment Server.
Important: The Deployment Server machine name must be defined in UPPER CASE. All machine names (Deployment, Database, HTML, and Enterprise Servers) must be a maximum of 15 characters, as limited by the JD Edwards EnterpriseOne database table and application design.

Database Server

Enter the name of the IBM i machine. For example:
MYISERIES

HTML Server

Enter the same name as above. For example:
MYISERIES

Enterprise Server

Enter the same name as above. For example:
MYISERIES

The machine name must match the network ID, matching case (usually UPPER CASE).

15. Click the Next button.

16. On the summary information panel, verify that the appropriate components are selected.
If there is insufficient disk space available to complete the installation on the Deployment Server target machine, an error message is displayed.

17. Click the Next button 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.

18. On JD Edwards EnterpriseOne Deployment Server Installer, click the Finish button to complete the installation and exit the JD Edwards EnterpriseOne Deployment Server Installer.

Tips:
Deployment Server Log Files. 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\E900\log.txt
Local Oracle Database Installation Failure. Occasionally the install of the local Oracle database fails due to some transient locking or authority problem on the Deployment Server. Review the OEEInstall.log on c:\ and also run the TestPlannerDBs.bat script which is in JDEdwards\E900\planner\data. This script tests the connection to each of the planner databases as well as the local Spec database.

3.4 Downloading and Installing the Latest Software Updates (optional)

Tip:
Tip: This is an optional step. To skip this step you can proceed to the section of this guide entitled: Section 3.5, "tnsnames.ora File Location". The Express Installation is already updated with the latest available Tools Release, ESUs, and Planner ESU available at the time of mastering the product.

Review the Readme document contained in the Express Installation Media Pack download in the Oracle Software Delivery Cloud. This document will identify the mastering cutoff date used for the currently available Express Installation solution.

Download and install the latest Tools Release, Tools Release Patch, and Planner Update from the Update Center on My Oracle Support.

Important:
The order in which the following Tools Release, patch, and updates are applied is very important. Do not deviate from the order below.

This section discusses:

- Section 3.4.1, "Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server"

- Section 3.4.2, "Installing the Latest Planner Update"

3.4.1 Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server

To install the latest tools release and latest tools release patch:

1. From My Oracle Support, download the latest JD Edwards EnterpriseOne Tools Release Patch (for example, 8.98.A1) and Tools Release documentation.

2. Using the Tools Release documentation, install the Tools Release Patch to the Deployment Server.

3.4.2 Installing the Latest Planner Update

Note:
Due to unpredictable timing issues, there is a possibility that at the end of the Deployment Server install, the databases or tablespaces that are needed for the planner environment may not automatically get attached as designed by the Installer. Not only will an unattached database or tablespace cause the installation of the planner update to fail, it will also prohibit signing on to the JDEPLAN environment. Navigate to the directory JDEdwards\E900\planner\data and run this script:
attach_planner.bat

Tip:
To attach the metadata local database, navigate to the Planner\spec directory and run this batch file:
attach_metadata.bat

To install the latest planner update:

1. From My Oracle Support, download the latest planner update for JD Edwards EnterpriseOne Applications Release 9.0 to the Deployment Server.

2. Run the self-extracting executable and follow the on-screen instructions to install the planner update on the Deployment Server.

3. Enter a valid JD Edwards EnterpriseOne user and password in order to initialize the Planner environment.
The shipped values are JDE for the user and JDE for the password.

Note:
The above login screen is displayed so that the Planner Update can update the metadata specifications on the Deployment Server.

4. When the installation finishes, review the information presented on the JD Edwards EnterpriseOne Deployment Server Setup screen to confirm that the installation was successful.
If the folder into which you expanded the Planner Update is empty, run the self-extracting executable (JLnnnnn.exe) again. When the Welcome screen comes up, click on Cancel to quit.

5. Follow the steps in the Special Instructions, which are contained within an HTML file that is shipped with the Planner Update. The special instructions file located in this directory with this file name:
x:\download_directory\planner_update_id\E900SpecialInstructions.htm

where download_directory is the directory where you downloaded the Planner Update.

Important:
Every time a new Planner update is applied, these two processes must be run:

1. SpecialInstrs.bat

2. R98403XB XJDE0002

3.5 tnsnames.ora File Location

The tnsnames.ora file is located in these directories:

..\Oracle\E1Local\NETWORK\ADMIN

..\System\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes

3.6 Rebooting the Deployment Server

The Deployment Server machine must be restarted after installing or deinstalling the local Oracle database, where:

- The Deployment Server install, which includes the OEE local database, should always be done using the JD Edwards EnterpriseOne Deployment Server installer, and

- The uninstall of the Deployment Server should always be done through Microsoft Windows Add/Remove Programs, and

- The deinstall of the OEE local database should be done using the Oracle Universal Installer.

3.7 Configuring the Planner Databases

The install disk images for the Oracle VM Deployment Server, used for the install for IBM i include the Installation Plan created at Oracle. It's not necessary to create and run an Installation Plan for the PS900, PY900, PD900, and DV900 environments. However, there are some steps that normally run during an Installation Plan that must be done on the Deployment Server. An Oracle Tools Accelerator has been provided to do these steps, and must be run subsequent to completing the Express Installation for IBM i, as described in Chapter 4, "Working with Express Installation for IBM i for JD Edwards EnterpriseOne."

1. Install the latest version of Change Assistant if not already done.

2. Set the Preferences in Change Assistant to store and find ESUs in the install location, for example:
c:\JDEdwards\E900\Change Assistant\Downloads\ESUs

1. Copy the IBM i JDBC driver to this folder:
x:\JDEdwards\E900\misc

Refer to the section of this guide entitled: Section 4.10, "Copying IBM i Java Utilities into the Express Installation Image."

2. Locate the jdbj.ini file in this directory:
x:\JDEdwards\E900\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes

3. Edit the jdbj.ini file to uncomment the entry for AS400 in the [JDBj-JDBC DRIVERS] section.

4 Working with Express Installation for IBM i for JD Edwards EnterpriseOne

This chapter contains the following topics:

- Section 4.1, "Completing the Pre-Install Worksheet"

- Section 4.2, "Adding an Entry to the Remote Database Directory"

- Section 4.3, "IBM i Express Installation Image System Changes"

- Section 4.4, "Update the IBM i TCP/IP Host Table with Deployment Server Information"

- Section 4.5, "Testing Long File Names on the IBM i"

- Section 4.6, "Rebuilding Cross Reference Tables on the IBM i"

- Section 4.7, "Adding a New Entry to the QAQQINI File"

- Section 4.8, "Setting Up a Network Share for iSeries Root"

- Section 4.9, "Obtaining and Preparing the IBM i Express Installation Image"

- Section 4.10, "Copying IBM i Java Utilities into the Express Installation Image"

- Section 4.11, "Installing Microsoft Windows Visual Studio"

- Section 4.12, "Running the Express Installation for IBM i"

- Section 4.13, "Understanding the IBM i HTTP, HTML, and Server Manager Agent Components Installation"

- Section 4.14, "Reinvoking the IBM i HTTP, HTML, and Server Manager Agent Components Installation Process"

- Section 4.15, "Troubleshooting Express Installation for IBM i"

- Section 4.16, "Post Installation Step"

- Section 4.17, "Starting the Server Manager Agent"

- Section 4.18, "Optional Steps - Enterprise Server"

4.1 Completing the Pre-Install Worksheet

Use the Pre-Install Worksheet to gather information required to answer the questions prompted by the Platform Pack installer as it executes. Prior to running the Platform Pack installer, complete the Pre-Install Worksheet with the requisite information. Doing so will reduce the potential for errors due to incorrect data entry information.

Note:
Since the scripts are designed to execute only once, incorrect data entry may result in a corrupted install and the need to deinstall and start the install again.

The following image is a depiction of the Pre-Install Worksheet

4.2 Adding an Entry to the Remote Database Directory

Add or verify the entry to the remote database directory by completing these steps:

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter WRKRDBDIRE.

3. Look for an entry on the IBM i for Remote Location *LOCAL. This entry must be identical to the IBM i hostname (CFGTCP Option 12). This includes the hostname's case, which can be upper, or lower, or mixed.

4. If there is no *LOCAL entry, enter 1 in the Option column and type the machine name in the Relational Database column, and press enter. In the Remote Location Name or Address field, enter *LOCAL and press Enter. If there is already a *LOCAL entry and the Relational database name is not the same as the host name (CFGTCP Option 12), remove the entry and add a new entry as previously described.

Note:
In previous JD Edwards EnterpriseOne releases, installation of Vertex required adding an entry to the Remote Database Directory, but no special naming was required. It is possible that in some cases an entry was added with some other naming convention for this purpose. Vertex will work with a Remote Database Directory entry that is correct for Release 9.0.

5. In a case where the relational database directory entry was not changed skip this step. If the entry is corrected, recycle the database host server prestart jobs by issuing these commands:
ENDPJ SBS(QSERVER) PGM(QSYS/QZDAINIT) OPTION(*IMMED)

ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT) OPTION(*IMMED)

ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASSINIT) OPTION(*IMMED)

STRPJ SBS(QSERVER) PGM(QSYS/QZDAINIT)

STRPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT)

STRPJ SBS(QUSRWRK) PGM(QSYS/QZDASSINIT)

Note:
Users will not be able to use JD Edwards EnterpriseOne while these commands are running.

4.3 IBM i Express Installation Image System Changes

The IBM i Express Installation Image installer may make changes to the IBM i system.

1. JD Edwards EnterpriseOne services require that the TCP service *EDRSQL is running. Consequently the IBM i Express Installation Image installer will do the following:

1. Change the TCP service for *EDRSQL to autostart *YES so that it starts when TCP services are started.

2. Start the *EDRSQL Service.

2. Two IBM i system values might be changed. The IBM i Express Installation Image installer verifies these values and makes changes if they are not optimally set.

System Value

Change Value

QJOBMSGQMX

64

QJOBMSGQFL

*PRTWRAP

3. Four job queues will be created with a maximum active job setting of '1' in library QGPL. The job queues are named QBATCH1, QBATCH2, QBATCH3, and QBATCH4. These job queues will be attached to the QBATCH subsystem. If the QBATCH subsystem cannot be found, the job queues will not get created.
The JD Edwards EnterpriseOne table F986130 (application P986130) will contain definitions for the job queues.

4. An output queue named QGPL/ONEWORLD will be created. The JD Edwards EnterpriseOne printer definition (F986163) and default printer configuration (F986167) tables will contain a definition targeting this output queue.

5. The PATH system environment variable will be updated to prepend the following to the existing path definition:
'/usr/bin:.:'

4.4 Update the IBM i TCP/IP Host Table with Deployment Server Information

Add a TCP/IP Host Table Entry on the IBM i for the Deployment Server. The entry must include both host and host.domain information.

To update the IBM i TCP/IP Host Table use the following commands:

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter the text below with the amended substitutions.
cmd: ADDTCPHTE INTNETADR('10.139.15.215')

HOSTNAME((ISRVRIXS) (ISRVRIXS.JDEDWARDS.COM))

where ISRVRIXS is the Deployment Server host name, and where ISRVRIXS.JDEDWARDS.COM is the fully qualified (host.domain) name, and where 10.139.15.215 is the Deployment Server IP address.

3. On the command line, type CFGTCP and press ENTER. Select option 10 to "Work with TCP/IP host table entries." Make certain the newly created entry appears in the table (depicted in bold font below).

4.5 Testing Long File Names on the IBM i

Before running the IBM i Express Installation Image installer, it might be necessary to rebuild the cross-reference table. This table enables tables of long file names (more than 10 characters) to be created on the IBM i. Rebuilding the table causes the system to be in a restrictive state. Coordinate this activity with the system administrator.

To test long file name support on the IBM i:

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter STRSQL.
This command will start a SQL session on the IBM i.

3. To test a long file name, enter this SQL statement:
CREATE TABLE QGPL/LONGFILENAME (FIELD CHAR(10))

where LONGFILENAME is the name of your file.

Your system is ready if the file is created in the QGPL library. You can ignore the journal setting.

4. To remove the file that you just created in the QGPL library, enter the following SQL statement:
DROP TABLE QGPL/LONGFILENAME

Note:
If the table with a long name cannot be created, it is likely the system cross reference tables are corrupt. The system cross reference tables must be rebuilt before proceeding. Refer to Section 4.6, "Rebuilding Cross Reference Tables on the IBM i".

4.6 Rebuilding Cross Reference Tables on the IBM i

The cross reference tables must be rebuilt only if database tables with long names cannot be created. To rebuild cross reference tables on the IBM i:

1. Stop all subsystems using this command:
ENDSBS *ALL *IMMED

2. After the jobs have successfully stopped, run the following command:
RCLSTG SELECT(*DBXREF)

Note that this command may run for as much as several hours.

3. Restart all subsystems using this command:
STRSBS QCTL

The cross reference tables are now rebuilt and ready for use.

4.7 Adding a New Entry to the QAQQINI File

Once the latest PTFs have been applied on the IBM i, the new LOB locator functionality must be enabled. If this is not done, the Specifications Merge and Package Build will fail.

1. Open the QAQQINI file on the Enterprise Server using this command:
WRKOBJ QUSRSYS/QAQQINI *FILE

2. If the QAQQINI file does not exist, add it using this command:
CRTDUPOBJ QAQQINI QSYS *FILE QUSRSYS DATA(*YES)

3. Start iSeries Navigator.

4. Navigate the Databases node and then expand to show the IBM i name.

5. Right click on the machine name and select Run SQL Scripts.
Run these SQL commands:

SELECT * FROM QUSRSYS.QAQQINI

In the results, search for this entry:

LOB_LOCATOR_THRESHOLD

If the LOB_LOCATOR_THRESHOLD entry does not exist, insert it by running this command:

INSERT INTO QUSRSYS.QAQQINI VALUES('LOB_LOCATOR_THRESHOLD','10000', default)

If the LOB_LOCATOR_THRESHOLD does exist, update it by running this command:

UPDATE QUSRSYS.QAQQINI SET QQVAL='10000' WHERE QQPARM='LOB_LOCATOR_THRESHOLD'

Tip:
If STRSQL is available on the IBM i, the commands can be executed from that program.

6. Sign out of the iSeries Navigator and make sure the QZDASOINIT job is terminated. This is required because a new database connection must be started with the new values for QZDASOINIT.

4.8 Setting Up a Network Share for iSeries Root

Use this procedure to set up a network share on the IBM i root directory.

1. Start iSeries Navigator

2. Expand the IBM i name in the tree.

3. Drill down into the Network node.

4. Drill down into the Servers node.

5. Highlight TCP/IP.

6. In the right hand panel find iSeries NetServer.
If it has a status of Stopped, right click and start it.

7. Double click on the started iSeries NetServer.

8. Navigate from File | New | File and complete these fields:

- Share Name
Enter this value: ROOT

- Description
Enter the Root directory in IFS.

- Access
Use the pulldown to choose Read/Write.

9. On iSeries NetServer - File Share Properties <machine_name>, click OK.

10. On iSeries NetServer File Share Properties, right click on Root and go to properties and make sure that Access is set to Read/Write.

Note:
Note: The default value is Read only.

11. Click OK to save the Read/Write setting.

4.9 Obtaining and Preparing the IBM i Express Installation Image

Important:
The IBM i Express Installer will be running in Microsoft Windows. Before running the installation program, shut down all programs running on the Windows machine (usually the Deployment Server) that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). Also make sure there are no jobs running on the IBM i host that could cause locking problems. These programs can be restarted after running the Express Installation.

The IBM i Express Installation images can be obtained from the Oracle Software Delivery Cloud site:

http://edelivery.oracle.com

To install from images downloaded from Oracle Software Delivery Cloud:

1. Create a parent download directory on a disk with at least seven (7) GB disk space. For example:
c:\ExpressI

2. Download the source disk images for the JD Edwards EnterpriseOne Express Installation for IBM i into the directory you created in Step 1.

3. Using Extract Here option, unzip each of the disk images into the directory you created in Step 1.
After unzipping all disk images, the structure should be:

c:\ExpressI\Disk1\
JDEINI
oui
SAVF
Stage
VS2008Sp1_redist
c:\ExpressI\Disk2\SAVF
c:\ExpressI\Disk3\SAVF

4. You must manually move the contents of the Disk2\SAVF and Disk3\SAVF directories into this directory:
c:\ExpressI\Disk1\SAVF

Important:
The only directory on Disk2 and Disk3 is the SAVF directory. Before running the Express Installation, all SAVF files must be in the Disk1\SAVF directory.

4.10 Copying IBM i Java Utilities into the Express Installation Image

Note:
This step must be done before starting the installer. The installer attempts to load all jar files needed for the process right at the start.

1. On the Windows machine where the install image was downloaded, map a network drive to the root directory on the IBM i machine which is the target of this install.

2. Navigate to this directory:
QIBM\ProdData\HTTP\Public\jt400\lib

3. Copy the jt400.jar and util400.jar to this directory:
Disk1\stage\ext\jlib

Note:
IBM i Access for Windows must be loaded on the machine running the install. However, the versions of these jar files on the IBM i machine will likely be more current than the files on the Windows computer. These files must be in the location described above before starting the Express installation.

Note:
On IBM i release V7R1, there is another version of jt400.jar and util400.jar in this directory:
QIBM\ProdData\HTTP\Public\jt400\lib\java6

Do NOT use the java6 version; doing so will cause the install to fail.

4.11 Installing Microsoft Windows Visual Studio

Before running the IBM i Express Installation, install the Visual Studio 2008 SP1 RunTime. Refer to Section 1.3, "Accessing Minimum Technical Requirements" in this guide. The Visual Studio 2008 Runtime is available from the Microsoft Download Center. Download and install one of the following:

Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) - 32-bit vcredist_x86.exe

Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) - 64-bit vcredist_x64.exe

Note:
Choose the 32-bit or the 64-bit installer that is appropriate for the Microsoft Windows platform on which the Express Installation for IBM i will be run.

4.12 Running the Express Installation for IBM i

Note:
The Express Installation for IBM i delivers JD Edwards EnterpriseOne logic, database and HTML servers on the same IBM i machine. This model must be followed to complete a successful install.

To run the Express Installation for IBM i:

1. Navigate to this directory:
Disk1\oui\bin

2. Run this executable by doubling clicking on the file:
setup.exe

Note:
Windows 2008. If running the installer on a Windows/2008 machine, you must right-click on setup.exe and choose the Run As Administrator option.

3. On Welcome, click the Next button.

4. On Select Installation Type, the default value is Typical, which only installs the PS900 and PY900 environments for JD Edwards EnterpriseOne. For IBM i installations, you must change default installation type to Custom.

Note:
The Express Installation for IBM i delivers JD Edwards EnterpriseOne logic, database and HTML servers on the same IBM i machine. This model must be followed to complete a successful install.
The Express Installation for IBM i requires the installation of all four standard JD Edwards EnterpriseOne Environments. This model must be followed to complete a successful install.

5. Click the Next button.

6. On Specify Home Details, enter these values:

Field

Value

Name

EOne_PPack_900

Path

c:\JDEdwardsPPack\E900

By default, the installer populates the values on this screen with _1 suffix. The _1 suffix can be removed, if desired. The actual value between Name and Path need not be consistent. It is only used by the Oracle Universal Installer.

If desired, change the install location from the c: drive. During the installation process itself, only a small amount of disk space is required on the Microsoft Windows machine for the Oracle Inventory for this install and a few temporary text files like jde.ini.

7. Click the Next button.

8. On Available Product Components, assuming Custom was chosen on the Select Installation Type screen, accept the default values.
Do not uncheck any of the components on this screen. The configuration data delivered with the Express Installation for IBM i has references to all four standard JD Edwards EnterpriseOne environments (DV900 PD900 PS900 PY900). Use the scroll bar to roll down and see what will be installed.

9. Click the Next button.

10. On Would you like to Install or Upgrade EnterpriseOne?, select the Install radio button.
This selection installs Central Objects and Business Data / Control Tables for the selected environments.

Note that the installer checks for the existence of the Business Data and Control Tables libraries and will not proceed if any of these libraries already exist:

Environment

Business Data

Control Table

DV900

TESTDATA

TESTCTL

PD900

PRODDTA

PRODCTL

PY900

CRPDTA

CRPCTL

11. Click the Next button.

12. On IBM i Server and User Profile, complete these fields:

Field

Description

IBM i Server Name

Enter the name of the IBM i machine.

IBM i User Profile

Enter QSECOFR or another user on the host that has *ALLOBJ *SECADM *SAVSYS *IOSYSCFG *JOBCTL rights.
Note this user profile name as the deinstall process requests the password for this user profile. The deinstall process automatically uses the user profile specified when the Express Installation was run.

IBM i Password

Enter the password for the User Profile above.

Enter Secure Password

This password allows you to change the password for users created on the IBM i. The default creates user profiles with password = user (for example, JDE JDE). If this violates the password rules on your IBM i machine, supply a secure password that will pass your password rules, then change the INI files and change the JD Edwards EnterpriseOne security definitions using JD Edwards EnterpriseOne applications P980001 and P98OWSEC before starting services.
Leaving this as the default password, will allow the JD Edwards EnterpriseOne services to be started immediately after the installation.

Confirm Password

Leave this as the default unless the Secure Password has been entered.

13. Click the Next button.

Note:
If you enter an invalid user or password, you will see the following screen pop up multiple times. At this point you should start the Windows Task Manager, find the OUI process (javaw.exe) and end it. Then start the installer again.

14. On Additional Information for IBM i Express Install, complete these fields:

Note:
The Deployment Server name must be defined in UPPER CASE.

15. Field

Value

Location (Name)

Enter any valid up to 15 characters long. The value entered here is used by Package Build and Deploy to group machines. This must match the Location name chosen during the Deployment Server install.

Deployment Server

The installer provides a default value for this field with the name of the machine on which the installer is run. If the installer is not run on the Deployment Server, enter the Deployment Server name.

16. The information on this screen is used to change the preconfigured CNC data that was delivered with the install disk images.

17. Click the Next button.

18. The Summary screen display the available and required disk space on the target IBM i machine on which the JD Edwards EnterpriseOne Express Installation for IBM i will be installed.

19. Click the Install button to start the installation.

The installation process begins by copying OUI installer components.

The installation process continues with the installation of JD Edwards EnterpriseOne components.

During the install, the progress of the install can be monitored by displaying the OWINSTALL/OWINSTALL message queue on the IBM i machine using this command:

DSPMSG OWINSTALL/OWINSTALL

At this point the EnterpriseOne IBM i install is complete.

20. Click the Exit button to exit the Oracle Universal Installer.

4.13 Understanding the IBM i HTTP, HTML, and Server Manager Agent Components Installation

The Oracle Universal Installer will invoke a process which installs the following:

Feature

Profile

Port / Container / Function

Description

HTTP Server Profile

E1JAS

Port 79

http://<ibm_i_hostname>:79

WebSphere Application Server

E1JAS

server1
Port: 9061

http://<ibm_i_hostname>:9061/ibm/console

AS_JS_80
Port: 80 - PD

http://<ibm_i_hostname>/jde/E1Menu.maf

AS_JS_81
Port: 81 - PY

http://<ibm_i_hostname>:81/jde/E1Menu.maf

AS_JS_80
Port: 82 - DV

http://<ibm_i_hostname>:82/jde/E1Menu.maf

AS_JS_80
Port: 83 - PS

http://<ibm_i_hostname>:83/jde/E1Menu.maf

JD Edwards EnterpriseOne Server Manager Agent

iTemplate

IBM i IFS Install Location:
/JDEdwards/iTemplate

In the course of installing the HTTP, WebSphere HTML, and Server Management Agent components the WebSphere wsadmin and other functions generate spool files which are placed in an output queue JDEOW/JDEDWARDS.

The process which installs the above listed components requires that the underlying product minimum technical requirements (MTR) are met on the system IBM i. This includes but is not limited to the IBM HTTP and WebSphere Application Server products and their associated fix packs and/or iFixes. Failure to meet the MTRs will result in failure.

Note:
Failure to successfully install the above listed components will not interfere with the Platform Pack process. The process to install these components can be invoked independently of the Oracle Universal Installer.

If the process failed to successfully install the components, use the uninstall process to completely remove the unsuccessfully applied components. Refer to Section 10.5, "Uninstalling the IBM i Delivered HTTP, HTML, and Server Manager Agent Components" in this guide for instructions.

4.14 Reinvoking the IBM i HTTP, HTML, and Server Manager Agent Components Installation Process

Isolate the cause for the initial failed installation, such as an unmet MTR. Correct these items and make certain to uninstall these components as directed above.

Note:
It is possible to uninstall and reinstall the IBM i Express Installation image components for HTTP, WebSphere HTML, and Server Manager Agent independently of the other IBM i Express Installation platform pack.

To reinvoke the installation of the IBM i Express Installation image components (HTTP, WebSphere, Server Manager Agent):

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter the following:
cmd: CALL QCMD

3. On the command line, enter the following:
cmd: SBMJOB CMD(JDEOW/ITEMPLATE DEPSVR(ISRVRIXS) DEPSVRDMN(JDEDWARDS.COM)) JOB(ITEMPLATE) CURLIB(JDEOW) LOG(4 00 *SECLVL) LOGCLPGM(*YES)

where ISRVRIXS represents the Deployment Server host name and JDEDWARDS.COM represents the concatenated domain name.

As before the installation and configuration of HTTP, WebSphere HTML, and Server Management Agent components will generate spool files which are placed in this output queue:

JDEOW/JDEDWARDS

4.15 Troubleshooting Express Installation for IBM i

During the install, the progress of the install can be monitored by looking in the logs as described below. Otherwise, display the messages on the IBM i machine using this command:

DSPMSG OWINSTALL/OWINSTALL

The IBM i Express Installer copies SAVFs to the OWINSTALL library for all the logic components (for example, PD900 library), then restores them for each environment. It then runs the Web Components install, which produces spool files in this output queue:

OWINSTALL/JDEDWARDS

The installer next copies the SAVFs for all database components, and restores them for each environment. Following this, it runs SQL scripts to copy the package repositories and update the CNC information. The SQL scripts produce spool files in QPRINT with names like CPYPKG, RAPIDICNC and RAPIDIDV.

If the OUI installer for IBM i fails after installing the Web Components (ITEMPLATE command), the Web Component must be uninstalled before running the Express Installation again. (The Deinstall through OUI, will perform the uninstall of the Web Components). See Section 10.5, "Uninstalling the IBM i Delivered HTTP, HTML, and Server Manager Agent Components" in this guide for details on running the UNINSTWAS command.

To troubleshoot any issues with the Express Install, start by looking at the install logs in this directory:

c:\Program Files\Oracle\Inventory\logs

The OUI logs every action taken by the install in a log with a name such as:

installActions2011-12-14_02-41-52PM.log

The filename of the log file contains the date and time that the install was run. The Express Installation for IBM i also produces an additional log in the same location with the same name, but with .out for the file extension. This contains a list of all IBM i commands run during the install, and any messages issued by the IBM i when the command was run.

If the install fails and you are unable to run the OUI Deinstaller, delete any inventory entries in the Home you chose when starting the install. For example, your Home might be:

C:\JDEdwardsPPack\E900_1

In this example, delete the E900_1 directory before trying to re-run the install. The preferred method is to run the OUI Deinstaller because it will delete the inventory.

4.16 Post Installation Step

After completing the IBM i Express Installation, you must install the Server Manager Console and run the Tools Accelerator TLIBMI001 that will update the Package inf and ini files. The Change Assistant tool should be configured as described in Chapter 3, "Working with the Deployment Server"Chapter 3. Working with the Deployment Server, Configuring the Planner Databases.

Note:
The TLI5001_20_99.par Tools Accelerator, which is referenced below, can be found on disk1 of the Express Installation Enterprise Server image within the TLIBMI0001 directory. Copy this par file into the \Downloads folder of Change Assistant. For example, the folder might be:
c:\JDEdwards\E900\Change Assistant\Downloads\

1. Start Change Assistant and deploy TLI5001_20_99.par which is in the location specified in the above Note. While the Tools Accelerator is running, from the Questions tab expand the Load node to monitor its progress. This Tools Accelerator will run for 30 minutes or more and perform the following:

1. Shares the install folder on the Deployment Server for Client Install and Package Build

2. Updates ESU entries in the registry for the shipped ESUs

3. Updates CNC information in the Planner database with IBM i specific information (machine types, platform names, data source types)

4. Configures the shipped install and package inf files and ini files

5. Configures the Package Feature records

6. Configures the manifest records for these shipped packages:
- PS900FA

- PY900FA

- PD900FA

- DV900FA

Note:
If all four standard environments are not installed as recommended, the Tools Accelerator will fail for each environment not installed. However, this does not prevent it from running correctly for each standard environment that is installed.

2. Install the Server Manager Console onto the Deployment Server if not already done.

Note:
Download Server Manager from http://edelivery.oracle.com/ (available as part of the Express Installation media pack) and follow the installation instructions in the JD Edwards EnterpriseOne Server Manager Guide. This installation process assumes that Server Manager has been installed on the Deployment Server. The control files for the IBM i Server Manager Agents are updated to reference the Deployment Server.

Once the Tools Accelerator has been run, the JD Edwards EnterpriseOne and HTML services can be started.

Tip:
The Enterprise Server has not been started yet at this point. To start the Enterprise Server, refer to the section in this guide entitled: Section 5.1, "Starting and Shutting Down Network Services on the Enterprise Server."

3. Logon to the Enterprise Server (IBM i) as ONEWORLD to initialize the user profile and create the ONEWORLD message queue.

4. Logon to the Enterprise Server (IBM i) as JDE, again to initialize the user profile and create the JDE message queue.

4.17 Starting the Server Manager Agent

After completing the IBM i Express Install, make certain the Server Manager Console located on the Deployment Server is running. Start the Server Manager Agent as instructed directly below. The user profile used to start the Server Manager Agent must have the following special authorities: *ALLOBJ, *JOBCTL, *SAVSYS, and *SECADM.

1. From a System i telnet session, login using a user profile with the above listed special authorities.

2. To start the Server Manager Agent services invoke the following from command line:

cmd: SBMJOB CMD(STRQSH
CMD('cd /JDEdwards/iTemplate/bin;startAgent &'))
JOB(STARTAGENT) JOBQ(QTXTSRCH)

3. To stop the Server Manager Agent services invoke the following from command line:

cmd: SBMJOB CMD(STRQSH
CMD('cd /JDEdwards/iTemplate/bin;stopAgent &'))
JOB(STOPAGENT) JOBQ(QTXTSRCH)

4. To restart the Server Manager Agent services invoke the following from command line:

cmd: SBMJOB CMD(STRQSH
CMD('cd /JDEdwards/iTemplate/bin;restartAgent &'))
JOB(STOPAGENT) JOBQ(QTXTSRCH)

4.18 Optional Steps - Enterprise Server

At this point the Enterprise Server is ready to start (see Chapter 5, "Working With the Enterprise Server"). However, consider these optional steps.

Log in as QSECOFR and perform these optional steps:

1. The Express Installation creates and pre-delivers tables and files which reference user profile accounts and passwords using the standard simple password. You may consider changing the passwords for the JDE and ONEWORLD users. Make sure to remember the new passwords. If you modify the passwords you must change the JD Edwards EnterpriseOne security definitions using JD Edwards EnterpriseOne applications P980001 and P98OWSEC. You will also need to change the JDE.INI file on the Enterprise Server to match this JDE password.

2. Tune the JDE.INI file to match the site-specific hardware and user load based upon any sizing recommendations from your hardware vendor.

Note:
The HTML Web Server has not been started yet at this point. To start the HTML Web Server, refer to the chapter in this guide entitled: Chapter 6, "Starting the HTML Server".

5 Working With the Enterprise Server

This chapter contains the following topics:

- Section 5.1, "Starting and Shutting Down Network Services on the Enterprise Server"

- Section 5.2, "Verifying the Release 9.0 Enterprise Server Installation Using PORTTEST"

5.1 Starting and Shutting Down Network Services on the Enterprise Server

The network services are started when you do the following steps:

1. Log on to the Enterprise Server as ONEWORLD.

2. Select the E900SYS version and type:
GO A98OWMNU

3. Start services by selecting option 5.

4. You can end services by selecting option 6 on this menu.

5.2 Verifying the Release 9.0 Enterprise Server Installation Using PORTTEST

To verify the Enterprise Server installation using PORTTEST:

1. Log on to the Enterprise Server as ONEWORLD.

2. Select the E900SYS version and type:
GO A98OWMNU

3. Start PORTTEST by selecting option 4 and type in the following arguments.
Enter this command for each environment, for example:

This program initializes a user and an environment (assuming Release 9.0 is installed and configured correctly). The program displays messages that indicate the selection of records from a Release 9.0 table. If it does not, review the jde_xxxxxx.log file in the IFS directory path /JDE900.

Note:
If PORTTEST fails to run, for diagnostic assistance refer to the chapter entitled: Using the PORTTEST Checklist in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries.

6 Starting the HTML Server

The HTML Servers can be started from command line. Log in as QSECOFR or a user with sufficient rights to stop and start HTTP and WebSphere services.

- The E1JAS HTTP Services must be running. Use this command to verify:
cmd: STRTCPSVR SERVER(*HTTP) HTTPSVR(E1JAS)

Note:
To configure HTTP services the HTTP *ADMIN service must be running.
cmd: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

http://<ibm_i_hostname>:2001/HTTPAdmin

- Use these command to start the WebSphere HTML Services from the command line, where the commands are a single contiguous command line:
QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;startServer AS_JS_80')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;startServer AS_JS_81')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;startServer AS_JS_82')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;startServer AS_JS_83')

- Use these command to stop the WebSphere HTML Services from the command line, where the commands are a single contiguous command line:
QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;stopServer AS_JS_80')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;stopServer AS_JS_81')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;stopServer AS_JS_82')

QSH CMD('cd /QIBM/UserData/WebSphere/AppServer/V7/Express/ profiles/E1JAS/bin;stopServer AS_JS_83')

Alternately, you can start and stop these services through the WebSphere Administration Console or from Server Manager.

Note:
Note: See IBM System i Performance and Tuning Tips for Oracle's JD Edwards EnterpriseOne 8.12, WebSphere 6.0, and WebSphere 6.1 (Document ID WP100985) for tips on tuning your WebSphere Application Server JVM. Within that document, refer to section WebSphere Application Server Tuning and follow the WebSphere 6.1 tuning tips.

Note:
Consider tuning the jas.ini and jdbj.ini files to match the site-specific hardware and user load requirements using JD Edwards EnterpriseOne Server Manager based upon any sizing recommendations from your hardware vendor.

7 Testing the JD Edwards HTML Web Server Connection

To test the JD Edwards HTML Web Server connection:

1. Start a web browser such as Firefox or Internet Explorer.

2. Enter this URL:
http://<ibm_i_hostname>:80/jde/owhtml

where <ibm_i_hostname> is the name of the JD Edwards HTML Web Server installed by the IBM i Express Installation. For a list of delivered URLs, refer to the section of this guide entitled: Section 4.13, "Understanding the IBM i HTTP, HTML, and Server Manager Agent Components Installation".

Note:
Network connectivity is required between the PC or workstation where the web browser is opened and the HTML Web Server before entering the URL.

The login screen for JD Edwards EnterpriseOne should appear. The default user ID is JDE, with password JDE. By default, the only environment available is JPD900.

8 Installing the Workstations for Developers and System Administrators

This chapter contains the following topics:

- Section 8.1, "Overview of Workstation Installation"

- Section 8.2, "Preparing for Workstation Installation"

- Section 8.3, "Copying the Configured tnsnames.ora File"

- Section 8.4, "Copying the JDBC drivers to the Client Install Directory"

- Section 8.5, "Copying the JDK to the Deployment Server"

- Section 8.6, "Working With Workstation Installation"

- Section 8.7, "Understanding Third-Party Products"

- Section 8.8, "Working with the Workstation JDE.INI on the Deployment Server"

8.1 Overview of Workstation Installation

Release 9.0 software is first installed on the Deployment Server, and then deployed from the Deployment Server to developer and system administrator workstations. The workstation installation can occur using either interactive mode, silent mode, or push mode. Push mode is described in the JD Edwards EnterpriseOne Tools Package Management Guide.

The workstations for developers and system administrators are Microsoft Windows-based machines. Refer to the Section 1.3, "Accessing Minimum Technical Requirements" for specifically-supported versions of Microsoft Windows.

Note:
The JD Edwards EnterpriseOne 9.0 Installation delivers pre-built packages that are ready for use as delivered. For the workstation to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and workstations, in addition to the procedures to verify and modify the JDE.INI on the workstations and the JDE.INI on the Enterprise Server.

See Also

- JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries in the chapter entitled: Language Process Overview for more information about how you enable multilingual installations on workstations.

- JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express

- JD Edwards EnterpriseOne Tools Package Management Guide

8.2 Preparing for Workstation Installation

To prepare for the installation of Release 9.0 on individual workstations, you must modify the workstation JDE.INI on the Deployment Server and the JD Edwards EnterpriseOne system administrator must create a user profile for every user before that user can log on to Release 9.0. You must also copy the configured tnsnames.ora from the oracle\E1local directory to the \client directory on the Deployment Server, as specified in the next section of this guide entitled: Section 8.3, "Copying the Configured tnsnames.ora File".

The workstation installation program copies all necessary components of Release 9.0 to a workstation. During installation, the installation program verifies that enough disk space exists and, if not, you are prompted to create more space before continuing.

Note:
Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express for additional details on installing the Development Client.

Prerequisites

Before installing Release 9.0 on a workstation used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in Accessing Minimum Technical Requirements. Also refer to the appropriate Microsoft documents for installation information.

The names of the Deployment Server, Enterprise Server, and client workstation cannot exceed 15 characters in length.

Note:
Note: You do not need full administrator privileges to install Release 9.0 on the workstation. However, you do need proper privileges for writing to the disk and the registry. If you do not have these privileges, you will receive a warning during the installation. If you receive a warning, contact your administrator, who can perform the installation or can grant proper disk and registry access.
For more information about granting disk and registry access, see the section entitled: Granting Disk and Registry Access for Microsoft Windows Workstations in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries.

During workstation installation, connectivity is required for:

- Read/write access to this client install directory on the primary Deployment Server in the base location:
\oneworld

- Read access to the subdirectories located under this directory:
\pathcode\package

For example:

\\deployment_server_name\E900\PD900\package

- Read/write access to this directory on the primary Deployment Server:
\client

For example:

\\deployment_server_name\E900\client

8.3 Copying the Configured tnsnames.ora File

Use this procedure to ensure the Client Installer and the OH4A installer are using the correct the tnsnames.ora file.

To copy the configured tnsnames.ora file:

1. On the Deployment Server, drill down to this folder:
oracle\E1Local\NETWORK\admin

2. Locate the tnsnames.ora file in the above folder and copy it to this folder:
\\deployment_server_name\E900\client

3. When prompted whether to overwrite the existing file, you must choose to overwrite it.

8.4 Copying the JDBC drivers to the Client Install Directory

When you ran the Deployment Server installer it copied the Oracle JDBC driver to this directory:

x:\JDEdwards\E900\OneWorld Client Install\ThirdParty\WebDevFeature\JDBC

You must also copy the IBM i JDBC driver (jt400.jar) to this same location.

8.5 Copying the JDK to the Deployment Server

As with the JDBC drivers, you must store the correct version of JDK in a defined directory on the Deployment Server. This application is then automatically downloaded to the Development Client during the installation process. To set up this process, the administrator must first obtain the required JDK from Sun Microsystems and copy this application to the Deployment Server as described below.

1. On the Deployment Server, create a directory called \JDK under the folder that contains the Development Client installation program. For example:
OneWorld Client Install\ThirdParty\WebDevFeature\JDK

2. Refer to Section 1.3, "Accessing Minimum Technical Requirements" to determine the correct JDK required for this installation.

3. Locate and download the appropriate JDK from the Sun web site. In some cases you must select a Previous Release hyperlink to download older Java versions.
http://www.oracle.com/technetwork/java/javase/downloads/index.html

The JDK may be called Java 2 Platform, Standard Edition (J2SE) for Windows or just J2SE.

Note:
Do not install a JDK with a version higher than what is indicated in the MTRs for the Development Client unless instructed to do so by JD Edwards EnterpriseOne support.

4. Save the JDK to a temporary directory.

5. From Windows Explorer, navigate to the temporary directory and run the executable program as an administrator.

6. Click Next.

7. Select Accept and click Next.

8. Click Change, and select the \JDK directory you created in Step 1.

9. Accept all other default values, and click Next.

10. Deselect both Browse Registration options.

11. Click Install.
The installation process takes several minutes.

12. When the process is complete, click Finish.

8.6 Working With Workstation Installation

The workstation installation program copies all necessary components of Release 9.1 to a workstation. During installation, the installation program verifies that enough disk space exists and, if not, you are prompted to create more space before continuing.

Caution:
Before starting a JD Edwards EnterpriseOne workstation installation, you must close all other applications running on that machine. The installation process may not run correctly if other applications are open.

This section discusses these topics:

- Section 8.6.1, "Creating a Desktop Shortcut"

- Section 8.6.2, "Using a Shared Drive"

- Section 8.6.3, "Understanding Third-Party Products"

8.6.1 Creating a Desktop Shortcut

A system administrator can create a shortcut to InstallManager.exe from the JD Edwards EnterpriseOne client install directory on the Deployment Server and can deploy the shortcut to the workstation. For example, the client install directory is typically:

\JDEdwards\E910\OneWorld Client Install

To ensure that the shortcut works correctly, ensure the Start in: field contains the location of the installmanager.htm file.

To create a desktop shortcut:

1. To edit the Start in: field, in Microsoft Windows Explorer or on the desktop, right-click the shortcut.

2. Click Properties, and then click the Shortcut menu.

3. Double-click the Release 9.1 InstallManager shortcut to start the Release 9.1 installation manager.

4. Skip to the next task entitled: Section 8.6.2, "Using a Shared Drive".

8.6.2 Using a Shared Drive

An installer can connect to the\JDEdwards\E910 shared drive on your Deployment Server from Microsoft Windows Explorer.

To use a shared drive:

1. Double-click InstallManager.exe to start the Release 9.1 installation manager.
The InstallManager.exe file is located in this folder:

OneWorld Client Install

2. On JD Edwards EnterpriseOne Release 9.1 Installation Manager, click Workstation Install.

3. On Client Workstation Setup, click Next.
If you do not have the latest version of Microsoft Internet Explorer the Release 9.1 Client Workstation Setup Third Party Application form appears. The option to install Internet Explorer is selected. To install this application, click Next. If you do not want to install these applications at this time, clear the option for one or both of them, and click Next.

If the latest version of Internet Explorer are already installed, the Third Party Application form is not displayed.

4. On Client Workstation Setup Package Selection, select the package you want to install and click Next.

Tip:
Click the Filters ON button to narrow the displayed list of available packages. This can help you find the package you want. Notice that a short description of each package appears below the list.

5. On Client Workstation Setup Type, complete these fields:

Field

Description

Select Setup Type

Select Development or Production objects. You should only select the Development option if you intend to develop Release 9.1 applications.
Note: Select the Development option only if you intend to develop JD Edwards EnterpriseOne applications.

Install Path

Select the drive and directory in which to install the package. For example, this is the typical path for Release 9.1:
c:\E910

6. To install the package, click Finish.
InstallManager shows the status of the installation process through a series of forms.

The Congratulations form indicates that the installation finished successfully. InstallManager creates a Release 9.1 shortcut in the Programs folder of your Start menu and on your desktop.

7. Reboot if necessary.

Caution:
The JD Edwards EnterpriseOne client workstation installation process verifies that several of the system DLL files are current. If they are not current, you receive a message to reboot your system. When you reboot, the system updates the DLL files in your Microsoft Windows directories.

8.6.3 Understanding Third-Party Products

A local Oracle Enterprise Edition (OEE) is required for Release 9.1 Workstations (Development Clients). The OUI installer for the Development Client installs OEE and the Development client separately. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express.

The use of Microsoft Internet Explorer is optional. Adobe Acrobat Reader 6.0 or greater is strongly recommended to view reports online. Neither the browser or reader applications are delivered with the JD Edwards EnterpriseOne Applications Release 9.1 installation.

Microsoft Internet Explorer provides:

- An option for a Web-like menu view within JD Edwards EnterpriseOne Explorer.

- An option for an Internet connection capability directly from the JD Edwards EnterpriseOne Explorer interface.

8.7 Understanding Third-Party Products

The use of Microsoft Internet Explorer is optional. Adobe Acrobat Reader 6.0 or greater is strongly recommended to view reports online. Neither the browser or reader applications are delivered with the JD Edwards EnterpriseOne 9.0 Installation.

Microsoft Internet Explorer provides:

- An option for a Web-like menu view within JD Edwards EnterpriseOne Explorer.

- An option for an Internet connection capability directly from the JD Edwards EnterpriseOne Explorer interface.

8.8 Working with the Workstation JDE.INI on the Deployment Server

This section discusses:

- Section 8.8.1, "Understanding the Workstation JDE.INI on the Deployment Server"

- Section 8.8.2, "Modifying the Workstation JDE.INI on the Deployment Server"

8.8.1 Understanding the Workstation JDE.INI on the Deployment Server

To facilitate the administration and maintenance of the JDE.INI for multiple client workstations, all instances of the JDE.INI are stored on the Deployment Server. To make a change to a JDE.INI for a workstation, change the original file on the Deployment Server. The file is then copied from the Deployment Server to its respective workstation during the Development Client installation process.

This task describes modifications required to make to the workstation JDE.INI before installing Release 9.0 on the workstation.

When using a double-byte language, modify the ODBCDataSource.inf on the Deployment Server by adding this value to all ODBC Data Sources:

DBCSNoTruncErr=1

Important:
If the ODBC Data Sources do not have this registry value on the workstations, some records will not be inserted into tables and Insert Record Failed errors will appear.

Use this procedure to modify settings in the JDE.INI in this directory on the Deployment Server:

\JDEdwards\E900\OneWorld Client Install\Misc

8.8.2 Modifying the Workstation JDE.INI on the Deployment Server

To modify the workstation JDE.INI on the Deployment Server:

1. Open the workstation JDE.INI and modify these settings:

Note:
For language installations, ensure that the workstation is set up correctly for language preferences to display and print forms. If multiple languages are installed, verify that the appropriate JDE.INI values are set to your preferred language. See for appropriate values.

Setting

Description

[INTERACTIVE RUNTIME]

For the language you are installing, enter:
Initial_Language_Code = x

where x is the value for the language installed or, if multiple languages are installed, for the preferred language.

[INSTALL]

Verify that the LocalCodeSet value and code page setting are set to the appropriate values. The system reads the JDE.INI setting for the installed language.

[JDENET]

Verify that the port number specified for ServiceNameListen and ServiceNameConnect matches the port number in the Enterprise Server JDE.INI.

2. Save and close the file.

9 Next Steps

After you have installed the JD Edwards EnterpriseOne IBM i Server, you may wish to perform some of these tasks:

- Working with Sign-on Security

- Applying an Oracle Business Accelerator

- Building and Testing Packages

- Installing Languages

- Creating a Language-Only Plan

- Adding a Server to an Existing Configuration

- Setting up Microsoft Windows Security on Deployment Server

- Using Adobe SVG Viewer on Web Clients

- Building Task Word Search Tables

- Configuring JD Edwards EnterpriseOne for use with Vertex

- Enabling CRM

- Enabling Verity Search Capability

- Copying an Environment to Another Environment

Note:
Basic security has been set up in the Security tables on the Database Server. The Security Server is running on the Enterprise Server. You must turn on the Security Server on the Deployment Server before running an Oracle Business Accelerator.

The above tasks are described in detail in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries, which is available in this document on My Oracle Support:

JD Edwards EnterpriseOne Applications Release 9.0 Installation Guides, Update (Doc ID 705463.1)

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocID=705463.1&from=BOOKMARK&bmDocDsrc=KB&viewingMode=1143))

Important:
The Support Assistant is delivered with the Deployment Server installation and is located inside the Change Assistant folder. This is an executable that collects information such as configuration and logs. In the event that you place a Service call, Global Customer Service may request that you run the Support Assistant.

Note:
For tips on tuning your system, refer to the IBM Redbook entitled IBM System i Performance and Tuning Tips for Oracle's JD Edwards EnterpriseOne 8.12, WebSphere 6.0, and WebSphere 6.1 (Document ID WP100985).
Download this Redbook from an IBM searchable website. Although the document was written for WebSphere and HTTP, it has numerous tips for tuning your entire IBM i system. Examples of tip topics include:

- QSQSRVR jobs

- SQLPKGs

- Index tuning

Further, you can consider those WebSphere 6.1 tuning tips that are applicable to WebSphere 7.

10 Uninstalling the Software

This chapter contains the following topics:

- Section 10.1, "Understanding the Uninstallation Process"

- Section 10.2, "Uninstalling the Software from the Workstations"

- Section 10.3, "Uninstalling the Deployment Server"

- Section 10.4, "Deinstalling the IBM i Server"

- Section 10.5, "Uninstalling the IBM i Delivered HTTP, HTML, and Server Manager Agent Components"

10.1 Understanding the Uninstallation Process

Because the Deployment Server is only installed on Microsoft Windows-based machines, you can uninstall it by using Add/Remove programs on the machine on which the installation was initially run.

The Uninstaller program restricts you from uninstalling a mandatory component without also removing all associated optional components that were previously installed. The relationship between the mandatory and optional components is shown in this table:

Server

Mandatory Component

Optional Components

Deployment Server

JD Edwards EnterpriseOne Files

Production Environment
Prototype Environment

Development Environment

Pristine Environment

Enterprise Server

JD Edwards EnterpriseOne Foundation

ES Production
ES Prototype

S Development

ES Pristine

10.2 Uninstalling the Software from the Workstations

You can remove previous JD Edwards EnterpriseOne installations from workstations by running the uninstallation program from Add/Remove Programs in the Microsoft Windows Control Panel.

The uninstallation program performs the following tasks:

- Deletes the JD Edwards program group

- Deletes jde*.* from the root directory

- Removes the LOCAL data source

- Deletes the path

- Unregisters services

- Removes the uninstall directory

- Increments licenses on the Deployment Server

- Deletes the installation directory tree

- Deletes the registry entry

Note:
You can ignore messages about security that appear during the uninstallation procedure. If error messages say that you cannot remove certain objects, make sure that you have not selected Read Only on the object property sheet, and then rerun the uninstallation program.

10.3 Uninstalling the Deployment Server

When you run the InstallShield Wizard to uninstall the Deployment Server, the program is removed from the machine and also from the list of installed programs.

1. On the Microsoft Windows-based machine which you initially installed the Deployment Server, navigate to Add/Remove Programs and click the Change/Remove button for this program:
JD Edwards | EnterpriseOne Deployment Server

2. On JD Edwards | EnterpriseOne Deployment Server Installer, click the Next button.

3. On JD Edwards | EnterpriseOne Deployment Server Installer, feature selection, choose the components you wish to uninstall and click the Next button.

4. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information, review the selections and click the Next button to begin the uninstallation.

5. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information, verify the uninstallation successfully complete and click the Finish button.

10.4 Deinstalling the IBM i Server

To deinstall the IBM i server:

1. You must stop all JD Edwards EnterpriseOne services on the IBM i server before starting the deinstall. You can do this using Server Manager.

2. On the Microsoft Windows-based machine which you used to do the IBM i install, click on:
Start | Programs | Oracle - EOne_PPack_900 | Oracle Installation Products | Universal Installer

Important:
The OUI Installer used for the IBM i Express Installation is version 11.2. You cannot use a 10.2 version of OUI to deinstall the IBM i server. For example, the 10.2 version of OUI was used to install E1Local local database.

3. On Welcome, click the Deinstall Products… button.

4. On Inventory, on the Contents tab, in the list of Oracle homes, select this Oracle Home:
EOne_Pack_900

5. Click the Remove button.

6. On the confirmation dialog, click the Yes button.

7. On User Input, the OUI deinstaller prompts you to enter the password that was used during the Install.
Note: The user profile that was used during the install is stored in the Oracle Inventory. However, the password is not stored. You must supply the correct password for the IBM i user profile used to install the IBM i Express Installation.

8. Click the OK button.

9. The Deinstall removes the logic components from the IBM i server, but it does not delete any data. You must sign onto the IBM i server and manually delete the following libraries in order to complete your deinstall process:

- SVM900

- SY900

- OL900

- DD900

- COPD900

- PRODDTA

- PRODCTL

- COPY900

- CRPDTA

- CRPCTL

- CODV900

- TESTDTA

- TESTCTL

- COPS900

- PS900DTA

- PS900CTL

10. There are other IBM i objects created by the Installer that will not be deleted by the Deinstall. These IBM i objects do not need to be manually deleted before an Express Installation re-install is performed - the installer recognizes them.

- ONEWORLD JOBD in QGPL

- OWJRNL library

- JDEOW library

- OWINSTALL library

- /OWINSTALL IFS directory

- /OneWorld/packages IFS directory

- ONEWORLD and JDE user profiles

11. On Inventory, click the Close button to exit the Oracle Universal Installer.

10.5 Uninstalling the IBM i Delivered HTTP, HTML, and Server Manager Agent Components

It may be necessary to uninstall the IBM i Express Installation image components for HTTP, WebSphere HTML, and Server Manager Agent. For example, you may need to uninstall if the Minimum Technical Requirements (MTRs) were not met all or a portion of these components may fail to install or configure. In such cases, these components must be uninstalled, the system must be updated to meet MTRs, and the aforementioned components must be reinstalled.

Note:
It is possible to uninstall and reinstall the Express Installation for IBM i image components for HTTP, WebSphere HTML, and Server Manager Agent independently of the other IBM i Express Installation products.

To uninstall the Express Installation for IBM i image components (HTTP, WebSphere, Server Manager Agent):

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter the following:
cmd: SBMJOB CMD(JDEOW/UNINSTWAS) JOB(UNINSTWAS) CURLIB(JDEOW) LOG(4 00 *SECLVL) LOGCLPGM(*YES)

Important:
This Uninstall process will end the services for and remove the following:

- E1JAS HTTP Server,

- E1JAS WebSphere Application Server Profile, and

- Server Manager Agent iTemplate home location.

Thus, care must be run when running this job.

3. The above listed uninstall job will perform the following steps:

- Shutdown the HTTP TCP service for E1JAS and delete the E1JAS configuration.

- Shutdown and uninstall the Server Manager Agent.

- End each delivered E1JAS WebSphere Servers: server1, AS_JS_80_PD, AS_JS_81_PY, AS_JS_82_DV, and AS_JS_83_PS. The WebSphere E1JAS profile will then be removed.

4. To reinstall the HTTP, HTML, and Server Manager Agent Components see the section in this guide entitled: Section 4.14, "Reinvoking the IBM i HTTP, HTML, and Server Manager Agent Components Installation Process".

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.