JD Edwards EnterpriseOne

Applications Installation Guide

Applications Release 9.1 and Tools Release 9.1.x for IBMi with DB2/400

E23315-14

September 2016

JD Edwards EnterpriseOne Applications Installation Guide, Applications Release 9.1 and Tools Release 9.1.x for IBMi with DB2/400

E23315-14

Copyright © 2011, 2016, 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, 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.

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 of The Open Group.

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.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Understanding JD Edwards EnterpriseOne

- 1.1 Understanding This Guide

- 1.2 Understanding the Installation Process

- 1.2.1 Understanding the Deployment Server Installation

- 1.2.2 Understanding the Platform Pack Installation

- 1.2.3 Understanding the Installation Planner

- 1.2.4 Understanding Installation Workbench

- 1.2.5 Understanding the Workstation Installation

- 1.3 Considering Additional Factors

- 1.3.1 Accessing Minimum Technical Requirements (Certifications)

- 1.3.2 Understanding Machine Names

- 1.3.3 Accessing IBM i Performance Tuning and White Papers

- 1.3.4 Using JD Edwards EnterpriseOne Support

- 1.3.5 Understanding Documentation Conventions

- 1.3.5.1 Documentation Updates

- 1.3.5.2 Tips

- 1.3.5.3 Fonts and Type Styles

- 1.4 Working With the Customer Checklist

- 1.5 Environments Overview

- 1.5.1 Understanding Environments

- 1.5.2 Planner Environment (JDEPLAN)

- 1.5.2.1 Planner Pathcode

- 1.5.2.2 Planner Database

- 1.5.3 Pristine Environment (PS910)

- 1.5.4 Deployment Environment (DEP910)

- 1.5.5 Development Environment (DV910)

- 1.5.6 Prototype Environment (PY910)

- 1.5.7 Production Environment (PD910)

- 1.5.8 Additional Considerations

- 1.5.8.1 Cluster Software Options

- 1.5.8.2 Web-Based Options

- 1.5.9 Release History

- 1.6 Language Process Overview

- 1.6.1 Language Architecture

- 1.6.1.1 Base Language

- 1.6.1.2 Alternate Language Components

- 1.6.1.3 Language Preference Codes

- 1.6.2 Database Character Set and Code Page Considerations

- 1.6.2.1 Unicode

- 1.6.2.2 Code Page Settings

- 1.6.2.2.1 DB2\400 Code Page Settings

- 1.6.2.2.2 Workstations and Deployment Server

- 1.6.3 National Language Support

- 1.6.3.1 Single-Byte and Double-Byte Considerations

- 1.6.3.2 Font Considerations

- 1.6.3.3 User Display Preferences

2 Before You Begin the Installation

- 2.1 Verifying Software and Hardware Requirements

- 2.1.1 Adding a New Entry to the QAQQINI File

- 2.1.2 Setting up Your IBM i

- 2.1.2.1 Setting Up AS\400 TCP\IP Services

- 2.1.2.2 Setting Up a Network Share for IBM i Root

- 2.1.2.3 Starting the EDRSQL Service

- 2.2 Verifying the Disk Space Requirements

3 Working with the Deployment Server

- 3.1 Using IXS (Integrated xSeries Server) for Deployment

- 3.2 Planning for IBM i Integration

- 3.3 Installing Microsoft Windows Visual Studio

- 3.4 Understanding the Deployment Server

- 3.5 Local Oracle Enterprise Edition (OEE) Considerations

- 3.5.1 32-Bit Oracle Database Client (Required for both 32-bit and 64-bit versions of OEE)

- 3.5.2 EnterpriseOne Application P96717

- 3.5.3 Best Practices for OEE Performance

- 3.5.4 Microsoft Windows Internet Protocol Version 4 (IPv4)

- 3.6 Obtaining and Preparing the Deployment Server Install Image

- 3.7 Working with JDBC Drivers on the Deployment Server

- 3.7.1 Obtaining the JDBC Drivers

- 3.7.2 Copying the JDBC Drivers to the Deployment Server

- 3.8 Installing the Deployment Server

- 3.8.1 Prerequisites

- 3.8.2 Installation Process Flow

- 3.8.3 Before Launching the Deployment Server Installer

- 3.8.4 Understanding Destination Paths

- 3.8.5 Using InstallManager to Install a Local Database on the Deployment Server

- 3.8.5.1 Using InstallManager to Install a Local Database in the Default Location

- 3.8.5.2 Running OEESetup to Install a Local Database in a Directory Other Than the Default Location

- 3.8.6 Examine the Local Database Installer Logs

- 3.8.7 Understanding the JD Edwards EnterpriseOne Deployment Server Installer

- 3.8.7.1 Understanding EnterpriseOne Files Location

- 3.8.7.2 Running the JD Edwards EnterpriseOne Deployment Server Installer

- 3.9 Adding Additional Environments (Rerunning the Deployment Server Installer)

- 3.10 Downloading and Installing the Latest Software

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

- 3.10.2 Installing the Latest Planner Update and Running the Special Instructions

- 3.11 Troubleshooting Deployment Server Installation

- 3.11.1 Verify Local Planner Tablespaces are Not Attached

- 3.11.2 OEE Installer Logs

- 3.11.3 Configuration Files

- 3.11.4 Path Code Master (F98611)

- 3.11.5 Oracle Enterprise Edition

- 3.11.5.1 File Locations

- 3.11.5.1.1 Oracle Installation Directory

- 3.11.5.1.2 OEE Logs

- 3.11.5.1.3 tnsnames.ora

- 3.11.5.2 Rebooting the Deployment Server

- 3.11.5.3 EnterpriseOne Access to the Local Oracle Database

- 3.11.5.4 Process Explorer

- 3.11.5.5 Verifying the Local Oracle Database Installation

- 3.11.5.6 Deployment Server Installation Problems

- 3.11.5.7 Runtime Problems

- 3.11.5.7.1 Jde.log shows ORA-12541: TNS:no listener

- 3.11.5.7.2 User gets a pop-up window prompting for E1Local DB user and password and Jde.log shows OCI0000141 - Error - ORA-01017: invalid username/password; logon denied

- 3.11.5.7.3 tnsnames.ora

- 3.11.5.8 Administering the Local Oracle Database Using SQL Plus

- 3.11.5.9 Encrypting the Password of the Local Oracle Database

- 3.11.5.10 Decrypting the Password of the Local Oracle Database

- 3.11.5.11 Import and Export Tablespaces to the Local Oracle Database

- 3.11.5.11.1 Import Tablespace Script (attach_planner.bat)

- 3.11.5.11.2 Export Tablespace Script (detach_planner.bat)

- 3.11.5.12 Updating the InstallManager.htm File

- 3.11.5.13 Deployment.inf and <Package_name>.inf

4 Working with the Platform Pack on the IBM i

- 4.1 Understanding the Platform Pack

- 4.2 Platform Pack Process Flow

- 4.3 Configuring the Enterprise Server Prior to Installing the Platform Pack

- 4.3.1 Understanding the Prerequisites

- 4.3.2 Understanding Security for the Platform Pack Installer

- 4.3.3 Setting the System Values

- 4.3.4 Setting up the TCP\IP Protocol for Enterprise Server

- 4.3.5 Setting up IBM i Access on your Enterprise Server

- 4.3.6 Starting the Remote Database TCP\IP Service (Optional)

- 4.3.7 Optimizing Machine Resources

- 4.3.8 Cleaning Up From Prior Installations

- 4.3.9 Testing Long File Names on the IBM i

- 4.3.10 Checking for Co-existence Tables

- 4.3.11 Adding Entries to the System Reply List

- 4.3.12 Rebuilding Cross Reference Tables on the IBM i

- 4.4 Understanding the Platform Pack Installation on the IBM i

- 4.5 Running the JD Edwards EnterpriseOne Platform Pack Installer for the IBM i

- 4.6 Troubleshooting the IBM i Platform Pack Installation

- 4.6.1 Invalid User or Password

- 4.6.2 Abnormal Program Termination - jt400.jar and/or utill.jar Missing

- 4.6.3 Business Data or Control Tables Already Exist

- 4.6.4 Business Data or Control Tables Do Not Exist

- 4.7 Rerunning the JD Edwards EnterpriseOne Platform Pack Installer

- 4.7.1 Enterprise Server

- 4.7.2 Database Server

- 4.8 Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server

- 4.9 Working with Database Security

5 Working with Installation Planner for an Install

- 5.1 Understanding Installation Planner

- 5.1.1 Language Information

- 5.1.2 Location Information

- 5.1.3 Deployment Server Information

- 5.1.4 Enterprise Server Information

- 5.1.5 JD Edwards EnterpriseOne HTML Web Server Information

- 5.1.6 Data Source Information

- 5.1.7 Environment Information

- 5.2 Working with JD Edwards EnterpriseOne Software Requirements

- 5.3 Reviewing Installation Planner Processing Options

- 5.3.1 Assumptions About Reviewing Installation Planner Processing Options

- 5.3.2 Accessing Processing Options

- 5.3.3 Choosing Processing Option Values

- 5.3.3.1 Specifying the Prompt Mode

- 5.3.3.2 Specifying the Process Mode

- 5.3.3.3 Specifying the Default Mode

- 5.3.3.4 Verifying Status Change Values Have Not Changed

- 5.3.3.5 Specifying Plan Completion Processes

- 5.3.3.6 Specifying Replication Options

- 5.4 Working with a Typical Installation Plan

- 5.4.1 Assumptions About Defining a Typical Installation Plan

- 5.4.2 Starting Installation Planner

- 5.4.3 Entering a Plan Description

- 5.4.4 Entering Location Information

- 5.4.5 Entering Deployment Server Information

- 5.4.6 Entering Enterprise Server Information

- 5.4.7 Enter Data Source Information for Server Map

- 5.4.8 Entering HTML Web Server Information

- 5.4.9 Verify the Data Sources

- 5.4.9.1 Verifying the Data Source for Data Dictionary

- 5.4.9.2 Verifying the Object Librarian Data Source

- 5.4.9.3 Verifying the OWJRNL Data Source

- 5.4.9.4 Verifying the System Data Source

- 5.4.10 Selecting Default Environments

- 5.4.10.1 Verifying the Data Source for Business Data

- 5.4.10.2 Verifying the Data Source for Central Objects

- 5.4.10.3 Verifying the Data Source for Control Tables

- 5.4.10.4 Verifying the Data Source for Data Dictionary

- 5.4.10.5 Verifying the Data Source for Versions

- 5.4.11 Finalizing the Installation Plan

- 5.4.12 Concluding the Planner Validation Report

- 5.5 Creating a Custom Installation Plan

- 5.5.1 Understanding a Custom Installation Plan

- 5.5.2 Starting Installation Planner

- 5.5.3 Entering a Plan Description

- 5.5.4 Entering Location Information

- 5.5.5 Entering Deployment Server Information

- 5.5.6 Entering Enterprise Server Information

- 5.5.7 Enter Data Source Information for Server Map

- 5.5.8 Entering HTML Web Server Information

- 5.5.9 Entering Data Server Information

- 5.5.10 Entering Shared Data Source Information

- 5.5.10.1 Specifying (Custom or Default) Shared Data Source Setup Information

- 5.5.10.2 Verifying the Data Source for Data Dictionary

- 5.5.10.3 Verifying the Object Librarian Data Source

- 5.5.10.4 Verifying the OWJRNL Data Source

- 5.5.10.5 Verifying the System Data Source

- 5.5.11 Working with Environment Setup

- 5.5.11.1 Understanding Environment Setup

- 5.5.11.2 Setting Up Environments

- 5.5.11.2.1 Selecting an Environment

- 5.5.11.2.2 Specifying Environment Data Load Parameters

- 5.5.11.3 Working with Environment Data Sources

- 5.5.11.3.1 Understanding Environment Data Sources

- 5.5.11.3.2 Selecting an Environment Data Source Setup Option

- 5.5.11.3.3 Setting Up the Data Source for Business Data

- 5.5.11.3.4 Setting Up the Data Source for Central Objects

- 5.5.11.3.5 Setting Up the Data Source for Control Tables

- 5.5.11.3.6 Verifying the Data Source for Data Dictionary (Pristine Only - PS910)

- 5.5.11.3.7 Verifying the Data Source for Versions

- 5.5.12 Adding a Remote Location

- 5.5.13 Finalizing the Installation Plan

- 5.5.14 Concluding the Planner Validation Report

- 5.6 Deleting Machines from an Installation Plan

6 Working With Installation Workbench

- 6.1 Understanding Workbench Components

- 6.1.1 Verifying the Network Share on the Deployment Server

- 6.1.2 Loading Data (Demo Data and Production Data)

- 6.1.3 Creating the Job Queue

- 6.2 Adding an Entry to the Remote Database Directory

- 6.3 Working with Unattended Workbench Mode

- 6.3.1 Selecting Attended or Unattended Workbench Mode

- 6.3.2 Setting a Task Break in Unattended Workbench Mode

- 6.4 Starting Installation Workbench

- 6.5 Working With Initial Tasks Workbench

- 6.5.1 Changing the Status of Initial Tasks Workbench

- 6.6 Configuring Your Locations

- 6.7 Configuring Your Data Sources

- 6.8 Configuring Your Environments

- 6.9 Using Machine Workbench

- 6.10 Using the Package Workbench

- 6.11 Using Remote Location Workbench

- 6.11.1 Configuring Remote Locations

- 6.12 Finishing Installation Workbench

- 6.13 Deploying an Oracle or Partner Business Accelerator Configuration (optional)

7 Working With the Enterprise Server

- 7.1 Verifying the Enterprise Server Installation Using PORTTEST

- 7.2 Starting Network Services on the Enterprise Server

- 7.3 Stopping Network Services on the Enterprise Server

- 7.4 Creating an Output Queue for the Default Printer

- 7.5 Creating the Job Queue

- 7.6 Working with OCM Generation

- 7.6.1 Understanding OCM Mappings

- 7.6.2 Understanding Data Source Setup

- 7.6.3 Understanding OCM Creation

- 7.6.3.1 Understanding Database Data Sources

- 7.6.3.2 Understanding Logic Data Sources

- 7.6.4 Understanding OCM Customization

- 7.6.4.1 Understanding Data Classes

- 7.6.4.2 Creating a New Data Class

- 7.6.4.3 Modifying the Data Source Template

- 7.6.4.4 Associating Table Data Classes

- 7.7 Setting Up a Printer on the Enterprise Server

- 7.7.1 Adding a New Printer

- 7.7.2 Defining a Default Printer

8 Installing the Development Clients for Developers and System Administrators

- 8.1 Understanding Development Client Installation

- 8.2 Preparing for Development Client Installation

- 8.3 Working With Development Client Installation

- 8.3.1 Creating a Desktop Shortcut

- 8.3.2 Using a Shared Drive

- 8.3.3 Understanding Third-Party Products

- 8.4 Understanding User Profiles and Languages

9 Understanding Media Object Queues

- 9.1 Overview

- 9.2 Modifying Media Object Queues

- 9.3 Specifying the Help Location Used by the Web Client and Development Client

10 Performing Post Installation Tasks

- 10.1 Setting Up Microsoft Windows Security on Release 9.1 Directories

- 10.1.1 Setting Security on the Pathcode Directory

- 10.1.2 Setting Security on the Database Directory

- 10.1.3 Setting Security on the Data Dictionary Directory

- 10.1.4 Setting Security on the Helps Directory

- 10.1.5 Setting Security on the Media Object Directory

- 10.1.6 Setting Security on the Planner Directory

- 10.1.7 Setting Security on the Print Queue Directory

- 10.1.8 Setting Security on the System Directory

- 10.2 Using the Adobe SVG Viewer on Web Clients

- 10.3 Setting Up Solution Explorer

- 10.3.1 Setting Up Solution Explorer HTML Documentation Path

- 10.3.2 Setting Up the Home Page for Solution Explorer

- 10.4 Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications

- 10.4.1 Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path

- 10.4.2 Configuring the Release 9.1 Database Connections for Vertex Quantum Tax Applications

- 10.4.3 Mapping Objects to the Enterprise Server

- 10.4.4 Testing the Vertex Quantum Connection from Release 9.1

- 10.4.4.1 Adding an Entry for a Remote Database Directory for Vertex

- 10.5 Enabling CRM Functionality

- 10.5.1 Enabling CRM on the CRM Mobile Client

- 10.5.2 Enabling CRM on the Enterprise Server

- 10.6 Enabling Verity Enhanced Search Capability

- 10.7 Working with the Data Dictionary

- 10.7.1 Recreating Replicated Data Dictionary Files

- 10.8 Working with SETOWAUT

- 10.9 UBE Performance ' SQL Package Location

11 Working With Signon Security

- 11.1 Setting Up Signon Security

- 11.2 Enabling Server-Side Signon Security

- 11.3 Enabling Client-Side Signon Security

- 11.4 Setting Up JD Edwards EnterpriseOne Single Sign-on

12 Building and Testing Packages

- 12.1 Understanding Packages

- 12.2 Obtaining the JDK\JRE

- 12.3 Installing Application Fixes

- 12.4 Reviewing Pre-Package Build Issues

- 12.4.1 Verifying Available Space in DBMS

- 12.4.2 Verifying Specific UBEs are Mapped Locally

- 12.4.3 Verifying the Server-Side Settings

- 12.4.4 Configuring the Enterprise Server for Simultaneous Builds

- 12.4.5 Adding a Security Override for Running Package Build

- 12.5 Reviewing Troubleshooting Tips

- 12.6 Building an Alternate Language Package

- 12.6.1 Package Build Considerations

- 12.6.2 Package Deployment Considerations

- 12.7 Assembling a Package that Contains Published Business Services

13 Copying an Environment to Another Environment

- 13.1 Setting up the Database Components for the Target Environment

- 13.2 Running the Copy Environment Application (P989400)

14 Troubleshooting

- 14.1 Using the PORTTEST Checklist

- 14.2 Resolving Data Errors

- 14.3 Planner Update Special Instructions

- 14.4 Resolving Errors Due to Lack of *ALLOBJ and *JOBCTL Authority

15 Creating a Remote Installation Plan

- 15.1 Understanding Remote Installation Plans

- 15.2 Starting Installation Planner

- 15.3 Entering Information in Installation Planner

- 15.4 Entering Plan Location Information

- 15.5 Entering Deployment Server Information

- 15.6 Entering Enterprise Server Information

- 15.7 Enter Data Source Information for Server Map

- 15.8 Entering HTML Web Server Information

- 15.9 Entering Data Server Information

- 15.10 Replicating Information to Remote Locations

- 15.11 Entering Shared Data Source Information

- 15.12 Setting Up Environments

- 15.13 Setting Up Data Sources for Environment

- 15.14 Remote Location Packages

- 15.15 Finalizing the Installation Plan

- 15.16 Concluding the Planner Validation Report

16 Adding a Server to an Existing Configuration

- 16.1 Assumptions about Adding a Server to an Existing Installation Plan

- 16.2 Starting Installation Planner

- 16.3 Entering a Plan Description

- 16.4 Entering a Plan Location

- 16.5 Selecting Additional Server Types

- 16.6 Entering Deployment Server Information

- 16.7 Specifying an Enterprise Server

- 16.7.1 Entering Enterprise Server Information

- 16.7.2 Entering Enterprise Server Data Source Information

- 16.7.2.1 Specifying Custom or Default Data Source Information

- 16.7.2.2 Verifying Custom Server Map Data Source Information

- 16.7.2.3 Adding another Enterprise Server

- 16.8 Entering HTML Web Server Information

- 16.9 Entering Data Server Information

- 16.10 Entering Shared Data Source Information

- 16.10.1 Specifying (Custom or Default) Shared Data Source Setup Information

- 16.10.2 Verifying the Data Source for Data Dictionary

- 16.10.3 Verifying the Object Librarian Data Source

- 16.10.4 Verifying the OWJRNL Data Source

- 16.10.5 Verifying the System Data Source

- 16.11 Setting Up Environments

- 16.11.1 Selecting an Environment

- 16.11.2 Specifying Environment Data Load Parameters

- 16.11.3 Selecting Languages

- 16.12 Setting Up Environment Data Sources

- 16.12.1 Selecting an Environment Data Source Setup Option

- 16.12.2 Setting Up the Data Source for Business Data

- 16.12.3 Setting Up the Data Source for Central Objects

- 16.12.4 Setting Up the Data Source for Control Tables

- 16.12.5 Verifying the Data Source for Versions

- 16.13 Finalizing the Installation Plan

- 16.14 Concluding the Validation Planner Report

- 16.15 Configuring Additional Servers

17 Creating a Language-Only Installation Plan

- 17.1 Understanding Language-Only Installation Plans

- 17.2 Reviewing Requirements for a Language Installation

- 17.3 Installing Languages on the Deployment Server

- 17.4 Running Installation Planner

- 17.4.1 Accessing Installation Planner

- 17.4.2 Entering Information into Installation Planner

- 17.4.3 Selecting Custom or Default Parameters

- 17.4.4 Selecting an Environment

- 17.5 Selecting a Language

- 17.6 Running Installation Workbench

- 17.7 Verifying Enterprise Server Requirements

- 17.8 Verifying Workstation Requirements

- 17.9 Completing the Language Installation

- 17.10 Building and Deploying Alternate Language Packages

18 FTP on the IBM i

- 18.1 Setting up FTP on the IBM i

- 18.2 Starting the FTP Server

- 18.3 Copying assembly.dat to the IBM i IFS Directory (optional)

19 Understanding JD Edwards EnterpriseOne Directory Structures

- 19.1 Deployment Server Directory Structure

- 19.2 Language Directory Structure

- 19.3 IBM i Libraries

- 19.4 Workstation General Directory Structure

20 Understanding Data Source Charts

- 20.1 Business Data

- 20.2 Central Objects

- 20.3 Control Tables

- 20.4 Data Dictionary

- 20.5 Logic

- 20.6 Object Librarian

- 20.7 Language

- 20.8 Local

- 20.9 OWJRNL

- 20.10 Server Map

- 20.11 System

- 20.12 Versions

21 Major Technical Tables

22 Working with Reports

- 22.1 Installation Planner Validation Report (R9840B)

- 22.1.1 Setting Processing Options

- 22.1.2 How to Read the Report

- 22.2 Environment Database Creation Report (R98403)

- 22.2.1 Setting Processing Options

- 22.2.1.1 Version XJDE0001 for Installations and Upgrades

- 22.2.1.2 Version XJDE0004 for Updates

- 22.2.1.3 Version XJDE0024 for Running Pristine Data

- 22.2.1.4 How to Read the Report

- 22.2.1.5 Errors and How to Resolve Them

- 22.3 Index Recreation (R9698713)

- 22.4 Pathcode Copy (R9800942)

23 Deinstalling the Software

- 23.1 Understanding the Deinstallation

- 23.2 Deinstalling the Software from the Workstations

- 23.3 Deinstalling the Local OEE from the Deployment Server

- 23.4 Manual Cleanup of a Deinstalled Oracle Database on the Deployment Server

- 23.5 Using the OUI Installer to Deinstall JD Edwards EnterpriseOne from the Deployment Server

- 23.6 Dropping DB2\400 Libraries

- 23.7 Deinstalling the Platform Pack

A Understanding IBM i Databases

Preface

Welcome to the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide.

Audience

This guide is intended for system administrators and technical consultants who are responsible for installing, upgrading, and configuring JD Edwards EnterpriseOne.

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.

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 of 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.

The most current versions of this guide and all other JD Edwards EnterpriseOne Tools and Installation/Upgrade documentation is available on the Oracle Technology Network:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

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. For additional details, refer to 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

This chapter discusses:

- Section 1.1, "Understanding This Guide"

- Section 1.2, "Understanding the Installation Process"

- Section 1.3, "Considering Additional Factors"

- Section 1.4, "Working With the Customer Checklist"

- Section 1.5, "Environments Overview"

- Section 1.6, "Language Process Overview"

1.1 Understanding This Guide

This guide is designed to direct you through a basic JD Edwards EnterpriseOne installation. It is not a substitute for the database administration manuals provided by your Relational Database Management System (RDBMS) vendor, the network administration manuals provided by your network vendor, or the installation and configuration manuals for third-party products used with JD Edwards EnterpriseOne.

Note:
You should always check My Oracle Support for revisions to this guide subsequent to the initial release, which coincides with the General Availability of Release 9.1. Generally, this document is republished in its entirety only for the next major applications release of JD Edwards EnterpriseOne.

The book contains only the procedures required for a typical base installation with predefined typical environments and databases. However, the installation is flexible enough to enable you to:

- Select specific components to install from multiple predefined environments and databases.

- Install the Platform Pack to either of these machine combinations:

- Enterprise Server and Database Server on one machine and one drive - the Installer runs once.

- Enterprise Server and Database Server on separate machines (or different drives in the same machine) - the Installer runs twice, once for each server.

This guide is designed for management information system (MIS) managers and installers. It outlines the procedures for installing Release 9.1.

This guide also describes the procedures to migrate from existing JD Edwards World to Release 9.1.

To successfully install Release 9.1, you must understand:

- Hardware and software requirements

- Database setup and management

- Enterprise platforms and operating systems

- JD Edwards EnterpriseOne Tools Foundation Guide

- JD Edwards EnterpriseOne 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

At a minimum, review these guides before beginning:

In addition, it is recommended to complete the database product courses that your database vendors provide.

1.2 Understanding the Installation Process

This documentation explains the process used to install Release 9.1 software using the installation process, which consists of these steps:

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

- Install the Platform Pack (see Concurrent Installation below for concurrent operations)

- Set up the installation plan by running Installation Planner

- Run the Installation Workbench

- Install the HTML Web Server

Note:
A JD Edwards EnterpriseOne HTML Web Server is mandatory to run web-enabled JD Edwards EnterpriseOne applications, which includes all end-user applications and selected tools applications. This guide only describes the definition of the HTML Web Server in regards to the Installation Planner and the Installation Workbench. The installation of the HTML Web Server itself is not covered by this guide. Separate guides describe the separate installation process for the HTML Web Server on the supported platforms using Server Manager. Topics relating to the HTML Web Server other than installation using Server Manager are covered in platform-specific reference guides. Such topics include the installation and configuration of the underlying application servers.
Refer to these Tools Release guides which are available on the JD Edwards EnterpriseOne Documentation library. This library is located on the Oracle Technology Network, which can be accessed at this link:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

- Server Manager Guide

- HTML Web Server Reference Guide for WebSphere on IBM i

- Install the workstations for developers and system administrators

Concurrent Installation

You can concurrently install the Deployment Server, the Platform Pack, and the HTML Web Server assuming the installation programs are run on different machines (not recommended for VM environments). This can decrease the overall time it takes to complete the installation.

Recommended Configurations

You can set up your Release 9.1 configuration in many ways. You should follow the typical setup and naming conventions whenever possible, unless there is a strong business case that supports the need to change.

See Also

Typical Customer Configuration in the JD Edwards EnterpriseOne Configurable Network Computing Implementation Guide for more information about the typical customer configuration provided with Release 9.1.

Note:
JD Edwards EnterpriseOne Release 9.1 does not support coexistence.

This section discusses:

- Section 1.2.1, "Understanding the Deployment Server Installation"

- Section 1.2.2, "Understanding the Platform Pack Installation"

- Section 1.2.3, "Understanding the Installation Planner"

- Section 1.2.4, "Understanding Installation Workbench"

- Section 1.2.5, "Understanding the Workstation Installation"

1.2.1 Understanding the Deployment Server Installation

The Deployment Server is the focus of the Release 9.1 installation process. The installation program for the Deployment Server copies the Release 9.1 software and a language, if applicable, from the language installation image to the Deployment Server. From the Deployment Server, the Release 9.1 software is distributed to one or more workstations. Since the Deployment Server and Platform Pack have separate Installers, they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines).

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

1.2.2 Understanding the Platform Pack Installation

Rather than transferring all the software from the Deployment Server, the Platform Pack installs the code and database directly to the Enterprise Server. This more direct installation method increases performance during this part of the process. It is especially beneficial in situations in which the Enterprise Server is connected to the Deployment Server using a wide area network (WAN). Since the Deployment Server and Platform Pack have separate Installers, they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines).

1.2.3 Understanding the Installation Planner

Installation Planner is an application that runs as a stand-alone program on the Deployment Server. Installation Planner configures the environments for all machines within the enterprise. It also is a system administration tool that stores all information about the installation plan in a set of preloaded tables in the Planner data source. Installation Planner guides you through setting up the installation plan step-by-step based on options you choose.

Note:
Languages are installed using the Installation Planner from the Language installation image. To install additional languages, you perform the language-specific procedures after you have executed the initial installation described in this guide. For additional details, refer to Chapter 17, "Creating a Language-Only Installation Plan".

Installation Planner manages these processes:

- Language setup

- Location setup

- Deployment Server setup

- Enterprise Server setup

- HTML Web Server

- Additional server setup
This includes setup to servers such as a Database Server.

- Data source setup
This includes setup for both Enterprise Server-specific and shared environment data sources.

Some data sources remain the same between releases:

- Business data

- Control tables

Other data sources are release specific:

- System and data dictionary

- Server map
The server map is machine-specific and release-specific if separate environments are maintained.

- Environment setup
This includes all environments for a typical customer configuration, and creation of a new environment, such as PD910. This process ensures that the Object Configuration Manager (OCM) mappings are correct and the new environments point to the correct path codes. This could include creating custom environments and path codes.

1.2.4 Understanding Installation Workbench

Installation Workbench runs the plan created during Installation Planner. It functions as a central point for all the processes required to install environments. Some of the processes that install environments might require procedures to be performed manually. However, Installation Workbench assures that procedures are performed in the proper order, and insulates you as much as possible from platform-specific environment setup.

1.2.5 Understanding the Workstation Installation

The JD Edwards EnterpriseOne Development Client (also known as a Web Development Client, "Fat" Client, Administrative Client, Windows client, or Workstation) contains components that run as standard Microsoft Windows applications (for example, Active Console, Forms Design Aid (FDA), and Report Design Aid (RDA)) and components that run in a web browser.

Note:
This document uses the following terminology when discussing JD Edwards EnterpriseOne clients:

- Web Client
Components that run in a web browser.

- Development Client
Composed of standard Windows components and Web Client.

The Web Client part of the Development Client runs inside an Application Server. The supported Application Servers are:

- Oracle Application Server (OAS)

- IBM WebSphere Application Server (WAS) Express or WebSphere Application Server for Developers.

The Oracle Application Server is included as part of the JD Edwards EnterpriseOne system code and is automatically configured to work with the Web Client when you install the Web Client for OAS. This version of the Web Client is known by any of the following names:

- Oracle Containers for Java HTML for Applications,

- OC4J for H4A, or simply

- OH4A.

Although OAS is included with JD Edwards EnterpriseOne system code, you can choose to use WAS Express or WAS for Developers as the Application Server for the EnterpriseOne Web Client. Both products are similar; either one may be manually installed before installing the Web Client for WAS. Whereas WAS Express requires a licensing fee to IBM, WAS for Developers is free. The version of the Web Client that is installed on either WAS product is referred to by either of these names:

- HTML for Applications or

- H4Ax (where the "x" denotes the version of WAS Express or WAS for Developers; currently, the supported version is 7).

This guide describes how to install Web Clients for both Application Servers: OH4A and H4A7. In addition, it covers the installation of WAS 7 Express or WAS 7 for Developers.

The first time setup of the JD Edwards EnterpriseOne Development Client installer and installation package on an EnterpriseOne Deployment Server is described in a separate guide entitled: JD Edwards EnterpriseOne Deployment Server Reference Guide. This setup on the Deployment Server must be done before a user can install a JD Edwards EnterpriseOne Development Client on a workstation. The installation package specifies the components to install and may or may not include the Web Client.

1.3 Considering Additional Factors

This section discusses:

- Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)"

- Section 1.3.2, "Understanding Machine Names"

- Section 1.3.3, "Accessing IBM i Performance Tuning and White Papers"

- Section 1.3.4, "Using JD Edwards EnterpriseOne Support"

- Section 1.3.5, "Understanding Documentation Conventions"

1.3.1 Accessing Minimum Technical Requirements (Certifications)

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.html

Access the current Minimum Technical Requirements (MTR) from My Oracle Support (https://support.oracle.com) by searching for this document:

745831.1 (JD Edwards EnterpriseOne Minimum Technical Requirements Reference)

https://support.oracle.com/epmos/faces/DocumentDisplay?id=745831.1

1.3.2 Understanding Machine Names

Due to underlying requirements in the machine name tables, you must ensure that all machines names in the JD Edwards EnterpriseOne environment conform to specific rules. Whenever you manually enter a machine name in JD Edwards EnterpriseOne, or whenever a machine name is programmatically determined, it is important to note that the machine name:

- Is case-sensitive

- Cannot exceed 15 characters

- Must be alphanumeric only and cannot contain any special characters, such as underscores or hyphens

Any machine whose name does not conform to these rules cannot be used in the JD Edwards EnterpriseOne environment.

1.3.3 Accessing IBM i Performance Tuning and White Papers

In order to optimize performance for JD Edwards EnterpriseOne customers running on IBM i, users should be aware of the IBM tuning guide (White Paper WP101777):

IBM Power Systems with IBM i Performance and Tuning Tips for Oracle's JD Edwards EnterpriseOne 9.0

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101777

On this IBM Techdocs (Technical Sales Library) web site, you can locate the above referenced White Paper and other documents by searching for "EnterpriseOne" and the EnterpriseOne release number (for example, 9.0 or 9.1):

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/Web/TechDocs

1.3.4 Using JD Edwards EnterpriseOne Support

Use My Oracle Support to access customer support functions and information including issues, Software Action Requests (SARs), and to access the Oracle JD Edwards Update Center. Through the Update Center, you can research and download Service Packs, Electronic Software Updates (ESUs), view SARs and objects, and documentation.

If you need further assistance with Release 9.1 installation, contact Oracle customer support by phone, fax, or e-mail. For questions about operating systems, databases, and other software products, contact the appropriate vendor.

1.3.5 Understanding Documentation Conventions

This section explains these typographic and design conventions used throughout this documentation.

- Section 1.3.5.1, "Documentation Updates"

- Section 1.3.5.2, "Tips"

- Section 1.3.5.3, "Fonts and Type Styles"

1.3.5.1 Documentation Updates

The Oracle Technology Network for JD Edwards Documentation always contains the most recent documentation, which may include document updates and other information about installing and upgrade JD Edwards EnterpriseOne. You can use this link to access the Oracle Technology Network for JD Edwards Documentation:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

1.3.5.2 Tips

This documentation contains tips containing information that can make the JD Edwards EnterpriseOne setup process easier. Tips information is helpful but optional.

1.3.5.3 Fonts and Type Styles

Special fonts and type styles are used in this guide. Nearly all of the commands in this guide are case sensitive. Enter them exactly as written. In addition, all of the commands described illustrate the recommended directory structure. If your machine's directory structure is different, modify the commands to match your directory structure.

Italic type style designates variables used in the guide. For example, for the variable deployment_server in a command, substitute the actual name of your Deployment Server. Also, the names of other JD Edwards EnterpriseOne guides are in italic type style. For example, JD Edwards EnterpriseOne Tools Package Management Guide.

Courier font indicates explicit file names, commands, or other information that must be typed into the system. For example, a common file name used by JD Edwards EnterpriseOne is an initialization file called the jde.ini.

1.4 Working With the Customer Checklist

The Release 9.1 support structure consists of components such as databases, operating systems, and hardware. To install Release 9.1 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 Section 1.5, "Environments Overview".

- If the installation involves a secondary language, review Section 1.6, "Language Process Overview" in this chapter.

- Assess the network.

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

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

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

- Verify that HTML Web Server hardware and software meet minimum technical requirements.

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

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

1.5 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.1 has a specific use. The following sections explain each environment in more detail.

- Section 1.5.1, "Understanding Environments"

- Section 1.5.2, "Planner Environment (JDEPLAN)"

- Section 1.5.3, "Pristine Environment (PS910)"

- Section 1.5.4, "Deployment Environment (DEP910)"

- Section 1.5.5, "Development Environment (DV910)"

- Section 1.5.6, "Prototype Environment (PY910)"

- Section 1.5.7, "Production Environment (PD910)"

- Section 1.5.8, "Additional Considerations"

1.5.1 Understanding Environments

The Release 9.1 software includes several environments that represent the typical customer configuration as defined in the JD Edwards EnterpriseOne Configurable Network Computing Implementation Guide. These environments are preset to make the installation process as easy as possible. This section contains additional information about these environments and their role in the installation and upgrade process.

Follow the setup recommendations and naming standards described in this guide to minimize confusion when communicating with those outside of your implementation team. In addition, future upgrades are simpler if you use JD Edwards EnterpriseOne naming conventions. If you customize your configurations during the process, you should change only the descriptions provided with the typical setup.

JD Edwards EnterpriseOne provides the following preset environments:

- Deployment (DEP910)

- Planner (JDEPLAN)

- Prototype (PY910)

- Pristine (PS910)

- Development (DV910)

- Production (PD910)

- HTML Web Server (J)

1.5.2 Planner Environment (JDEPLAN)

The software installation and upgrade process includes a planning stage called the planner environment. Using this approach you can define the main components of your software configuration without affecting the production environment.

Every environment must have an associated pathcode and a set of OCM mappings. The planner environment uses a planner pathcode, which is shipped with the software, and a set of OCM mappings, which point to a planner database. All pathcodes share a complete set of runtime central objects on the Deployment Server.

1.5.2.1 Planner Pathcode

Release 9.1 provides a full set of runtime objects, which are used during the installation process. The software stores these objects on the Deployment Server in the planner directory. The planner pathcode contains the only complete set of runtime central objects on the Deployment Server, which are shared by all pathcodes.

The planner pathcode includes preloaded packages used during the update specification merge process. A package indicates the necessary objects for a workstation, a point-in-time snapshot of the central objects on the Deployment Server, and where the installation program finds them.

1.5.2.2 Planner Database

All information created and updated during the planning stage is saved in these Oracle tablespaces:

- JDEPlan910

- JDECTL910

- JDEDD910

- JDSYS910

- JDEVL910

- JDEOL910

- JDEData910

When using the planner environment to change your configuration:

- Planner database tables are updated with the change.

- A plan is defined and run to move the change to the production environment.

When using the deployment or production environment to change your configuration after finishing the process:

- Production environment tables in the System pathcode are updated in real-time.

- Planner database tables are not updated.

For the deployment and production environments, OCM and data source information comes from the planner database.

You should use the production environment system (technical) tables to make changes to environments, pathcodes, packages, and OCM.

1.5.3 Pristine Environment (PS910)

Use the pristine environment (PS910) to test pristine (un-customized) objects with JD Edwards EnterpriseOne demonstration data or for training classes. The pristine environment is also used to run Table Conversion processes during an upgrade. This environment is required to compare modified objects to pristine objects. When encountering a software problem that JD Edwards EnterpriseOne Global Support cannot duplicate, they will ask you to sign on to the pristine environment to duplicate the problem. Routinely, either monthly or quarterly, refresh the data for this environment from the JDEPLAN environment on the Deployment Server.

You should apply all software updates, ESUs, and Service Packs to the Pristine environment.

1.5.4 Deployment Environment (DEP910)

Use the deployment environment to run packages builds on the Deployment Server. The deployment environment uses the planner pathcode and has OCM mappings to the production environment system tables and local data. Only one deployment environment is required because all environments created by the installation process share common data sources.

The deployment environment uses system information, such as environments, packages, and user profiles. The OCM mappings and data source information are supplied by the planner database.

1.5.5 Development Environment (DV910)

The development environment is for development objects (DV910 pathcode). Log on to this environment to modify and test objects before transferring them to the prototype environment (PY910) pathcode. After transferring the objects into PY910, build and install a full or partial prototype package (for example, PY910FA or PY910PA), and then log on to the prototype environment for additional testing. The Development environment is delivered with JD Edwards EnterpriseOne Demonstration data.

1.5.6 Prototype Environment (PY910)

The prototype environment is the staging environment for production. Constants tables and master tables, such as company constants, fiscal date patterns, and item master are populated with production data during the prototype process. Copy the tables to the production environment before going live.

After running Installation Workbench, no business data exists until it is entered. When appropriate, refresh the data this environment uses from your production environment (PD910)

1.5.7 Production Environment (PD910)

Production users have a tested and released package on their system. Batch applications can run on the Enterprise Server.

1.5.8 Additional Considerations

Additional considerations include:

- Section 1.5.8.1, "Cluster Software Options"

- Section 1.5.8.2, "Web-Based Options"

1.5.8.1 Cluster Software Options

When using cluster software, additional issues exist that must be taken into consideration before installing Release 9.1.

1.5.8.2 Web-Based Options

The HTML Web Server installation enables the use of Web-enabled functions in Release 9.1.

See Also

HTML Web Server, Java Server, or JAS in the JD Edwards EnterpriseOne Tools HTML Web Server Installation Guide for more information about Web-based options.

1.5.9 Release History

This version of JD Edwards EnterpriseOne is Release 9.1. The following list shows the currently supported previous releases of JD Edwards EnterpriseOne:

- Release 9.0

- Release 8.12

- ERP8, 8.11, and 8.11 SP1 (8.11 and 8.11 SP1 are on extended support only)

- OneWorld Xe

1.6 Language Process Overview

Note:
Languages are installed using the Installation Planner. The Language installation image is required to implement this functionality. If you install additional languages, you will perform the procedures after you have executed the initial installation described in this guide. For additional details, refer to the chapter Chapter 17, "Creating a Language-Only Installation Plan" in this guide.

This section is provided in this guide for references purposes. The language installation process automatically copies the text from a language database to the production Release 9.1 database and merges the alternate language text with the original English base. These automated processes are described throughout this guide. When installing language for the first time, a language-only plan may be chosen after completing the initial plan.

See Also

- Section 5.4, "Working with a Typical Installation Plan"

- Chapter 17, "Creating a Language-Only Installation Plan" for the tasks that must be completed when choosing to install an alternate language after completing the base installation.

1.6.1 Language Architecture

The software language architecture incorporates multinational language functionality for international customers. The software specifies the language preference for forms and reports. For example, users who share the same environment may want to view the same text in multiple languages, such as French, Spanish, and English. All language text is stored in a central location and deployed to the individual workstation.

JD Edwards EnterpriseOne provides all software with a base language of English. The package build process enables the building of packages for multiple languages. Multiple languages can be installed using the processes outlined in this guide. Language text is accessed by the language preference code settings in the user profile associated with the alternate language installed.

1.6.1.1 Base Language

Release 9.1 language support works in conjunction with the English base language. The base release contains English and must be installed before creating custom modifications to include changes or additions to the translated text. All control files must also have an English record prior to adding an alternate language text record.

1.6.1.2 Alternate Language Components

An alternative language component is not included in this release; you must build the language package.

An alternate language includes major components whereby language text is stored in the Central Objects, System, Control Table, and Data Dictionary data sources. The data is loaded to the Deployment Server during the installation and copied to the Central Objects and the other data sources through the language installation process.

For Release 9.1, JD Edwards EnterpriseOne is shipped with 21 languages. Single-byte languages run on single-byte or double-byte operating systems, but double-byte languages must run on double-byte operating systems.

Instructions in this guide explain how to set up these features.

See Also

Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for more details on how to build a language package.

1.6.1.3 Language Preference Codes

The language preference codes are the standard language codes used throughout the software. The Language Preference Code field, located in the Release 9.1 user profile, determines which language is displayed on forms or reports. All users are assigned a language preference code within the user profile.

A blank language preference code specifies the base language of English. Alternate language records always have a value in the language preference code.

The alternate language text tables contain language preference codes. The tables contain several records for each item, such as a user defined code value as well as possible multiple records for a code value, with each code representing a different language.

If the language preference code does not have a corresponding translated language record, the base English record is the default record.

Certain database tables, such as the Business Unit Master, AAIs, Account Master, and Item Master, also contain the language preference code in an additional description table. This information is not translated in the JD Edwards EnterpriseOne demonstration data.

Release 9.1 applications support the use of languages. Refer to the individual applications to set up and use multiple languages.

1.6.2 Database Character Set and Code Page Considerations

Data within a database is defined by a set of parameters. Each character within the database is identified by a specific language preference code value. A collection of characters within a defined database is called a character set or code page. A character set or code page setting is a scheme for encoding character data. Every character is defined by a unique hexadecimal value. These values can change between databases and languages. Every language is represented by at least one character set. Some character sets may contain multiple languages.

For example, the Western European character set contains all characters common to the Western European languages (Aa - Zz) and all special characters unique to specific languages, such as ', ', ', and '. Asian character sets are specific to one language.

The software uses code page conversions to control the consistent or desired display of data. A code page conversion adjusts the hexadecimal values of different characters so that the appearance of text on the desktop is the same with different code pages.

When installing or upgrading the database, set up the code page for the language before loading your language specifics for Release 9.1.

See Also

Section 1.6.3.1, "Single-Byte and Double-Byte Considerations" to determine the LocalCodeSet and code page settings for your database machine environment.

1.6.2.1 Unicode

Unicode specifies that the data stored in the data source is in Unicode format. For installs, all data sources default to Unicode.

For DB2\400, the code page is stored at the table level. Therefore, the Unicode attribute must be consistent within a data source (that is, within a library).

Note that the code page still must be set to the correct value even though the data sources may all be Unicode. The Unicode flag only indicates what column type is used to store character data in a Unicode database. For example, for DB2\400, it indicates GRAPHIC\VARGRAPHIC with CCSID 13488 is used. Refer to the following section for the code page settings.

See Also

JD Edwards EnterpriseOne Unicode Data Conversion Guide for information on how to convert data to Unicode.

JD Edwards EnterpriseOne Tools Development Standards for Business Function Programming Guide for information on how to convert Business Functions to support Unicode text strings.

JD Edwards EnterpriseOne Flat File Conversion Guide for information on how to convert Flat Files to Unicode.

1.6.2.2 Code Page Settings

You should use the code page settings in this guide. The correct code page should be set when the database is created.

1.6.2.2.1 DB2\400 Code Page Settings

The DB2\400 character set (CCSID) for the database needs to be set correctly depending on the language used as listed in this table:

Tier

Language

DB2\400 for IBM i (CCSID)

1

English

37

1

French

37

1

German

37

1

Italian

37

1

Spanish

37

1

Portuguese

37

1

Japanese

939

2

Danish

37

2

Dutch

37

2

Finnish

37

2

Norwegian

37

2

Swedish

37

2

Korean

933

2

Traditional Chinese

937

2

Simplified Chinese

935

3

Arabic

N\A

3

Czech

870

3

Hungarian

870

3

Polish

870

3

Greek

875

3

Russian

1025

3

Turkish

1026

1.6.2.2.2 Workstations and Deployment Server

Code page settings for individual languages are specified in Microsoft Windows System locale. Verify that the Deployment Server code page is set correctly prior to upgrade.

1.6.3 National Language Support

National Language Support (NLS) is a set of common standards that enable data to be entered, displayed, stored, retrieved, and printed in multiple languages, in different databases, and on different platforms.

NLS is information that requires the set up of code pages and the JDE.INI jde.ini for the Enterprise Server and JDE.INI for the web development workstations. By using NLS standards, JD Edwards EnterpriseOne maintains consistent data within all databases and hardware platforms. The same database can store alternate language text, relying on NLS standards to manage the text storage and retrieval. JD Edwards EnterpriseOne uses NLS, on all supported platforms, to interact with any computer system (hardware and software) within your own environment.

For the workstation to reflect the language installed on the Deployment Server, perform the tasks for both the Enterprise Server and workstations to verify and modify the JDE.INI jde.ini settings. These procedures are described throughout this guide.

1.6.3.1 Single-Byte and Double-Byte Considerations

Many single-byte languages support either national code pages or multinational code pages. The double-byte languages support specific individual national code pages by language.

Single-byte character sets use a collection of phonetic characters that require one byte to create a single character. Conversely, the double-byte character sets use ideographic characters and require two bytes to create a single character.

Single-byte languages can generally be run on single-byte or double-byte systems. Double-byte languages, such as Japanese, Chinese, and Korean, must run on machines configured to support a double-byte system. For example, a double-byte SQL Server or Oracle database is required for Chinese and Japanese languages.

The software can perform a Query By Example (QBE) on any character. However, when using a double-byte language, this process may not necessarily use an understandable collating sequence, although it can still use QBE for any double-byte column.

The following table shows the languages that the software supports and the LocalCodeSet values set in the JDE.INIjde.ini for each platform:

Tier

Language

Language Code

LocalCodeSet Value

1

English

E

US_EBCDIC

1

French

F

US_EBCDIC

1

German

G

US_EBCDIC

1

Italian

I

US_EBCDIC

1

Spanish

S

US_EBCDIC

1

Portuguese

P

US_EBCDIC

1

Japanese

J

JA_EBCDIC

2

Danish

DN

US_EBCDIC

2

Dutch

DU

US_EBCDIC

2

Finnish

FN

US_EBCDIC

2

Norwegian

NO

US_EBCDIC

2

Swedish

W

US_EBCDIC

2

Korean

KO

KO_EBCDIC

2

Traditional Chinese

CT

TC_EBCDIC

2

Simplified Chinese

CS

SC_EBCDIC

3

Arabic

AR

n\a

3

Czech

C

EE_EBCDIC

3

Hungarian

HU

EE_EBCDIC

3

Polish

PO

EE_EBCDIC

3

Greek

GR

GR_EBCDIC

3

Russian

RU

RS_EBCDIC

3

Turkish

TR

TK_EBCDIC

1.6.3.2 Font Considerations

JD Edwards EnterpriseOne includes standard language fonts in a separate file. Some languages (such as double-byte) require special fonts to display and print correctly. The software stores the font settings in files according to language. Individual users can choose fonts by language for forms, grids, and reports.

1.6.3.3 User Display Preferences

User display preferences are individually defined sets of Release 9.1 characteristics that are stored in the user profile. The software uses these preferences to determine how menus and forms are presented to individual users and where language is to be used in Release 9.1 for that user. After user display preferences are set up for a given user, the values remain the same on any workstation that the user accesses. Refer to the JD Edwards EnterpriseOne Tools System Administration Guide for information about modifying user profiles.

2 Before You Begin the Installation

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

This chapter discusses:

- Section 2.1, "Verifying Software and Hardware Requirements"

- Section 2.2, "Verifying the Disk Space Requirements"

2.1 Verifying Software and Hardware Requirements

Certain minimum hardware and software requirements must be met to run Release 9.1 on various operating systems and servers. Verify that the Deployment Server, Enterprise Servers, and workstations meet the hardware and software requirements.

Because the software and hardware requirements change rapidly as manufacturers constantly update their products, requirements are not provided in this documentation. Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)".

Note:
Make sure that you have taken and installed the latest Planner Update ESU from the Oracle JD Edwards Update Center. Failing to do so may prevent proper installation of the software.
Additionally, a new compiler requirement is added for Release 9.1. Before you run the Deployment Server or Platform Pack installer, you should install a Microsoft Visual C++ compiler on any machine on which the installer will be run. The MTRs list supported C++ compilers on Microsoft Windows-based machines. Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)"

2.1.1 Adding a New Entry to the QAQQINI File

Once you have put the latest PTFs onto the IBM i, you need to enable the new LOB locator functionality. If you do not do this, 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 IBM i Navigator.

4. Navigate the Databases node and then expand to show your machine name.

5. Right click on your machine name and select Run SQL Scripts.

6. Run these SQL commands:
SELECT * FROM QUSRSYS.QAQQINI

In the results, you should search for this entry:

LOB_LOCATOR_THRESHOLD

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

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

If the LOB_LOCATOR THRESHOLD entry does exist, you should ensure that the value for QQVAL is set to 10000. If the QQVAL value is set to anything other than 10000 (for example, *DEFAULT), you must change it using this command:

Tip:
If you haveSTRSQL, you can also run this command directly from that program.

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

7. Sign out of the IBM i 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.

2.1.2 Setting up Your IBM i

This section contains these tasks:

- Setting Up AS\400 TCP\IP Services

- Setting Up a Network Share for IBM i Root

- Starting the EDRSQL Service

2.1.2.1 Setting Up AS\400 TCP\IP Services

Use this procedure to set up the TCP\IP services on your IBM i.

1. In IBM i Navigator, open the node for your IBM i machine and drill down to Network | Servers | TCP\IP and right click on IBM i NetServer, and select Properties.

2. On IBM i NetServer File Share Properties - <machine_name>, click the Next Start button.

3. On IBM i NetServer General Next Start - <machine_name>, click to enable the checkbox for this setting:
Start when TCP\IP is started

4. Click OK to close the General Next Start dialog, and then click OK again to close the NetServer Properties dialog.

2.1.2.2 Setting Up a Network Share for IBM i Root

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

1. Start IBM i Navigator

2. Expand your machine 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 IBM i NetServer.
If it has a status of Stopped, right click and start it.

7. Double click on the started IBM i 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 IBM i NetServer - File Share Properties <machine_name>, click OK.

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

Note:
The default value is Read only.

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

2.1.2.3 Starting the EDRSQL Service

Tip:
Alternatively, instead of using IBM i Navigator as detailed in this procedure, you can logon to a TN5250 session as QSECOFR and invoke this command:
STRTCPSVR SERVER(*EDRSQL)

1. On IBM i Navigator, while still on Network | Servers | TCP\IP, right click on EDRSQL, choose Properties.

2. On Setting Up AS\400 TCP\IP ServicesEDRSQL Properties, click in the checkbox to enable this setting:
Start when TCP\IP is started

2.2 Verifying the Disk Space Requirements

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

During the install you cannot choose to have Printqueue and build areas installed onto another location. Additionally you must have sufficient disk space on either the Enterprise Server or a separate Database Server for the scripts and the database components.

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

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

3 Working with the Deployment Server

This chapter discusses:

- Section 3.1, "Using IXS (Integrated xSeries Server) for Deployment"

- Section 3.2, "Planning for IBM i Integration"

- Section 3.3, "Installing Microsoft Windows Visual Studio"

- Section 3.4, "Understanding the Deployment Server"

- Section 3.5, "Local Oracle Enterprise Edition (OEE) Considerations"

- Section 3.6, "Obtaining and Preparing the Deployment Server Install Image"

- Section 3.7, "Working with JDBC Drivers on the Deployment Server"

- Section 3.8, "Installing the Deployment Server"

- Section 3.9, "Adding Additional Environments (Rerunning the Deployment Server Installer)"

- Section 3.10, "Downloading and Installing the Latest Software"

- Section 3.11, "Troubleshooting Deployment Server Installation"

3.1 Using IXS (Integrated xSeries Server) for Deployment

This section describes the unique installation of the Microsoft Windows operating system if the Deployment Server is an integrated part of the IBM i. After verifying the hardware and software required for the Deployment Server on My Oracle Support (requirements are the same as for an external Deployment Server), use this section for an overview of the Integrated xSeries Server installation. The actual step by step instructions are found on the IBM IBM i Information Center web site (see below).

With this choice, the IBM i system arrives with the integrated Deployment Server in a non-configured state. The integrated server is one of these two types:

- Integrated xSeries Server for IBM i (IXS)
This server is essentially a Personal Computer (PC) on a card. It contains an Intel processor and memory but is diskless. With the IXS there is a PC card inside the IBM i system ready to become the Deployment Server.

- Integrated xSeries Adapter for IBM i (IXA)
This adapter consists of two parts:

1. An HSL bus adapter with cables ready to be plugged into a supported Netfinity or xSeries Server, and

2. One of the supported IBM Netfinity or xSeries Servers, separately ordered, without any disk. This integrated server will appear as an HSL attached expansion unit to the IBM i system.

Neither the internal IXS nor the external IXA contains disk drives; OS/400 disk storage will get allocated to either server type. The IBM i should have been ordered with enough disk to support the dedicated the Deployment Server.) The disk can be configured as one or more virtual drives called network storage spaces of varying capacities. These virtual drives are allocated within the OS/400 integrated file system. The Microsoft Windows software perceives them as physical hard drives. The IXS card is the usual choice for the Deployment Server because it meets the MTRs at a lower price than the IXA. The rest of this section, therefore, is based on the IXS.

There are three IBM redbooks that contain detailed installation and configuration information. Refer to this link:

http://www.redbooks.ibm.com/

- Consolidating Microsoft Windows 2000 Servers in IBM i: An Implementation Guide for the IBM Integrated xSeries Server for IBM i, SG24-6056, December, 2000

- Direct Attach xSeries for the IBM IBM i Server: A guide to Implementing xSeries Servers in IBM i, SG24-6222-00, December, 2001

- Microsoft Windows Server 2003 Integration with IBM i, SG24-6959-00, December, 2003

The Microsoft Windows Integration Home page offers additional information concerning OS/400, hardware specifications, etc.

The total disk used for the Release 9.1 Deployment Server is allocated across at least three Network Server Storage spaces associated with the Integrated xSeries Server:

1. Microsoft Windows system files represent the c: drive on the Microsoft Windows Server.

Note:
Take these considerations into account when estimating the size of the c: drive on your Microsoft Windows Server:

- The more memory you have installed on the integrated server hardware, the larger you should make the c: drive. Microsoft Windows Server creates a virtual memory paging file (pagefile.sys) on the system drive. Microsoft Windows Server calculates the size of the paging file based on the amount of physical memory (RAM) installed on the server. It is generally recommended that you allocate at least 150% of the installed memory size as additional disk storage on the system drive to accommodate the paging file. For example, on an IXS Server with 512 MB of RAM, you should plan for a paging file size of 768 MB when considering how large to make the system drive.

- When applications are installed on the server, many of them install some of their files on the system (c:) drive, so you should plan for this requirement.

- When you install a Microsoft Windows Server service pack, you have the option of saving the files that are replaced, in case you need to uninstall the service pack. Therefore, if you choose the uninstall option, you may require up to 100 MB of additional free space on the system drive.

- Future versions of Microsoft Windows Server may require additional free space on the c: drive to plan for an upgrade of the existing installation.

Tip:
The recommended configuration is:

- Microsoft Windows 2000 Server
c: drive = 1,250 MB + (1.5 times installed memory) + Applications (for example, Microsoft Visual C++, OEE, etc.)

- Microsoft Windows Server 2003
c: drive = 1,500 MB + (1.5 times installed memory) + Applications (for example, Microsoft Visual C++, OEE, etc.)

2. Installation source files represent the d: drive on the Microsoft Windows Server. This drive also contains the files supplied by IBM as part of the integration for Microsoft Windows Server. The d: drive only needs to be large enough to accommodate the Microsoft Windows Server installation source files, client-side integration software, and any future updates to the integration software (provided by service packs).

Tip:
The recommended configuration is:

- Microsoft Windows 2000 Server
d: drive = 500 MB

- Microsoft Windows Server 2003
d: drive = 800 MB

3. Storage space is required for the Release 9.1 code, where the total space required depends on the JD Edwards EnterpriseOne files and on the number of pathcodes you install. See Before You Begin the Installation or Upgrade of this manual to calculate your Release 9.1 exact requirements for the size of the Deployment Server.

The first two disk drives, Microsoft Windows system and installation source spaces, get created and linked to the network server description during the INSWNTSVR command. The Release 9.1 drive will need to be created and linked to the network server description after the INSWNTSVR command and Microsoft Windows Server installation completes. Keep in mind that the total amount of disk allocated to these network storage spaces is instantly unavailable to the IBM i so you need to size correctly. Track % disk utilization for the network server storage spaces in WRKDSKSTS or IBM i Navigator both before and after the installation. See the redbooks mentioned for additional details on creating and linking storage spaces.

The instructions for setting up the operating environment for this Deployment Server (prior to installing Release 9.1) are in the IBM IBM i Information Center.

Choose your region, OS/400 version and language. This web site provides the installation, configuration, operational and general use information for the IXS and IXA features. This topic is also available as a printable PDF file. Locate the documentation searching for Windows Server.

It is advisable to read through the entire Microsoft Windows server on IBM i topic, especially the Pre-installation Checklist, as you will need to be familiar with most of these points concerning the Integration software, hardware and set up process.

3.2 Planning for IBM i Integration

The steps in this section correspond to those in the topic Plan for IBM i Integration for Microsoft Windows Server installation for Microsoft Windows 2000 or Microsoft Windows 2003 Server. These are the main basis of the installation, with helpful hints highlighted.

1. Microsoft Windows Server Installation Advisor. This step consists of answering configuration questions either via the worksheet or on the web site using the interactive wizard. After you answer the questions to the Microsoft Windows Server installation advisor, it displays the Planning Worksheet which provides a summary of the values that were specified on the previous panels of the advisor. An example is shown below.

Field

Description

Network server description

Name: AS4IXS1
Description: Deployment, Microsoft Windows 2000, Lin06, 1.6 GHz, 1 GB memory

Hardware type

2892

Resource name

lin06

Microsoft Windows version

Microsoft Windows 2000

Language version

Primary national language of OS/400

Keyboard layout

Default keyboard layout

Microsoft Windows source directory

First optical device

System drive

8000 MB

NTFS

Convert system drive to NTFS.

Installation source drive

500 MB

Message logging

Do not log messages.

Event log

Log these messages:

- System

- Security

- Application

Synchronization

Synchronize Microsoft Windows date and time with OS/400 date and time every 30 minutes.

Propagate domain users

Propagate domain users using this server.

Restricted device resources

Do not restrict tape or optical devices.

Client license type

Each computer has a client license.

Terminal Services

Do not install Terminal Services.

Domain role

Server.

Server domain name

Join this workgroup:
workgroup

TCP/IP local domain name

Use the configured OS/400 local domain name.

Private LAN

For the private LAN between Microsoft Windows and OS/400, use the generated IP addresses.

TCP/IP port

Use these TCP/IP values for Port 1:
IP address: 10.230.14.90

Subnet mask: 255.255.255.0

Gateway: 10.223.1.124

TCP/IP name server

Use the name servers that are configured for OS/400.

Clustering

Do not use clustering; it is not supported.

Using the wizard is preferred because the end result is the OS/400 command (INSWNTSVR) that can be pasted into your green screen and then executed in step 3.

2. Install IBM i Integration for Microsoft Windows Server - this step is unique to the IBM i and a pre-requisite to setting up the integrated Deployment Server via the installation command. It loads the Integrated Microsoft Windows software (5722-WSV) and any PTFs that are required on IBM i.

3. Install the Microsoft Windows server- this step loads the Microsoft Windows software using regular Microsoft Windows CDs similar to an external Deployment Server except the process is begun with the OS/400 command (INSWNTSVR) that invokes the Microsoft Windows installation. When you click on next in the wizard from step 1, the screen below summarizes the answers from the advisor onto a command line which can be copied and pasted onto your green screen.

Note:
Before you hit Enter for the INSWNTSVR command, be sure to have your keyboard, mouse, and CRT attached to the IXS card. The reason is that the command continues by booting the IXS card and instructing you to continue at the Microsoft Windows server console; if the hardware is not attached in advance, you will have to vary off the IXS and repeat this step.

Copy the resulting command containing your choices onto your green screen, similar to this one:

INSWNTSVR NWSD(your server name) INSTYPE(*FULL) RSRCNAME(your communication line) DMNROLE(*SERVER) WNTVER(*WIN2000) TCPPORTCFG((1 '10.230.14.90' '255.255.255.0' '10.224.1.124')) EVTLOG(*ALL) SVRSTGSIZE(xxx yyyy) CVTNTFS(*YES) TOWRKGRP('workgroup') RSTDDEVRSC(*NONE) TEXT('Deployment, Win2k, lin06, 1.6 GHz, 1 GB memory')

where xxx is the size of your installation source drive and yyyy is the size of your Microsoft Windows C: drive. Be sure to put the first Microsoft Windows install CD into your IBM i CD-ROM drive, and hit Enter. This command loads Microsoft Windows and creates your C and D drives out of IBM i disk, a C drive for boot and Microsoft Windows system drive, and a D drive for Microsoft Windows installation source drive.

Note:
The green screen will remain input inhibited until the completion indicator is shown and responded to at the Microsoft Windows server console. Now move to the Microsoft Windows screen.

4. Continue the Microsoft Windows 2000 or Microsoft Windows 2003 Server Installation from the Microsoft Windows server console. This step requires you to click Finish and restart the Integrated Microsoft Windows Server.

Note:
Rebooting the IXS card does not affect the rest of the IBM i system. Restarting the IXS card can be accomplished from the Microsoft Windows screen using normal Microsoft Windows commands such as Shutdown or Control-Alt-Delete. (If the IXS card happens to be powered off at any time, then the IXS card will need to be varied on under WRKCFGSTS *NWS or under IBM i Navigator Network, Microsoft Windows Administration, Integrated xSeries Servers and right click on name of your IXS server.)

5. Complete Microsoft Windows 2000 or Microsoft Windows 2003 Server Installation. Refer to the Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)" for the recommended Microsoft Windows Service Pack level that you get from Microsoft. Apply it normally via Microsoft Windows. An IBM maintenance wizard is used to install the Microsoft Windows Integration software service pack of PTFs from IBM that get downloaded to Microsoft Windows from IBM i. This step also includes directions for setting your Microsoft Windows server to automatically vary on with TCP/IP (which includes at IPL time). Vary on to your Deployment Server and validate it.

Note:
In this integrated environment, OS/400 and Microsoft Windows typically share the IBM i CD-ROM drive. In order for Microsoft Windows to use the drive, it must first be "locked". From Microsoft Windows via Start, Programs, IBM IBM i, Integration for Microsoft Windows Server, name of your IXS server, IBM i devices, OPT01 (or your optical drive name), All Tasks, then right click and lock device. Be sure to unlock it after use, if the IBM i needs it next. Rebooting the Deployment Server always unlocks the optical device automatically so be sure to relock it if Deployment Server will use it again after a reboot.

After completing the above four steps of the Microsoft Windows installation, you will need to carve out at least one additional Network Server Storage space from IBM i disk to be used as dedicated Deployment Server disk for Release 9.1 with an assigned drive letter.

CRTNWSSTG NWSSTG(AS4IXS14) NWSSIZE(40000) TEXT('Release 9.1 G drive')

Once the storage spaces are created, you can vary the IXS off again in order to link the drives to the Microsoft Windows server. After the Release 9.1 drive is linked, you will vary the Deployment Server back on and you are ready to proceed with the normal set up of Microsoft Visual C++, TCP/IP, FTP, etc.

Note:
It is a good idea to create a *SAVF, and back up your C drive in case you need to recover the Microsoft Windows operation system quickly:
CRTSAVF FILE(QGPL/IXS1CDRIVE)

Vary off the Deployment Server and then enter these commands:

SAV DEV('/QSYS.LIB/QGPL.LIB/IXS1CDRIVE.FILE')

OBJ('/QFPNWSSTG/AS4IXS1') DTACPR(*YES)

Note:
It is a good idea to increase the size of your application event file on the Deployment Server, such as increasing from 512 KB to 2 MB, before beginning the deployment process to prevent it from filling up and halting the job.

3.3 Installing Microsoft Windows Visual Studio

Before running the Deployment Server Installation, install the Visual Studio 2008 SP1 RunTime. Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)" 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 OUI Installation for Deployment Server will be run.

3.4 Understanding the Deployment Server

The Deployment Server for JD Edwards EnterpriseOne must reside on an Intel Pentium-based computer running Microsoft Windows. The JD Edwards EnterpriseOne software installation and upgrade programs enable you to create and maintain installation plans and deploy Release 9.1 to the Enterprise Servers and workstations.

Beginning with JD Edwards EnterpriseOne Applications Release 9.1, the Deployment Server installation program is based on the Oracle Universal Installer (OUI). You can use the OUI to:

- Install the JD Edwards EnterpriseOne Deployment Client on a local or remote Deployment Server
This installation includes attaching and importing the Planner and Workbench tables into the local database on the Deployment Server.

Also beginning with Release 9.1, only the Oracle Enterprise Edition (OEE) database is supported as the local database on the Deployment Server.

Note:
The Oracle Universal Installer (OUI) requires the Microsoft Visual Studio 2008 VS2008SP1 Run Time. Refer to the section of this guide entitled: Section 3.3, "Installing Microsoft Windows Visual Studio".

A local OEE database must exist before you can run the OUI-based Deployment Server installer. The JD Edwards program called InstallManager is used to start the installation of the local OEE database.

No separate end-user licensing is required for installation of the local OEE database. It should be noted, however, that the installed OEE database is not fully functional relative to the commercial versions of the Oracle databases that are available.

For additional considerations, refer to Section 3.5, "Local Oracle Enterprise Edition (OEE) Considerations".

3.5 Local Oracle Enterprise Edition (OEE) Considerations

The Deployment Server installer includes the OEE database (version 11gR2) for local use by the Deployment Server. The installation includes GUI tools for database administration.

Caution:
Because the Deployment Server installer must have access to a local OEE database, you must install the 32-bit database client prior to installing the Deployment Server.

This section discusses these topics:

- Section 3.5.1, "32-Bit Oracle Database Client (Required for both 32-bit and 64-bit versions of OEE)"

- Section 3.5.2, "EnterpriseOne Application P96717"

- Section 3.5.3, "Best Practices for OEE Performance"

- Section 3.5.4, "Microsoft Windows Internet Protocol Version 4 (IPv4)"

3.5.1 32-Bit Oracle Database Client (Required for both 32-bit and 64-bit versions of OEE)

If you installed OEE on a 64-bit version of Microsoft Windows, you must also install a 32-bit version of the Oracle database client and then copy your tnsnames.ora file to a subdirectory under the database client installation directory.

Caution:
Because the Deployment Server installer must have access to a local OEE database, you must install the 32-bit database client prior to installing the Deployment Server.

To install a 32-bit Oracle database client:

1. Download the 32-bit Oracle 11g database client from the Oracle Software Delivery Cloud located at this link:
http://edelivery.oracle.com

2. Install the database client.

Caution:
PATH environment variable. If you installed the 64-bit Oracle database, the installer placed the path to the database (for example, c:\Oracle\E1local\bin) at the start of the Windows PATH environment variable. Then when you installed the 32-bit Oracle database client, the installer placed the path to the database client (for example, c:\Oracle\product\11.2.0\client_1\bin) at the start of the Windows PATH environment variable.
When EnterpriseOne runs, it looks for database drivers in each directory from start to finish in the PATH. The first occurrence of a driver DLL that EnterpriseOne finds will be loaded. This means that the path to the 32-bit Oracle database client must come BEFORE the path to the 64-bit Oracle database.

If you installed the 64-bit database and 32-bit database client in that order, the order in the PATH should be correct. However, if you installed them in the opposite order, you need to correct the order in the PATH.

To reverse the order of the 64-bit database and 32-bit database client paths in the Windows PATH, follow these steps:

1. From the Start button, select Control Panel and then System.

2. On the left side of the window that comes up, click Advanced system settings.

3. Click the Advanced tab.

4. Click Environment Variables….

5. In the "System variables" box, highlight the variable Path and click Edit….

6. In the "Variable value" field, cut the 32-bit database client's path and the following semicolon (for example, c:\Oracle\product\11.2.0\client_1\bin;).

7. Paste the client's path and semicolon at the start of the Path value.

8. Click OK.

9. Click OK to exit from the Environment Variables window.

10. Click OK to exit from the System Properties window.

11. Close the Control Panel's System window.

3. After you install the Deployment Server, you can copy this tnsnames.ora file that the installation delivered:
From:

\\<deployment server name>\<release>\client

To:

<32-bit Oracle Client Install Dir>\network\admin

3.5.2 EnterpriseOne Application P96717

Best practices in JD Edwards EnterpriseOne environments are to never directly modify an EnterpriseOne database outside of EnterpriseOne. You should always use the JD Edwards EnterpriseOne application P96717 to perform the following Oracle database actions:

- Import Tablespace

- Export Tablespace

- Create Tablespace

- Drop Tablespace

3.5.3 Best Practices for OEE Performance

You should always verify that your Deployment Server machine meets the MTRs (refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)"). 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

Oracle database engine requires approximately 1.7 GB of disk space
JD Edwards EnterpriseOne specifications require approximately 1.7 GB of disk space

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.

3.5.4 Microsoft Windows Internet Protocol Version 4 (IPv4)

The JD Edwards EnterpriseOne Deployment Server requires Microsoft Windows Internet Protocol Version 4 (IPv4) for connectivity. It cannot function using IPv6.

If your Deployment Server is not working as expected, use this procedure to determine if the problem is due to your Windows machine using IPv6 and if so, to remedy:

1. After installing the local Oracle database, use a text editor to open the log.xml file which is typically located in this directory
C:\Oracle\diag\tnslsnr\[MACHINE NAME]\listener\alert\.

2. Examine the contents of the log.xml file for indicators that the machine is using IPv6 addresses.
IPv6 addresses can be distinguished by alphanumeric digits separated by colons, rather than periods as in IPv4 addresses.

One example is if you see host_addr='::1'>. This indicates an IPv6 address, which in this case is the machine's local loopback address, whose equivalent IPv4 address is 127.0.0.1.

Another example that indicates the use of IPv6 is if this string exists:

host_addr='fe80::7045:1aba:cb6d:1b50%13'

3. If you see references to IPv6 addresses in the logs after installing the Oracle local database, then you may need to deinstall the Deployment Server and Oracle database as described in the chapter of this guide entitled: Chapter 23, "Deinstalling the Local OEE from the Deployment Server,".
Also, you may possibly need to perform additional cleanup for the Oracle Database as described in the section of this guide entitled: Section 23.4, "Manual Cleanup of a Deinstalled Oracle Database on the Deployment Server".

4. After the deinstall and cleanup is complete, you must apply a software patch from Microsoft to disable IPv6 before reinstalling the Oracle local database and EnterpriseOne Standalone or Web Development Client. The Microsoft patch for disabling IPv6 is at the following link:
How to disable IPv6 or its components in Windows

http://support.microsoft.com/kb/929852

On the above Microsoft web page, click the link labelled Disable IPv6 (Microsoft Fix it 50409).

5. After you apply the Microsoft patch to disable IPv6, you can reinstall the Oracle database and EnterpriseOne Standalone Client using the procedures in this guide.
MICROSOFT DISCLAIMER ON DISABLING IPV6

Important: Internet Protocol version 6 (IPv6) is a mandatory part of Windows Vista and later versions. We do not recommend that you disable IPv6 or its components, or some Windows components may not function. For more information, see the "What are Microsoft's recommendations about disabling IPv6?" question in IPv6 for Microsoft Windows: Frequently Asked Questions at this link:

http://technet.microsoft.com/en-us/network/cc987595.aspx

3.6 Obtaining and Preparing the Deployment Server Install Image

You install the Deployment Server Install image from DVD images obtained from the Oracle e-delivery web site:

http://edelivery.oracle.com

To install from images downloaded from the Oracle e-delivery web site:

1. Create a parent download directory on a disk with at least 15 GB free space. For example:
c:\DepSvr\Disk1

2. Download the source DVD images for the JD Edwards EnterpriseOne Deployment Server into the directory you created in Step 1.

3. You must use either the 7-Zip or WinZip program to unzip each of the DVD images into the directory you created in Step 1 (to verify successful extraction see Caution below).

Note:
During the extraction if you receive a message indicating that ..\META-INF\MANIFEST\MF already exists, at the prompt you can choose either Ignore or Replace.

Caution:
You cannot use the built-in Microsoft Windows Explorer functionality to extract the zip files otherwise the result is an incomplete install image. You must use WinZip or 7Zip.
To verify a successful extraction, check the file size of SPEC_MASTER.DBF. This file should be 1.8 GB.

After unzipping all DVDs, you should have a structure that looks like this:

c:\DepSvr\Disk1\
DeploymentServer\
Install\
META-INF\
Misc\
stage\
InstallManager.exe
InstallManager.htm
InstallManager.ico
ONEWORLD.ICO
OracleLogo.gif
README.TXT

Caution:
The directories contained on the Disk2, Disk3, Disk4, Disk5, and Disk6 images are all at the same hierarchal level as the \Disk1\DeploymentServer directory.
When your unzip operation is complete, all the files must be in the same structure as the \Disk1\DeploymentServer directory.

You should not have either a Disk2, Disk3, Disk4, Disk5, or Disk6 directory.

3.7 Working with JDBC Drivers on the Deployment Server

The Deployment Server requires database-specific JDBC drivers for several purposes as described below. This section describes:

- Section 3.7.1, "Obtaining the JDBC Drivers"

- Section 3.7.2, "Copying the JDBC Drivers to the Deployment Server"

3.7.1 Obtaining the JDBC Drivers

Based on the database being used on your JD Edwards EnterpriseOne Enterprise Server, you should obtain the required java-based JDBC driver files from your database vendor. Access the current Minimum Technical Requirement (MTR) listing from My Oracle Support for the proper JDBC driver files to obtain. For help with locating MTRs, refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)". Place the driver files in the location specified in the section of this guide entitled: Section 3.7.2, "Copying the JDBC Drivers to the Deployment Server".

In addition, for JD Edwards EnterpriseOne Release 9.1, all installations of OEE on the Deployment Server require a driver for local database connectivity on the Deployment Server (required to build and deploy ESUs) and to perform installations of the Web Development Client (workstation). You can locate the Oracle database driver in these locations:

- Oracle Enterprise Edition Database (on your JD Edwards EnterpriseOne Enterprise or Database Server)
Your installation of an Oracle 11gR2 database product includes the Oracle JDBC driver(s). Typically the driver is located in this directory of your Oracle 11gR2 installation:

\jdbc\lib

- Oracle Technology Network (OTN)
http://www.oracle.com/technetwork/indexes/downloads/index.html

You cannot have multiple Oracle JDBC driver files (such as ojdbc5.jar and classes12.jar) in the same folder (\misc) or else the drivers will conflict, which will cause access failure to the Oracle database on your Enterprise Server. The Oracle JDBC driver (for example, ojdbc5.jar) is added to the \misc folder by the Deployment Server installer.

Note:
You must manually copy the driver files from the installed location to the location specified in the section of this guide entitled: Section 3.7.2, "Copying the JDBC Drivers to the Deployment Server".

3.7.2 Copying the JDBC Drivers to the Deployment Server

Caution:
This step must be done before starting the installer, as one of its first steps the installer attempts to load all jar files needed for the process.

After you have obtained the JDBC driver(s) from the database vendor(s), you should copy the driver file(s) (and, if applicable, any associated license files) in this directory on the Deployment Server:

x:\DepSvr\Disk1\Misc

where "x" is a drive name, and

where DepSvr\Disk1\Misc is the Deployment Server install image.

You must supply this directory location and name when you run the Deployment Server Installer.

3.8 Installing the Deployment Server

Caution:
Microsoft Windows 2008. If you are running the JD Edwards EnterpriseOne Deployment Server on a Microsoft Windows 2008 platform, you must be signed onto the machine as administrator. Additionally you must run all JD Edwards EnterpriseOne installers and processes 'as Administrator '.
Due to the security model on Microsoft Windows 2008, failure to run the JD Edwards EnterpriseOne processes 'as Administrator ' will likely result in random and unpredictable failures in the processes at run time.

Caution:
Remote Desktop. If you are using Remote Desktop to connect to the Deployment Server, you must use the /admin argument to launch Remote Desktop. For example:
C:\WINDOWS\system32\mstsc.exe /F /admin

If you do not run Remote Desktop with the /admin argument, Microsoft Windows blocks several important installer functions although Microsoft Windows reports success to the installer. For example, some registry entries will be missing and the Share for the Deployment Server will not be correctly created.

The Oracle Universal Installer (OUI) process creates temporary files during the install. By default these are placed on the c: drive of your Windows-based Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully.

Microsoft Windows 2008

For Microsoft Windows 2008, pay special attention to the various Cautions in the steps in this chapter.

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

Server

Mandatory Component

Optional Components

Deployment Server

Deployment Client
EnterpriseOne Files

Development environment
Prototype environment

Pristine environment

Production environment

The installation process for the Deployment Server performs these functions:

- Installs the objects from the CDs.

- Creates the path code directory structures (such as PS910 and PD910) based on your selections.

- Updates the Microsoft Windows Registry.

Note:
You can run the Deployment Server and the Platform Pack installation concurrently (assuming the installation programs are run on different machines).

After verifying the support structure as shown in the section of this guide entitled: Section 3.6, "Obtaining and Preparing the Deployment Server Install Image", you can install the Deployment Server. This process installs the Deployment Server from CDs.

Note:
You must install the Deployment Server locally; you cannot install the Deployment Server from a remote machine. However, you can choose to install JD Edwards EnterpriseOne files and environments on a remote machine using a mapped drive. Prior to installing to a remote machine, you must have already setup the drive with network mapping.

This section describes these topics:

- Section 3.8.1, "Prerequisites"

- Section 3.8.2, "Installation Process Flow"

- Section 3.8.3, "Before Launching the Deployment Server Installer"

- Section 3.8.4, "Understanding Destination Paths"

- Section 3.8.5, "Using InstallManager to Install a Local Database on the Deployment Server"

- Section 3.8.6, "Examine the Local Database Installer Logs"

- Section 3.8.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer"

3.8.1 Prerequisites

Before you run the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). You can restart these programs after you finish installing the Deployment Server.

3.8.2 Installation Process Flow

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

3.8.3 Before Launching the Deployment Server Installer

Before you launch the Deployment Server installer, you should obtain the JDBC drivers for the Enterprise Server database and also for your local database, which is Oracle Enterprise Edition (OEE). You can place the JDBC drivers in the CD images directory on your Deployment Server either before or after running OUI to install the Deployment Server; however, it is preferable that you copy the drivers before running OUI. For instructions on obtaining and placing the requisite JDBC drivers, refer to the section Section 3.7, "Working with JDBC Drivers on the Deployment Server".

Note:
The Deployment Server OUI installer delivers the requisite JDK/JVM.

Tip: Installation Methods

You can install the Deployment Server using any of these methods:

- Directly from the Deployment Server installation DVD.

- From a copy of the Deployment Server installation DVD that exists on a hard disk drive.

- From a downloaded and unzipped image of the installation DVD that was obtained from the Oracle E-Delivery web site.

3.8.4 Understanding Destination Paths

Each Oracle product that is installed on a machine has what is termed an Oracle Home directory or path. This is a directory that contains all the files associated with the product. This path has a name as well. You can specify a name that is intuitive so you do not have to remember the path.

When you install the JD Edwards EnterpriseOne Deployment Server, you specify an Oracle Home and name for that installation as well. For example, you may enter C:\JDEdwards\E910 as the Oracle Home path and JDE DEP910_HOME as the Oracle Home name. Following the this example, your Oracle Home on the Deployment Server would be:

Oracle Home Path

Oracle Home Name

Comment

C:\JDEdwards\E910

JDE_DEP910_HOME

This is the Oracle Home of the Deployment Server

3.8.5 Using InstallManager to Install a Local Database on the Deployment Server

If you have not already installed the database engine and a database called E1Local does not exist on your Deployment Server, use the procedures in this section to install these requisite components before installing the JD Edwards EnterpriseOne Deployment Server. If the local database engine is already installed and an E1Local database exists, do not reinstall the database engine; go to the section entitled: Section 3.8.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer".

If you want to install the local database under the default location (that is, c:\Oracle), you can run InstallManager to do so. If you want to install into another directory, you must run the database installation program OEESetup.exe from a command prompt and provide one or more arguments.

This section discusses these topics:

- Section 3.8.5.1, "Using InstallManager to Install a Local Database in the Default Location"

- Running OEESetup to Install a Local Database in a Directory Other Than the Default Location

3.8.5.1 Using InstallManager to Install a Local Database in the Default Location

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

2. Log on to the Deployment Server as a user with Administrator rights.

Caution:
Ensure that the Administrator account name that you use does not contain any special characters.

3. If you have not already done so, expand all disk images to be under a common directory called Disk1 on your Deployment Server.

Tip:
Refer to the preceding Tip: Installation Methods for a list of various installation methods.

Caution:
Microsoft Windows 2008. For Windows/2008, if you are using a physical DVD and the installation starts automatically, you must cancel this process and start the installation manually.

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, you must right-click on the executable and select Run as Administrator from the drop-down.

4. From the Disk1 image, execute the InstallManager.exe file from the root folder.
\Disk1\InstallManager.exe

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, you must right-click on the executable and select Run as Administrator from the drop-down.

5. On JD Edwards Install Manager, select this link to install the local OEE database:
EnterpriseOne Database Engine

6. Click the Run button to launch the OEESetup.exe installer.

7. If you receive an Install Manager - Security warning dialog with the message "The publisher could not be verified", click the Run button to begin the installation of the local database. This installation process can take quite some time. Upon completion a local database called E1Local will exist.

Caution:
You must reboot your machine before continuing with the installation of the JD Edwards EnterpriseOne Deployment Server as described in the next section in this guide entitled: Section 3.8.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer".

3.8.5.2 Running OEESetup to Install a Local Database in a Directory Other Than the Default Location

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

2. Log on to the Deployment Server as a user with Administrator rights.

Caution:
Ensure that the Administrator account name that you use does not contain any special characters.

3. If you have not already done so, expand all disk images to be under a common directory called Disk1 on your Deployment Server.

Tip:
Refer to the preceding Tip: Installation Methods for a list of various installation methods.

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, if you are using a physical DVD and the installation starts automatically, you must cancel this process and start the installation manually.

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, you must right-click on the executable and select Run as Administrator from the drop-down.

4. Open a command prompt window.

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, you must right-click on the command prompt's executable (cmd.exe) and select Run as Administrator from the drop-down.

5. From within the command prompt window, change directory (cd) to directory that contains the extracted contents of the Disk1 image. For example:
DeploymentServer\OneWorld Client Install\ThirdParty\ORACLE

6. Run the following command:
OEESetup.exe -i installation_directory

where

the -i switch tells OEESetup.exe where to install the local database E1Local. If both this switch and the installation_directory argument are omitted, the local database will be installed under the default location c:\Oracle. If the default location is used, the database will then reside in this directory (instead of a user-specific directory):

c:\Oracle\E1Local

The argument installation_directory is optional; it represents the path where the local database will be installed. Do not include E1Local as part of this path. If this argument is not provided, you will be prompted for the path as shown below:

7. If you specified the -i switch but did not provide the installation_directory argument, you will see the above screen. On the screen entitled Oracle Base Directory, in the Path field, enter or browse to the directory into which you want to install the local Oracle database. For example:
c:\Oracle

Note:
This installation process can take quite some time. Upon completion a local database called E1Local will exist in the specified directory. Using the example above, the database would be installed in this directory
c:\Oracle\E1Local

Caution:
You must reboot your machine before continuing with the installation of the JD Edwards EnterpriseOne Deployment Server as described in the next section in this guide entitled: Section 3.8.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer".

3.8.6 Examine the Local Database Installer Logs

Even though the screen indicates that the installation was successful, you should perform the following checks to verify that the database truly installed correctly:

1. Examine the log file

- The log file is in this folder:
C:\Program Files\Oracle\Inventory\logs

- The log file name is named:
installActionsyyyy-mm-dd_hh-mm-ssAM|PM.log

where the syntax is:

- yyyy is the year

- mm is the month

- dd is the day of the month

- hh is the hour

- mm is the minutes

- ss is the seconds

- AM|PM is either AM or PM

- For additional details on log file names and location, refer to the section of this chapter entitled: Section 3.11.2, "OEE Installer Logs".

2. Verify that the OEE services exist and are running

1. From the Microsoft Windows Control Panel, navigate to Administrative Tools > Services.

2. In the list of Services, look for these services:
OracleE1LocalTNSListener

OracleServiceE1LOCAL

3. If either of the above services is missing, it indicates that there was a problem in completing all the installation and configuration steps. You should examine the logs specified in the table in the section of this guide entitled: Section 3.11.2, "OEE Installer Logs".
To remedy you will probably need to deinstall the database engine using the steps in the section of this guide entitled: Section 23.5, "Using the OUI Installer to Deinstall JD Edwards EnterpriseOne from the Deployment Server" , reboot the Deployment Server machine, and then reinstall the OEE database.

3.8.7 Understanding the JD Edwards EnterpriseOne Deployment Server Installer

A local OEE database engine and a database called E1Local must already exist on this machine. If not, use the procedures in the preceding section entitled: Section 3.8.5, "Using InstallManager to Install a Local Database on the Deployment Server".

This section describes:

- Section 3.8.7.1, "Understanding EnterpriseOne Files Location"

- Section 3.8.7.2, "Running the JD Edwards EnterpriseOne Deployment Server Installer"

3.8.7.1 Understanding EnterpriseOne Files Location

The software component called EnterpriseOne Files is a pre-defined grouping of files that can be installed on your local machine or a mapped network drive. It includes EnterpriseOne system files and pathcodes for these four (4) environments:

- Development

- Prototype

- Pristine

- Production

By default the installer assumes the local machine is the Deployment Server. As such it provides a default value for your Oracle Home path.

You cannot change this local path value after the installation is complete; it must remain whatever value you specified at the time of installation.

Optionally you can choose to install EnterpriseOne (E1) Files to a remote machine as the Deployment Server. If you do so, the installer creates a unique "planner client" on the local machine that contains only the Planner pathcode. You should only set up one "planner client" machine to do the Deployment Server jobs such as applying software updates, running installation plan, and so on.

Using a Remote Machine as the Deployment Server

If you intend to use a remote machine as the Deployment Server, prior to running the Deployment Server installer you must first map a network drive using this procedure:

1. On the remote Deployment Server, create a folder as the target location in which the installer will place the EnterpriseOne (E1) files. For example:

E:\JDEdwards\E910

2. Using the example above, share the target folder E910 with full permissions.

3. Caution:
Because the Deployment Server installer must be run as an Administrator, you must also map a network drive as an Administrator.

Start a Command Prompt as Administrator and map a network drive on the local machine to the remote Deployment Server machine. For example, map Z:\ to \\Remote_Deployment_Server_Machine_name\E910

Tip:
You can verify that the drive is being mapped as an Administrator by confirming that "Administrator:" is displayed in the title bar of the Command Prompt window.

The below screen shows a sample of a properly mapped network drive for the remote Deployment Server:

Note:
In a later separate process described in Section 3.8.7.2, "Running the JD Edwards EnterpriseOne Deployment Server Installer", when you are prompted by the installer for the location of the remote Deployment Server, in the location field you can browse to or enter the mapped drive including the drive letter designation. Using the above example in Step 3, the value would be the Z: drive. Using the above screen shot as an example, the value would be the L: drive.
The same installer validates the location that you enter for the remote location. If the mapping to the remote location is not valid or the directory specified in Step 1 above does not exist on the remote machine, the installer will not continue.

Note:
The installer validates the location. If the mapping to the remote location is not valid the installer cannot continue. Likewise the directory specified in Step 1 must exist on the remote machine or else the installer cannot continue.

3.8.7.2 Running the JD Edwards EnterpriseOne Deployment Server Installer

Use the procedure in this section to install the JD Edwards EnterpriseOne Deployment Server.

1. Log on to the Deployment Server as a user with Administrator rights.

Caution:
Ensure that the Administrator account name that you use does not contain any special characters such as ampersands, asterisks, or underscores.

2. Locate the disk 1, which is either a physical disc or disc image directory, for the Deployment Server installation DVD.

Tip:
Refer to the preceding Tip: Installation Methods for a list of various installation methods.

Caution:
Microsoft Windows 2008. For Windows/2008, if you are using a physical DVD and the installation starts automatically, you must cancel this process and start the installation manually.

Caution:
Microsoft Windows 2008. On the Microsoft Windows 2008 platform, you must right-click on the executable and select Run as Administrator from the drop-down.
You must right-click on the executable and select Run as Administrator from the drop-down.

3. From disk1, execute the InstallManager.exe file from the root folder. For example:
\Disk1\InstallManager.exe

4. On JD Edwards Install Manager, select this link:
EnterpriseOne E910 Deployment Server

5. If you get the above prompt, click the Run button to execute the Deployment Server OUI installer, which is called by the setup.exe program. This process opens a Microsoft Windows command window as shown in the below example.

After the OUI installer is launched, the command window is closed and the Welcome screen is displayed.

6. On Welcome, select the Next button.

7. On Select Installation Type, select the appropriate radio button for these installation types:

- Typical
The Typical selection installs environments for Deployment Client (Planner), prototype, pristine and also installs JD Edwards EnterpriseOne files on the local machine. This selection is recommended for the general user.

- Custom
The Custom selection lets you choose the specific environments you want to install on the deployment server. The deployment client (Planner) is always installed on the local machine. You may choose to install JD Edwards EnterpriseOne Files and environments on a remote machine. In that case, first you need to setup a mapped drive as described in the section of this guide entitled: Section 3.8.7.1, "Understanding EnterpriseOne Files Location". This selection is only recommended for an expert user.

8. After you have selected an installation type, select the Next button.

9. On Specify Home Details, you must specify an Oracle Home path and a name for that path.

Tip:
For more information about Oracle Homes and recommendations for naming the Oracle Homes for the JD Edwards EnterpriseOne Deployment Server, see the section in this guide entitled: Section 3.8.4, "Understanding Destination Paths".

Each Oracle product that is installed on a machine has what is termed an Oracle Home path. This path contains all the files for each Oracle product. This path has a user-specified name as well.

On Specify Home Details, complete these fields:

Field

Description

Name

Enter a name for the Oracle Home for the JD Edwards EnterpriseOne Deployment Server. For example:
JDE_DEP910_HOME

Path

The path you enter here is for the Oracle Home path where the E1 Deployment Server will be installed. For example, the path might be:
C:\JDEdwards\E910

Do not specify the same Oracle Home name or path into which you installed the local database; however, you can specify a path that is a subdirectory of the database's Parent Oracle Home.

For local installation, you must use the default value. For remote installation, this value must be the letter designation of the mapped drive. For additional details, refer to the section of this chapter entitled: Section 3.8.4, "Understanding Destination Paths".

10. Select the Next button.

Tip:
If you chose Typical installation on the preceding screen (Select Installation Type), you can skip directly to Step 16 located later in this task to complete the Deployment Server installation.
If you chose Custom installation on the preceding screen (Select Installation Type), proceed with the following steps.

Note:
The Available Product Components screen and subsequent screens until the Summary are displayed if you chose Custom installation on Select Installation Type in Step 7.

11. On Available Product Components, EnterpriseOne Deployment Server, enable the checkboxes to select these features components you want to install:

- EnterpriseOne Deployment Client
The selection for EnterpriseOne Deployment Client is mandatory in order to select other components. If you do not select this component, you cannot select any other components. This installs the planner pathcode and databases on the local machine. You will be given an option to install other components on a remote share.

- EnterpriseOne Files
The selection for EnterpriseOne Files includes mandatory system files. If you do not select this component you cannot select any other environment components. Likewise, if you re-run the JD Edwards EnterpriseOne Deployment Server Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne files.

- Development Environment

- Prototype Environment

- Pristine Environment

- Production Environment

Tip:
You can use the Select All button to select all components.

12. On Specify EnterpriseOne Files Location, you can accept the default local value or enter a mapped network drive.

The installer provides a default value which is your Oracle Home path. For example:

C:\JDEdwards\E910

If you prefer to install JD EnterpriseOne Files to a remote Deployment Server, you can specify a mapped drive. For example:

Z:\

For more on the proper use of mapped drives and network drives, refer to the following Caution.

Caution:
You cannot enter a network path such as:
\\machine_name\network_share

If you enter a network path instead of a mapped drive, the installer will give an error.

When you click Browse to select the drive, if the mapped remote drive is not listed, perform these steps:

1. Start a Command Prompt session by right clicking and selecting Run as Administrator.
This command prompt opens on the Microsoft 2008 Server with Administrator:cmd in the header.

2. In the command window, type this command:
net use z: \\<MachineName>\<SharedPath>

where z: is the drive on which you mapped drive exists.

13. Select the Next button.

14. On Choose E1Local User Password, you can specify a secure password to be used for the E1Local Database Users on the Deployment Server. This unique password will be used for all database accounts created by the Deployment Server installer.
The default password is the same as the user name of the database account. For example, if the user name of the local database account is JDE, the default password is JDE.

If you do not specify a E1Local user password, by default the installer will use this value: DEFAULT. You cannot leave this field blank.

15. Select the Next button.
Sample Summary Screen for Typical Installation

Sample Summary Screen for Custom Installation

16. On Summary, verify the list of items to be installed is correct.

If there is insufficient disk space to complete the installation is available on the Deployment Server target machine, an error message is displayed.

17. Click the Install button.

The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation.

18. When the installation of the database finishes, the End of Installation screen is displayed.

Caution:
Examine the Installer Logs. Even though the screen indicates that the installation was successful, you should you should always check the logs before you attempt to run the Deployment Server. The file is named log.txt and is located in the Deployment Server installation directory. For example:
C:\Program Files (x86)\Oracle\Inventory\logs\InstallActions\ installActionsyyyy-mm-dd_hh-mm-ssPM.log

For additional details on log file names and location, refer to the section of this chapter entitled: Section 3.11.2, "OEE Installer Logs".

19. On End of Installation, select the Exit button.

3.9 Adding Additional Environments (Rerunning the Deployment Server Installer)

Caution:
If you want to add an additional environment that you did not install when you first ran the Deployment Server Installer, you must re-run the installer from the original disk image. You cannot re-run the installer using the OUI-based installer.
You can only use the installer located accessed by Start > All Programs > Oracle - JDE_DEP910_HOME > Oracle Installation Products > Universal Installer for deinstalling the Deployment Server.

To rerun the Deployment Server Installer, follow the instructions in the preceding section of this chapter entitled: Section 3.8, "Installing the Deployment Server"

3.10 Downloading and Installing the Latest Software

Caution:
You must start Change Assistant as Administrator. Right-click on the shortcut and select 'Run as Administrator from the drop-down.

Before continuing with the installation, download and install the latest Tools Release, Tools Release Patch, and Planner Update ESU from the JD Edwards EnterpriseOne Update Center.

Note:
The order in which the following Tools Release and updates are applied is very important. Do not deviate from the order described in these procedures.

This section discusses:

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

- Section 3.10.2, "Installing the Latest Planner Update and Running the Special Instructions"

3.10.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 the JD Edwards EnterpriseOne Update Center home page, download the latest Tools Release Patch (for example, 9.1.1.0) and Tools Release documentation.

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

Caution:
You must right-click on the executable and select Run as Administrator from the drop-down.

Note:
If you have ever used the Drag and Drop method of moving between Tools Releases for service packs, it is necessary to run the ReconfigureMSDE utility to encrypt the "system" database user's password. Refer to the section of this guide entitled: Section 3.11.5.9, "Encrypting the Password of the Local Oracle Database".

3.10.2 Installing the Latest Planner Update and Running the Special Instructions

Caution:
As part of the local database installation, which is bundled with the Deployment Server Installer, the password for the system user on the E1Local database is encrypted. If you re-set this password, several JD Edwards EnterpriseOne functions will fail. If you should inadvertently reset the password, you can encrypt it again to the expected default password. Refer to the section of this guide entitled: Section 3.11.5.9, "Encrypting the Password of the Local Oracle Database".

To install the latest planner update:

1. From My Oracle Support, download the latest planner update for your Tools Release 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. You must enter a valid JD Edwards EnterpriseOne user and password to initialize the Planner.
The shipped values are JDE for the user and JDE for the password.

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

4. When the installation finishes, view the JD Edwards EnterpriseOne Deployment Server Setup form to confirm that the installation was successful.

Tip:
If the folder into which you expanded the Planner Update is empty, you should run the self-extracting executable (JMnnnnn.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 is in this directory with this file name:
x:\download_directory\planner_update_id\E910SpecialInstructions.htm

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

Caution:
Every time you apply a new Planner Update you must run both of these:

- SpecialInstrs.bat

- R98403XB XJDE0002

3.11 Troubleshooting Deployment Server Installation

This section discusses:

- Section 3.11.2, "OEE Installer Logs"

- Section 3.11.3, "Configuration Files"

- Section 3.11.4, "Path Code Master (F98611)"

- Section 3.11.5, "Oracle Enterprise Edition"

3.11.1 Verify Local Planner Tablespaces are Not Attached

If you are re-installing your Deployment Server, you must ensure that the local Planner tablespaces (OEE) are not attached. To detach the tablespaces, run these batch files:

jdedwards\e910\planner\data\detach_planner.bat

jdedwards\e910\planner\data\detach_metadata.bat

3.11.2 OEE Installer Logs

This section lists the log files for installations on the Deployment Server:

- x:\jdedebug.log

Note:
The location is defined by this jde.ini setting:
[DEBUG]
DebugFile=d:\jdedebug.log

- x:\jde.log

Note:
The location is defined by this jde.ini setting:
[DEBUG]
JobFile=D:\jde.log

- C:\ReconfigureMSDE.log

- \InstallLogs\attach_plannerdata.log

- \InstallLogs\attach_plannerspec.log

- \InstallLogs\Configurexxxspec.log
Where xxx denotes that there are several of these logs, which contain logging for predefined package specs. For example:

ConfigureDV910FAspec.log

- X:\JDEdwards\E910\Detachxxx.log
Where xxx denotes that there are several of these logs, which contain logging for predefined package specs. For example:

DetachDV910FAspec.log

See Also

For OEE-specific logs, refer to Section 3.11.5.1.2, "OEE Logs" in this chapter.

3.11.3 Configuration Files

Note:
This section is provided for reference. You are not required to manually configure these files because the Deployment Server installer configures the .ini files appropriately for the OEE local database.

The data source definitions for OEE are defined in these configuration files:

- jde.ini

- jdbj.ini

The following lists some of the settings within the various configuration files that are related to the local database.

- jde.ini

[DB SYSTEM SETTINGS]
Type=E
LOBFlag=Y

[DB SYSTEM SETTINGS  ' SECONDARY]
Type=E
LOBFlag=Y

- jdbj.ini
The jdbj.ini file specifies location of the tnsnames.ora file.

The jdbj.ini file also specifies the JDBC driver for Oracle as ojdbc5.jar, which replaces the version (classes12.jar) used in prior releases of JD Edwards EnterpriseOne.

[JDBj-BOOTSTRAP DATA SOURCE]
databaseType=E
lob=true

[JDBj-SPEC DATA SOURCE]
databaseType=E
lob=true

[JDBj-JDBC DRIVERS]
ORACLE=oracle.jdbc.driver.OracleDriver

Caution:
The shipped jdbj.ini file in the following folder contains specifications for each database type:
System\OC4J\j2ee\home\applications\ webclient.ear\webclient\WEB-INF\classes

You must manually comment out (with a semicolon) every database driver that you are not using. For example, if you are connecting to only Oracle databases, your file would look like this:

[JDBj-JDBC DRIVERS]
ORACLE=oracle.jdbc.driver.OracleDriver
;AS400=com.ibm.as400.access.AS400JDBCDriver
;SQLSERVER=com.microsoft.sqlserver.jdbc.SQLServerDriver
;UDB=COM.ibm.db2.jdbc.app.DB2Driver

3.11.4 Path Code Master (F98611)

The Path Code Master (F98611) contains changes to support OEE. It contains values for use of EMDBSY column to indicate type of specs and type of local database. These values are used by JDB, JDBj, and Package Build.

EMDBSY Value

Spec Type

Local DB Type

0

TAM

MSDE

1

XML

MSDE

2

TAM

SSE

3

XML

SSE

5

XML

Oracle

3.11.5 Oracle Enterprise Edition

This section discusses these topics:

- Section 3.11.5.1, "File Locations"

- Section 3.11.5.2, "Rebooting the Deployment Server"

- Section 3.11.5.3, "EnterpriseOne Access to the Local Oracle Database"

- Section 3.11.5.4, "Process Explorer"

- Section 3.11.5.5, "Verifying the Local Oracle Database Installation"

- Section 3.11.5.6, "Deployment Server Installation Problems"

- Section 3.11.5.7, "Runtime Problems"

- Section 3.11.5.8, "Administering the Local Oracle Database Using SQL Plus"

- Section 3.11.5.9, "Encrypting the Password of the Local Oracle Database"

- Section 3.11.5.10, "Decrypting the Password of the Local Oracle Database"

- Section 3.11.5.11, "Import and Export Tablespaces to the Local Oracle Database"

- Section 3.11.5.12, "Updating the InstallManager.htm File"

- Section 3.11.5.13, "Deployment.inf and <Package_name>.inf"

3.11.5.1 File Locations

This section discusses the location for these critical files:

- Section 3.11.5.1.1, "Oracle Installation Directory"

- Section 3.11.5.1.2, "OEE Logs"

- Section 3.11.5.1.3, "tnsnames.ora"

3.11.5.1.1 Oracle Installation Directory

Deployment Server. The default installation location of the local Oracle database on the Deployment Server is:

C:\Oracle\E1Local

Note:
This location can be changed at installation time.

Client. The default installation location of the local Oracle database on the Web Development Client (also called the Administration client or fat client or workstation) is:

C:\Oracle\E1Local

Note:
This location can be changed at installation time.

3.11.5.1.2 OEE Logs

The following table lists the locations of the various log files.

Log File

Location

Import for Planner databases

<E1_install_dir>\planner\Data\Imp*.log

Import for Planner specs

<E1_install_dir>\planner\spec\Imp*.log

Oracle import log for package specifications (created during Install and also during Package Workbench)

<E1_install_dir>\<pathcode>\package\<pkg_name>\Spec\imp*.log and Imp*.log

Oracle export log for specifications (created during Install and also during Package Workbench)

<E1_install_dir>\<pathcode>\package\<pkg_name>\Spec\exp*.log and Exp*.log

Local Oracle database runtime

C:\Oracle\diag\rdbms\e1local\e1local\alert\

Local Oracle database listener

C:\Oracle\diag\tnslsnr\<this_machine>\listener\alert\

Log for ReconfigureMSDE.exe

C:\ReconfigureMSDE.log

Local Oracle database install logs

c:\Program Files\Oracle\Inventory\logs

Log for OEESetup.exe

c:\OEEInstall.log

3.11.5.1.3 tnsnames.ora

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.11.5.2 Rebooting the Deployment Server

You must reboot the Deployment Server after installing or deinstalling the local Oracle database.

3.11.5.3 EnterpriseOne Access to the Local Oracle Database

The Deployment Server Installation Workbench generates and encrypts a password and then changes the local Oracle database "system" and "sys" accounts' passwords to that password. During the rest of the Installation Workbench and at runtime of the Deployment Server, the local Oracle database is accessed via the "system" account and this generated and encrypted password.

This table lists the relationship between the local Oracle database accounts and the password.

Local Oracle Database Account

Default Password

System

Generated and encrypted by the Deployment Server installer.

Sys

Generated and encrypted by the Deployment Server installer.

JDE

JDE
Note: The default password may be changed by DBA but if Security Server is not used, it must match the password of EnterpriseOne user JDE.

<tablespace_name>
For example:

- JDESY910

- JDEOL910

<tablespace_name>
For example:

- JDESY910

- JDEOL910

Note: The default password may be changed by DBA. This value does not affect the runtime operation of JD Edwards EnterpriseOne because it does not access the local Oracle database in this manner.

3.11.5.4 Process Explorer

If you cannot delete the directory for the E1Local Oracle Home because a process has it locked, you can use Process Explorer to determine which process has it locked, and subsequently kill that process.

To obtain Process Explorer, you can download and install a free version at this link:

http://technet.microsoft.com/en-us/sysinternals

To use Process Explorer:

1. Navigate to Find > Find Handle or DLL....

2. In the Handle or type field, enter the full name of the directory that cannot be deleted. For example:
c:\oracle\e1local

3. Click the Search button.

4. On the search results screen, note the PID(s) (Process IDs) that are associated with the specified directory.

5. Cancel the Process Explorer Search window to return to Process Explorer.

6. Use Process Explorer to kill the identified process(es).

Note:
If one or more of the processes is Windows Explorer (explorer.exe), killing it may cause the computer to lock up. If that happens, you will need to reboot the Deployment Server machine.
The process Oracle.exe is the local Oracle database engine. If it has a file locked, you can stop the service OracleServiceE1LOCAL.

7. If one or more of the processes locks a file in the directory you are trying to delete even after rebooting, you may have to determine which service is automatically starting that process and change the service to manual startup. Then reboot the Deployment Server machine and delete the directory.

3.11.5.5 Verifying the Local Oracle Database Installation

To verify that the installation of the local Oracle database was successful:

1. Inspect the latest logs in these directories:
<E1_install_dir>\InstallLogs

C:\Program Files\Oracle\Inventory\logs

2. Resolve any issues that are identified in the logs.

3.11.5.6 Deployment Server Installation Problems

You cannot reinstall the local Oracle database using the Deployment Server installer if there are indications that the local Oracle database already exists. The Deployment Server installer will skip the installation of the local Oracle database if either of these conditions is true:

- The local Oracle database service OracleServiceE1LOCAL is running.

- This registry key exists:
\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_E1Local

3.11.5.7 Runtime Problems

This section discusses:

- Section 3.11.5.7.1, "Jde.log shows ORA-12541: TNS:no listener"

- Section 3.11.5.7.2, "User gets a pop-up window prompting for E1Local DB user and password and Jde.log shows OCI0000141 - Error - ORA-01017: invalid username/password; logon denied"

- Section 3.11.5.7.3, "tnsnames.ora"

3.11.5.7.1 Jde.log shows ORA-12541: TNS:no listener

Verify that the Oracle listener service OracleE1LocalTNSListener is running. It is possible that the service may not have started due to slow bootup of the machine.

3.11.5.7.2 User gets a pop-up window prompting for E1Local DB user and password and Jde.log shows OCI0000141 - Error - ORA-01017: invalid username/password; logon denied

Verify that the E1Local database system account password is valid. If the following command executes successfully, it means that the password is not encrypted. If so, you must encrypt the password in order to enable database access.

SQLPlus.exe system/admin@E1Local

where "admin" is the password. This password may have been set to "admin" by one of the EnterpriseOne database scripts, or it may be a plain-text word that someone set by running ReconfigureMSDE.

If the password was decrypted with ReconfigureMSDE, you should re-encrypt it using ReconfigureMSDE.exe. Refer to to the section of this guide entitled: Section 3.11.5.9, "Encrypting the Password of the Local Oracle Database".

3.11.5.7.3 tnsnames.ora

When the Deployment Server installer installs the local Oracle database (E1Local), the \bin directory is added to the start of the Windows PATH. If you have both the local Oracle database and the Oracle client installed (for example, if you are connecting to an Oracle database on a machine other than the Deployment Server), the local Oracle database version of the executables and tnsnames.ora are used. In order to maintain functionality of the Oracle client, you should add the remote database server tnsnames entries into the tnsnames.ora used by E1Local, which is located in this directory:

<OEE_installation_path>\network\admin

By default, the <OEE_installation_path> is C:\Oracle\E1Local, but the actual value is specified during OEE installation.

3.11.5.8 Administering the Local Oracle Database Using SQL Plus

The command-prompt program SQLPlus.exe and GUI program SQL Developer are provided with the installation of the local Oracle database using the Deployment Server installer. You can use either tool to access the local Oracle database where both the user and default password are the same as the tablespace name. If using SQLPlus, the command to sign into a database is:

SQLPlus.exe <user>/<password>@E1Local

For example, if the tablespace JDESY910 exists in the E1Local database, use the following to sign in:

SQLPlus.exe JDESY910/JDESY910@E1Local

3.11.5.9 Encrypting the Password of the Local Oracle Database

JD Edwards EnterpriseOne connects to the local Oracle database (E1Local) through the system account using an encrypted password. Some of the administrative database scripts on the Deployment Server decrypt this password before submitting database commands. Upon exit, such programs subsequently then re-encrypt the password. If one of these scripts fails to complete (for example, it is killed or it otherwise dies) before it can encrypt the password again, EnterpriseOne will not be able to connect to the database. You can determine if this is the case by attempting to sign into the local Oracle database using this command:

SQLPlus.exe system/admin@E1Local

where "admin" is the default password that the scripts use.

If you can sign in, the password must still be decrypted. You must re-encrypt the system account password using the following steps for EnterpriseOne to operate correctly:

1. Locate this program:
<E1_install_dir>\system\bin32\ReconfigureMSDE.exe

2. Right click on ReconfigureMSDE.exe and select Run as administrator.

Tip:
Do not let the "MSDE" part of the program name mislead you. This program was originally created when EnterpriseOne supported Microsoft's MSDE database. It was not renamed when support for OEE was added.

3. Be sure the E1Local database is selected.

4. Enter the "system" user's old password (in this case, enter "admin" without the quotes) in the field "Change from password…."

5. Under "To password", click on "Encrypted E1 Password."

6. Click OK.

7. Click OK.

8. Watch the status bar at the bottom of the dialog for informational messages.

9. If changing the password fails, attempt to stop and restart the database services OracleServiceE1LOCAL and OracleE1LocalTNSListener and then retry ReconfigureMSDE.exe.

3.11.5.10 Decrypting the Password of the Local Oracle Database

To decrypt the system account password:

1. Locate this program:
<E1_install_dir>\system\bin32\ReconfigureMSDE.exe

2. Right click on ReconfigureMSDE.exe and select Run as administrator.

Tip:
Do not let the "MSDE" part of the program name mislead you. This program was originally created when EnterpriseOne supported Microsoft's MSDE database. It was not renamed when support for OEE was added.

3. Be sure the E1Local database is selected.

4. Under "Change from password…", click on "Encrypted E1 Password."

5. Enter the "system" user's new password in the field "To password."

6. Reenter the new password and click OK.

7. Click OK.

8. Watch the status bar at the bottom of the dialog for informational messages.

9. If changing the password fails, attempt to stop and restart the database services OracleServiceE1LOCAL and OracleE1LocalTNSListener and then retry ReconfigureMSDE.exe.

Caution:
If you manually decrypt the system account password, ensure that you re-encrypt the password before attempting to run JD Edwards EnterpriseOne. If the password is not encrypted, JD Edwards EnterpriseOne will fail because it cannot access the local Oracle database.

3.11.5.11 Import and Export Tablespaces to the Local Oracle Database

You can use the JD Edwards EnterpriseOne application P96717 to import and export tablespaces except the Planner. To import or export the Planner tablespaces, you must use scripts that are delivered with the installation of the Deployment Server. The scripts are located in this directory:

For Planner Databases:

<E1_install_dir>\planner\data

For local metadata repository database (for example, specs and serialized objects):

<E1_install_dir>\planner\spec

This section discusses:

- Section 3.11.5.11.1, "Import Tablespace Script (attach_planner.bat)"

- Section 3.11.5.11.2, "Export Tablespace Script (detach_planner.bat)"

3.11.5.11.1 Import Tablespace Script (attach_planner.bat)

To use the import tablespace script:

1. Navigate to the directory JDEdwards\E910\planner\data and run this script:
TestPlannerDBs.bat

2. Edit the attach_planner.bat file such that any tablespaces that you do not intend to import are commented out. These lines start with:
call %DATA_PATH%\IMPORT_TABLESPACE.BAT

3. Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.

4. Change directory to the location of the batch files.

5. Run the batch file to import the tablespace using this syntax:
attach_planner.bat <Oracle_dir> <E1_install_dir>

where <Oracle_dir> is the parent of the E1Local directory.

For example:

attach_planner.bat c:\Oracle c:\JDEdwards\E910

Note:
This import batch file for the local metadata repository is in the spec directory:
attach_metadata.bat

3.11.5.11.2 Export Tablespace Script (detach_planner.bat)

To use the export tablespace script:

1. Edit the jdedwards\E910\planner\data\detach_planner.bat file such that any tablespaces that you do not intend to import are commented out. These lines start with:
call %DATA_PATH%\EXPORT_TABLESPACE.BAT

2. Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.

3. Change directory to the location of the batch files.

4. Run the batch file to import the tablespace using this syntax:
detach_planner.bat <Oracle_dir> <E1_install_dir>

where <Oracle_dir> is the parent of the E1Local directory.

For example:

detach_planner.bat c:\Oracle c:\JDEdwards\E910

Note:
This export batch file for the local metadata repository is in the spec directory:
detach_metadata.bat

3.11.5.12 Updating the InstallManager.htm File

To install a database or the Development Client onto a Development Client machine, the user runs this program:

\\<deployment server name>\<release>\OneWorld Client Install\InstallManager.exe

This program displays a Graphical User Interface that provides several options for the user to perform. The options that InstallManager.exe displays are read from the file InstallManager.htm that resides in the same directory as InstallManager.exe.

The JD Edwards EnterpriseOne administrator can edit this file to rename the options or to add new options. Instructions are inside the file.

Caution:
Although InstallManager.htm is in HTML format, it is a restricted HTML that the InstallManager.exe can read. Some text file editing programs add extraneous HTML tags that InstallManager.exe cannot recognize.
The Microsoft Windows program Notepad.exe is an example of a program that is known to not add these extra tags, making it safe to use. Before you make any changes to the file, it is good practice to save a copy in case any changes that you make are not recognized by InstallManager.exe when it reads it.

Note that the installation path of the Development Client's installer (setup.exe) changed with Tools Release 9.1. This means that you will need to change the path of the Development Client's installer in the InstallManager.htm when you first install Tools Release 9.1 onto a Deployment Server that has a tools release prior to 9.1 installed.

The following is an example of a line in a pre-9.1 InstallManager.htm that creates the link to install the Development Client (this should be on a single line):

<a class="sectionItem" id="LaunchLink" link="setup.exe" href="InstallManager.htm">EnterpriseOne Client</a>

The Development Client's installer prior to Tools Release 9.1 is called setup.exe. It should be in the same directory as InstallManager.exe and InstallManager.htm. The value of the link in the above line should be a path and executable for the installer. If a relative path is used (for example, the path starts with neither a drive letter followed by a colon nor a backslash), the path is relative to the location of InstallManager.exe. If no path is given, Setup.exe and InstallManager.exe are in the same directory.

Here is an example of a similar line for Tools Release 9.1 (this should be on a single line):

<a class="sectionItem" id="LaunchLink" link="install\setup.exe" href="InstallManager.htm">EnterpriseOne Client</a>

Note the addition of this relative path: install. With Tools Release 9.1, the Development Client's installer (which, is also called setup.exe) is now located in a subdirectory called install under the path where InstallManager.exe resides.

3.11.5.13 Deployment.inf and <Package_name>.inf

The following lists specific settings within the Deployment.inf and <Package_name>.inf for OEE.

- Deployment.inf

[ThirdPartyApps]ORACLE=ThirdParty\ORACLE\OEESetup.exe,

- <Package_name>.inf (example from a DV910FA.inf file)

[Oracle Databases]
JDELocal_DV910=ORACLE
SPEC_DV910FA=ORACLE

[JDELocal_DV910]
SourceTableSpace=JDELocal
Server=127.0.0.1
UserID=SYSTEM
DataFileDestDir=$DDV910DATA\JDELocal_DV910.dbf
DumpFileDestDir=$DDV910DATA\JDELocal_DV910.dmp

[SPEC_DV910FA]
SourceTableSpace=SPEC_DV910FA
Server=127.0.0.1
UserID=SYSTEM
DataFileDestDir=$DDV910\Spec\SPEC_DV910FA.dbf
LogFileDestDir=$DDV910\Spec\SPEC_DV910FA.dmp

4 Working with the Platform Pack on the IBM i

This chapter discusses:

- Section 4.1, "Understanding the Platform Pack"

- Section 4.2, "Platform Pack Process Flow"

- Section 4.3, "Configuring the Enterprise Server Prior to Installing the Platform Pack"

- Section 4.4, "Understanding the Platform Pack Installation on the IBM i"

- Section 4.5, "Running the JD Edwards EnterpriseOne Platform Pack Installer for the IBM i"

- Section 4.6, "Troubleshooting the IBM i Platform Pack Installation"

- Section 4.7, "Rerunning the JD Edwards EnterpriseOne Platform Pack Installer"

- Section 4.8, "Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server"

- Section 4.9, "Working with Database Security"

4.1 Understanding the Platform Pack

The Platform Pack installs these major components:

- JD Edwards EnterpriseOne Server code

- JD Edwards EnterpriseOne database tables

Note:
To reinstall any Enterprise Server components, refer to Section 4.7, "Rerunning the JD Edwards EnterpriseOne Platform Pack Installer".

This table lists the mandatory and optional components of the Platform Pack installation:

Server

Mandatory Component

Optional Components

Enterprise Server

JD Edwards EnterpriseOne Foundation

ES Production
ES Prototype

ES Development

ES Pristine

Database Server

System Database

Production Databases
Prototype Databases

Development Databases

Pristine Databases

4.2 Platform Pack Process Flow

The Platform Pack installation process installs Release 9.1 system and path code files.

The diagram below illustrates the process flow for the Oracle Universal Installer for the JD Edwards EnterpriseOne Platform Pack.

4.3 Configuring the Enterprise Server Prior to Installing the Platform Pack

Install any IBM i server upgrades that are required to support Release 9.1.

Before you install Release 9.1 software on the Microsoft Windows Enterprise Server, you must create the Release 9.1 administrator user, verify disk space, and set up and verify the hosts file.

This section discusses:

- Section 4.3.1, "Understanding the Prerequisites"

- Section 4.3.2, "Understanding Security for the Platform Pack Installer"

- Section 4.3.3, "Setting the System Values"

- Section 4.3.4, "Setting up the TCP\IP Protocol for Enterprise Server"

- Section 4.3.5, "Setting up IBM i Access on your Enterprise Server"

- Section 4.3.6, "Starting the Remote Database TCP\IP Service (Optional)"

- Section 4.3.7, "Optimizing Machine Resources"

- Section 4.3.8, "Cleaning Up From Prior Installations"

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

- Section 4.3.10, "Checking for Co-existence Tables"

- Section 4.3.11, "Adding Entries to the System Reply List"

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

4.3.1 Understanding the Prerequisites

Verify this list of prerequisites is met prior to installing the JD Edwards EnterpriseOne Platform Pack on your IBM i-based Enterprise Server:

- Refer to the Language Process Overview for the National Language Support tables and other information related to multilingual installations.

- Install the requisite IBM i upgrades.

- Verify that you have met the hardware and software requirements for the Release 9.1 release you are installing. See Release 9.1 Hardware and Software Requirements.

- If you prefer to perform the configuration tasks in this chapter (set up TCP\IP and IBM i Access) in a language other than the language for which the IBM i is currently configured, change the value for the code character set ID. For example, to perform these configuration tasks in English, set the code character set ID to 37. After completing these configuration tasks, reset the code character set ID to its original value.

4.3.2 Understanding Security for the Platform Pack Installer

The following is a list of security actions performed by the JD Edwards EnterpriseOne Installer:

1. Recreates the ONEWORLD job description.

2. Creates the user profiles for JDE and ONEWORLD, each with user class *PGMR.

3. Grants the JDE user rights to the ONEWORLD user profile.

4. Grant rights to QRECOVERY library for users JDE and ONEWORLD so that they can create SQL Packages in there for UBEs and CALLOBJ kernels.

5. If the PSFT user profile exists, for each environment that you are upgrading, uses GRTOBJAUT to grant authority for all tables in business data and control tables for JDE.

4.3.3 Setting the System Values

Because the JD Edwards EnterpriseOne Platform Pack Installer cannot run with the default QJOBMSGQFL system value, you may need to change it.

To verify the existing QJOBMSGQFL system value, and change if necessary:

1. Enter this command:
WRKSYSVAL QJOBMSGQFL

2. Enter option 5.
If the value displayed is *NOWRAP, you must change it to *WRAP or *PRTWRAP. Be sure to note the existing value so you can reset it after you complete the JD Edwards EnterpriseOne Platform Pack installation.

To allow the JD Edwards EnterpriseOne services to run, you must change the value for QUSEADPAUT to *NONE before installing the Enterprise Services. Then once the JD Edwards EnterpriseOne Platform Pack installation is complete, you can change this value back to its original setting.

To set the system values:

1. Enter this command:

WRKSYSVAL QUSEADPAUT

2. Enter option 5.
If the value displayed is anything other than *NONE, you must change from that value to *NONE. Be sure and note the existing value so you can reset it after you complete the installation of the JD Edwards EnterpriseOne Platform Pack.

4.3.4 Setting up the TCP\IP Protocol for Enterprise Server

Note:
Set up the TCP\IP service to start automatically each time you IPL the IBM i. For more information about setting it up, contact your system administrator or see the appropriate IBM documentation.

To set up the TCP\IP protocol for your IBM i Enterprise Server:

1. Log on to the Enterprise Server as QSECOFR (or as any user who can access the Configure TCP\IP menu).

2. On Current OneWorld Versions, choose the version of the software for which you are setting up the TCP\IP protocol.

3. To access the Configure TCP\IP menu, enter CFGTCP.

4. Select Work With TCP\IP Host Table Entries.

5. On Work With TCP\IP Host Table Entries, find the network (Internet) address for the Enterprise Server.
A single machine could have more than one entry for the same network address. Verify that an entry exists for the Enterprise Server network address and that it matches the format that follows. Search for the Enterprise Server network address by entering the Enterprise Server name only (for example, SYS1). If one does not exist, you must add one by choosing Add.

In the Host Name field, your Enterprise Server (machine) name should appear in this format:

hostname.domainname

where hostname is the name of your machine and domainname is the local domain of the machine on the network. For example, SYS1.MFG.ABC.COM, in which SYS1 is the Enterprise Server name and MFG.ABC.COM is the domain name. The combined Enterprise Server name and local domain name represent the location of the Enterprise Server on the network.

Note:
Network Considerations. To avoid problems when applications running on separate machines need to communicate with applications running on other machines on the same network, make sure that each machine name (host name) has a single unique dot decimal address. For example, SYS1 could have a dot decimal address of, for instance, 140.252.13.33, but you could not assign any other address to it.

6. To verify that the local domain and Enterprise Server names represent the correct location of the IBM i, choose Change Local Domain and Host Names from the Work With TCP\IP Host Table Entries form.
Verify that the Local Domain Name and Local Host Name fields match the combined hostname.domainname network address.

Following the example in this task, the local domain name would be MFG.ABC.COM and the local host name would be SYS1.

4.3.5 Setting up IBM i Access on your Enterprise Server

The IBM i Access terminal emulation program enables workstations to communicate with IBM i servers. This task describes the procedure to set up the component of IBM i Access that runs on the IBM i server.

To set up IBM i Access on your JD Edwards EnterpriseOne Enterprise Server:

1. To determine the number of prestart jobs that are available and have been submitted for program QZDASOINIT, enter this command:
DSPACTPJ QUSRWRK QSYS\QZDASOINIT

Information about the number of your system's prestart jobs, prestart jobs submitted, and program start requests appears.

The number of prestart jobs depends on the number of concurrent and active ODBC user connections. This change is iterative as users or applications are added or removed. If you do not have enough prestart jobs, your system could be slow to make connections. If connections fail, they could be successful with the second attempt. If too many prestart jobs are waiting, the system will end some of them automatically. Also, the system initiates prestart jobs as additional ones are submitted.

Note:
Troubleshooting. To determine the number of prestart jobs you should set up, be aware that each OneWorld user typically uses three to five ODBC connections. Each ODBC connection uses one QZDASOINIT program. Therefore, the initial value for QZDASOINIT could be set to four times the number of expected concurrent connected users.

The current maximum number of prestart jobs is 9,999. If more jobs are needed, they will be created as necessary.

2. To see the current settings, enter this command:
DSPSBSD QUSRWRK

3. Choose option 10, and then choose option 5 for program QSYS\QZDASOINIT.

4. To access the form on which you can change the number of prestart jobs, enter this command and press F4 to prompt:
CHGPJE

5. Change the number of prestart jobs as needed, and then press Enter.

6. Restart the QUSRWRK subsystem for your changes to take effect.

4.3.6 Starting the Remote Database TCP\IP Service (Optional)

If your installation will have separate IBM i machines for the Enterprise Server and the Data Server, you will need to start the remote database TCP\IP service on the Enterprise Server.

To start the remote database TCP\IP service:

1. Enter this command:

STRTCPSVR SERVER(*EDRSQL)

2. In order to change the attribute of this server to autostart when TCPIP starts, you will need to use IBM i Navigator from a Microsoft Windows client:

1. Open the node for your IBM i machine.

2. Open the Network node.

3. Open the Servers node.

4. Double click on TCPIP.
A list of TCPIP servers is displayed in the right hand pane.

5. Right click on EDRSQL, select Properties, and enable the option Start when TCP\IP Starts.

Tip:
You can also start and stop this server from this screen.

4.3.7 Optimizing Machine Resources

Ideally you should run the Platform Pack Installer when the machine is not busy. However, if there are other processes running on the same IBM i as the Installer, their performance will be impacted by the Platform Pack installation.

The Platform pack install uses a prestart job in the QUSRWRK subsystem (program QZRCSRVS) which does Restores. This job runs at priority 20. In order to reduce the performance impact of this job, you can change its run priority during the install.

To change the run priority of the install job running in the QUSRWRK subsystem and optimize machine resources:

1. Enter this command:
WRKACTJOB SBS(QUSRWRK)

2. Look for the job running program QZRCSRVS, type option 5 next to it, and press Enter.
If there is more than one job running QZRCSRVS, the one using the most machine resources is most likely the one running the Platform Pack Installer. You can also check the job logs to find jobs unique to the Platform Pack Installer. Examples of such jobs are restores and CHGOBJOWN.

3. For the job you selected in the previous step, enter option 40 (change job) press Enter.

4. Enter 51 as the Run Priority and press Enter.

4.3.8 Cleaning Up From Prior Installations

If you have previously run the Platform Pack installer on your IBM i machine, prior to re-running it you must ensure that all QACX ' files are cleared from this folder:

\tmp\

4.3.9 Testing Long File Names on the IBM i

Before running Installation Workbench, you may need to rebuild the cross-reference table. This table enables tables of long (more than 10 characters) file names to be created on the IBM i. Rebuilding the table causes your system to be in a restrictive state. Coordinate this activity with the system administrator.

To test long file names 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 you are unable to create the table with a long name, likely your system cross reference tables are corrupt. You must rebuild them before proceeding. Refer to Rebuilding Cross Reference Tables on the IBM i.

4.3.10 Checking for Co-existence Tables

Before running the Table Conversion Workbench, you must check whether any of your tables are in Co-Existence (DDS) format. If you run Table Conversions against DDS format tables it will lead to data corruption and cause TCs to fail.

Use this procedure to check for co-existence tables:

1. Log on to the IBMi as QSECOFR.

2. On the command line, start a SQL session by entering this command:
STRSQL

3. Run the following SQL statement, substituting in your Control Tables and Business Data library names

SELECT TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE FROM SYSTABLES WHERE TABLE_SCHEMA
IN ('PRODCTL','PRODDTA') AND TABLE_TYPE = 'P'

where

TABLE_TYPE='P' is DDS (World-created) tables

TABLE_TYPE='T' is SQL (EnterpriseOne created) tables

If there are DDS created tables in these libraries, you must follow the additional procedures in the Co-Existence Upgrade Guide (Doc ID: 702770.1), which is located on My Oracle Support.

4.3.11 Adding Entries to the System Reply List

To add entries to the System Reply List:

1. Verify the existing entries in the Reply List with this command:
WRKRPYLE

2. Verify that this entry does not exist and that the sequence number 3283 has not been used:
ADDRPYLE SEQNBR(3283) MSGID(CPA32B2) RPY('I')

3. If the above entry does not exist, you can add it using this command:
ADDRPYLE SEQNBR(3283) MSGID(CPA32B2) RPY('I')

4.3.12 Rebuilding Cross Reference Tables on the IBM i

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 table is now rebuilt and ready for use.

4.4 Understanding the Platform Pack Installation on the IBM i

The Platform Pack installation process installs Release 9.1 system and database files on the IBM i. The Platform Pack installer does not run on the IBM i machine; it can only run on a Microsoft Windows machine. Oracle recommends that you run the installer from the JD Edwards EnterpriseOne Deployment Server so that the Oracle Inventory and install history will be preserved. As a prerequisite to running the installer, IBM i Access for Windows must be installed on the Deployment Server.

Caution:
In some cases the JDEOW library may not be properly updated with the new JD Edwards EnterpriseOne programs as expected during the JD Edwards EnterpriseOne Upgrade process. To ensure the new JD Edwards EnterpriseOne programs are properly installed, rename your existing JDEOW library prior to running the JD Edwards EnterpriseOne Platform Pack Installer.
To rename JDEOW, run the following command while signed onto your IBM i JD Edwards EnterpriseOne server:

RNMOBJ OBJ(QSYS\JDEOW) OBJTYPE(*LIB) NEWOBJ(JDEOW_SAVE)

Note:
If you are installing any JD Edwards EnterpriseOne component on multiple IBM i machines (for example, if you are installing multiple logic servers), you must run the Platform Pack installer from a different Microsoft Windows machine for each separate machine you install. Otherwise, the installer detects that some components (for example Foundation for a logic server) have already been installed, and by design ignores subsequent requests to install the same component, regardless of whether the installation is intended for a different target machine.

4.5 Running the JD Edwards EnterpriseOne Platform Pack Installer for the IBM i

The user profile you specify during the Platform Pack install must not be limited by network security. Most of the Platform Pack install is done through commands and JAVA code that uses TCP\IP to send work between various OS\400 service jobs. To find out whether there are network security limitations in place:

1. Enter the WRKREGINF command.

2. Page down to the QIBM_QZ* entries which are for the IBM i Access Host Servers.

3. Use Option 8 on any of these to see if an exit program is in place.

In addition, a Platform Pack installer failure can occur if any of the RSTxxx commands have been changed from the IBM defaults relative to the environments in which they can run.

To run the JD Edwards EnterpriseOne Platform Pack Installer for the IBM i Enterprise Server:

1. Log on to the Microsoft Windows machine where you will be running the Platform Pack installer for IBM i. If you follow the recommendation, this will be the JD Edwards EnterpriseOne Deployment Server.

Caution:
Ensure that the Administrator account name that you use does not contain any special characters.

2. Create a folder into which you will copy the two .zip files that comprise the Platform Pack image. For example, the folder might be named:
c:\IBMPPack

3. Extract the two zip files within the root of the folder created above. Using the example in this guide, a correctly extracted structure is:

4. Locate the jt400.jar and util400.jar from the location where you installed IBM i Access for Windows. For example, the location might be:
c:\Program Files\IBM\Client Access\jt400\lib

5. Copy these two .jar files to this structure in your install image:
..\stage\ext\jlib

6. In the above extracted structure, locate the setup.exe file under the \install subdirectory, right-click on it, and select Run as Administrator.

Note:
The Oracle Universal Installer takes a few minutes to start up.

7. On Welcome, click the Next button.

8. On Select Installation Type, choose your installation type:

- Typical
Choose this setup type if you wish to complete the Platform Pack installation with no further specifications. This installation option is recommended for most users and includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.

- Custom
This mode is recommended for experienced users, choose this setup type if you wish to complete the Platform Pack installation by specifying the installation of a subset of pre-defined environments.

- Custom
In most cases this is the mode you should choose for Upgrades.

This mode is recommended for experienced users, choose this setup type if you wish to complete the Platform Pack installation by specifying the installation of a subset of pre-defined environments.

Tip:
If you choose Custom installation, continue with the steps below in this task which immediately follow.

- Typical
Choose this setup type if you wish to complete the Platform Pack installation with no further specifications. This installation option includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.

- Click the Next button.

9. On Specify Home Details, complete these fields:

- Name
Enter a unique name for the JD Edwards EnterpriseOne Platform Pack installation. For example:

JDE_PPack910_HOME

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.

- Path
Enter the drive and directory where you want the installer files installed on your Deployment Server (from where you are running the Platform Pack installer). For example:

Z:\JDEdwardsPPack\E910

This process will store files directly related to the OUI installer (for example, the OUI inventory) in this location. This does not affect where libraries and paths are created on the IBMi.

10. Click the Next button.
If you chose the Typical installation type, the Available Products screen will not display; you can skip to the Step 12.

If you chose the Custom installation type, the Oracle Universal Installer displays a list of available JD Edwards EnterpriseOne product components, as shown in the example below:

Tip:
Use the scroll bar to on the right hand side of the screen to view the complete list of available components. This is shown in the following screen sample.

On Available Product Components, select from these choices:

JD Edwards EnterpriseOne Database Server

- System Database

Note:
This selection includes mandatory system files. If you do not select this box, the JD Edwards EnterpriseOne Platform Pack Installer will select this component. Likewise, if you rerun the JD Edwards EnterpriseOne Platform Pack Installer to add an environment it will check to ensure that this component is already installed. Also if rerunning, you will not be given an option to install the environment in a different ORACLE_HOME.

- Production Databases

- Prototype Databases

- Development Databases

- Pristine Databases

JD Edwards EnterpriseOne Enterprise Server

- JD Edwards EnterpriseOne Foundation

Note:
This selection includes system files. You must choose this feature for all initial installations of the Enterprise Server. If you do not select this feature, the JD Edwards EnterpriseOne Platform Pack Installer automatically selects it for installation.

- ES Production

- ES Prototype

- ES Development

- ES Pristine

Note:
For Upgrades, you should always select the Pristine environment. Otherwise, Table Conversions may not process correctly.

11. After you have verified your selection of components, click the Next button.

12. On Would you like to Install or Upgrade EnterpriseOne?, choose whether you want to install or upgrade JD Edwards EnterpriseOne. The list below describes each run mode.

- Install (Install EnterpriseOne)
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:

- DV910

- PD910

- PY910

- TESTDTA

- PRODDTA

- CRPDTA

- TESTCTL

- PRODCTL

- CRPCTL

- Upgrade (Upgrade EnterpriseOne)
In this mode, the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of the Business Data and Control Tables libraries which are prerequisites to an upgrade of JD Edwards EnterpriseOne.

Caution:
You should always back up all databases that you want to preserve.

13. Click the Next button.

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

- 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.

- 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.

15. Click the Next button.
If the installer begins with no errors, you can proceed to the Step 16. Otherwise, refer to the next section of this guide entilted: Section 4.6, "Troubleshooting the IBM i Platform Pack Installation".

If all specified conditions are valid, the installer displays the Summary screen.

16. On Summary, in the top half of the screen review your selections and in the bottom half of the screen review the NOTES, which detail the disk space requirements for OUI support files and also for the Platform Pack being installed on the IBM i machine.

17. Click the Install button.
As the installer runs it displays the Install progress, as shown in the following example.

After the installation is complete, the following End of Installation screen is displayed.

18. On End of Installation, verify the installation of the EnterpriseOne Platform Pack was successful.
Review the Please remember ... portion for the installer log file location. The log file name is specified with the date and stamp when the installer ran. For example:

c:\Program Files (x86)\Oracle\Inventory\logs\installActions2011-09-14_03-40-11-PM.log

19. Click the Exit button to exit OUI.

20. On Exit, click the Yes button.

4.6 Troubleshooting the IBM i Platform Pack Installation

This section discusses these potential error or warning conditions and their probable causes and resolutions when running the JD Edwards EnterpriseOne Platform Pack Installer:

- Section 4.6.1, "Invalid User or Password"

- Section 4.6.2, "Abnormal Program Termination - jt400.jar and/or utill.jar Missing"

- Section 4.6.3, "Business Data or Control Tables Already Exist"

- Section 4.6.4, "Business Data or Control Tables Do Not Exist"

4.6.1 Invalid User or Password

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.

4.6.2 Abnormal Program Termination - jt400.jar and/or utill.jar Missing

If you receive the following message, it indicates that you have failed to correctly copy the jt400.jar and util400.jar into the ..\stage\ext\jlib directory. To remedy, you must copy these files to the appropriate directory, exit from the installer, and restart the installer.

4.6.3 Business Data or Control Tables Already Exist

If you select Install Mode and the Business Data or Control Tables already exist, the installer displays the following error:

To remedy the above error, your choices are: must: or Deselect the Prototype Database or

- Change the Install Type to Upgrade

- Deselect the Prototype Database

- Delete the CRPDTA and CRPCTL library (if they are empty)

4.6.4 Business Data or Control Tables Do Not Exist

The following is displayed if you selected the Upgrade mode but the Business Data or Control Tables do not exist:

4.7 Rerunning the JD Edwards EnterpriseOne Platform Pack Installer

You must rerun the JD Edwards EnterpriseOne Platform Pack Installer to support these scenarios:

- You want to install the Enterprise Server and the Database Server on physically different machines.

- You want to add an Enterprise Server environment to the Enterprise Server.

- You want to add a Database Server database to the Database Server.

- You want to reinstall the JD Edwards EnterpriseOne Foundation on the Enterprise Server.

- You want to reinstall the System Database on the Database Server.

You should never reinstall any optional components without first uninstalling the components. If you select to uninstall the mandatory components you must also select to uninstall or have already uninstalled all related optional components. This table lists the mandatory and related optional components:

Server

Mandatory Component

Optional Components

Enterprise Server

JD Edwards EnterpriseOne Foundation

ES Production
ES Prototype

ES Development

ES Pristine

Database Server

System Database

Production Databases
Prototype Databases

Development Databases

Pristine Databases

4.7.1 Enterprise Server

If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add environments, you must specify the same DB2/400 instance as that which you selected for JD Edwards EnterpriseOne Foundation during the initial installation of the Platform Pack.

Note:
If you are installing any JD Edwards EnterpriseOne component on multiple IBM i machines (for example, if you are installing multiple logic servers), you must run the Platform Pack installer from a different Microsoft Windows machine for each separate machine you install. Otherwise, the installer detects that some components (for example Foundation for a logic server) have already been installed, and by design ignores subsequent requests to install the same component, regardless of whether the installation is intended for a different target machine.

4.7.2 Database Server

If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add databases, you must specify the same DB2/400 instance as that which you selected for System Database during the initial installation of the Platform Pack.

4.8 Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server

Caution:
The Tools Release level must match what was installed on the Deployment Server.
For instructions on installing the tools release, refer to JD Edwards EnterpriseOne Tools Release 8.98 Installation Guide, which is available by platform.

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

1. From the Update Center home page, download the latest Tools Release Patch (for example, 9.1.A1) and Tools Release documentation.

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

4.9 Working with Database Security

The libraries and tables delivered by the Platform Pack installation are not secured. In order to provide sufficient security, you should run the tool SETOWAUT which allows you to 'lock down ' libraries and IFS directories delivered by the Platform Pack installation. You can obtain the latest version of the SETOWAUT tool from the Update Center using the Change Assistant.

In order to maximize your database security, you should change the passwords on all table owners created during the Platform Pack installation; these are created with the user and password equal to the same value. Such a user and password relationship could expose you to worms and viruses aimed at gaining access to your database. Consult with your DBA for advice on changing passwords to meet the security requirements of your database installation.

The Installation Workbench assumes that the database user is JDE and that the password is the same, unless it finds this override in the jde.ini file on the Deployment Server. Once the database passwords have been changed, you will need to add this section to the jde.ini file:

[DSPWD]
JDE=new_password

For example, if you changed the password for JDE to alaska5, your section would look like this:

[DSPWD]
JDE=alaska5

Caution:
The Installation Workbench can only process passwords equal to or less than 10 characters in length. Therefore, you cannot use passwords greater than 10 characters even if your RDMS allows it.

After you change the [DSPWD] section of the jde.ini file, logon to OneWorld in the JDEPLAN environment on the Deployment Server with the new password in the correct case.

Caution:
Whenever you change the password on your database, as recommended for security purposes, you must also ensure that your security settings in the Enterprise Server jde.ini file match that of your database. Refer to Chapter 11, "Working With Signon Security" in this guide for applicable instructions.
You should secure the jde.ini file on the Deployment Server to prevent unauthorized access.

You should delete the [DSPWD] section once the install or upgrade is complete.

Note:
If you are upgrading from JD Edwards EnterpriseOne Releases 8.10 or 8.11, you should consider disabling the legacy user, which is PSFT.

5 Working with Installation Planner for an Install

This chapter discusses:

- Section 5.1, "Understanding Installation Planner"

- Section 5.2, "Working with JD Edwards EnterpriseOne Software Requirements"

- Section 5.3, "Reviewing Installation Planner Processing Options"

- Section 5.4, "Working with a Typical Installation Plan"

- Section 5.5, "Creating a Custom Installation Plan"

- Section 5.6, "Deleting Machines from an Installation Plan"

See Also

- A separate chapter in this guide entitled: Chapter 15, "Creating a Remote Installation Plan"

- A separate chapter in this guide entitled: Chapter 16, "Adding a Server to an Existing Configuration"

- A separate chapter in this guide entitled: Chapter 17, "Creating a Language-Only Installation Plan,"

5.1 Understanding Installation Planner

Installation Planner is a Release 9.1 application that runs on the Deployment Server. It is a system administration tool to guide through the process of configuring the machines on which you will run Release 9.1.

Installation Planner guides you through setting up:

- Section 5.1.1, "Language Information"

- Section 5.1.2, "Location Information"

- Section 5.1.3, "Deployment Server Information"

- Section 5.1.4, "Enterprise Server Information"

- Section 5.1.5, "JD Edwards EnterpriseOne HTML Web Server Information"

- Section 5.1.6, "Data Source Information"

- Section 5.1.7, "Environment Information"

5.1.1 Language Information

Installation Planner enables you to create a plan for installing an alternate language or multiple languages as you create your master plan.

- You should follow the system prompts to choose which languages will be installed for each environment.

- For initial installations, you can complete your master plan and install languages later by creating a language-only plan. Refer to Chapter 17, "Creating a Language-Only Installation Plan" for more information about setting up an alternate language after the master plan.

5.1.2 Location Information

Locations are user-defined groups of machines, databases, and environments. The use of multiple locations is recommended for configurations across a wide area network (WAN).

Two types of locations exist: base locations and remote locations. Each installation plan can have only one base location. It is the central point for planning and executing the deployment process. The base location does not have a parent location and does not use a location code. You can have any number of tiered locations; each has a parent location and a location code.

To set up locations for installation plans, you must provide the installation program with the location, location description, location code (if there is a secondary location), and parent location (if there is a secondary location).

The location code is a three-character alphanumeric code that you specify. This location code is used as part of the name of the data sources for secondary locations in the plan. Locations are stored in the Deployment Locations Definition table (F9654).

See Also

Refer to Chapter 15, "Creating a Remote Installation Plan" for information about setting up remote locations.

5.1.3 Deployment Server Information

To set up the plan information for the Deployment Server, you must provide the installation program with the machine name and the directory share name. This information populates the Release Master (F00945) and Path Code (F00942) tables, and stores additional Deployment Server information in the Machine Master (F9650) and Machine Detail (F9651) tables.

Note:
If you installed JD EnterpriseOne files to a remote Deployment Server, the deployment server name is the remote machine name by default.

5.1.4 Enterprise Server Information

To set up the plan for the Enterprise Server, you must provide Installation Planner with the name of the Enterprise Server, its platform type, and the database it uses. Installation Planner populates the F9650 and F9651 Enterprise Server tables and defines the data sources for the Enterprise Server. The Data Source information is stored in the Data Source Master table (F98611).

5.1.5 JD Edwards EnterpriseOne HTML Web Server Information

To set up the plan for the JD Edwards EnterpriseOne HTML Web Server, you must provide Installation Planner with the name of the HTML Web Server machine, its platform type, and other information. Installation Planner populates the F9650 and F9651 Enterprise Server tables.

5.1.6 Data Source Information

When you run Installation Planner, these data sources are set up once and shared across all environments:

- Server Map
Server Map data sources are specific to each Enterprise Server, so you must create one for each server.

- Data Dictionary
This is the data source for the Release 9.1 Data Dictionary tables. It is identified by the Release 9.1 release (for example, Data Dictionary - 910).

- Object Librarian
This is the data source for the Object Librarian tables. It is identified by the Release 9.1 release (for example, Object Librarian - 910).

- System
The data source for the System tables. It is identified by the Release 9.1 release (for example, System - 910).

You must also set up these data sources for each environment:

- Control Tables
This is the data source for the Control Tables. You can have multiples (for example, Control Tables - Prod, Control Tables - Test, and Control Tables - CRP).

- Central Objects
The data source for the Central Objects specification tables is identified by the type and version number of the software. You can have multiple sets of Central Objects specifications (for example, Central Objects - PD910, Central Objects - PS910, Central Objects - DV910, and Central Objects - PY910). However, you can have only one Central Objects data source for each path code.

- Business Data
This is the data source for the Business Data tables. You can have multiple sets of Business Data data sources (for example, Business Data - CRP, Business Data - PROD, Business Data - TEST, and Business Data - PS910).

Depending on the environment you create, the Business Data data source can be your test, production, or any other data library that resides on your IBM i. When prompted for the Business Data data source during Installation Planner, modify this data source to call the library on the IBM i for this environment. You can also create a new Business Data library on your IBM i. This new Business Data data source might or might not have data, depending on the type of Release 9.1 environment you create. If you build additional environments on your IBM i to use with Release 9.1, you will create one or more of these libraries before running Installation Workbench:

- PS910DTA

- CRPDTA

- TESTDTA

- PRODDTA

- Versions
The data source for the Versions List table (F983051). You can have multiple sets of versions tables (for example, Versions - PD910, Versions - PS910, Versions - DV910, and Versions - PY910). However, you can have only one Versions data source for each path code.

See Also

Chapter 21, "Major Technical Tables" for more information about individual tables and their uses

5.1.7 Environment Information

Installation Planner enables you to select default environments for your installation that are predefined, or you can choose to define them manually. Likewise, Installation Planner enables data load using default data load options, or you can choose to define them manually and override the default data load options.

5.2 Working with JD Edwards EnterpriseOne Software Requirements

The goal of the JD Edwards EnterpriseOne Release 9.1 Installation is to include the most current tools releases and updates at the time the installation image is mastered. However, subsequent to that time it is possible that critical fixes may become necessary and available. You should check Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)" to verify if any such JD Edwards EnterpriseOne Release 9.1 Installation fixes are required.

5.3 Reviewing Installation Planner Processing Options

Processing options control how Installation Planner responds as you set up plans and options you see as you work through the custom planner. If processing options are not set up correctly, you will not see the appropriate options as you work through the planner. You set up these processing options to control replication functions and business functions mapping.

You should review the default processing options for the Installation Planner application prerequisite to create the plan. First-time users can set up the processing options to step through the planner with informational messages. If you do not want to see these messages, you can turn them off.

5.3.1 Assumptions About Reviewing Installation Planner Processing Options

This table lists the assumptions about reviewing the processing options for the installation planner.

Personnel

Installer

Logon Status

On the Deployment Server, logged on as user JDE with the database password for user JDE, in the Planner environment.

Prerequisites

The Deployment Server must be installed.

Concurrent Tasks

The Platform Pack installer can be running.

5.3.2 Accessing Processing Options

To access processing options, you must first log on to Release 9.1 and specify your installation plan type.

1. Log on to Release 9.1 as user JDE with the database password for user JDE.

2. Access the planner environment (JDEPLAN).

3. From the System Installation Tools menu (GH961), right-click either Typical Installation Plan or Custom Installation Plan.

4. Choose Prompt for Values.
The Processing Options form appears.

5.3.3 Choosing Processing Option Values

Once you have accessed processing options, perform the following tasks to choose the processing option values:

- Section 5.3.3.1, "Specifying the Prompt Mode"

- Section 5.3.3.2, "Specifying the Process Mode"

- Section 5.3.3.3, "Specifying the Default Mode"

- Section 5.3.3.4, "Verifying Status Change Values Have Not Changed"

- Section 5.3.3.5, "Specifying Plan Completion Processes"

- Section 5.3.3.6, "Specifying Replication Options"

5.3.3.1 Specifying the Prompt Mode

To specify the prompt mode:

1. Select the Prompt Mode tab.

2. On the Prompt Mode tab, select a prompt mode:

Value

Model

Description

0

Silent

Installation Planner displays only the data entry forms.

1

Additions Prompt

Installation Planner prompts you to add servers.

2

Verbose

Installation Planner directs you through creating a plan with a series of prompting forms.

5.3.3.2 Specifying the Process Mode

To specify the process mode:

1. Select the Process Mode tab.

2. On the Process Mode tab, select the options for the processes that you want to run when you create your plan:

- Additional Servers
Enter 1 to add servers to your existing setup (Deployment Server, Enterprise Server, Database Server, HTML Web Server). Enter 0 or leave blank for regular plans.

- Installation
Enter 1 to run the JD Edwards EnterpriseOne installation automatically.

5.3.3.3 Specifying the Default Mode

To specify the default mode:

1. Select the Default Mode tab.

2. On the Default Mode tab, enter these values into the processing option fields:

Value

Description

0

Do not use default values and do not prompt.

1

Prompt for default options at run-time.

2

Default mode. Always use defaults without prompting.

- Default Data Source Information
Select whether you want the ability to modify data source information or just take the default values.

- Default Environments
Select whether you want the ability to select environments or take the default values.

- Default Data Load
Select whether you want the ability to modify data load parameters or take the default values.

- Default Advanced Parameters
Select whether you want the ability to modify advanced parameters or take the default values.

- Default Languages
Select whether you want the ability to select an alternate language or take the default values.

- Upgrade/Update Plan Generation
Select whether you want the ability to generate a plan automatically from locations and machines defined in a previous version of the software.

5.3.3.4 Verifying Status Change Values Have Not Changed

On the Status Change tab, this tab form appears.

Note:
Do not make any changes on this tab. These values are hard coded in the application

5.3.3.5 Specifying Plan Completion Processes

To specify plan completion processes:

1. Select the Completion tab.

2. On the Completion tab, complete the fields using these values:
After defining the plan, the options on this tab specify which processes are run. one of the following values:

Value

Description

0

Do not run automatically.

1

Prompt to be run.

2

Run automatically.

- Finalize Plan
Enter the default option 2 to run automatically.

- Validate Plan
Enter the default option 2 to run automatically.

5.3.3.6 Specifying Replication Options

To specify replication options:

1. Select the Replication tab.

2. On the Replication tab, complete the fields using these values:

Value

Description

0

Do not use and do not prompt.

1

Prompt for option at run-time.

2

Always use without prompting .

- Replicate System Tables
Select whether you have the option to replicate system tables automatically for remote locations.

- Replicate Data Dictionary Tables
Select whether you have the option to replicate data dictionary tables automatically for remote locations.

- Replicate Control Tables
Select whether you have the option to replicate control tables, menus, and user defined codes automatically for remote locations.

- Replicate Constant Tables
Select whether you have the option to replicate constant tables automatically for remote locations. Business data tables are Object Librarian type 280.

- Replicate Master Tables
Select whether you have the option to replicate master tables automatically for remote locations. Business data tables are Object Librarian type 210 and 211.

5.4 Working with a Typical Installation Plan

This section discusses:

- Section 5.4.1, "Assumptions About Defining a Typical Installation Plan"

- Section 5.4.2, "Starting Installation Planner"

- Section 5.4.3, "Entering a Plan Description"

- Section 5.4.4, "Entering Location Information"

- Section 5.4.5, "Entering Deployment Server Information"

- Section 5.4.6, "Entering Enterprise Server Information"

- Section 5.4.7, "Enter Data Source Information for Server Map"

- Section 5.4.8, "Entering HTML Web Server Information"

- Section 5.4.9, "Verify the Data Sources"

- Section 5.4.10, "Selecting Default Environments"

- Section 5.4.11, "Finalizing the Installation Plan"

5.4.1 Assumptions About Defining a Typical Installation Plan

This table outlines assumptions for the Installation Planner phase.

Personnel

Installer

Logon Status

On the Deployment Server, log on to Release 9.1 as user JDE in the JDEPLAN environment.

Prerequisites

Because the Planner applications runs on the Deployment Server, you must verify that the Deployment Server is installed and the correct Tools Release, Tools Release Patch, and Planner Update have been installed on it, in that order.
The Platform Pack installation on the Enterprise Server at the corresponding release level iwth the Deployment Server must be completed and you should verify that it completely installed the Pristine database and loaded the Pristine Central Objects.

Concurrent Tasks

None.

5.4.2 Starting Installation Planner

To start Installation Planner from within JD Edwards EnterpriseOne:

1. Access the System Installation Tools Menu (GH961).

2. On the System Installation Tools menu, double-click Typical Installation Plan.

3. On Work with Installation Plans, click Add.

The Installation Planner form appears.

4. Enter a Plan description.

5.4.3 Entering a Plan Description

To enter a plan description:

1. On Installation Planner, complete these fields:

Field

Description

Name

Enter the name of the installation plan.

Description

Enter the description of the installation plan.

Status

Choose 10 (the default value) as the status of the installation plan.

Install Type

Click the Install (the default value) radio button.

To Release

Verify that the release number is E910 (default value).

2. Click OK to continue.

5.4.4 Entering Location Information

A location groups related Deployment Servers for use in a multi-tier environment.

To enter location information:

1. On Location Revisions, complete these fields:

Field

Description

Location

Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company.

Description

Enter a description for this location.

Location Code

If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable.

Parent Location

If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable.

2. Click OK.

5.4.5 Entering Deployment Server Information

While Release 9.1 enables more than one Deployment Server to be defined, only the primary Deployment Server is defined at this time. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server.

Note:
If you installed JD EnterpriseOne files to a remote Deployment Server, the deployment server name is the remote machine name by default.

To enter Deployment Server information:

1. On Deployment Server Revisions, complete or verify these fields:

Field

Description

Machine Usage

The value 15 appears by default, indicating that this is a Deployment Server.

Machine Name

The name of the Deployment Server appears by default. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.
Remote Deployment Server. If you installed JD EnterpriseOne files to a remote Deployment Server, the deployment server name is the remote machine name by default.

Description

Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server.

Release

Enter the JD Edwards EnterpriseOne release number you are installing or use the visual assist button to choose one from the list. The default value is E910.

Host Type

The value 50 appears by default, indicating that the server type is Intel NT.

Location

Your current location is the default value.

Primary User

The user to whom an email is sent when a package is deployed. The default value for Primary User is listed in the jde.ini.

2. On the Deployment tab, complete this field:

Field

Description

Primary Deployment Server

The hierarchy of the servers. Valid values are:
1- Primary Deployment Server (default value)

0 - Secondary Deployment Server

The server share name of the directory to which you installed Release 9.1 on your Deployment Server. Verify that the server share name for Release 9.1 is:

\E910

3. Click OK.

Tip:
If you enter invalid information into a field on a tab, a stop sign symbol appears next to the tab name, such as Workstation. Click the stop sign icon in the bottom right of the form to see more info about the error.

4. On Deployment Server, to add another Deployment Server, click Yes and repeat steps 1 through 3.

5. To continue with Installation Planner setup, click No.

5.4.6 Entering Enterprise Server Information

Note:
During the definition of the Enterprise Server, a port number must be defined. While Enterprise Servers running the same release can use the same port number, an Enterprise Server running two different versions of software must use two different port numbers.

To enter Enterprise Server information:

1. On Enterprise Server Revisions, verify or complete these fields:

Field

Description

Machine Name

The name of the primary Enterprise Server. The name is case sensitive and should not contain any special characters.
Because the machine name is used to create the Server Map datasource name, and because the Platform Pack Installer does not restrict you from entering a machine name that results in a datasource name greater than 30 characters; if the machine name for the Enterprise Server is longer than 13 characters, the resulting datasource name will be longer than the allowed 30 characters. For example, if your machine name is 15 characters (A23456789012345), the base datasource name in the server jde.ini will be: A23456789012345 - 910 Server Map

Note: The field in table F98611 is a hard restriction; the field only allows 30 characters. The actual field size cannot be modified or changed.

When the Planner runs it truncates the value to 30 characters because that is the restriction in the F98611 table. The Platform Pack does not truncate the value when it builds the jde.ini for the Enterprise Server. Therefore, any value greater than 30 characters will result in a mismatch between the jde.ini and the F98611 table. That is, using the previous example, the jde.ini would have the full length value A23456789012345 - 910 Server Map (which is 32 characters) while the F98611 populated by the Planner would have a value of A23456789012345 - 910 Server M.

To remedy, you could do any one of the following:

- Manually modify values in table F98611 to match the truncated value in the jde.ini file.

- Ensure that the value is not truncated by limiting the datasource name to 30 characters (this would mean limiting the machine name for the Enterprise Server to 13 characters).

- Manually truncate the value in the F98611 table (for example, A23456789012345 - 910 Svr Map.

In any case, you must ensure that the values for Server Map datasource names in the F98611 table exactly match those in the jde.ini file on the Enterprise Server.

Description

Enter a description for the machine.

Release

Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E910.

Host Type

Click the visual assist button and select the type of Enterprise Server you are adding to the plan. In this case, iSeries.

Location

The location chosen for this plan appears by default.

Primary User

The user to whom an email is sent when a package is deployed. The default value for Primary User is listed in the jde.ini.

Note:
The case of machine name must also match the network ID for that machine.

Caution:
For information on supported clustering environments, see Release 9.1 on a Cluster in JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide and the clustering vendor's software documentation.

2. On Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields:

Field

Description

Port Number

The port number value (6016) for this Enterprise Server as supplied from the jde.ini.

Logical Machine Name

The Installation Planner detects and provides a default value based on the current machine name on which the program is running. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Database Type

Enter the value for your database:
I - DB2 400

Server Map Data Source

Whenever you enter a host type, the Installation Planner populates this field with a default value:
machinename - 910 Server Map

where machinename is the name of your machine.

Installation Path

Verify that the default value is the installation directory path to which you want to install Release 9.1 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 9.1 the default path is:
\JDEdwards\PPack\E910SYS

This is the system library.

Caution: You must change the value that defaults into the Installation Path field as shown in the screen capture above.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary.

Note:
If you change the port number to a value other than 6016, you must also change this setting in both the Enterprise Server and client jde.ini.

3. Click OK.

5.4.7 Enter Data Source Information for Server Map

To enter information for the Server Map data source:

1. On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data. If you select the default data, you can skip to Section 5.4.8, "Entering HTML Web Server Information".

2. On Data Source Revisions, verify the accuracy of the Server Map data source.

3. Click OK.

4. On the Would you like to add another Enterprise Server? dialog, click the Yes or No button.

5.4.8 Entering HTML Web Server Information

Note:
For Release 9.1 the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web 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.

Caution:
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface.

To enter HTML Web Server information:

1. On HTML Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 30 indicates that this is a HTML Web Server.

Machine Name

Enter the name of your HTML Web Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the HTML Web Server machine.

Release

Enter E910 to indicate the release number that you are installing.

Host Type

The default value of 50 specifies the server type as Intel NT. Select the correct server type.

Location

The location chosen for this plan appears in this field by default.

Primary User

The user to whom an email is sent when a package is deployed. The default for Primary User is listed in the jde.ini.

2. On the HTML tab, complete these fields:

Field

Description

Primary HTML Server

When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1").

Protocol

This is the protocol used by the HTML Web Server. Valid values are http or https.

Server URL

This is the Domain Name System (DNS) host name of the HTML Web Server.
For example: www.oracle.com

HTTP Port

This is the port number the HTML Web Server is listening to.
For HTTP, the typical port number is 80.

For HTTPS, the typical port number is 443.

Note: You can choose to implement a HTML Web Server using a different port number.

JDENET Listen Port

This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne.
For JD Edwards EnterpriseOne Release 9.1, the value is 6016.

Default Login

Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are:

- Standard
The URL generated will point to a servlet on the Primary HTML Web Server.

- Redirector
The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system.

- Explicit Servlet Name
The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server.

Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need.

Installation Path

Enter the installation directory path to which you are installing Release 9.1 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running.
For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Reference Guide ( WebSphere for IBM i). Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this HTML Web Server is attached. A Deployment Server name appears in this field by default, but you can change it if necessary.

3. Click OK.

4. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

5.4.9 Verify the Data Sources

On Data Source, click the OK button to verify these data sources for your installation.o select default environments:

- Section 5.4.9.1, "Verifying the Data Source for Data Dictionary"

- Section 5.4.9.2, "Verifying the Object Librarian Data Source"

- Section 5.4.9.3, "Verifying the OWJRNL Data Source"

- Section 5.4.9.4, "Verifying the System Data Source"

5.4.9.1 Verifying the Data Source for Data Dictionary

To verify the data source for Data Dictionary:

1. On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source.
The library name in the Library Name field is the Release 9.1 data dictionary library (DD910).

2. Click OK.

5.4.9.2 Verifying the Object Librarian Data Source

To verify the Object Librarian data source:

1. On Data Source Revisions, verify the accuracy of the settings for the Object Librarian data source.

2. Click OK.

5.4.9.3 Verifying the OWJRNL Data Source

To verify the OWJRNL data source:

1. On Data Source Revisions, verify the accuracy of the settings for the OWJRNL data source.

2. Click OK.

5.4.9.4 Verifying the System Data Source

To verify the System data source:

1. On Data Source Revisions, verify the accuracy of the settings for the System data source.

2. Click OK.

5.4.10 Selecting Default Environments

The Environment Selection screen is displayed.

1. To configure all valid environments for your installation, check the Default Environments box. Otherwise, uncheck the Default Environments box to select and verify individual environments.

2. Click OK.

3. Click the OK button to verify your environments.

Caution When Choosing Take Defaults
In order to ensure the validity of all subsequent plan information, it is strongly recommended that even advanced users should not choose the Take Defaults option. Instead, you should step through plan and verify that the Planner is populating information exactly as you expect to match your requirements.:

You can verify these default environments:

- Section 5.4.10.1, "Verifying the Data Source for Business Data"

- Section 5.4.10.2, "Verifying the Data Source for Central Objects"

- Section 5.4.10.3, "Verifying the Data Source for Control Tables"

- Section 5.4.10.4, "Verifying the Data Source for Data Dictionary"

- Section 5.4.10.5, "Verifying the Data Source for Versions"

5.4.10.1 Verifying the Data Source for Business Data

To verify the data source for business data:

1. On Data Source Revisions, verify the data source for your Business Data.

2. Click OK.

5.4.10.2 Verifying the Data Source for Central Objects

Caution:
You should change the data source if Central Objects are not on an IBM i machine.

To verify the data source for central objects:

1. On Data Source Revisions, verify the information for your central objects data source.

Caution:
If you are putting central objects on the IBM i, verify that the data library name is CO pathcode. For example:
COPY910

2. Click OK.

5.4.10.3 Verifying the Data Source for Control Tables

To verify the data source for control tables:

1. On Data Source Revisions, verify the accuracy of the Control Tables data source.

Field

Description

Data Source Name

Verify the name of the data source.

Server Name

Verify the name of the Enterprise Server.

Library Name

Enter the name of the library housing your Control Tables for the selected environment.

ODBC Data Source Name

Enter the name of the data source. For example, Control Tables - Test.

Note:
Control tables data sources are specific to the environment and pathcode.

2. Click OK.

5.4.10.4 Verifying the Data Source for Data Dictionary

To verify the data source for Data Dictionary:

1. On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source.
The library name in the Library Name field is the Release 9.1 data dictionary library (DD910).

2. Click OK.

5.4.10.5 Verifying the Data Source for Versions

To verify the data source for versions:

1. On Data Source Revisions, verify the accuracy of the versions data source.

Note:
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced form must be selected.

2. Click OK.

Note:
When you click OK at this point, the Plan begins to finalize; the below screen is displayed with progress indicated in the lower left-hand portion.

When the plan complete the finalization process, the following dialog is displayed:

5.4.11 Finalizing the Installation Plan

When the plan is finalized:

- The status is set to 20, signaling that several adjustments to OCM mappings and tables are made according to your plan.

- The system creates the OCM mappings and the .jde.ini

- These tables are updated:

- Release Master table (F00945).

- Path Code Master table (F00942).

- Package Plan table (F98404).

- Machine Detail table (F9651).

- Language table (F984031), if you are installing a language.

To finalize the Installation Plan:

1. On the Information Prompt that indicates Installation Planner has concluded, click OK to exit the message box and initiate the Planner Validation Report.

- If the processing option default was selected, Planner Validation Report automatically prompts you to run this report.

- If the processing option default was not selected, click Validate on the tree view of your plan to initiate the Planner Validation Report.

5.4.12 Concluding the Planner Validation Report

To conclude the planner validation report:

1. On Report Output Destination, select On Screen or To Printer.

2. Click OK.

3. Review the report to confirm that all records were validated.
For more information about Section 22.1, "Installation Planner Validation Report (R9840B)", refer to Chapter 22, "Working with Reports".

4. On Work With Installation Plans, click Expand to review the plan you created.

See Also

- A separate chapter in this guide entitled: Chapter 15, "Creating a Remote Installation Plan"

- A separate chapter in this guide entitled: Chapter 16, "Adding a Server to an Existing Configuration"

- A separate chapter in this guide entitled: Chapter 17, "Creating a Language-Only Installation Plan"

5.5 Creating a Custom Installation Plan

This chapter includes the following processes for creating a custom installation plan:

- Section 5.5.1, "Understanding a Custom Installation Plan"

- Section 5.5.2, "Starting Installation Planner"

- Section 5.5.3, "Entering a Plan Description"

- Section 5.5.4, "Entering Location Information"

- Section 5.5.5, "Entering Deployment Server Information"

- Section 5.5.6, "Entering Enterprise Server Information"

- Section 5.5.7, "Enter Data Source Information for Server Map"

- Section 5.5.8, "Entering HTML Web Server Information"

- Section 5.5.9, "Entering Data Server Information"

- Section 5.5.10, "Entering Shared Data Source Information"

- Section 5.5.11, "Working with Environment Setup"

- Section 5.5.12, "Adding a Remote Location"

- Section 5.5.13, "Finalizing the Installation Plan"

See Also

- A separate chapter in this guide entitled: Chapter 15, "Creating a Remote Installation Plan"

- A separate chapter in this guide entitled: Chapter 16, "Adding a Server to an Existing Configuration"

- A separate chapter in this guide entitled: Chapter 17, "Creating a Language-Only Installation Plan"

5.5.1 Understanding a Custom Installation Plan

Note:
After installing the Deployment Server, you must define and run the installation plan. You must either define and run a Typical or a Custom Installation Plan -- do not do both.

Note:
If you installed JD EnterpriseOne files to a remote Deployment Server, the deployment server name is the remote machine name by default.

Within a custom installation plan, the information you provide on the Installation Planner forms, such as database type and Enterprise Server type, determines the information displayed on the remaining forms. The Installation Planner processing options also determine which choices are available while setting up your plan. For a complete description of the processing options, refer to Section 5.3, "Reviewing Installation Planner Processing Options".

Data Source Considerations

JD Edwards EnterpriseOne configures your Release 9.1 data sources as completely as possible. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration.

5.5.2 Starting Installation Planner

To start Installation Planner from within JD Edwards EnterpriseOne:

1. Access the System Installation Tools Menu (GH961).

2. On the System Installation Tools menu, double-click Custom Installation Plan.

3. On Work with Installation Plans, click Add.
The Installation Planner form appears.

4. Enter a Plan description.

5.5.3 Entering a Plan Description

To enter a plan description:

1. On Installation Planner, complete the following fields:

Field

Description

Name

Enter the name of the plan.

Description

Enter the description of the plan.

Status

Choose 10 (the default value).

Install Type

Click the Install (the default value).

To Release

Verify that the release number is E910 (the default value).

Include Languages

This is an optional selection that is only available if you have a language installation image installed on the Deployment Server. Select Yes if you are installing an alternate language.
Note: If you prefer, you can install an alternate language after you complete your master plan. To do so, select the Language Only option on this form. For more information, refer to Chapter 17, "Creating a Language-Only Installation Plan"

2. Click OK.

3. On the Location dialog, click OK.

5.5.4 Entering Location Information

A location groups related Deployment Servers for use in a multi-tier environment.

To enter location information:

1. On Location Revisions, complete these fields:

Field

Description

Location

Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company.

Description

Enter a description for this location.

Location Code

If this is the base location, this field will be grayed out.

Parent Location

For the base location, this field will be grayed out.

2. Click OK.

5.5.5 Entering Deployment Server Information

While Release 9.1 enables more than one Deployment Server to be defined, only the primary Deployment Server is defined at this time. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server.

To enter Deployment Server information:

1. Click OK to add a Deployment Server.

2. On Deployment Server Revisions, complete or verify these fields:

Field

Description

Machine Usage

Displays the value 15 by default to indicate that this is a Deployment Server.

Machine Name

The name of the Deployment Server appears by default. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server.

Release

Enter the release number you are installing or use the visual assist button to choose one from the list. The default value is E910.

Host Type

Displays the value 50 appears by default, indicating that the server type is Intel NT.

Location

Displays the current location.

Primary User

Displays the user to whom an email is sent when a package is deployed. The default value for Primary User is JDE.

3. On the Deployment tab, complete this field:

Field

Description

Primary Deployment Server

Enter the hierarchy of the servers. Values are:
1- Primary Deployment Server (default value)

0 - Secondary Deployment Server

The server share name of the directory to which you installed Release 9.1 on your Deployment Server. Verify that the server share name for Release 9.1 is:

\E910

4. Click OK.

Tip:
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form.

5. To add another Deployment Server, click Yes and repeat steps 1 through 3.

6. To continue with Installation Planner setup, click No.

5.5.6 Entering Enterprise Server Information

Note:
During the definition of the Enterprise Server, a port number must be defined. While Enterprise Servers running the same release can use the same port number, an Enterprise Server running two different versions of software must use two different port numbers.

On Enterprise Server, click the OK button to define a new Enterprise Server, or click the Select button to choose an existing Enterprise Server.

1. On Enterprise Server Revisions, verify or complete these fields:

Field

Description

Machine Name

The name of the primary Enterprise Server. The name is case sensitive and should not contain any special characters.
Because the machine name is used to create the Server Map datasource name, and because the Platform Pack Installer does not restrict you from entering a machine name that results in a datasource name greater than 30 characters; if the machine name for the Enterprise Server is longer than 13 characters, the resulting datasource name will be longer than the allowed 30 characters. For example, if your machine name is 15 characters (A23456789012345), the base datasource name in the server jde.ini will be:

A23456789012345 - 910 Server Map

Note: The field in table F98611 is a hard restriction; the field only allows 30 characters. The actual field size cannot be modified or changed.

When the Planner runs it truncates the value to 30 characters because that is the restriction in the F98611 table. The Platform Pack does not truncate the value when it builds the jde.ini for the Enterprise Server. Therefore, any value greater than 30 characters will result in a mismatch between the jde.ini and the F98611 table. That is, using the previous example, the jde.ini would have the full length value A23456789012345 - 910 Server Map (which is 32 characters) while the F98611 populated by the Planner would have a value of A23456789012345 - 910 Server M.

To remedy, you could do any one of the following:

- Manually modify values in table F98611 to match the truncated value in the jde.ini file.

- Ensure that the value is not truncated by limiting the datasource name to 30 characters (this would mean limiting the machine name for the Enterprise Server to 13 characters).

- Manually truncate the value in the F98611 table (for example, A23456789012345 - 910 Svr Map.

In any case, you must ensure that the values for Server Map datasource names in the F98611 table exactly match those in the jde.ini file on the Enterprise Server.

Description

Enter a description for the machine.

Release

Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E910.

Host Type

Click the visual assist button and choose the type of Enterprise Server you are adding to the plan. In this case, IBM i.

Location

The location chosen for this plan appears by default.

Primary User

The user to whom an email is sent when a package is deployed. The default value for Primary User is JDE.

Note:
The case of machine name must also match the network ID for that machine.

2. Continuing on Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields:

Field

Description

Port Number

The port number value (6016) for this Enterprise Server appears by default from the jde.ini.

Logical Machine Name

The Installation Planner detects and provides a default value based on the current machine name on which the program is running. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Database Type

Enter the value for your database:
I - DB2 400

Server Map Data Source

Whenever you enter a host type, the Installation Planner populates this field with a default value:
machinename - 910 Server Map

where machinename is the name of your machine.

Installation Path

Verify that the default value is the installation directory path to which you want to install Release 9.1 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 9.1 the default path is:
\JDEdwards\PPack\E910SYS

This is the system library.

Caution: You must change the value that defaults into the Installation Path field as shown in the screen capture above.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary.

Note:
If you change the port number to a value other than 6016, you must also change this setting in both the Enterprise Server and workstation JDE.INIjde.ini.

3. Click OK.

5.5.7 Enter Data Source Information for Server Map

To enter information for the Server Map data source:

1. On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data. If you select the default data, you can skip to Section 5.5.8, "Entering HTML Web Server Information".

2. On Data Source Revisions, verify the accuracy of the Server Map data source.

3. Click OK.

4. On the Would you like to add another Enterprise Server? dialog, click the Yes or No button.

5.5.8 Entering HTML Web Server Information

Note:
For Release 9.1, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web 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.

Caution:
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface.

To enter HTML Web Server information:

1. Click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.
If you choose Select, you are presented with the Machine Search table, from which you can make your selection.

2. On HTML Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 30 indicates that this is a HTML Web Server.

Machine Name

Enter the name of your HTML Web Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the HTML Web Server machine.

Release

Enter E910 to indicate the release number that you are installing.

Host Type

The default value of 50 specifies the server type as Intel NT. Select the correct server type.

Location

The location chosen for this plan appears in this field by default.

Primary User

The user to whom an email is sent when a package is deployed. The default for Primary User is listed in the jde.ini.

3. On the HTML tab, complete these fields:

Field

Description

Primary HTML Server

When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1").

Protocol

This is the protocol used by the HTML Web Server. Valid values are http or https.

Server URL

This is the Domain Name System (DNS) host name of the HTML Web Server.
The syntax is:

server_name:port\jde\owhtml

For example:

DEVNTA:81\jde\owhtml

Http Port

This is the port number the HTML Web Server is listening to.
For HTTP, the typical port number is 80.

For HTTPS, the typical port number is 443.

However, you can choose to implement a HTML Web Server using a different port number.

Default Login

Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are:

- Standard
The URL generated will point to a servlet on the Primary HTML Web Server.

- Redirector
The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system.

- Explicit Servlet Name
The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server.

Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need.

Installation Path

Enter the installation directory path to which you are installing Release 9.1 on your HTML Web Server.Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running.
For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Reference Guide (WebLogic for Windows, WebLogic for UNIX, WebSphere for Windows, WebSphere for UNIX, WebSphere for IBM i. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator.

Deployment Server Name

Using the visual assist button, choose the name of the DeploymentServer to which this HTML Web Server is attached. A DeploymentServer name appears in this field by default, but you can change it ifnecessary.

4. Click OK.

5. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

5.5.9 Entering Data Server Information

1. On Data Server, choose one of these options:

- OK
If your database resides on a separate server, choose click OK to continue entering unique Data Server information.

- Select
Click this option to select an existing Data Server.

- Skip
Click this option if you do not want to define a Data Server. Continue with the Planner using the environment selection in step 6 of this task.

- On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data.

2. On Data Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 25 indicates that this is a Database Server.

Machine Name

Enter the name of the Database Server where your central objects reside. If you are using the IBM i to store your central objects, enter the name of this server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the Database Server machine.

Release

Enter the release number you are installing, for example, E910.

Host Type

Select the type of Database Server that you are adding to the plan. Values are:

- 10 — IBM i

- 25 — Sun Solaris

- 30 — RS\6000

- 35 — Linux

- 50 — Microsoft Windows (Intel)

- 80— Client - Microsoft Windows

- 90 — Client - Microsoft Windows

Location

The Installation Planner populates this field by default, based on previous selections.

Primary User

The user to whom an email is sent once a package is deployed. The default for Primary User is JDE.

3. On the Data tab, complete the following field:

Field

Description

Data Source Type

Choose the type of data source. For example:

- I - IBM i

4. Click OK.

5. To add another Data Server, click Yes and repeat steps 1 through 4 to define another Data Server.

6. On Data Source, click OK to entering and verify unique shared data source information as described in the next section of this guide entitled: Section 5.5.10, "Entering Shared Data Source Information".

5.5.10 Entering Shared Data Source Information

This section discusses:

- Section 5.5.10.1, "Specifying (Custom or Default) Shared Data Source Setup Information"

- Section 5.5.10.2, "Verifying the Data Source for Data Dictionary"

- Section 5.5.10.3, "Verifying the Object Librarian Data Source"

- Section 5.5.10.4, "Verifying the OWJRNL Data Source"

- Section 5.5.10.5, "Verifying the System Data Source"

5.5.10.1 Specifying (Custom or Default) Shared Data Source Setup Information

When you are prompted to enter the data source information for the shared data sources, to use the Release 9.1 data sources, click Take Defaults, or click OK to specifically enter the data source information.

See Also

For more information about System data source fields or fields for other data sources mentioned in this process, refer to Chapter 19, "Understanding Data Source Charts".

5.5.10.2 Verifying the Data Source for Data Dictionary

To verify the data source for Data Dictionary:

1. On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source.
The library name in the Library Name field is the Release 9.1 data dictionary library (DD910).

2. Click OK.

5.5.10.3 Verifying the Object Librarian Data Source

To verify the Object Librarian data source:

1. On Data Source Revisions, verify the accuracy of the settings for the Object Librarian data source.

2. Click OK.

5.5.10.4 Verifying the OWJRNL Data Source

To verify the OWJRNL data source:

1. On Data Source Revisions, verify the accuracy of the settings for the OWJRNL data source.

2. Click OK.

5.5.10.5 Verifying the System Data Source

To verify the System data source:

1. On Data Source Revisions, verify the accuracy of the settings for the System data source.

2. Click OK.
The Environment Selection screen appears.

5.5.11 Working with Environment Setup

This section discusses:

- Section 5.5.11.1, "Understanding Environment Setup"

- Section 5.5.11.2, "Setting Up Environments"

- Section 5.5.11.3, "Working with Environment Data Sources"

5.5.11.1 Understanding Environment Setup

By default, Installation Planner configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 9.1 displays one or more of the following parameters, which you can customize in the following tasks:

- Environments

- Data load options

You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Installation Planner displays a customization form for each parameter that you clear.

5.5.11.2 Setting Up Environments

To set up environments:

1. On Environment Selection, clear the options that you do not want to customize.

Note:
Different parameters appear depending on the options that you chose at the beginning of the planning process.

2. Click OK.

Note:
If you selected the default option, which is to include all parameters, skip to Section 5.5.11.3, "Working with Environment Data Sources".

Skip the tasks for those parameters that you did not clear. Otherwise, this section discusses these topics:

- Section 5.5.11.2.1, "Selecting an Environment"

- Section 5.5.11.2.2, "Specifying Environment Data Load Parameters"

Note:
Adding a Custom Environment. Previous releases of JD Edwards EnterpriseOne allowed you to add a custom environment using P98410 to Add or Copy a custom Environment. Beginning with Release 9.0, you should instead use P989400 Environment Copy from GH961 > Advanced Operations. Refer to the section of this guide entitled: Chapter 13, "Copying an Environment to Another Environment".

5.5.11.2.1 Selecting an Environment

To select an environment:

1. On Select Environments, double-click the environment that you want to define. Selected environments are indicated with a green checkmark in the left-most column of the grid.

Note:
J xx environments are required for the HTML Web Server.

To set up multiple environments, select and define them one at a time.

2. Click the Close button to exit the Select Environments screen.

5.5.11.2.2 Specifying Environment Data Load Parameters

If you turned off Default Data Load on the Environment Selection form, the Data Load Parameters form appears. For example, if you chose the PS910 environment, this Data Load Parameters screen is displayed:

Note:
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 9.1 because data is automatically loaded by the Platform Pack Installer.
For additional details, refer to Section 6.1.2, "Loading Data (Demo Data and Production Data)".

5.5.11.3 Working with Environment Data Sources

This section discusses:

- Section 5.5.11.3.1, "Understanding Environment Data Sources"

- Section 5.5.11.3.2, "Selecting an Environment Data Source Setup Option"

- Section 5.5.11.3.3, "Setting Up the Data Source for Business Data"

- Section 5.5.11.3.4, "Setting Up the Data Source for Central Objects"

- Section 5.5.11.3.5, "Setting Up the Data Source for Control Tables"

- Section 5.5.11.3.6, "Verifying the Data Source for Data Dictionary (Pristine Only - PS910)"

- Section 5.5.11.3.7, "Verifying the Data Source for Versions"

5.5.11.3.1 Understanding Environment Data Sources

Once you have set up the environments, you must set up the data sources for those environments. If you created a custom environment, data source information is generated from the data source template provided by JD Edwards EnterpriseOne.

See Also

To modify this template, refer to the JD Edwards EnterpriseOne Configurable Network Computing Implementation Guide.

5.5.11.3.2 Selecting an Environment Data Source Setup Option

Installer Planner prompts you to set up data sources for the environment you just configured.

To select an environment data source setup option:

1. On Data Source, click OK to manually enter the data sources and continue with the following task, or click Take Defaults to accept the Release 9.1 default data sources.

5.5.11.3.3 Setting Up the Data Source for Business Data

To set up the data source for business data:

1. On Data Source Revisions, verify the data source for your Business Data.

2. From the Form menu, click Advanced.

3. Click OK.

5.5.11.3.4 Setting Up the Data Source for Central Objects

Caution:
You should change the data source if Central Objects are not on an IBM i machine.

To set up the data source for central objects:

1. On Data Source Revisions, verify the information for your central objects data source.

Caution:
If you are putting central objects on the IBM i, verify that the data library name is CO pathcode. For example:
COPY910

2. Click OK.

3. On Data Source Revisions, click the Advanced form option.

4. On Advanced Set-Up, because the central objects data source must be Unicode, verify the Unicode setting is checked.
For IBM i, ensure the AS/400 BLOB Support setting is checked.

5.5.11.3.5 Setting Up the Data Source for Control Tables

To setup the data source for control tables:

1. On Data Source Revisions, verify the accuracy of the Control Tables data source.

Field

Description

Data Source Name

Verify the name of the data source.

Server Name

Verify the name of the Enterprise Server.

Library Name

Enter the name of the library housing your Control Tables for the selected environment.

ODBC Data Source Name

Enter the name of the data source. For example, Control Tables - Test.

Note:
Control tables data sources are specific to the environment and pathcode.

2. Click OK.

5.5.11.3.6 Verifying the Data Source for Data Dictionary (Pristine Only - PS910)

To verify the data source for Data Dictionary:

Caution:
This task is only applicable to the Pristine Environment (PS910)

1. On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source for the Pristine Environment.
The library name in the Library Name field is the Release 9.1 data dictionary library (DD910).

2. Click OK.

5.5.11.3.7 Verifying the Data Source for Versions

To verify the data source for versions:

1. On Data Source Revisions, verify the accuracy of the versions data source.

Note:
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced form must be selected.

2. Click OK.

3. On Select Environments, click the Close button to exit the form.

5.5.12 Adding a Remote Location

To add a remote location:

1. On Location, choose one of the following options:

- Click Yes to add a remote location.

Repeat all processes for adding a location starting with Section 5.5.4, "Entering Location Information". Refer to the Creating a Remote Installation Plan for information about adding remote locations to your plan.

- Click No to conclude the Installation Plan setup.

2. Continue with Section 5.5.13, "Finalizing the Installation Plan" task.

5.5.13 Finalizing the Installation Plan

When you click No on the Location dialog, the Planner begins to finalize the plan, as indicated by a status message in the lower left-hand portion of the screen:

Installation Planner displays a message to let you know that the installation plan has been finalized.

On the Information Prompt that indicates Installation Planner has concluded, click OK to exit the message box and initiate the Planner Validation Report.

- If the processing option default was selected, Planner Validation Report automatically prompts you to run this report.

- If the processing option default was not selected, click Validate on the tree view of your plan to initiate the Planner Validation Report.

When the plan is finalized:

- The status is set to 20, which signals that several adjustments to tables were made according to your plan.

- The OCM is created.

- The jde.ini is modified.

- The following tables are upgraded:

- Release Master table (F00945).

- Path Code Master table (F00942).

- Package Plan table (F98404).

- Machine Detail table (F9651).

- Language table (F984031), if you are installing an alternate language.

5.5.14 Concluding the Planner Validation Report

To conclude the planner validation report:

1. On Report Output Destination, select On Screen or To Printer.

2. Click OK.

3. Review the report to confirm that all records were validated.
For more information about Section 22.1, "Installation Planner Validation Report (R9840B)", refer to Chapter 22, "Working with Reports".

4. On Work With Installation Plans, click Expand to review the plan you created.

See Also

- A separate chapter in this guide entitled: Chapter 15, "Creating a Remote Installation Plan"

- A separate chapter in this guide entitled: Chapter 16, "Adding a Server to an Existing Configuration"

- A separate chapter in this guide entitled: Chapter 17, "Creating a Language-Only Installation Plan"

5.6 Deleting Machines from an Installation Plan

As you work through the Installation Planner application, you might find that you need to delete a server or machine that you have created. You can use Installation Planner to delete machines as needed; however, doing so can affect related databases, shared Enterprise Servers and Deployment Servers, and associated records.

To delete machines from an installation plan:

1. In the Release 9.1 planner environment, enter P9654A in the Fast Path field and press Enter.

2. On Work With Locations and Machines, click Find.

3. Expand the location.
A list of your locations, machines, or servers appears for the base location in the tree view.

4. Select the location, machine, or server that you want to delete.

5. Click Delete.

6. To close the application, click Close.

6 Working With Installation Workbench

This section discusses:

- Section 6.1, "Understanding Workbench Components"

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

- Section 6.3, "Working with Unattended Workbench Mode"

- Section 6.4, "Starting Installation Workbench"

- Section 6.5, "Working With Initial Tasks Workbench"

- Section 6.6, "Configuring Your Locations"

- Section 6.7, "Configuring Your Data Sources"

- Section 6.8, "Configuring Your Environments"

- Section 6.9, "Using Machine Workbench"

- Section 6.10, "Using the Package Workbench"

- Section 6.11, "Using Remote Location Workbench"

- Section 6.12, "Finishing Installation Workbench"

- Section 6.13, "Deploying an Oracle or Partner Business Accelerator Configuration (optional)"

6.1 Understanding Workbench Components

After planning the Release 9.1 installation using Installation Planner, you should run the plan using Installation Workbench. The logic of this program runs specific workbench programs according to the plan you created.

Installation Workbench can be run in attended mode or unattended mode. In attended mode, you start each workbench after the previous workbench completes. In unattended mode (the default value), each workbench runs without user intervention. You can set task breaks before or after any specific workbench to stop the process at any point. If using unattended mode, you must check that each task ran successfully.

This section describes:

- Section 6.1.1, "Verifying the Network Share on the Deployment Server"

- Section 6.1.2, "Loading Data (Demo Data and Production Data)"

- Section 6.1.3, "Creating the Job Queue"

As listed in this table, Installation Workbench includes the components, some or all of which might be used for your installation, depending on your installation plan:

Installation Workbench Component

Functional Description

Initial Tasks Workbench

When using unattended workbench mode, this workbench runs Release Master after Installation Workbench is started and before Location Workbench begins.

Location Workbench

This workbench copies all locations that are defined in the plan from the F9654 and F984021 tables in the Planner data source to the System - 910 data source.

Data Source Workbench

Copies all data sources that are defined in the plan from the F98611 and F986115 tables in the Planner data source to your System - 910 data source. It also updates the F98401 table to indicate completion.

Environment Workbench

Copies the F0094, F00941, and F00942 tables, as well as the F986101 table for each environment, from your Planner data source to your System - 910 data source. It then updates the F98403 table to indicate completion. Depending on the plan settings, it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables.

Machine Workbench

Copies the F9650 and F9651 tables from the Planner data source to the System - 910 data source. It then updates the F98402 table to indicate completion and uses the environment information to populate the F986101 and F98611 tables in the Server Map data source. Only valid environments, data sources, and server map tables are created.

Control Table Workbench

Copies the language text from the local database that contains the language text into the control table database and central object database. This workbench runs only for users who are adding an alternate language to their installations.

Package Workbench

Transfers the F9603 and F9631 tables from the Planner data source to the System - 910 data source. It then updates the F98404 table to indicate completion.

See Also

Chapter 21, "Major Technical Tables" in this guide for more information about individual tables and their uses.

6.1.1 Verifying the Network Share on the Deployment Server

When you created the plan, this network share was created:

\\depsvrname\E910

where depsvrname is the name of your Deployment Server.

Because several of the Workbenches update files through the network share, these workbenches will fail if the share is not writeable. Sometimes the security settings on your Deployment Server will prevent the Planner from creating the share as a writeable share.

Use this procedure to ensure that the share is writeable before proceeding:

1. On the Deployment Server, navigate to Start | My Computer | Manage

2. Open Shared Folders.

3. Open Shares.

4. Right click on E910 and select Properties and then Share Permissions.

5. Select properties then select Share Permissions

6. Make sure that Everyone is set to Full Control, Change, Read permissions.

Note:
Even after the Workbenches are complete, you will still need these settings on the Deployment Server's share in order to successfully perform client installs.

6.1.2 Loading Data (Demo Data and Production Data)

While previous versions of JD Edwards EnterpriseOne used Workbench components to load data, for Release 9.1 the Platform Pack Installer loads appropriate data into specific environments as follows:

- Demo data to Development and Pristine environments.

- Production data to Production and Prototype environments.

To load demo data in Production or Prototype environments, you must run a UBE (R98403E) to copy the data to those environments.

Note:
The "from" (source) environment can be the Planner environment or your Pristine environment.

Caution:
You should not change the record selection on this UBE.

1. Run R98403E using the XJDE0009 version and set the processing options as follows:

2. On Processing Options 1-4, complete these fields:

- Option 1
Enter the name of the source environment, which is the environment of the table to be copied. For example, JDEPLAN.

- Option 2
This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources.

- Option 3
Enter the name of the target environment, which is the environment to which you wish to copy the table. In this case, you would specify either the Production or Prototype environments. For example, PD910.

- Option 4
This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources.

3. Click OK to continue specifying processing options.

4. On Processing Options 5-9, complete these fields:

Field

Description

Option 5

The recommended value is 1, which copies the table.
The default value is 0, Proof Mode.

Option 6

The recommended value is N, which copies tables only if they exist in the source.
Enter Y to copy tables whether or not they exist in the source data source.

The default value is N.

Option 7

The recommended value is Y, which recreates tables that already exist in the target data source.
Note: If you do not recreate the tables, you will end up with a mixture of production and demo data in the tables.

The default value is N.

Option 8

The recommended value is N, which forces a copy of the data, ignoring the CPYD flag.
Note: A value of Y will leave almost all tables empty. That is, a production data load.

The default value is N.

Option 9

The recommended value is N, which creates the indexes on the tables before copying the data. This prevents duplicate rows.
Note: A value of Y copies the data and then create the indexes.

The default value is N.

5. Click OK to accept the values and start the UBE.

6.1.3 Creating the Job Queue

You may set up the job queues before running the Installation Workbench. If you do not, Initial Tasks Workbench will create a default entry for QBATCH with a setting of maximum=4.

Note:
If running an Install, you can set up the queues at any stage before running a Package Build. If you set up queues after the Installation Workbench, sign onto DEP910.

To create the job queue:

1. Enter GH9013 in the Fast Path field and start the Job Queues program (P986130).

2. Click Add.

3. On Job Queue Revisions, add a queue by completing these fields:

Field

Description

Host

Enter the Enterprise Server name.

Job Queue

Ensure that the queue name matches the batch queue name on the IBM i. Typically IBM i machines use the batch queue QBATCH as their default.

Default Queue

Turn on this option by clicking the check box.

Job Queue Status

Enter 01.

Queue Type

Enter 02.

Maximum Batch Jobs

Enter a value that equals the number of processors on the Enterprise Server machine.

Port Number

Enter 6016.
If you receive a Network Failed error, you can safely ignore it in this case.

4. Add another queue called I-ACTIVE.

5. On Job Queue Revisions, add a queue by completing these fields:

Field

Description

Host

Enter the Enterprise Server name.

Job Queue

Enter the Job Queue name: I-ACTIVE.

Default Queue

Turn off this option by clicking the radio button.

Job Queue Status

Enter 01.

Queue Type

Enter 02.

Maximum Batch Jobs

Enter a value that equals the number of processors on the Enterprise Server machine.

Port Number

Enter 6016.

6.2 Adding an Entry to the Remote Database Directory

You can add an 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 your IBM i for Remote Location *LOCAL. This entry must have the same name as your machine.

4. If you do not have an entry like this, enter 1 in the Option column and type you machine name in the Relational Database column, and press enter. In the Remote Location Name or Address field, enter *LOCAL and press Enter. If you already have a *LOCAL entry and the Relational database name is not the same as your machine name, you must remove the entry that you have 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, 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.1.

5. Once you have added or change the entry, you should 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 you are running these commands.

6.3 Working with Unattended Workbench Mode

This section discusses:

- Section 6.3.1, "Selecting Attended or Unattended Workbench Mode"

- Section 6.3.2, "Setting a Task Break in Unattended Workbench Mode"

6.3.1 Selecting Attended or Unattended Workbench Mode

The workbenches can be run manually (attended workbench mode) or automatically (unattended workbench mode). When running Workbench in unattended mode, start Installation Workbench as described below, and then the status of each workbench is displayed as the workbench begins. Unattended workbench is the default value.

In unattended workbench, if an error is encountered in any of the individual workbenches, the process stops. After fixing the error, unattended workbench resumes where it left off.

To choose attended workbench mode:

1. Open the System Installation Tools menu (GH961).

2. Right-click on Installation Workbench.

3. Select Prompt For and then Values.
The Processing Options form appears.

4. In the appropriate field, enter 1 for unattended workbench mode or 0 (zero) for attended workbench mode.
The default value is 1 (unattended).

5. Click OK.
Work with Installation Plan appears.

6.3.2 Setting a Task Break in Unattended Workbench Mode

In unattended workbench, you can set task breaks before or after any of the individual workbenches. You can use the task break to verify successful completion of a workbench or for other tasks. For example, set a task break after Table Conversion Workbench to verify that all table conversions completed successfully. An automatic task break occurs after Control Table Workbench, preceding Table Conversion Workbench.

To set a task break in unattended workbench mode:

1. Open the System Installation Tools menu (GH961).

2. Select Advanced Operations.

3. Double-click Work with Task Breaks.
The Work with Task Breaks form appears.

4. Click Find.
A list of the workbenches appears.

5. To set a break before or after a workbench, choose the workbench name, and, on the Row menu, select Break Before or Break After.
You can clear task breaks on the Row menu.

6. On Task Break Revisions, specify the following fields:

- email Address (optional)
Specify (or choose from a list) the address book number of the person who is to be notified when the task break occurs.

- Task Break
Specify (blank) for no task break or 2 for a customer task break. If the field is left blank, then no task break is configured.

- Task Break Short Text (required)
Enter a short text description of the task break.

- Optional Detail (optional)
Enter detailed information about the task break.

7. Click OK.
Task Break Revisions closes, and Work with Task Breaks reappears. Specify any further task breaks.

8. Click Close.

6.4 Starting Installation Workbench

Caution:
Do not lock the Deployment Server during Installation Workbench processes (for example, with a screen saver password); doing so pauses some processes.
Do not run Installation Workbench from a remote access program that simulates a local connection.

To start the Installation Workbench:

1. On your Deployment Server, log in to the Planner environment, which is JDEPLAN.

2. From the System Installation Tools menu (GH961), choose Installation Workbench.
When this application is run the first time, the system downloads all required objects using Just In Time Installation (JITI).

- If you specified attended workbench mode, use the following procedures, including the Initial Tasks Workbench, to complete the workbenches.

- If you specified unattended workbench mode, the process begins and all workbenches are completed automatically, unless task breaks are set. If you did not set any task breaks, continue with Chapter 7, "Working With the Enterprise Server".

3. On Work with Installation Plan, double-click your plan.

6.5 Working With Initial Tasks Workbench

Before the workbench is run, the F00945 table in the System data source is blank because it is no longer populated when a plan is validated. However, after you run the Initial Task Workbench several tables in the System data source are populated including the F00945 table.

The Initial Tasks Workbench form lets you complete the Release Master task before the individual workbenches begin.

You use this procedure if you are running Workbench in attended mode or if you set a task break before Initial Tasks Workbench.

6.5.1 Changing the Status of Initial Tasks Workbench

You use this procedure if you are running Workbench in attended mode or if you set a task break before Initial Tasks Workbench.

To change the status of Initial Tasks Workbench:

You might want to change the status of one or more of the initial workbench tasks. To change the status of a task, use the following procedure.

1. Enter GH961 in the Fast Path field to open the System Installation Tools menu.

2. Double-click Custom Installation Plan.

3. On Work with Installation Plans, select your installation plan.

4. Select Expand on the Row menu.
The plan components, including the initial tasks, appear.

5. Select the task whose status you want to change.

6. On the Row menu, click Disable, Enable, or Complete (see the table below).
The task status changes.

- Disable
Displays a status of 70 to indicate the task is incomplete, and will not be rerun.

- Enable
Displays a status of 10 to indicate the task will be rerun.

- Complete
Displays a status of 60 to indicate the task is complete, and will not be rerun.

6.6 Configuring Your Locations

Location Workbench copies all locations that are defined in the plan from the F9654 table in the Planner data source to the System - 910 data source. It also updates the F984021 table. Use this procedure when running Workbench in attended mode or if you set a task break before Location Workbench.

1. On Location Workbench, verify that all of your locations are listed.

2. Select Configure from the Form menu.
Locations are configured, and the Data Source Workbench form appears.

The system updates the Detail Status to 60 and changes the Status Description from Validated to Installed.

6.7 Configuring Your Data Sources

Data Source Workbench copies all data sources that are defined in the plan from the F98611 table and the F986115 table in your Planner data source to your System - 910 data source. It also updates the F98401 table to indicate completion. Use this procedure when running Workbench in attended mode or if you set a task break before Data Source Workbench.

1. On Data Source Workbench, verify that all of your data sources are listed as illustrated in this example.

2. Select Configure from the Form menu.
Your data sources are configured, and the Environment Workbench form appears.

When the system has configured your data sources, it updates Detail Status to 60 and changes the Status Description from Validated to Installed.

6.8 Configuring Your Environments

Environment Workbench copies the F0094, F00941, and F00942 tables, as well as the F986101 table for each environment, from your Planner data source to your System - 910 data source. It then updates the F98403 table to indicate completion. Depending on the plan settings, it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables.

Environment Workbench can run multiple batch applications simultaneously, which enables Release 9.1 to load multiple environments at the same time. This reduces the amount of time it takes to load environments.

Use this procedure when running Workbench in attended mode or if a task break is set before Environment Workbench.

1. On Environment Workbench, review each environment and its associated parameters to make sure the values are correct.

2. After you review the environments, select Configure.

3. When Environment Workbench has completed, verify that the status of each environment has been updated to 60 and that the status description has changed from Validated to Installed.

4. Using Adobe Acrobat, review all XJDE reports, and confirm that all configuration statuses indicate Success.

6.9 Using Machine Workbench

Machine Workbench copies the F9650 and F9651 table from the Planner data source to the System - 910 data source. It then updates the F98402 table to indicate completion and uses the environment information to populate the F986101 and F98611 tables in the Server Map data source.

Note:
Only valid environments, data sources, and server map tables are created.

1. On Machine Workbench, review each server and its associated parameters for the correct values.

2. Select Configure from the Form menu.
When the system has configured your servers, it changes the detail status to 60, and Status Description changes from Validated to Installed.

6.10 Using the Package Workbench

Package Workbench transfers the F9603 and F9631 tables from the Planner data source to the System - 910 data source. It then updates the F98404 table to indicate completion.

Use this procedure when running Workbench in attended mode or if a task break is set before Package Workbench. Refer to the JD Edwards EnterpriseOne Tools Package Management Guide for complete information about building and configuring packages.

1. On Package Workbench, review your packages.

2. Select Configure from the Form menu.

6.11 Using Remote Location Workbench

Note:
This workbench only appears when Remote Locations have been set up.

Remote Location Workbench loads business (master and constant), control, data dictionary, and system tables from base location to remote location servers, by launching different versions of R98403 (XJDE0043, XJDE0044, XJDE0045, XJDE0046 and XJDE0047). It also pushes delivered packages to primary Deployment Servers at remote locations by launching the multi-tier UBE (R98825C). This workbench is processed only if you opted to install remote locations and chose to load replicated data and push packages.

Use this procedure when running Workbench in attended mode or if a task break is set before Remote Location Workbench.

6.11.1 Configuring Remote Locations

To configure remote locations:

To configure your remote locations:

1. On Remote Location Workbench, Release 9.1 displays all remote location activities in the detail area.

2. On the Form menu, select Configure to launch the workbench.

3. After all remote location activities are complete, click Next.

6.12 Finishing Installation Workbench

To finish the Installation Workbench:

1. From Congratulations, on the Form menu, click Finish.

2. From Work with Installation Plans, click Close.

Note:
Post Install Procedures still need to be completed from a client. See Chapter 10, "Performing Post Installation Tasks".

6.13 Deploying an Oracle or Partner Business Accelerator Configuration (optional)

If you choose to deploy a Business Accelerator Configuration, this must be done prior to installing any ESUs or Updates other than the Planner Update. The execution of the Q&A portion can be done even before JD Edwards EnterpriseOne has been installed. However, the resulting configuration cannot be deployed until all Installation Workbenches have successfully completed.

You must build a full package after deploying the Business Accelerator in order to see all the changes that the Business Accelerator delivers.

For detailed instructions on downloading and deploying Business Accelerators, see the Oracle Business Accelerators for JD Edwards EnterpriseOne Installation Guide, which is available from My Oracle Support (https:\\support.oracle.com). From that site, you can locate this document by search for this document ID: 705506.1.

7 Working With the Enterprise Server

This chapter contains these sections:

- Section 7.1, "Verifying the Enterprise Server Installation Using PORTTEST"

- Section 7.2, "Starting Network Services on the Enterprise Server"

- Section 7.3, "Stopping Network Services on the Enterprise Server"

- Section 7.4, "Creating an Output Queue for the Default Printer"

- Section 7.5, "Creating the Job Queue"

- Section 7.6, "Working with OCM Generation"

- Section 7.7, "Setting Up a Printer on the Enterprise Server"

7.1 Verifying the Enterprise Server Installation Using PORTTEST

Note:
When running PORTTEST after installing the Enterprise Server, the test returns a failure message. This is because it is not able to access the F0902 table at this time, (the format of the F0902 table changes during the Table Conversion Workbench). Ignore any errors relating to accessing the F0902 table, (for example, Select all on table F0902 failed - rcode=0). Once the Workbench tasks are all complete, and the Enterprise Server is configured, rerun PORTTEST.

To verify the Enterprise Server installation using PORTTEST:

1. Log on to the IBM i Enterprise Server as ONEWORLD (or other Release 9.1 user).

2. On Current Release 9.1 Versions, select the version of Release 9.1 that you want to use and press Enter.

3. To verify that Release 9.1 is installed correctly on the Enterprise Server, enter these command:
GO JDEOW\A98OWMNU

4. On the A98OWMNU menu, select selection 4 to run PORTTEST.
This program initializes a user and an environment. The program selects records from the F0902 table, which appear as messages on your screen. If messages indicating your selections do not appear, review the jde.log file. You should log on to each environment that you installed using JDE as the user and JDE as the password.

Note:
If you are running PORTTEST prior to running Table Conversions, it will fail half-way through because the F0009 and F0010 are not in the correct format.

Tip:
If PORTTEST fails to run, refer to Section 14.1, "Using the PORTTEST Checklist" for diagnostic assistance.

7.2 Starting Network Services on the Enterprise Server

To start the network services on the Enterprise Server:

1. Log on to the IBM i Enterprise Server as ONEWORLD (or other Release 9.1 user).

2. On Current 9.0 Versions, select the version of Release 9.1 that you just installed, and press Enter.

3. The first time you start the IBM i Enterprise Server, enter these commands and options:
GO JDEOW\A98OWMNU

select selection 6 to end JDE Server.

select selection 7 to clear the IPC.

4. To start the Enterprise Server, use these options:
select selection 5 to start the JDE Server.

select selection 8 to display active jobs.

5. Verify that the entry NETWORK is running with PGM-JDENET N in SELW status.

7.3 Stopping Network Services on the Enterprise Server

To stop the network services on the Enterprise Server:

1. Log on to the IBM i as ONEWORLD.

2. On the IBM i command line, enter this command:

ENDNET

This command ends JDENET from an IBM i display, ends the JDENET jobs, and cleans up JDENET run-time structures.

3. On the IBM i command line, enter:

ENDSBS SBS(JDE) OPTION(*CNTRLD)

where is the release to which you are installing (for example, E910).

This command ends the JDE subsystem.

4. On the IBM i command line, enter:

WRKACTJOB SBS(JDEx)

where x is the release to which you are installing (for example, E910).

Wait until the JDE subsystem ends before you continue.

7.4 Creating an Output Queue for the Default Printer

To create an output queue for the default printer:

1. Log on to the IBM i as the QSECOFR.

2. Enter this command:
GO JDEOW\A98OWMNU

3. Enter the appropriate selection to create an output queue.

4. Complete these fields and press Enter:

Field

Description

Outqueue Name

The outqueue name for the printer.

Printer IP Address

The network address of your printer.

Remote Printer Queue

You are required to set the remote printer queue (parameter RMTPRTQ) to something other than ( ` ) and ( ' ) for some printers. For example, you must set this parameter to PASS for the IBM network Printer 4317. See the printer's user manual for additional information.

7.5 Creating the Job Queue

To create the job queue:

1. Log on to the IBM i as the QSECOFR.

2. Enter this command:

GO JDEOW\A98OWMNU

3. From the menu, select this option:
11 - Create Job Queue

4. To determine the unused sequence number, enter this command:

DSPSBSD SBSD(QBATCH)

Select the option for Job Queue Entries, and then record an unused sequence number.

7.6 Working with OCM Generation

This section discusses:

- Section 7.6.1, "Understanding OCM Mappings"

- Section 7.6.2, "Understanding Data Source Setup"

- Section 7.6.3, "Understanding OCM Creation"

- Section 7.6.4, "Understanding OCM Customization"

7.6.1 Understanding OCM Mappings

JD Edwards EnterpriseOne does not ship Object Configuration Manager (OCM) records for standard environments in Release 9.1. They are generated when you finalize an installation plan. OCM is created based on the Data Class for data sources and for a table or GT object. The Data Class is stored on the Data Sources By Environment (F98511), Data Source Master (F98611) and Object Librarian Master (F9860) tables.

7.6.2 Understanding Data Source Setup

Before OCM can be created, you must configure your data sources. Data source configuration and prompting is driven by the data in the F98511 table.

The first set of data sources to be configured is the Enterprise Server data sources. This includes the Server Map data source. Also, logic data sources are automatically configured without prompting. OCM records are not created for the server map data source. UBE, BSFN, RTE, and XAPI mappings are created for the logic data sources.

The next set of data sources to be configured is the shared data sources. This includes System, Data Dictionary, and Object Librarian data sources. The first time these data sources are configured, the shared data source template (F98511.SPLL = *SHARED) is copied and tokens are replaced in the data source name and properties to create the shared data source records (F98511.SPLL = DEFAULT). These defaults are then used to create the data source definition in the F98611 table. If record in the F98611 tables already exists, the defaults from the F98511 table are overridden by the current definition. The user is then optionally prompted to customize the data source.

The last set of data sources is the environment data sources. A set of data sources is configured for each environment. This includes Business Data, Control Tables, Central Objects and Versions.

The environment data source template (F98511.SPLL = *ENV) stores defaults for environment data sources. As data sources are configured for an environment, these records are copied and tokens are replaced in the data source name and properties to create records for the environment (F98511.SPLL = Environment Name). These defaults are then used to create the data source definition in the F98611 table. If records in the F98611 table already exists, the defaults from the F98511 table are overridden by the current definition. The user is then optionally prompted to customize the data source.

Given that the standard environments do not always follow the defaults that are specified in the *ENV template, JD Edwards EnterpriseOne provides preconfigured records for the standard environments. Thus, the *ENV template is only used for custom environments.

7.6.3 Understanding OCM Creation

After your data sources have been defined and the plan is complete, the plan is finalized. OCM is created during finalization.

This section describes:

- Section 7.6.3.1, "Understanding Database Data Sources"

- Section 7.6.3.2, "Understanding Logic Data Sources"

7.6.3.1 Understanding Database Data Sources

The process finds the data class for each table or GT object in Object Librarian (F9860.SICLDF). Based on the environment that is being configured and the data class for the object, the data source name is fetched from F98511. If a record is not found, it looks for a record for the data class where environment name is DEFAULT (to determine whether it should be mapped to a shared data source). If a record is not found, no mapping is created and the table is effectively mapped to the default data source. If a record is found and that record is set as the default mapping data source (F98511.SPDFLTMAP), a mapping with object name DEFAULT is created; otherwise the actual object name is used. Mappings are not created for tables in the Planner and Internal data classes.

7.6.3.2 Understanding Logic Data Sources

The OCM generation algorithm for UBEs and BSFNs are identical to each other, but the output depends on whether the default mapping is LOCAL or an Enterprise Server.

The following table shows the default mappings for UBE and BSFN objects.

UBE or BSFN

Base EnvironmentDV910, PS910, PD910, PY910

HTML Web Server EnvironmentJDV910, JPS910, JPD910, JPY910

UBE

Enterprise Server

Enterprise Server

BSFN

LOCAL

Enterprise Server

The algorithm is:

- If the default is LOCAL, a default mapping to LOCAL is created. Server mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in Object Management Workbench (OMW) is Server Only (F9860.SIBFLOCN = 3).

- If the default is Enterprise Server, a default mapping to the Enterprise Server is created. LOCAL mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in OMW is Client Only (F9860.SIBFLOCN = 1).

7.6.4 Understanding OCM Customization

This section discusses:

- Section 7.6.4.1, "Understanding Data Classes"

- Section 7.6.4.2, "Creating a New Data Class"

- Section 7.6.4.3, "Modifying the Data Source Template"

- Section 7.6.4.4, "Associating Table Data Classes"

7.6.4.1 Understanding Data Classes

The data class is at the center of automatic OCM generation. It categorizes the type of data stored in data sources and tables, for example, in the Business Data data source the data class is B while in the System data source the data class is S. If you want to split business data into multiple data sources, you need to create a new data class, add a data source to the data source template for that data class (so Installation Planner prompts for the data source) and assign tables and GT objects to that data class. OCM will be created based on this information. You should do these steps before creating your plan.

7.6.4.2 Creating a New Data Class

You must create a new data class by adding a value to the H96/DU User Defined Code (UDC) for data sources and H96/CL UDC for table and GT objects.

7.6.4.3 Modifying the Data Source Template

A data source template defines the set of data sources that will be used by an environment, and the default values for the properties of the data source. They are stored in the F98511 table.

The information in this table can be edited using Data Source Templates By Environment (GH9611) program. By understanding this application, you can implement custom environment naming standards and ease the creation of environments.

Typically, you will add records to the template for new environments. The template can be found by filtering on *ENV in the environment field. Installation Planner prompts for this set of data sources whenever a new environment is created. The first time data sources are configured for a new environment, these records are copied and tokens replaced to create records specific to the new environment.

If you want to add a new data source to a standard JD Edwards EnterpriseOne environment, enter the environment name into the filter field and add a record specifically for that environment.

Records with an environment *LOGIC are for logic and server map data sources. They are set up when selecting an Enterprise Server.

7.6.4.4 Associating Table Data Classes

A table is associated with a data class using a field on the Object Librarian table (F9860.sicldf). Table data classes can be modified two ways.

- Object Management Workbench (GH902) - Select the table in the left tree view in OMW and click Design.
Select the Install\Merge Codes tab and modify the data class value. Click OK. Modifying the data class does not affect existing OCM mappings, it is only used when creating mappings for a new environment.

- Table Data Classes - This application can be used to modify the data class for several tables at once.
This should only be used by a JD Edwards EnterpriseOne administrator. Go to GH9611 and open Table Data Classes. Use the QBE to filter the list of tables in the grid. Select one or more tables whose data class will be changed. Click Select. Type in the new data class value and click OK.

Once these three steps have been taken, planner will prompt for the new data source and create OCM mappings for the new data source whenever an environment is added to a plan and the plan is finalized.

Environment

Object Name

User/Group

Data Source

ENV1

DEFAULT

*PUBLIC

Business Data - ENV1

ENV1

F0094

*PUBLIC

System - 910

ENV1

F9860

*PUBLIC

Object Librarian - 910

ENV1

F9200

*PUBLIC

Data Dictionary - 910

ENV1

F0004

*PUBLIC

Control Tables - ENV1

ENV1

F983051

*PUBLIC

Versions - PY910

ENV1

GT92002

*PUBLIC

Data Dictionary - 910

ENV1

GT9860A

*PUBLIC

Object Librarian - 910

ENV2

DEFAULT

*PUBLIC

Business Data - ENV2

ENV2

F0094

*PUBLIC

System - 910

ENV2

F9860

*PUBLIC

Object Librarian - 910

ENV2

F9200

*PUBLIC

Data Dictionary - 910

ENV2

F0004

*PUBLIC

Control Tables - ENV2

ENV2

F983051

*PUBLIC

Versions - DV910

ENV2

GT92002

*PUBLIC

Data Dictionary - 910

ENV2

GT9860A

*PUBLIC

Object Librarian - 910

7.7 Setting Up a Printer on the Enterprise Server

This section describes these tasks, which must be performed in the deployment environment:

- Section 7.7.1, "Adding a New Printer"

- Section 7.7.2, "Defining a Default Printer"

You also can print Release 9.1 reports, modify existing printers, and delete printers. These tasks are described in detail in the JD Edwards EnterpriseOne Tools System Administration Guide. Refer to that document to learn more about setting up a printer to run from the Release 9.1 Enterprise Server.

7.7.1 Adding a New Printer

Release 9.1 provides a Printer Setup director to help you add printers. Instructions appear on each form of the director to guide you through the printer addition process. This procedure is used in conjunction with the steps that appear on the forms of the Printer Setup director.

To install your first printer:

1. On the Printers menu (GH9013), select Printers (P98616).
The Printers form appears.

2. On the Printers form, click Add Printer.
The welcome page for the Printer Setup director appears. This page describes the tasks that the director helps you perform.

3. Review the welcome page and click Next.
The Platform Information form appears. The platform type may appear by default, depending on the operating system on which Release 9.1 is running.

4. On Platform Information, complete these fields:

Field

Description

Platform Type

Enter the platform type on which you are installing or use the visual assist button to select a platform type.

Library Name

The physical printer name must be the same as the outqueue name. If you use the default QGPL library to store your outqueues, you need only enter the outqueue name in this field. Valid characters are all alpha (A-z), numeric (0-9), at ( @ ), and underscore ( _ ).

Ouputqueue Name

If your outqueues reside in a library other than the default QGPL library, you need to enter the library name and the outqueue name in this field. For example, QUSRSYS\DEVDES3A. Valid characters are all alpha (A-z), numeric (0-9), at ( @ ), and underscore ( _ ).

5. After you complete the requisite fields, click Next to access the Printer Setup form.
Use this form to set information for the printer such as the printer model, physical location of the printer, printer definition language (PDL), and paper types.

6. On the General tab, complete these fields:

- Printer Model

- Printer Location

7. On the Details tab, in the box labeled Printer Definition Language, select one of these options:

- PostScript

- PCL

- Line Printer

- Custom

8. In the Default box, specify one of the Printer Definition Language options as the default value.
You can select multiple PDLs, but only one default PDL. A user can override this default PDL at the time a batch process is submitted.

Choosing PostScript or Printer Command Language (PCL), Release 9.1 disables the Line Printer option. Choosing Line Printer, Release 9.1 disables the PostScript and PCL options.

When choosing the Line Printer option, this logic occurs:

- Release 9.1 disables the grid at the bottom of the form and any paper types you have chosen are cleared.
JD Edwards EnterpriseOne automatically provides a printer type of *JDE LINE PAPER for the printer.

- The Fields in the box labeled Line Printers are used to set the paper dimensions and line parameters.
This procedure is explained in later steps in this section.

The custom option uses advanced features of the printers application, which are explained in the later steps in this procedure.

9. On the Details tab, when choosing the PostScript option, the Paper Source box appears and you can change these options:

Field

Description

Max Number of Paper Sources

Enter a numeric value in this field to indicate the number of paper trays this printer has available.

Default Paper Source

Enter a numeric value in this field to indicate which tray number you want Release 9.1 to draw paper from as the default tray.

10. On the Details tab, when choosing the Line Printer option, fields appear in a box labeled Line Printers, which you use to set the paper dimensions and line parameters.
Complete these fields:

Field

Description

Characters Per Inch

Enter a value to specify the number of characters in one horizontal inch.

Columns Per Page

Enter a value to specify the number of characters in one line of text in the specified report.

Lines Per Inch

Enter a value to specify the number of lines of text in one vertical inch.

Lines Per Page

Enter a value to specify the number of lines of text on one printed page.

Printer Paper Width

Displays a value that is calculated automatically based on the values entered in the Line Printers box.

Printer Paper Height

Displays a value that is calculated automatically based on the values entered in the Line Printers box.

11. On the Details tab, the Custom option lets you specify a conversion filter to use.
When choosing the Custom option, a field appears beneath the Custom checkbox. Enter the name of the conversion filter you want to use or use the visual assist to select a filter from the Conversion Program Search and Select form.

12. If you do not want to change or add a conversion filter, skip to Step 16 in this task.
To change or add a conversion filter, from the Form menu, select Advanced, and continue with the steps in this procedure. The Advanced option is enabled only when Custom has been chosen.

The Work With Conversion Programs form appears.

13. Either click Add, or highlight one of the filters and click Copy or Select.
The Advanced Conversion Program form appears.

14. Change one or both of these fields:

Field

Description

Conversion Program

If you clicked Add or Copy on the previous form, the Conversion Program field is enabled. Enter the name of the conversion program that you want to add or copy. When making a copy, the Parameter String field is populated with the string that you highlighted on the previous form.

Parameter String

The JD Edwards EnterpriseOne system automatically enters the parameter string in native commands based on the host type from which you are printing and the type of printer (PostScript, PCL, or line).
For example:

-s string_name -l
library_name -f convertPDFToPS

where -s defines the string name, -l (the letter l, not the numeral 1) defines the library name, and -f defines the function name.

15. Click OK.
The Work with Conversion Programs form appears.

Click Close.

The Printer Setup form appears.

16. In the grid at the bottom of the Printer Setup form, double-click the row header for each paper type that your printer supports. A checkmark appears in the row header for each paper type that you select.

Note:
You can add new paper types as necessary. Instructions are included later in this task.

17. In the Default Type column, enter the numeral 1 in the row for the paper type you want to use as the default.
select only one paper type as the default. A user can override the default paper type when a batch process is submitted.

18. To add a new paper type, continue with these steps:

19. From the Form menu, select New Paper Type.
The Work With Paper Types form appears.

20. Click Add.
The Paper Type Revisions form appears.

21. Complete these fields:

- Paper Type

- Paper Height

- Paper Width

- Unit of Measure

The software saves the new paper type.

22. Click OK to return to the Work With Paper Types form, and then click Close to return to Printer Setup.
The new paper type is available in the grid on the Printer Setup form. All previous paper type selections are cleared and must be reselected if you want to use them again.

23. When finished entering information for the printer on the Printer Setup form, click End.
Release 9.1 saves the new printer setting and returns you to the first form in the Printers application.

Field

Description

Platform Type

Define the type of physical hardware on which the database resides.

Server Name

Define the computer that receives documents from clients.

Printer Name

Enter a name that refers to a shared resource on a server. Each shared directory on a server has a share name, which is used by clients to refer to the directory.

Printer Model

Define these attributes for your printer:

- Printer Model

- Printer Location
Designates the physical location of the printer

- Encoding

Paper Type

Enter a user defined code (H98\PT) to define the type of printer paper, such as letter or legal. For example, LETTER, LEGAL, and A4.

Paper Width

Define the width of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure.

Paper Height

Define the height of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure.

Unit of Measure

Enter a user defined code (00\UM) to define the quantity in which to express an inventory item. For example, CS (case) or BX (box). Form-specific information indicates the unit of measure in which the paper height and width are entered. For example, IN = Inches and MM = Millimeters.

Columns Per Page

Define the number of columns per page. For example, 80 or 132.

Characters Per Inch (CPI)

Define the horizontal printing density in characters per inch.
You should only define values that are supported by your printer.

Line Per Page

Define the number of lines per page. For example, 60 or 66.

Line Per Inch (LPI)

Define the line spacing in lines per inch.
You should only define values that are supported by your printer.

Values are:

4 - IBM 5219, 5224, 5225, and 3287 printers only

6 - IBM 5224 printer only

8 - IBM 5224 printer only

9 - IBM 5225 printer only

Note: The standard computer print is 6 LPI and 10 CPI. If you are printing on 8 1-2-inch x 11-inch paper, typically you would specify 8 LPI and 15 CPI.

Maximum Number of Output Tray

Define the maximum number of paper trays available on the printer you are setting up.

Output Tray Name

Define the output tray for a given batch print job.

7.7.2 Defining a Default Printer

To define a default printer:

1. On the Printers menu (GH9013), select the Printers (P98616) program.

2. On the Printers form, click Define Default Printer.
The Work With Default Printers form appears.

3. Click Add.

4. On Default Printer Revisions, complete these fields and then click OK.

Field

Description

User\Group

Click the visual assist to select either a particular user for this printer or to select an entire group.

Report Name

Click the visual assist to select a specific report to print. Enter *ALL for all reports.

Version Name

Click the visual assist to select a specific report to print. If the value in the Report Name field is *ALL, the system populates the Version Name field with the default value of *ALL and makes the field unavailable for subsequent modification.

Environment

JD Edwards EnterpriseOne provides a default value for this field based on the environment that you are currently logged onto. Enter *ALL for all environments. You can change this information.

Printer Name

Enter the name of your printer.

Host Name

Enter the name of the host server where reports will be processed. The visual assist displays the appropriate host names based on the printer name you select. To use this printer for all hosts in your environment, enter *ALL.

Object Status

Define the new printer as the default printer by changing its status to active. If an error occurs, it means that another printer is currently the active default. Change the original default printer to inactive before making the new printer active. Change multiple statuses from the Work With Default Printers form, as explained at the end of this task.

5. Click OK, and then click Cancel to access the Work With Default Printers form.

6. To change the status of a default printer, select a default record and, from the Row menu, select Change Status.
If another printer is already set as the active default, an error occurs. To change the original default printer to inactive, select it, select Change Status on the Row menu, and then select the new printer as the default.

8 Installing the Development Clients for Developers and System Administrators

This chapter includes these topics and tasks:

- Section 8.1, "Understanding Development Client Installation"

- Section 8.2, "Preparing for Development Client Installation"

- Section 8.3, "Working With Development Client Installation"

- Section 8.4, "Understanding User Profiles and Languages"

8.1 Understanding Development Client Installation

Release 9.1 software for Development Clients is first installed on the Deployment Server, and then deployed from the Deployment Server to Development Clients for developer and system administrator workstations.

The Development Clients are Microsoft Windows-based machines. Refer to the Oracle Certifications for specifically-supported versions of Microsoft Windows.

Note:
The JD Edwards EnterpriseOne installation delivers pre-built packages that are ready for use as delivered.
In order for the Development Client to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and Development Clients, in addition to the procedures to verify and modify the JDE.INI on the Development Clients and the JDE.INIjde.ini on the Enterprise Server.

See Also

- Refer to Section 1.6, "Language Process Overview" for more information about how you enable multilingual installations on Development Clients.

- JD Edwards EnterpriseOne Development Client Installation and Configuration Guide

- JD Edwards EnterpriseOne Tools Package Management Guide

8.2 Preparing for Development Client Installation

To prepare for the installation of Release 9.1 on Development Clients, you must modify the Development Client 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.1. 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, "Working With Development Client Installation"

Note:
Refer to the JD Edwards EnterpriseOne Development Client Installation and Configuration Guide for additional details on installing the Development Client.

Prerequisites

- Before installing Release 9.1 on a Development Client used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in the Minimum Technical Requirements (MTRs). Refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)". Also refer to the appropriate Microsoft documents for installation information.

- The names of the Deployment Server, Enterprise Server, and the Development Client cannot exceed 15 characters in length.

- IPv4 Requirement
The Development Client requires Microsoft Windows IPv4 for connectivity. It cannot function with IPv6. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide details.

Note:
You must have full administrator privileges to install Release 9.1 on the Microsoft Windows 7-based Development Clients. For details, refer to the JD Edwards EnterpriseOne Development Client Installation and Configuration Guide on the Oracle Technology Network (OTN).

During Development Client 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\E910\PD910\package

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

For example:

\\deployment_server_name\E910\client

- Refer to the Deployment Server Reference Guide in Setting Up a Development Client Installer on the Deployment Server for these topics:

- Understanding the JD Edwards Clients (Development and Web)

- Understanding the Oracle Universal Installer

- Creating the Web Development Feature

- Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server

- Updating the Database Drivers in the JDBJ.ini File

- Copying the JDK to the Deployment Server (OH4A Only)

- Updating the InstallManager.htm File

- Updating the oraparam.ini File

- Setting Up Local Database Installers

- Refer to the Development Client Installation Guide for these topics:

- Understanding the Development Client Installation
This section describes Understanding Installation Steps and Understanding Destination Paths.

- Installing WebSphere Express 7.0 or WebSphere for Developers 7.0

- Installing the Local Database

- Installing the Development Client

- Working With SnapShot on the Development Client

- Deinstalling the Development Client

- Removing the Local Database

- Troubleshooting the Installation Process

- Installing a Development Client from the Command Line

- Manual Cleanup of a Deinstalled Development Client

- Manual Cleanup of a Deinstalled Oracle Database

- Installing Multiple Pathcodes

8.3 Working With Development Client Installation

The Development Client installation program copies all necessary components of Release 9.1 to a Development Client. 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 Development Client 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.3.1, "Creating a Desktop Shortcut"

- Section 8.3.2, "Using a Shared Drive"

- Section 8.3.3, "Understanding Third-Party Products"

8.3.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 Development Client. 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: Using a Shared Drive.

8.3.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 Development Client 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.3.3 Understanding Third-Party Products

A local Oracle Enterprise Edition (OEE) is required for Release 9.1 Development Clients. The OUI installer for the Development Client installs OEE and the Development client separately. Refer to the Development Client Installation Guide.

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.4 Understanding User Profiles and Languages

Note:
Release 9.1 supports group preferences for user profile Development Client configuration and environment assignment.

For user and group profiles, you should use the preloaded users to perform the installation process. The system administrator needs to create a user profile before the user can log on to Release 9.1.

All users are assigned a language preference code within the user profile. The language preference code field specifies which language is presented on the applicable form or report. You can set up your users and groups when determining how groups are to be organized and what preferences each group shared to have.

For languages, the JDE.INI on the Windows-based Deployment Server are updated automatically. For multiple language usage, both the Enterprise Server and Development Client JDE.INIjde.ini need to be modified for the preferred language being installed.

See Also

- JD Edwards EnterpriseOne Tools System Administration Guide for more detailed information about setting up group profiles and how to use them, as well as for information about defining user display preferences.

9 Understanding Media Object Queues

This chapter discusses these topics:

- Section 9.1, "Overview"

- Section 9.2, "Modifying Media Object Queues"

- Section 9.3, "Specifying the Help Location Used by the Web Client and Development Client"

9.1 Overview

Media objects enable the attachment of information to Release 9.1 applications. Media Object Queues enable you to specify the storage location of media objects to be tracked by reference as opposed to physical network location. This enables easier administration of media locations.

Media object queues provide the system administrator the ability to easily manage the storage of media objects and helps in a Release 9.1 configuration. Within Release 9.1, set up media object queues in order to use images that are outside the domain of the imaging product (for example, scanned images).

Define a media object queue to identify the pointer to the location where the actual image files or Object Linking and Embedding (OLE) objects reside. For OLE objects, the name of the queue must be OLEQUE. The media object queues must reside on a Microsoft Windows-based machine. A valid network-qualified path must exist for this machine. Use the Deployment Server or any other Microsoft Windows-based machine.

If you modify the OLEQUE path, make sure to copy the image files and OLE objects to the new location.

When using the Deployment Server to store media object queues, remember to make the machine available for use daily by Release 9.1 applications.

Media object queue paths are shipped with generic server names. To enable media object queues at the customer site, enter the Deployment Server name in the media object queue path.

See Also

Media Objects and Imaging in the JD Edwards EnterpriseOne Tools System Administration Guide for more information about the use of media objects.

9.2 Modifying Media Object Queues

To modify your media object queues:

1. Log into Release 9.1 as JDE in the DEP910 environment.

2. From System Administration Tools (GH9011), select Media Object Queues (P98MOQUE).

3. To define the location for a new OLE queue, click Add.

4. Complete these fields:

- Name
Enter a valid value for your queue.

- Path
Generally the queue paths include server_name and queue_name. Replace server_name with the name of the Deployment Server or the location of the media object queue. A valid queue path for a network location might be:

\\server_name\E910\queue_name

where server_name is your Deployment Server and queue_name is the name of the media object queue.

When using ComposerCBT, the media object queue path does not require \\ or server_name. ComposerCBT is shipped with an x for the drive name. To enable the Composer CBT queue, replace the x with the drive letter that the workstation uses to access the server where the media object queues reside. For example: N:\Mediaobj\ComposerCBT.

5. To change an existing media object queue, click Find to display a list of queue names and their paths.

6. On Work With Media Object Queues, select the queue name you want to modify.

7. On Media Object Queues, change the information in the Queue Path On-Line field to reflect the new location.

8. Copy the image files and OLE objects to the new location.

9. Exit Release 9.1 and log back on to enable the changes.

9.3 Specifying the Help Location Used by the Web Client and Development Client

To specify the help location used by the Web Client and Development Client:

1. From System Administration Tools (GH9011), select Media Object Queues (P98MOQUE).

2. To define the location for the Help file that is used by the Web Client, on Media Object Queues, enter Help in the Name field and click Find.

3. On Media Object Queue Revisions, complete these fields:

- Queue Path On-Line
Enter this value

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

- Queue Path Off-line
Enter the same value as the preceding field, which is:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

- Type
Enter the value 09. The Type field description changes to PeopleBooks Help Queue.

4. Click OK to return to the Work With Media Objects form.

5. To define the location for the Help Content Queue that is used by the Development Client, on Media Object Queues, enter Help Content in the Name field and click Find.

6. On Media Object Queue Revisions, complete these fields:

- Queue Path On-Line
Enter this value

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

- Queue Path Off-line
Enter the same value as the preceding field, which is:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

- Type
Enter the value 09. The Type field description changes to PeopleBooks Help Queue.

7. On Work With Media Object Queues, enter Help* in the QBE for Queue Name and verify the two help queues are added.

8. Exit Release 9.1 and log back on to enable the changes.

10 Performing Post Installation Tasks

This section contains these tasks:

- Section 10.1, "Setting Up Microsoft Windows Security on Release 9.1 Directories"

- Section 10.2, "Using the Adobe SVG Viewer on Web Clients"

- Section 10.3, "Setting Up Solution Explorer"

- Section 10.4, "Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications"

- Section 10.5, "Enabling CRM Functionality"

- Section 10.6, "Enabling Verity Enhanced Search Capability"

- Section 10.7, "Working with the Data Dictionary"

- Section 10.8, "Working with SETOWAUT"

- Section 10.9, "UBE Performance ' SQL Package Location"

10.1 Setting Up Microsoft Windows Security on Release 9.1 Directories

To set up Microsoft Windows security on the Release 9.1 directories and files on your Deployment Server. Use these charts to determine what permissions are required for the various types of Release 9.1 users and perform these tasks to set permissions on the Security tab:

- Section 10.1.1, "Setting Security on the Pathcode Directory"

- Section 10.1.2, "Setting Security on the Database Directory"

- Section 10.1.3, "Setting Security on the Data Dictionary Directory"

- Section 10.1.4, "Setting Security on the Helps Directory"

- Section 10.1.5, "Setting Security on the Media Object Directory"

- Section 10.1.6, "Setting Security on the Planner Directory"

- Section 10.1.7, "Setting Security on the Print Queue Directory"

- Section 10.1.8, "Setting Security on the System Directory"

Note:
Not all directories are available. The directory names listed in the table below are subdirectories of the \JDEdwards\E910 directory structure. You can apply the indicated permissions to all subdirectories and files except where noted.

10.1.1 Setting Security on the Pathcode Directory

This table lists the settings to set security on the pathcode directory:

User Type

Permissions

JDE
(all subdirectories except \pathcode and \package)

Change
Change

Production users
(all subdirectories except \pathcode and \package)

Read Only
Change

Development users
(all subdirectories except \pathcode and \package)

Change
Change

CNC administrators and application leads
(all subdirectories except \pathcode and \package)

Change
Change

10.1.2 Setting Security on the Database Directory

This table lists the settings to set security on the database directory:

User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

10.1.3 Setting Security on the Data Dictionary Directory

This table lists the settings to set security on the data dictionary directory:

User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

Change

10.1.4 Setting Security on the Helps Directory

This table lists the settings to set security on the Helps directory:

User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Read Only

10.1.5 Setting Security on the Media Object Directory

This table lists the settings to set security on the media object (literal name is mediaobj) directory:

User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Change

10.1.6 Setting Security on the Planner Directory

This table lists the settings to set security on the planner directory:

User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

10.1.7 Setting Security on the Print Queue Directory

This table lists the settings to set security on the print queue (literal name is printqueue) directory:

User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

10.1.8 Setting Security on the System Directory

This table lists the settings to set security on the system directory:

User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Change

10.2 Using the Adobe SVG Viewer on Web Clients

Per the Minimum Technical Requirements (MTRs) for JD Edwards EnterpriseOne web clients (refer to Section 1.3.1, "Accessing Minimum Technical Requirements (Certifications)"), you must have the Adobe Scalable Vector Graphics (SVG) viewer installed on your web clients in order to use specific JD Edwards EnterpriseOne applications, such as Demand Flow Manufacturing.

Within such JD Edwards EnterpriseOne applications, the Graphical Product Synchronization uses the Adobe SVG viewer for displaying the graphics associated with the product synchronization. The JD Edwards EnterpriseOne application automatically detects the Adobe viewer if it is already installed for the browser. If the viewer is not installed for the browser, the system displays a link that you can use to install the viewer from the Adobe web site. The URL for this link is:

http:\\www.adobe.com\svg\viewer\install\main.html

Note:
SVG is a graphics file format and web development language based on XML that enables dynamic creation of high-quality graphics with precise structural and visual control. It is based on standards defined by the World Wide Web Consortium (http:\\www.w3.org\TR\SVG\) .

Tip:
The installation of the SVG viewer may require administrator authority on your client machine.

10.3 Setting Up Solution Explorer

Solution Explorer is the Microsoft Windows-based interface that provides access to Release 9.1 applications, role-based menus, implementation and configuration options, documentation, and training materials. Solution Explorer is a convenient window into Release 9.1.

Users can access Solution Explorer to search and navigate quickly through Release 9.1 applications. Users also can customize Solution Explorer to create their own tasks and link tasks to other Web-based information.

10.3.1 Setting Up Solution Explorer HTML Documentation Path

When Release 9.1 is installed, the system automatically stores HTML documentation hierarchically in folders located in a common documentation directory. Using Media Object Queues, Solution Explorer locates these files and displays the associated documentation in its own window whenever a user selects a task.

The file path from Solution Explorer to the HTML documentation files is defined in the F98MOQUE table; it must be configured by accessing the corresponding program, called the Work with Media Object Queues (P98MOQUE) program. When JD Edwards EnterpriseOne installs the documentation files, it creates an entry in the Media Object Queue table that associates the Queue Name, called ActivEraData, with a generic path to the documentation. For Solution Explorer to link each HTML file with the correct task, you must open this program and change the server name for the directory path associated with the Queue Name ActivEraData. The directory path has this structure:

\\Server_Name\E910\SolutionExplorder\Data

where Server_Name is the name of your Deployment Server.

When the queue name ActivEraData is correctly mapped to the main HTML documentation directory, Solution Explorer locates and displays the associated documentation when a user accesses a Task Location or Task View Location. For example, if a task named JDE001234 exists, the path to the HTML file of the summary document for the task is:

\\Server_Name\PY910\SolutionExplorer\Data\JDE001234\summary.html

where Server_Name is the name of the Deployment Server

For more information on setting up the documentation path, refer to Section 9.2, "Modifying Media Object Queues".

10.3.2 Setting Up the Home Page for Solution Explorer

The home page is generally the first screen a user sees when logging on to Solution Explorer. This screen can be used to display information that is relevant to end users in the enterprise. It can be an external Web site, an intranet site, or even HTML files stored on any server on the network.

During the installation process, a directory called PortalLite is created when the Deployment Server is installed. This directory resides in this path:

x:\base_installation_directory\SolutionExplorer\PortalLite

where x:\base_installation_directory is the drive and directory where you installed Release 9.1 on your Deployment Server.

The PortalLite directory includes a set of HTML files that make up the default Home Page. Even though this directory is on the Deployment Server by default, the directory could reside anywhere on the network, such as on a HTML Web Server or on a local workstation.

When the Release 9.1 client is installed, the system updates the client JDE.INI to point to the location of the PortaLite directory. For example, if the name of the Deployment Server is DepServer1 and the share name is E910, the [Explorer] section of the JDE.INI is updated as follows:

[Explorer]
ExplorerHomeURL="\\DepServer1\E910\SolutionExplorer\portallite\index.html"
ExplorerStart=INTERNET

You can change the above parameters in the JDE.INI to display any HTML file or URL as the default Home Page. This table describes these parameters:

[Explorer] Parameter

Description

ExplorerHomeURL=

Defines the URL or filename of the Home Page that is displayed when the user logs on. The default value is:
\\Depserver1\E910\SolutionExplorer\portalite\index.html

ExplorerStart=

Defines the Explorer start mode. Values are:

- INTERNET
This is the default value. When you start Solution Explorer, the system displays the Internet view first.

- TASK
When you start Solution Explorer, the system displays the last task view the user viewed.

To display a specific task view, use this syntax:

ExplorerStart=TASK:xx

where xx is the task ID of the task view.

10.4 Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications

This topic describes how to configure JD Edwards EnterpriseOne to use the Vertex Quantum tax applications. If you do not use these applications with JD Edwards EnterpriseOne, skip this section.

Release 9.1 can be used with the following Vertex Quantum tax applications:

- Vertex Quantum for Payroll Tax

- Vertex Quantum for Sales and Use Tax

The Vertex Quantum applications should be installed on your system before starting the configuration tasks.

Note:
The Vertex Quantum applications can be used with the Indexed Sequential Access Method (ISAM) database or Oracle database (for either of the Vertex Quantum applications) or the SQL Server database (for Vertex Quantum for Sales and Use Tax). The ISAM database is installed as part of the Vertex Quantum application installation.

See Also

Vertex Quantum for Payroll Tax - Administrator's Guide

Vertex Quantum for Sales and Use Tax - Administrator's Guide

Before configuring Release 9.1 for use with Vertex Quantum applications, install Vertex Quantum for Payroll Tax, Vertex Quantum for Sales and Use Tax, or both on the Enterprise Server. For information about installing the Vertex Quantum applications, refer to the Vertex Quantum administration guides listed above. When installing the Vertex Quantum applications, note the following:

- Note the directory path on the Enterprise Server for the directory in which the Vertex Quantum applications are stored.
This information is needed when copying the Vertex libraries into the Release 9.1 directory structure.

- For Vertex Quantum for Sales and Use Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the SQL Server or Oracle database.

- For Vertex Quantum for Payroll Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the Oracle database.
You cannot use SQL Server with Vertex Quantum for Payroll Tax.

- When using the Vertex ISAM database, note the directory path on the Enterprise Server for the directory or directories in which the Vertex Quantum application databases are created.
This information is needed for establishing Release 9.1 database connectivity.

10.4.1 Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path

To add the Vertex Quantum application directory information to the Microsoft Windows server path:

1. From the Microsoft Windows Enterprise Server, access the Control Panel.

2. On Control Panel, click the System icon.

3. In System, select the Advanced tab.

4. On the Advanced tab, click the Environment Variables button.

5. In the System Variables window, scroll down until the keyword Path appears in the Variable column.

6. Click Edit to display the current path in the Variable Value field.

7. Search the current path (as shown in the Value field) for the Vertex Quantum application directory.
If the directory does not appear, you must add it to the path, as described in the following step. If the directory appears in the path, skip to step 9 in this task.

8. Place the cursor in the Value field, and use the right arrow to scroll to the end of the field and enter this path: x:\vertexDirectoryPath\vertex\utils
where x:\vertexDirectoryPath is the drive and path for the directory in which the Vertex Quantum applications are stored.

Note:
You might need to include a semicolon to separate this entry from previous entries.

9. Click Set.

The new value is saved.

10. After you finish setting the Environment Variables, repeat this task for User Variables, starting from Step 5 in this task.

11. Click OK and reboot the server.
The new path takes effect.

10.4.2 Configuring the Release 9.1 Database Connections for Vertex Quantum Tax Applications

To configure Release 9.1 database connections to use the Vertex Quantum applications:

1. In the Fast Path field, enter G731 to access Vertex Quantum Tax Processing.
The Vertex Quantum Tax Processing panel appears.

2. Highlight and right-click the Database Connections (P7308) program.
A context menu appears.

3. On the context menu, select Prompt for Values.
The Processing Options dialog appears.

4. On Processing Options, click the Quantum tab and enter the following information:

Option #1: Enter which Vertex Quantum applications are installed:

Value

Action

[blank]

Install both Vertex Quantum tax applications.

1

Install the Vertex Quantum for Sales and Use Tax application.

2

Install the Vertex Quantum for Payroll Tax application.

Option #2: Enter location information for the databases:

Value

Action

[blank]

Define databases for both Vertex Quantum tax applications in the same location.

1

Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations.

2

Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations, and the four databases for the Vertex Quantum for Sales and Use Tax application in separate locations.

Option #3: If processing option #2 is set to 1 or 2 (that is, if the Vertex databases are in separate locations), specify the GeoCode database location information:

Value

Action

[blank]

Define the Vertex Quantum Payroll Tax and Sales and Use Tax applications to use the same GeoCode database.

1

Define each of the Vertex applications to use a separate copy of the GeoCode database, and that the two copies are expected in separate locations.

5. Click OK.
The Vertex Quantum Database Connection panel is displayed. The Database Connection panel contains one or more tabs that correspond to the database connections that must be defined. The displayed tabs are determined by the values you entered in the processing options, in Step 4 of this task.

Note:
The GeoCode database is the only Vertex Quantum database that can be shared between the Vertex Quantum Payroll Tax and Sales and Use Tax applications. However, all of the Vertex Quantum databases can be installed in the same location or in different locations.

One or more of the following tabs appears on the Database Connection panel:

Tab

Description

All

All Vertex Quantum application databases for both applications are located on the same server and in the same location.

GeoCode

The same GeoCode database is used by both applications.

GeoCode-Sales and Use

The GeoCode database used by the Sales and Use Tax application is located on this server and location. A separate copy of the GeoCode database, at another location, is used by the Payroll Tax application.

GeoCode-Payroll

The GeoCode database used by the Payroll Tax application is located on this server and location. A separate copy of the GeoCode database, at another location, is used by the Sales and Use Tax application.

Sales and Use

The four databases used by the Sales and Use Tax application are located together, on this server and location.

TDM

The Test Data Management (TDM) database, used by the Sales and Use Tax application, is located on this server and location.

Register

The Register database, used by the Sales and Use Tax application, is located on this server and location.

Rate

The Rate database, used by the Sales and Use Tax application, is located on this server and location.

Payroll

The databases used by the Payroll Tax application are located on this server and location.

6. On the Database Connection panel, select each tab and enter the following information:

- Data Source
Enter the name of the library where the Vertex Quantum tables are located. The location you enter should be the location on the server used for the database when the Vertex applications were installed as previously descripted in this step.

- Server
Enter the name of the IBM i machine where the Vertex Quantum tables are located.

- User ID
Enter a user ID that can access the database.

- Password
Enter the password for the user ID specified above.

7. Click OK.
The changes do not take effect until you have logged off of your system and logged back on.

8. On the Form menu, use IBM i Library to specify the Vertex Quantum library that contains the Vertex Quantum APIs.
For Vertex Quantum for Sales and Use Tax, this library is typically called VERQSU. For Vertex Quantum for Payroll Tax, this library is typically called VERQPRT.

10.4.3 Mapping Objects to the Enterprise Server

Objects that call the Vertex Quantum APIs must execute on the server on which the Vertex Quantum APIs reside. Check that the following Release 9.1 objects are configured in the system OCM to execute on the server. Do not change the mappings.

For Vertex Quantum for Payroll Tax:

- R07200 (Pre-payroll Driver)

- B0700058

For Vertex Quantum for Sales and Use Tax:

- X00TAX.c (Tax Calculator)

- B7300002 (Validate Quantum GeoCodes)

- B7300004 (Retrieve Quantum GeoCodes)

- B7300012 (Validate Quantum Software Information)

- B0000182

- B0000183

10.4.4 Testing the Vertex Quantum Connection from Release 9.1

Use the following procedures to test the Vertex Quantum connection from Release 9.1.

To test the Vertex Quantum for Payroll Tax interface:

1. Access the Payroll Workbench menu (G07BUSP11), and select Pay Cycle Workbench.
The Work with Payroll Cycle Workbench panel appears.

2. Specify pre-payroll information and submit the pre-payroll.
For information about the Payroll Workbench and submitting pre-payroll, see Processing Pre-Payroll in the Release 9.1 Payroll Implementation Guide.

3. If no taxes are being calculated, there may be a setup or configuration problem.
Verify the following to make sure setup is correct:

- UBE R07200 is being executed on the server where the Vertex Quantum for Payroll Tax APIs reside.

- Correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel, as specified in Configuring the Release 9.1 Database Connections for Vertex Quantum Tax Applications.

4. For the Vertex Quantum for Sales and Use Tax interface:
In the Fast Path field, enter P73GEO.

The Retrieve GeoCode panel appears.

5. On the Retrieve GeoCode panel, enter CO in the State field and DENVER in the City field, and click Find.
The code 060310140 should appear in the grid.

6. If nothing appears in the grid, a setup or configuration problem might exist.
Verify the following to make sure setup is correct:

- These values are set in the Work with Quantum Constants Revision table, accessed by the Constants application (P7306) on menu G731:

Quantum Active: Y

Canada Country Code: CA

Note:
Changes to the Work with Quantum Constants Revision table do not take effect until you have logged off of your system and logged back on.

- Required Release 9.1 objects are mapped to the server where the Vertex Quantum for Sales and Use Tax APIs reside.
Also ensure that correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel. Instructions for both procedures are specified in this guide in the section entitled Mapping Objects to the Enterprise Server.

10.4.4.1 Adding an Entry for a Remote Database Directory for Vertex

To add an entry for a remote database directory:

1. Log on to the IBM i as QSECOFR.

2. On the command line, enter:
WRKRDBDIRE

3. Look for an entry on your IBM i for Remote Location *LOCAL. This entry must have the same name as your machine.

4. If you do not have an entry like this, enter 1 in the Option column and enter the machine name in the Relational Database column, and press enter.
In the Remote Location Name or Address enter *LOCAL and press Enter. If you already have a *LOCAL entry and the Relational database name is NOT the same as your machine name, you must remove the entry that you have and add a new entry as above.

10.5 Enabling CRM Functionality

To enable CRM functionality after the installation is complete, you must perform these procedures on the CRM Enterprise Server and the CRM client:

- Section 10.5.1, "Enabling CRM on the CRM Mobile Client"

- Section 10.5.2, "Enabling CRM on the Enterprise Server"

10.5.1 Enabling CRM on the CRM Mobile Client

To enable CRM functionality in JD Edwards EnterpriseOne and the JD Edwards EnterpriseOne mobile client, make sure that the F99410 table has records that contain the following system codes:

- SY90CA

- CRMMSL

- SY49

On your Enterprise Server, access the P99410 application and complete this procedure to enable CRM functionality:

1. On Work with EnterpriseOne System Control, click Add.

2. On EnterpriseOne System Control Revisions, enter each of these system codes, one at a time, in the Data Item field:

- 90CA
This code enables CRM functionality in JD Edwards EnterpriseOne.

- MMSL
With SY49, this system code enables CRM functionality in the mobile client.

- SY49
With CRMMSL, this system code enables CRM functionality in the mobile client.

3. Click Yes.

4. Click OK.

5. Repeat these steps to add each system code.

10.5.2 Enabling CRM on the Enterprise Server

Using an ASCII editor, you must modify the JDE.INIjde.ini on your Enterprise Server to add this section and setting:

[MAILMERGE]
FileLocation=location

where location is a temporary location that you specify for the CRM-related mail merge files that are generated on your Enterprise Server, for example:

\TEMP

10.6 Enabling Verity Enhanced Search Capability

If you are using the enhanced search capabilty with JD Edwards EnterpriseOne, you must download and install the Verity Software from the Oracle Software Cloud Web site at this link:

http:\\edelivery.oracle.com\

10.7 Working with the Data Dictionary

This chapter describes a scenario where you might be modifying your data dictionary on a machine other than your IBM i-based Enterprise Server or if you are modifying your Data Dictionary and not planning on building a package to reflect those changes. In such cases you need to use this mechanism to move the chances to your Enterprise Server.

Additionally, you might find this procedure useful for performance reasons if you do not want your Enterprise Server to JITI data dictionary specifications in real time.

This process is also useful to move generated serialized objects (required for web-enabled applications) from the Microsoft Windows web development workstation on which they were generated to the Enterprise Server.

10.7.1 Recreating Replicated Data Dictionary Files

To recreate replicated data dictionary files:

1. From the Data Dictionary Design menu (GH951), select Recreate Replicated Data Dictionary (R92TAM).

2. On Work with Batch Versions, select version XJDE0001.

3. On Version Prompting, from the Row menu, select Processing Options and enter the following information:

- Language Preference

Use the visual assist button to select the correct value for your language.

- All Languages

Enter the value 1.

4. Click OK.

5. Select version XJDE0001.

6. On Version Prompting, select Advanced from the Form menu.

7. On Advanced Version Prompting, activate the Override Location option.

8. Click OK.

9. On Version Prompting, click Submit.

10. After the job is completed, log off Release 9.1.

10.8 Working with SETOWAUT

SETOWAUT is a set of tools you can use to secure JD Edwards EnterpriseOne objects on your IBM i Enterprise Server. The SETOWAUT objects are delivered in a SAVF by the same name in the JDEOW library. However, it is recommended that you download the latest version of SETOWAUT from the Update Center.

This file can be restored using the RSTLIB command. It should be restored to a library called SETOWAUT. Instructions for using SETOWAUT are found in the JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide.

10.9 UBE Performance ' SQL Package Location

Once the Table Conversions are completed, change the jde.ini setting on the Enterprise Server that controls where SQL Packages are created. The applicable setting is:

[DB SYSTEM SETTINGS]
sqlPackageLibrary=value

where value controls the location where JD Edwards EnterpriseOne will place SQL packages on your IBM i-based Enterprise Server.

This is shipped with a value of 2 in order for Table Conversions to work correctly. You must change this value to 0 or 1 otherwise you will see a negative performance impact on UBEs. Values are listed in this table:

Value

Action

0

Indicates the system to create packages in the library defined in this jde.ini section:

[INSTALL]
DefaultSystem=e1_system

where for JD Edwards EnterpriseOne Release 9.1 the default value for e1_system is E910SYS.

1

Indicates the system will create packages in QRECOVERY and that UBE packages will be named Rnnnnn.
Caution: You will need to delete any old UBE SQL packages in QRECOVERY. Please note that no UBEs can be running on the server while you are deleting these packages.

2

Indicates the system will create packages in QRECOVERY and that UBEs are assigned unique names (job number). For example, a UBE name will be in the format T123456.
Note: You can use this setting for normal daily operations. However it will make the startup for your frequently run UBEs a little slower as they will not be able to use existing SQL packages.

11 Working With Signon Security

For initial installations of JD Edwards EnterpriseOne, you must setup system user(s) using the Work With System Users (P980001) program to populate the F98OWPU table. You must set up system users before you can add and associate a JD Edwards EnterpriseOne user to a system user using EnterpriseOne Security (P98OWSEC).

Caution:
If you attempt to add a user with the P98OWSEC program before you add the system user through the P980001 program, the system may add an invalid record to the F98OWPU table. You might have to delete the invalid record from F98OWPU using the SQL Query tool.
You must perform security setup signed on to JD Edwards EnterpriseOne from a deployed client. If you perform the steps signed on to the deployment server, you will not be updating the correct security tables for your JD Edwards EnterpriseOne system.

This chapter contains the following tasks:

- Section 11.1, "Setting Up Signon Security"

- Section 11.2, "Enabling Server-Side Signon Security"

- Section 11.3, "Enabling Client-Side Signon Security"

- Section 11.4, "Setting Up JD Edwards EnterpriseOne Single Sign-on"

11.1 Setting Up Signon Security

To set up signon security:

1. On P980001 [Work With System Users], click Add.

2. On System User Revisions, complete the following fields:

- System User
JDE

- Data Source
DEFAULT

- Password
Enter a valid password for your installation.

- Password Verify
Enter the same password that you entered in the password field.

3. Click OK.

4. Click Find to verify the new record was added.

5. On P98OWSEC [Work With User Security], complete the following field:

- User ID \ Role
JDE

6. Click Find.

7. Click Add.

8. On Security Revisions, complete the following fields:

- User ID
JDE

- Data Source
DEFAULT

- System User
JDE

- Password
Enter a valid password for your installation.

- User Status
Ensure the Enabled radio button is selected.

- Allowed password attempts
Enter a value applicable to your installation.

- Password change frequency
Enter a value applicable to your installation.

9. Click OK.

10. Click Find to verify that the record was added.

11.2 Enabling Server-Side Signon Security

Ensure the jde.ini on the Enterprise Server has these settings to support signon security:

[SECURITY]
SecurityServer=server_name
User=JDE
Password=JDE
Default Role=*ALL
DefaultEnvironment=PD910
DataSource=System - 910
History=0

After you modify the jde.ini on the Enterprise Server, you must restart the JD Edwards EnterpriseOne Services so the settings can take effect.

Caution:
If you have changed the password for the JDE user, the password you specify on Enterprise Server in jde.ini must be the new password.

11.3 Enabling Client-Side Signon Security

Locate the JD Edwards EnterpriseOne client JDE.INI that is deployed from the Deployment Server. Typically the file can be found at the following location:

x:\JDEdwards\E910\OneWorld Client Install\Misc\JDE.INI

where x: is the drive on which JD Edwards EnterpriseOne is installed.

Ensure that JD Edwards EnterpriseOne client JDE.INI has these settings:

[SECURITY]
SecurityServer=server_name
DataSource=System - 910
DefaultEnvironment=DV910
Default Role=*ALL
Row Security=NO_DEFAULT

11.4 Setting Up JD Edwards EnterpriseOne Single Sign-on

You must set up JD Edwards EnterpriseOne Single Signon Security using the procedures described in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools Security Administration Guide.

Caution:
Using default settings may expose a potential security risk. Thus, it is highly recommended to overwrite the single sign-on settings using the single sign-on configuration applications discussed in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools Security Administration Guide.

12 Building and Testing Packages

This section discusses:

- Section 12.1, "Understanding Packages"

- Section 12.2, "Obtaining the JDK\JRE"

- Section 12.3, "Installing Application Fixes"

- Section 12.4, "Reviewing Pre-Package Build Issues"

- Section 12.5, "Reviewing Troubleshooting Tips"

- Section 12.6, "Building an Alternate Language Package"

- Section 12.7, "Assembling a Package that Contains Published Business Services"

12.1 Understanding Packages

Building and testing packages provides a method to create a package, to define and build a package, to deploy packages to both servers and workstations, and to troubleshoot the packages. These features use a step-by-step director process and include package assembly, package build, and package deployment.

Package build is used to set up a workstation or server with Release 9.1 software. Examples scenarios include:

- Setting up a new workstation.

- Deploying custom solutions to all or to selected users.

- Creating a new pathcode for development.

- Deploying a fix.

- Changing the package from a full to a partial package on some workstations.

There are options to define three different package types, to build and define packages with custom solutions, and to distribute them through two different deployment options. These options are available to a single server, to a workstation or user, or to selected machines, groups, or individual users. These options can be delivered using just-in-time or scheduled installation methods.

You must define, build, and deploy a custom package in order to include any modifications (changed or added business functions or applications) into a package for deployment to workstations (for example, DV910FA or DV910PA).

The system administrator is required to build and test packages at the server level. An installer may complete the process for the workstations. These processes can take several hours, depending on the scope of your business. The procedures take place on the Deployment Server in the deployment environment as user JDE. Release 9.1 installation must be completed on the Enterprise Server before building and testing packages. The time required to build packages to the workstation varies depending on the database being used.

The package build and assembly process includes many critical tasks that must be successfully completed to install the packages correctly. This section includes a list of known issues associated with the package build, assembly, and deployment process and gives instructions for avoiding them. Before building a package, review these instructions to successfully complete this process.

See Also

Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for information about how to build and deploy packages.

JD Edwards EnterpriseOne Tools Development Standards for Business Function Programming Guide for information on how to convert business functions to support Unicode text strings.

12.2 Obtaining the JDK\JRE

You must have a specific JDK\JRE on the Deployment Server in order to build packages. You can obtain the requisite JDK\JRE from Sun.

See Also

For the supported version of the JDK\JRE, refer to Accessing Minimum Technical Requirements (Certifications) in Understanding JD Edwards EnterpriseOne of this guide.

12.3 Installing Application Fixes

Before you build packages, you should install all application fixes relevant to your business. Application fixes include maintenance packs, ESU bundles, and individual fixes. You should use Change Assistant to find relevant application fixes for system codes associated with the functionality you are using.

Change Assistant is a java-based tool that centralizes and economizes the process of searching, identifying, downloading, and deploying many types of software fixes such as ESUs and Tools Releases. It is available free of charge for maintenance paying customers, and can be downloaded from the Update Center.

Tests conducted in the Oracle labs on EnterpriseOne have shown that the use of this tool results in a significant reduction in elapsed time as well as a considerable reduction in manual steps - when compared to current search, download, and deploy processes.

For instructions on using Change Assistant, refer to Using the Change Assistant in the JD Edwards EnterpriseOne Software Update Guide.

12.4 Reviewing Pre-Package Build Issues

Check the following items before building packages in order to minimize errors during package builds. Perform each of the relevant tasks on the machine where the package will be built.

This section discusses:

- Section 12.4.1, "Verifying Available Space in DBMS"

- Section 12.4.2, "Verifying Specific UBEs are Mapped Locally"

- Section 12.4.3, "Verifying the Server-Side Settings"

- Section 12.4.4, "Configuring the Enterprise Server for Simultaneous Builds"

- Section 12.4.5, "Adding a Security Override for Running Package Build"

12.4.1 Verifying Available Space in DBMS

Package Deployment will copy the Central Objects tables in your server database to a new set of Metadata Specifications tables in the same database.

Verify there is enough free disk space for this extra copy.

Note the space used by your Central Objects tables and their indexes. The new set of Metadata Specifications tables will use additional space approximately the same size (for a full package) as your current Central Objects tables plus indexes. Those tables are:

- F98306

- F98710

- F98711

- F98712

- F98713

- F98720

- F98740

- F98741

- F98743

- F98745

- F98750

- F98751

- F98752

- F98753

- F98760

- F98761

- F98762

If you do not have enough free space to accommodate these tables, you must free up some disk space or drop the metadata specifications tables for old packages no longer in use.

12.4.2 Verifying Specific UBEs are Mapped Locally

To verify that specific UBEs are mapped locally:

1. Open the Object Configuration Manager (OCM).

2. Find each of the following UBEs and make sure each is mapped locally and is active: R9621, R9622, R98825C, and R98825D.

12.4.3 Verifying the Server-Side Settings

To verify the jde.ini settings on the Enterprise Server:

1. Open the jde.ini on the Enterprise Server.

2. Verify that the BuildArea setting in the [BSFN BUILD] section points to the PACKAGES directory on the Enterprise Server.
Verify that the following LinkFlags settings are correct:

- Ensure that the path to the system\bin32 directory on the Enterprise Server is valid.

- Ensure that LinkFlags references the path where Release 9.1 is installed.

12.4.4 Configuring the Enterprise Server for Simultaneous Builds

To ensure that simultaneous builds run properly on your Enterprise Server.

1. Open the jde.ini on the Enterprise Server.

2. In the [BSFN BUILD] section, change the SimultaneousBuilds setting to 5 or less (the default is zero, which enables unlimited builds)

12.4.5 Adding a Security Override for Running Package Build

If you have secured your EnterpriseOne libraries, the user running package build must sign on as a user who has rights to create tables in the Central Objects library. If you have Security Server turned on, set up a security override for the EnterpriseOne user so that when they connect to the data source, they connect as a system user (IBM i user profile) who has update rights to the library.

Adding a security override must be done by a security administrator. To add a security override, you must first add a system user for the user profile which has update rights to the library (for example, the library owner), and then add an override for the EnterpriseOne user who will run the package build.

Refer to the Package Management Guide for further details on setting up security overrides for package build.

12.5 Reviewing Troubleshooting Tips

The following troubleshooting tips are designed to help avoid known issues with the package build, assembly, and deployment process. Review these tips when working through the process.

- When naming your packages, do not use these names:

- CLIENT

- SERVER

- Verify the assemble and build processes completed.
After entering the package information on both the Assembly and Build forms, click the End icon to save the information.

- Verify setting on the package definition screen.
When selecting servers on the Build Definition form, ensure that a check mark appears next to each server selected. If no check mark appears, highlight the server in the grid and click Select.

- Recompress the parent packages.
After building an update package that updates the parent package, you must recompress the parent package. This step does not occur automatically.

- Verify the location of server packages.
When building an update server package, the specified parent package must be stored under the package directory on the server. If the parent package is not under the package directory, the update package does not build.

12.6 Building an Alternate Language Package

A package represents a copy of the central objects at a point in time. It contains replicated objects that Release 9.1 reads at run-time. If custom modifications or text overrides have been made at the time that a software upgrade is performed or to deploy development changes, including a specific language, to a local workstation, build a package and specify which language or languages to include in that package. This action involves the following considerations:

- Section 12.6.1, "Package Build Considerations"

- Section 12.6.2, "Package Deployment Considerations"

12.6.1 Package Build Considerations

Before beginning to build a language package, verify that the language installation is complete. To build the language package, first define the package. Building the package can take several hours, depending on the size of the package and the number of languages used. This task is completed on the Deployment Server, logged on as user JDE in DEP910.

To include language specifications in your package, specify the language in the package definition. The package build process then uses the language preference code. This code is specified as a parameter when building the package. It uses the relational database tables to build the form design aid text and report design aid text specifications. A language package can be a full, update, or partial package.

Caution:
When building the client package with translated processing option text, run the build using Microsoft Windows with the system locale set to the appropriate language. If the system locale on the operating system does not match the installed language, the translated text in processing options (POTEXT) will be corrupted.

Building server packages that include languages other than English requires that the LocalCodeSet value of the Release 9.1 client matches the LocalCodeSet value of the jde.ini on the Enterprise Server. If the LocalCodeSet value on the local client differs from the one specified on the Enterprise Server, the server package build fails and errors are logged in the jde.log on the Enterprise Server.

12.6.2 Package Deployment Considerations

A translated package cannot be deployed to a workstation if the appropriate character set is not installed on that workstation. For example, if creating a package containing Japanese text, the workstation must be loaded with Japanese Microsoft Windows to view the Japanese data correctly.

Caution:
To transfer translated objects to a server, complete the server package installation procedures. Define each object you have modified for languages. Therefore, track the objects you changed to include them in a package.

Note:
To move all objects, call Global Customer Support for assistance.

See Also

JD Edwards EnterpriseOne Tools Package Management Guide for more information about transferring objects to the server.

12.7 Assembling a Package that Contains Published Business Services

To assemble a Business Services package:

1. Navigate to the processing options for Package Assembly from to the Package and Deployment Tools menu by right-clicking the Package Assembly application (P9601), and selecting prompt for values.

2. Set the processing option entitled Business Services to a value of 1.

Note:
This processing option is blank by default.

3. Click OK.

See Also

- To begin the assembly process, refer to the chapter entitled Assembling Packages in the JD Edwards EnterpriseOne Package Management Guide.

- Building a Package with Published Business Services in the JD Edwards EnterpriseOne Package Management Guide.

- Deploying the Package to the Business Services Server in the JD Edwards EnterpriseOne Package Management Guide.

13 Copying an Environment to Another Environment

Once you have completed the setup and applied fixes and modifications to your Prototype environment, you should copy the data, Central Objects, tested full package, and related records to your Production environment using the process described in this chapter.

Note:
This process cannot be run for a target environment if the target environment and its path code are not already defined in tables F00941 and F00942. It also is dependent on the existence of Data Source Templates for the target environment so that OCM can be generated. You can verify such existence using the Data Source Templates by Environment application P98503 on menu GH9611. The Data Source templates for all standard environments are shipped in your planner database.

This chapter discusses:

Section 13.1, "Setting up the Database Components for the Target Environment"

Section 13.2, "Running the Copy Environment Application (P989400)"

13.1 Setting up the Database Components for the Target Environment

Before running the Environment Copy application, you must set up the database components for the Target environment on your Enterprise Server.

1. Sign onto the Enterprise Server as a user with authority to create libraries. Create the following libraries:

PRODDTA (substitute your business data library)
PRODCTL (substitute your control tables library)
PD910 (substitute your path code)
PD910FA (substitute your target package name)
COPD910 (substitute your Central Objects)

13.2 Running the Copy Environment Application (P989400)

Caution:
If the target path code directory already exists on the Deployment Server or Enterprise Server (for example, from a previous attempt to copy to that path code), you must remove it before you start the copy process. This is necessary because the copy process breaks if another process has a lock on anything within that directory.

For an IBM i Enterprise Server, ensure that you delete the target path code and package libraries that may have been created from a already exist from a previous attempt to copy that path code.

You must run the Copy Environment process on the Deployment Server.

1. From menu GH9611, run the application Environment Copy (P989400).

Note:
For information on Processing Options for this application, refer to Step 3 of this procedure.

Note:
If you have environment definitions, data source definitions, or path code definitions that exist in your System - 910 data source, but which are not defined on the Deployment Server which you will be using in this process, you can check the radio button for Copy Environment Definitions to copy the missing records from System - 910 to Planner - 910.

2. On P989400 - Copy Environment / Packages, click Next.

3. On Environment Copy [Copy to existing environment], complete these fields:

- Source Environment

- Target Environment

- Source Package

- Target Package

Note:
Any environment copy is dependent on the OCM for the target environment. If the OCM does not currently exist, you can enable the checkbox for Generate OCM in System / Server Map to create data sources and OCM for your target environment before doing the copies.

Note:
The Copy Metadata Repository and Rename Metadata Repository options are dependent on certain components having been copied before they are run:

- The package definition records for the target package must exist before the Copy Metadata Repository or Rename Metadata Repository runs. It is recommended that you allow the Copy Environment process to copy the path code and package on the Deployment Server, because that UBE (which runs before the Copy Metadata Repository or Rename Metadata Repository) also copies the package records and the package.inf.

- The Configure Package Manifest option (which is only selectable by running the following step in this procedure) is dependent on both local and enterprise package repositories having been created, and also depends on the target package definition records.

- The Rename Metadata Repository option assumes that you have used system or database utilities to copy all the tables in Central Objects to the new database / owner / library.

4. You can override the default copy flags by clicking on the Advanced Copy form exit which displays this screen:

5. On Advanced Options Environment / Path Codes, if you want to override the default flags, click the Override copy options button.
You are returned to the preceding screen where all the default copy options are unprotected, allowing you to pick and choose which components the process will copy. This non-default method is only recommended if you have provided for the copies in a non-standard way. For example, if you used SAVLIB / RSTLIB in order to make your own copies of Central Objects.

6. After you have set the Environment Copy options as described in Step 3, click Next.
If the data source definitions and OCM for the target environment do not exist, the application generates data source definitions for Business Data, Control Tables, Central Objects and Versions for the target environment. It assumes that the data will be on the same server as the corresponding data sources for the source environment, but you can change this on the Data Source Revisions screens. Below is a sample screen for Business Data:

7. Following the series of Data Source Revisions screens, the next screen Copy Environments - [ Machines].

This screen shows a list of enterprise servers that allows you to select to which enterprise servers you want to copy the package / path codes.

Note:
The process submits a UBE to each selected server. The source path code and package must exist on the selected servers.

8. On Copy Environments - [ Machines], highlight the desired machine from the node that lists Available Enterprise Servers and click the large right arrow to add the machine to the node that lists Selected Enterprise Servers.

9. Click Next.

This screen shows lists all the planned function of the processes of running the business functions and UBEs when you click the End button. All UBEs run locally except for the Enterprise Server Path Code copy, which is submitted to the Enterprise Server.

If you selected Generate OCM, a business function runs that generates data sources and OCM in Planner - 910 and copies them up to System - 910. This business function uses the template data source records in F98511, which can be viewed or revised using the Data Source Templates By Environment application on GH9611. The data source template records for the standard environments (DV910, PD910, PS910, PY910) are shipped with the Deployment Server install.

This table lists details of the UBEs that generate the Path Code Data:

Path Code Data

UBE Details

Business Data

Runs R98403 XJDE0021.

Control Tables

Runs R98403 XJDE0022.

Central Objects and Versions

Runs R98403 XJDE0019.

Deployment Server Directory

Runs R9800942.
This UBE also copies the Package Header / Detail records.

Checkout Records

Runs R989861 XJDE0001.

ESU History

Runs R9672 XJDE0001.

Path Code Directory on Enterprise Server

Submits R9894003 XJDE0001 to the server.

Copy Metadata Repository

Runs R9894005 XJDE0001 to copy the metadata repository within Central Objects.
The local repository is renamed by R9894005 XJDE0002, as the local package directory was copied by R9800942.

Configure Manifest

Runs in UBE R9894005 XJDE0002 to configure the manifest (F98770PD910FA) in Central Objects and in the target package on the Deployment Server.
This UBE also configures the spec.ini in the target package on the Deployment Server.

The application writes history records into F984052. To view the history, run the Table Conversion / Merge Log (P984052) on menu GH9611 by filtering on conversion type 95. This screen shows a sample conversion log:

10. After the process completes successfully, you must deploy the target server package to make it available on the Enterprise Server(s).

Caution:
OEE Local Database Consideration. When copying a package using a local Oracle database, there are additional .DBF files in the target package spec directory. For example, if copying PY910FULL to PD910FULL, these two DBF files would exist:
PD910\package\PD910FULL\spec\PD910FUL.DBF

PD910\package\PD910FULL\spec\PY910FULL.DBF

Before deploying the package, you must manually delete the source package DBF file (in this example, PY910FULL.DBF). This must be done manually because it is not possible for the R9894005 UBE to delete this file as the database keeps a lock on it until the UBE ends.

11. To access the processing options of the Copy Environment Application (P989400), from menu GH9611 right click on the application and select Prompt for Values.

12. In order to activate the Advanced Copy button, enter a value of Y in this field:
Advanced Copy Options Y/N

Click OK to return to the Environment Copy application and note that a new section with advanced options is available:

Directory copies

For example, if you choose to do all the database copies using database / system tools, you would set the copy options like this:

14 Troubleshooting

This chapter discusses:

- Section 14.1, "Using the PORTTEST Checklist"

- Section 14.2, "Resolving Data Errors"

- Section 14.3, "Planner Update Special Instructions"

- Section 14.4, "Resolving Errors Due to Lack of *ALLOBJ and *JOBCTL Authority"

14.1 Using the PORTTEST Checklist

If the PORTTEST program fails to run, use this checklist to diagnose the problem before calling Global Customer Support. Please have the answers to these questions as well as copies of error messages, your Enterprise Server , and any error logs, such as JDE.log or JDE_xx.log.

PORTTEST may fail if replication, security server, or transaction processing have been installed incorrectly. If problems occur after the installation of one or more of these services, check the setup of those services for incorrect parameters.

Additionally, if PORTTEST reports warnings that indicate data dictionary or company constants are invalid, it may be because the F0010 table is empty. As is true with the full JD Edwards EnterpriseOne installation, this is a normal condition in Pristine and Production environments.

General Issues

Yes\No

Is the user logged on with administrator privileges?

Is the JDENET Service starting with a network domain user?

Is the JDENET Service account included in the local administrator group?

Are all the environment variables set?

Is the C compiler installed with Unicode module?

Can you query the database on the Enterprise Server?

Is a PostScript or PCL printer connected to this machine?

Are the printer drivers for this printer installed?

Is this printer configured as the default printer?

jde.ini Issues

Yes\No

Is your jde.ini located in the correct directory?

Does your jde.ini have the correct permissions?

Are the following jde.ini parameters set properly?

[Network Queue Settings]
Default Printer OUTQ=your printer

[UBE]
If you use PostScript, is the correct filter set up?

[DB System Settings]
Verify all parameters, especially the following:

Default Env= your default environment

Default Pathcode = your default path code

Server = database server name

[JDENET]
serviceNameListen = port number

serviceNameConnect = port number

[INSTALL]
E910=your path

Communications Issues

Yes\No

Do the workstations and server agree on the IP address of the server?

Other Issues

Yes\No

Were your server map tables (F98611 and F986101) edited properly?

Run the Verify OCM application and verify:

Do only host databases exist?

No entries for batch applications exist.

Are OneWorld tables accessible to the host?

Can you query the F0902 table?

Does PORTTEST run without error for each valid path code?

Does the user name match that of a valid Release 9.1 account? Remember that the user name is case sensitive.

Is the password valid for the given Release 9.1 account?

Does the environment name match a valid Release 9.1 environment? Remember that the environment name is case sensitive.

Does JDENET start and stop properly?

If you answered no to any of these questions, your batch application might not run. If you answered yes to all the questions, submit a batch application now.

If your batch application does not run correctly, turn on error logging and resubmit the batch. This log helps Global Customer Support diagnose the exact problem.

14.2 Resolving Data Errors

If you are receiving data warnings against the F0010 table in the Pristine or Production environments, the table might be empty. This is how it is delivered. You can ignore these warnings, load demo data, or load your own data.

14.3 Planner Update Special Instructions

The Electronic Software Update (ESU) for the Planner Update Special Instructions was created with special features that updates the Planner pathcode on the Deployment Server. It includes all fixes for Release 9.1 installation and upgrade process.

You must run the specialInstrs.bat file to copy certain table records from the ESU database to the Planner databases on the Deployment server.

1. On the Deployment server, browse to this directory:
\JDEdwards\910\Planner\Package\JMxxxxxxx\Scripts

2. Run the batch file specialInstrs.bat. Note any success or failure messages that appear in the command window.
Review the SpecialInstrs.log file that is created in the same directory for details.

14.4 Resolving Errors Due to Lack of *ALLOBJ and *JOBCTL Authority

By default the Installation program grants *JOBCTL authority to the ONEWORLD user profile. You may have a temporary requirement to grant *ALLOBJ authority to ONEWORLD. This could be required if ONEWORLD needs to start journaling on a table but does not have OBJMGT rights to that table. For example, when submitting a UBE to the server for the first time, ONEWORLD needs to start journaling on F986111. Symptoms of this problem are errors indicating a transaction was cancelled because a commit cycle could not be start.

Of the multiple ways to grant the *ALLOBJ authority to ONEWORLD, the simplest is to give ONEWORLD rights to all tables using the SETOWAUT tool. Alternatively, you could run the GRTOBJAUT command to give ONEWORLD OBJMGT authority of to all tables in your business data, system, and server map libraries. Note that either method causes locks to be put on tables, which could interfere with other users on your system. In order to avoid that potential interference caused by locks, it may be preferable to temporarily grant *ALLOBJ authority to ONEWORLD, which you can revoke after a short while.

To grant *ALLOBJ authority, from a green screen enter the following command:

CHGUSRPRF USRPRF(ONEWORLD) SPCAUT(*ALLOBJ *JOBCTL) JOBD(*LIBL\ONEWORLD)

15 Creating a Remote Installation Plan

This section discusses:

- Section 15.1, "Understanding Remote Installation Plans"

- Section 15.2, "Starting Installation Planner"

- Section 15.3, "Entering Information in Installation Planner"

- Section 15.4, "Entering Plan Location Information"

- Section 15.5, "Entering Deployment Server Information"

- Section 15.6, "Entering Enterprise Server Information"

- Section 15.7, "Enter Data Source Information for Server Map"

- Section 15.8, "Entering HTML Web Server Information"

- Section 15.9, "Entering Data Server Information"

- Section 15.10, "Replicating Information to Remote Locations"

- Section 15.11, "Entering Shared Data Source Information"

- Section 15.12, "Setting Up Environments"

- Section 15.13, "Setting Up Data Sources for Environment"

- Section 15.14, "Remote Location Packages"

- Section 15.15, "Finalizing the Installation Plan"

- Section 15.16, "Concluding the Planner Validation Report"

15.1 Understanding Remote Installation Plans

Installation Planner is a Release 9.1 application that runs on the Deployment Server. It is a system administration tool that guides through the process of configuring the machines on which your company will run Release 9.1.

To set up Release 9.1 for a remote location, create a plan that includes remote locations. Complete the tasks in this section after you create and complete a basic installation plan, and are ready to add the remote locations to the configuration. This section includes information for installing an alternate language.

Before you begin, decide what your replication strategy is for Release 9.1. You can use Installation Workbench to copy the system, data dictionary, control, constant and master tables to your remote location. Ongoing replication of the data in these sources must be implemented using third-party software; as of release 8.9, JD Edwards EnterpriseOne no longer has a built-in replication engine. To use replication for Release 9.1, review the processing options for the Installation Planner to make sure that they are set correctly for replication.

The information that you provide on the Installation Planner forms, such as database type and Enterprise Server type, determines the information that the system displays on the remaining forms.

See Also

Reviewing Installation Planner Processing Options for more information about how the processing options for Installation Planner also affect the choices that you are given while setting up your plan

Note:
Installation Planner Considerations. Depending on which tables you want to replicate, you are prompted for different data source information. For example, if you choose to replicate the control tables, you are asked to define the control tables data source.

Note:
Data Source Considerations. JD Edwards EnterpriseOne provides configured data sources. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. Only data sources that are referenced in the replication forms appear when you create a remote plan.

15.2 Starting Installation Planner

To start Installation Planner:

1. Log on to Release 9.1 as user JDE with the database password for user JDE.

2. Access the planner environment (JDEPLAN).

3. From the System Installation Tools menu (GH961), click Custom Installation Plan.

4. On Work with Installation Plans, click Add.
The Installation Planner form appears.

15.3 Entering Information in Installation Planner

To enter information in Installation Planner:

1. On Installation Planner, complete these fields:

Field

Description

Name

Enter the name of your remote plan.

Description

Enter the description of your remote plan.

Status

Select 10 as the status of your remote plan.

Install Type

Select Install.

To Release

Verify that the release number is E910.

2. On Installation Planner, click OK.

3. On the Location dialog, click OK.

15.4 Entering Plan Location Information

To enter plan location information:

1. On Location Revisions, complete these fields:

Field

Description

Location

Enter the location to which this plan applies. The location could be a city, company headquarters, or a division of a company.

Description

Enter a description of the location name.

Location Code

For a remote location, enter a 3-character alphanumeric identification code. This 3-character code is used as a prefix for the environments of the remote location, and a suffix is attached for replicated data sources. For example, you might use DAL if the location were Dallas, Texas. In that case, the prototype environment would be named DALPY910, and the business data data source would be named Business Data - CRPDAL.

Parent Location

Enter the parent location to which this remote location is attached.

2. Click OK.

15.5 Entering Deployment Server Information

Once a plan location is specified, complete the information for the Deployment Server. You are given the option to enter a new Deployment Server or choose an existing one. For most situations, you will have a tiered Deployment Server for the remote location.

To enter Deployment Server information:

1. At the Installation Planner prompt asking if you want to enter new Deployment Server information, click OK to add a Deployment Server.

2. On Deployment Server Revisions, complete these fields:

Field

Description

Machine Usage

Displays the default value of 15 to indicate that this is a Deployment Server.

Machine Name

Enter the name of your Deployment Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the machine name. This name includes the location with which this Deployment Server is associated, and whether or not it is the primary server.

Release

Enter the Release 9.1 release number that you are installing, or use the visual assist button to choose one from the list. For example, E910 is the current release.

Host Type

Displays the default value of 50 to indicate that the server type is an Intel NT.

Location

Displays the default location chosen for this plan.

Primary User

Enter the user to whom email is sent when a package is deployed. The default for Primary User is JDE.

3. On the Deployment tab, complete these fields:

Field

Description

Primary Deployment Server

Enter the hierarchy of the servers. Type
0

(zero) if a primary Deployment Server for the location exists and this is a secondary server. Type 1 if this is the primary Deployment Server for the location.

Server Share Path

Enter the server share path where you installedRelease 9.1 on your Deployment Server. Make sure that this path is specific to your version of the release. For example, for Release 9.1, the path ends with\E910.

4. Click OK.

Tip:
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form.

5. Click OK.

Tip:
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form.

6. To continue with Remote Installation Planner setup, click No.

15.6 Entering Enterprise Server Information

Note:
During the definition of the Enterprise Server, a port number must be defined. While Enterprise Servers running the same release can use the same port number, an Enterprise Server running two different versions of software must use two different port numbers.

On Enterprise Server, click the OK button to define a new Enterprise Server, or click the Select button to choose an existing Enterprise Server.

1. On Enterprise Server Revisions, verify or complete these fields:

Field

Description

Machine Name

The name of the primary Enterprise Server. The name is case sensitive and should not contain any special characters.
Because the machine name is used to create the Server Map datasource name, and because the Platform Pack Installer does not restrict you from entering a machine name that results in a datasource name greater than 30 characters; if the machine name for the Enterprise Server is longer than 13 characters, the resulting datasource name will be longer than the allowed 30 characters. For example, if your machine name is 15 characters (A23456789012345), the base datasource name input into the Planner would be: A23456789012345 - 910 Server Map.

Note: The field in table F98611 is a hard restriction; the field only allows 30 characters. The actual field size cannot be modified or changed.

When the Planner runs it truncates the value to 30 characters because that is the restriction in the F98611 table. The Platform Pack does not truncate the value when it builds the jde.ini for the Enterprise Server. Therefore, any value greater than 30 characters will result in a mismatch between the jde.ini and the F98611 table. That is, using the previous example, the jde.ini would have the full length value A23456789012345 - 910 Server Map (which is 32 characters) while the F98611 populated by the Planner would have a value of A23456789012345 - 910 Server M.

To remedy, you could do any one of the following:

- Manually modify values in table F98611 to match the truncated value in the jde.ini file.

- Ensure that the value is not truncated by limiting the datasource name to 30 characters (this would mean limiting the machine name for the Enterprise Server to 13 characters).

- Manually truncate the value in the F98611 table (for example, A23456789012345 - 910 Svr Map.

In any case, you must ensure that the values for Server Map datasource names in the F98611 table exactly match those in the jde.ini file on the Enterprise Server.

Description

Enter a description for the machine.

Release

Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E910.

Host Type

Click the visual assist button and choose the type of Enterprise Server you are adding to the plan. In this case, IBM i.

Location

The location chosen for this plan appears by default.

Primary User

The user to whom an email is sent when a package is deployed. The default value for Primary User is JDE.

Note:
The case of machine name must also match the network ID for that machine.

2. Continuing on Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields:

Field

Description

Port Number

The port number value (6016) for this Enterprise Server appears by default from the jde.ini.

Logical Machine Name

The Installation Planner detects and provides a default value based on the current machine name on which the program is running. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Database Type

Enter the value for your database:
I - DB2 400

Server Map Data Source

Whenever you enter a host type, the Installation Planner populates this field with a default value:
machinename - 910 Server Map

where machinename is the name of your machine.

Installation Path

Verify that the default value is the installation directory path to which you want to install Release 9.1 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 9.1 the default path is:
\JDEdwards\PPack\E910SYS

This is the system library.

Caution: You must change the value that defaults into the Installation Path field as shown in the screen capture above.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary.

Note:
If you change the port number to a value other than 6016, you must also change this setting in both the Enterprise Server and workstation JDE.INIjde.ini.

3. Click OK.

15.7 Enter Data Source Information for Server Map

To enter information for the Server Map data source:

1. On Data Source, click OK to continue entering unique data source information.

2. On Data Source Revisions, verify the accuracy of the Server Map data source.

3. Click OK.

4. On the Would you like to add another Enterprise Server? dialog, click the Yes or No button.

15.8 Entering HTML Web Server Information

Note:
For Release 9.1, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web 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.

Caution:
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface.

To enter HTML Web Server information:

1. Click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.
If you choose Select, you are presented with the Machine Search table, from which you can make your selection.

2. On HTML Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 30 indicates that this is a HTML Web Server.

Machine Name

Enter the name of your HTML Web Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the HTML Web Server machine.

Release

Enter E910 to indicate the release number that you are installing.

Host Type

The default value of 50 specifies the server type as Intel NT. Select the correct server type.

Location

The location chosen for this plan appears in this field by default.

Primary User

The user to whom an email is sent when a package is deployed. The default for Primary User is listed in the jde.ini.

3. On the HTML tab, complete these fields:

Field

Description

Primary HTML Server

When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1").

Protocol

This is the protocol used by the HTML Web Server. Valid values are http or https.

Server URL

This is the Domain Name System (DNS) host name of the HTML Web Server.
The syntax is:

server_name:port\jde\owhtml

For example:

DEVNTA:81\jde\owhtml

Http Port

This is the port number the HTML Web Server is listening to.
For HTTP, the typical port number is 80.

For HTTPS, the typical port number is 443.

However, you can choose to implement a HTML Web Server using a different port number.

Default Login

Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are:

- Standard
The URL generated will point to a servlet on the Primary HTML Web Server.

- Redirector
The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system.

- Explicit Servlet Name
The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server.

Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need.

Installation Path

Enter the installation directory path to which you are installing Release 9.1 on your HTML Web Server.Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running.
For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Reference Guide (WebLogic for Windows, WebLogic for UNIX, WebSphere for Windows, WebSphere for UNIX, WebSphere for IBM i. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this HTML Web Server is attached. A Deployment Server name appears in this field by default, but you can change it if necessary.

4. Click OK.

5. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

15.9 Entering Data Server Information

1. On Data Server, choose one of these options:

- OK
If your database resides on a separate server, choose click OK to continue entering unique Data Server information.

- Select
Click this option to select an existing Data Server.

- Skip
Click this option if you do not want to define a Data Server.

- On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data.

For purposes of this procedure to setup a Remote Installation Plan, the Skip option is assumed.

2. Click OK.

15.10 Replicating Information to Remote Locations

The options on this form determine whether the software will configure data sources and mappings for the remote location. Ongoing replication must be implemented using third-party software.

To replicate information to remote locations:

1. On Control/System Replication, select the Replication Setup tab and select the following options to replicate information to remote locations:

Field

Description

Replicate System Tables

Select this checkbox to replicate all tables within the System data source. A new data source will be created for the remote location and the mappings for the remote environment will be activated to point to the new System data source.

Replicate Data Dictionary Tables

Select this checkbox to replicate all tables within the Data Dictionary data source. A new data source will be created for the remote location and the mappings for the remote environment will be activated to point to the new Data Dictionary data source.

Caution:
Replication must be implemented using a third-party tool.

2. Select the Data Load tab.

3. On the Data Load tab, choose from the following options to copy selected tables to the remote locations:

Field

Description

Load System Tables

Select this checkbox to initially load the replicated System Tables. The following version of R98403 will be launched to accomplish the task of copying system tables from the base location to remote locations.

Load Data Dictionary Tables

Select this checkbox to initially load the replicated Data Dictionary Tables. The following version of R98403 will be launched to accomplish the task of copying data dictionary tables from the base location to remote locations..

Note:
To edit or change the versions of the R98403 program that copy the control tables, constant tables, and master tables, click the Edit or Search buttons next to their respective versions.

Note:
If you have defined multiple locations, the system will prompt you to complete sets of the Replication Setup and Data Load screens for each location.

4. Click OK.

15.11 Entering Shared Data Source Information

This section describes entering the shared data source information for the Data Dictionary and System data sources.

1. When you are prompted to enter the data source information for the shared data sources, to use the Release 9.1 data sources, click OK to specify or verify the data source information.

2. On Data Source Revisions, enter the data source name for the Data Dictionary data source that will be used by the remote location. For example, Data Dictionary - 910ATL.

3. Complete the other fields as applicable for your database and platform.

4. Click the OK button.

5. On Data Source Revisions, enter the data source name for the System data source that will be used by the remote location. For example, Data Dictionary - 910ATL.

6. Complete the other fields as applicable for your database and platform.

7. Click the OK button.

15.12 Setting Up Environments

To set up environments:

1. On Environment Selection, with the Default Environments checkbox selected, click the OK button.

2. On Select Environments, double click on an Environment to select it.

3. Click the Close button.

4. On Control/System Replication, select the Replication Setup tab and select the following options to replicate information to remote locations:

Field

Description

Replicate Control Tables

Select this checkbox to replicate all tables within the Control Tables data source. A new data source will be created for the remote location and the mappings for the remote environment will be activated to point to the new Control Tables data source.

Replicate Constant Tables - Object Librarian Object Use = 280

Select this checkbox to replicate Constant Tables. A new data source will be created for the remote location and the mappings for the remote environment will be activated to point to the new Constant Tables data source.

Replicate Master Tables - Object Librarian Object Use = 210 and 211

Select this checkbox to replicate Master Tables. A new data source will be created for the remote location and the mappings for the remote environment will be activated to point to the new Master Tables data source.

Caution:
Replication must be implemented using a third-party tool.

5. Select the Data Load tab.

6. On the Data Load tab, choose from the following options to copy selected tables to the remote locations:

Field

Description

Load Control Tables

Select this checkbox to initially load the replicated Control Tables. The following version of R98403 will be launched to accomplish the task of copying Control tables from the base location to remote locations.

Load Constant Tables

Select this checkbox to initially load the replicated Constant Tables. The following version of R98403 will be launched to accomplish the task of copying Constant tables from the base location to remote locations.

Load Master Tables

Select this checkbox to initially load the replicated Master Tables. The following version of R98403 will be launched to accomplish the task of copying Master tables from the base location to remote locations.

Note:
To edit or change the versions of the R98403 program that copy the control tables, constant tables, and master tables, click the Edit or Search buttons next to their respective versions.

Note:
If you have defined multiple locations, the system will prompt you to complete sets of the Replication Setup and Data Load screens for each location.

7. Click OK.

15.13 Setting Up Data Sources for Environment

After specifying which tables to replicate, you can set up environment data sources.

1. On Data Source, click OK.

2. On Data Source Revisions, enter the data source name for the Business Data data source that will be used by the remote location. For example, Business Data - PS910ATL.

3. Complete the other fields as applicable for your database and platform.

4. Click the OK button.

5. On Data Source Revisions, enter the data source name for the Control Tables data source that will be used by the remote location. For example, Control Tables - PS910ATL.

6. Complete the other fields as applicable for your database and platform.

7. Click the OK button.

8. On Select Environments, click the Close button to exit the form.

15.14 Remote Location Packages

After you complete the data source setup for the environments, you can choose whether to push packages to a remote location.

1. On Remote Location Packages, click the OK button.

2. On Remote Location Packages, click the Select button to choose the highlighted package.

3. On Remote Location Packages, verify that "Selected" is displayed in the "Selected" column.

4. Click the Close button.

5. On Location, click the No button to finalize the plan.

6. On the Information Prompt that indicates Installation Planner has concluded, click OK to exit the message box and initiate the Planner Validation Report.

- If the processing option default was selected, Planner Validation Report automatically prompts you to run this report.

- If the processing option default was not selected, click Validate on the tree view of your plan to initiate the Planner Validation Report.

15.15 Finalizing the Installation Plan

Installation Planner finalizes your installation plan automatically. The Information Prompt message appears to let you know that the installation plan is finalized.

When the plan is finalized:

- The status is set to 20. This value means that several adjustments to OCM mappings and tables were made according to your plan.

- The following tables are now updated:
Release Master table (F00945).

Path Code Master table (F00942).

Create OCM (F986101).

Package Plan table (F98404).

Machine Detail table (F9651).

Table Conversion Scheduler (F98405).

Language table (F984031) - if you are installing an alternate language.

15.16 Concluding the Planner Validation Report

To conclude the planner validation report:

1. On Report Output Destination, select On Screen or To Printer.

2. Click OK.

3. Review the report to confirm that all records were validated.
For more information about Section 22.1, "Installation Planner Validation Report (R9840B)", refer to Chapter 22, "Working with Reports".

4. On Work With Installation Plans, click Expand to review the plan you created.

See Also

- A separate chapter in this guide entitled: Chapter 15, "Creating a Remote Installation Plan"

- A separate chapter in this guide entitled: Chapter 16, "Adding a Server to an Existing Configuration"

- A separate chapter in this guide entitled: Chapter 17, "Creating a Language-Only Installation Plan"

16 Adding a Server to an Existing Configuration

This section contains the procedures for adding additional servers to your configuration. Use these procedures only if you have already defined and run your initial installation plan and set up your environments.

This section discusses:

- Section 16.1, "Assumptions about Adding a Server to an Existing Installation Plan"

- Section 16.2, "Starting Installation Planner"

- Section 16.3, "Entering a Plan Description"

- Section 16.4, "Entering a Plan Location"

- Section 16.5, "Selecting Additional Server Types"

- Section 16.6, "Entering Deployment Server Information"

- Section 16.7, "Specifying an Enterprise Server"

- Section 16.8, "Entering HTML Web Server Information"

- Section 16.9, "Entering Data Server Information"

- Section 16.10, "Entering Shared Data Source Information"

- Section 16.11, "Setting Up Environments"

- Section 16.12, "Setting Up Environment Data Sources"

- Section 16.13, "Finalizing the Installation Plan"

- Section 16.14, "Concluding the Validation Planner Report"

- Section 16.15, "Configuring Additional Servers"

16.1 Assumptions about Adding a Server to an Existing Installation Plan

This table outlines assumptions for adding a server to an existing Installation Plan phase as a whole.

Personnel

Installer

Logon Status

On the Deployment Server, logged on as user JDE with the database password for user JDE, in the planner environment.

Prerequisites

Verify that the Deployment Server is installed and theRelease 9.1 directory is shared.
In order to run EnterpriseOne on an additional server, you must deploy JD Edwards EnterpriseOne to the server using either:

- Server Manager

- Platform Pack installer

Concurrent Tasks

None.

16.2 Starting Installation Planner

Caution:
In order to run EnterpriseOne on an additional server, you must deploy JD Edwards EnterpriseOne to the server using either:

- Server Manager

- Platform Pack installer

Begin your installation plan by logging on to Release 9.1 and starting Installation Planner.

To start the Installation Planner:

1. Log on to Release 9.1 as user JDE with the database password for user JDE.

2. Access the planner environment (JDEPLAN).

3. From the System Installation Tools menu (GH961), double-click Add-on Servers Plan.

4. On Work with Installation Plans, click Add.
Release 9.1 displays the following warning:

5. Click OK.
The Installation Planner form appears.

16.3 Entering a Plan Description

After starting Installation Planner, enter basic plan information, such as plan name and description.

To enter a plan description:

1. On Installation Planner, complete the following fields:

- Name
Enter the name of your installation plan.

- Description
Enter the description of your installation plan.

- Status
Select 10 as the status of your installation plan.

- To
Verify that the release number is E910.

2. Click OK.
The Location Search form appears.

16.4 Entering a Plan Location

Once basic plan installation information is entered, you must choose an existing plan location. For most instances, choose the location defined during your base installation.

To enter a plan location:

1. On Location Search, choose a location and click Select.

2. On Location Revisions, click OK.

16.5 Selecting Additional Server Types

Once a plan location is specified, specify the types of servers you want to add to your installation plan.

To select additional server types:

1. On Server Add, check the types of servers that you want to add to your configuration.

2. Click OK.
A Server Revisions form appears in the order listed on the Server Add form for each type of server that you chose.

3. Continue with the relevant sections that follow.

16.6 Entering Deployment Server Information

When choosing to add an additional Deployment Server to your plan, the Deployment Server Revisions form appears.

To enter Deployment Server information:

1. On Deployment Server Revisions, complete the following fields:

Field

Description

Machine Name

Enter the name of your additional Deployment Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the machine.

Release

Enter E910.

Location

Displays the system-provided default value chosen for this plan.

Primary User

This identifies the user to whom email is sent when a package is deployed. The default for Primary User is The default value for Primary User.

2. On the Deployment tab, verify or complete the following fields:

Field

Description

Primary Deployment Server

This field indicates the hierarchy of the servers. The default value for a secondary Deployment Server is 0.

Server Share Path

Enter the server share path where you installedRelease 9.1 on your Deployment Server. Verify that this path matches your version of the release; for example, for Release 9.1, the server share path is\E910.

3. Click OK.

Tip:
If you enter invalid information into a tab field, a stop sign icon appears next to the tab name, such as Deployment Server. For more information about the error, click on the stop sign icon in the bottom right-hand corner of the form.

4. You are prompted to add another Deployment Server.

- To add another Deployment Server, click Yes.
Repeat Section 16.6, "Entering Deployment Server Information".

- To continue with the additional server plan, click No.
Continue with the relevant sections that follow.

16.7 Specifying an Enterprise Server

This section discusses:

- Section 16.7.1, "Entering Enterprise Server Information"

- Section 16.7.2, "Entering Enterprise Server Data Source Information"

16.7.1 Entering Enterprise Server Information

To enter the base information for the Enterprise Server that you use in this plan:

1. On Enterprise Server Revisions, complete or verify the following fields:

Field

Description

Machine Usage

Displays the default value of 20 to indicate that this is an Enterprise Server.

Machine Name

The name of the primary Enterprise Server. The name is case sensitive and should not contain any special characters.
Because the machine name is used to create the Server Map datasource name, and because the Platform Pack Installer does not restrict you from entering a machine name that results in a datasource name greater than 30 characters; if the machine name for the Enterprise Server is longer than 13 characters, the resulting datasource name will be longer than the allowed 30 characters. For example, if your machine name is 15 characters (A23456789012345), the base datasource name input into the Planner would be: A23456789012345 - 910 Server Map.

Note: The field in table F98611 is a hard restriction; the field only allows 30 characters. The actual field size cannot be modified or changed.

When the Planner runs it truncates the value to 30 characters because that is the restriction in the F98611 table. The Platform Pack does not truncate the value when it builds the jde.ini for the Enterprise Server. Therefore, any value greater than 30 characters will result in a mismatch between the jde.ini and the F98611 table. That is, using the previous example, the jde.ini would have the full length value A23456789012345 - 910 Server Map (which is 32 characters) while the F98611 populated by the Planner would have a value of A23456789012345 - 910 Server M.

To remedy, you could do any one of the following:

- Manually modify values in table F98611 to match the truncated value in the jde.ini file.

- Ensure that the value is not truncated by limiting the datasource name to 30 characters (this would mean limiting the machine name for the Enterprise Server to 13 characters).

- Manually truncate the value in the F98611 table (for example, A23456789012345 - 910 Svr Map.

In any case, you must ensure that the values for Server Map datasource names in the F98611 table exactly match those in the jde.ini file on the Enterprise Server.

Description

Enter a description of the machine.

Release

Enter the release number to which this plan applies, or use the visual assist button to choose one from the list, such as E910.

Host Type

Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan, such as IBM i.

Location

Enter the default location chosen for this plan.

Primary User

Enter the user to whom email is sent when a package is deployed. The default for Primary User is JDE.

2. On the Enterprise tab, complete these fields:

Field

Description

Port Number

Displays the default value for this field, which is supplied the jde.ini. Change the port number for this Enterprise Server to a unique value, for example, 6016.

Logical Machine Name

Displays the system-supplied default value when you enter the host type. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Database Type

Enter the type of database that you want to use for data sources on the Enterprise Server. Value is:
I is for IBM i Access

Server Map Data Source

Displays the system-supplied default value when you enter the host type.

Installation Path

Verify that the default value is the installation directory path to which you want to install Release 9.1 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 9.1 the default path is:
\JDEdwards\PPack\E910SYS

This is the system library.

Deployment Server Name

Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. The system provides a default value for this field, but you can change it.

3. Click OK.
A message box appears prompting you to enter custom data sources or take the default data sources. Proceed to Section 16.10, "Entering Shared Data Source Information".

16.7.2 Entering Enterprise Server Data Source Information

After specifying Enterprise Server information, enter the data source information for the Enterprise Server you will use in this plan.

This section discusses:

- Section 16.7.2.1, "Specifying Custom or Default Data Source Information"

- Section 16.7.2.2, "Verifying Custom Server Map Data Source Information"

- Section 16.7.2.3, "Adding another Enterprise Server"

16.7.2.1 Specifying Custom or Default Data Source Information

You are prompted to enter custom data sources or take the default data sources for the Enterprise Server you just added. Choose one of the following options:

- To enter custom data sources, click OK.
Skip to Section 16.7.2.2, "Verifying Custom Server Map Data Source Information".

- To accept default data sources, click Take Defaults.
This option limits your customization choices.

16.7.2.2 Verifying Custom Server Map Data Source Information

To verify custom Server Map data source information:

1. On Data Source Revisions, verify your Server Map data source information.

Tip:
Default data sources are configured as completely as possible. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration.

2. Click OK.

16.7.2.3 Adding another Enterprise Server

On the prompt to add another Enterprise Server, choose one of the following options:

- To add another Enterprise Server, click Yes.
Repeat processes, starting with Section 16.7.1, "Entering Enterprise Server Information".

- To continue with Installation Planner setup, click No.
The Machine\Server Types form appears.

16.8 Entering HTML Web Server Information

To enter HTML Web Server information:

1. On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server.

2. On HTML Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 30 indicates that this is a HTML Web Server.

Machine Name

Enter the name of your HTML Web Server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the HTML Web Server machine.

Release

Enter E910 to indicate the release number that you are installing.

Host Type

The default value of 50 specifies the server type as Intel NT. Select the correct server type.

Location

The location chosen for this plan appears in this field by default.

Primary User

The user to whom an email is sent when a package is deployed. The default for Primary User is listed in the jde.ini.

3. On the HTML tab, complete these fields:

Field

Description

Primary HTML Server

When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1").

Protocol

This is the protocol used by the HTML Web Server. Valid values are http or https.

Server URL

This is the Domain Name System (DNS) host name of the HTML Web Server.
For example: www.oracle.com

HTTP Port

This is the port number the HTML Web Server is listening to.
For HTTP, the typical port number is 80.

For HTTPS, the typical port number is 443.

Note: You can choose to implement a HTML Web Server using a different port number.

JDENET Listen Port

This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne.
For JD Edwards EnterpriseOne Release 9.1, the value is 6016.

Default Login

Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are:

- Standard
The URL generated will point to a servlet on the Primary HTML Web Server.

- Redirector
The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system.

- Explicit Servlet Name
The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server.

Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need.

Installation Path

Enter the installation directory path to which you are installing Release 9.1 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running.
For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Reference Guide (WebLogic for Windows, WebLogic for UNIX, WebSphere for Windows, WebSphere for UNIX, WebSphere for IBM i. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator.

4. Click OK.

5. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

16.9 Entering Data Server Information

1. On Data Server, choose one of these options:

- OK
If your database resides on a separate server, choose click OK to continue entering unique Data Server information.

- Select
Click this option to select an existing Data Server.

- Skip
Click this option if you do not want to define a Data Server. Continue with the Planner using the environment selection in Step 6 of this task.

2. On Data Server Revisions, complete these fields:

Field

Description

Machine Usage

The default value of 25 indicates that this is a Database Server.

Machine Name

Enter the name of the Database Server where your central objects reside. If you are using the IBM i to store your central objects, enter the name of this server. The name is case sensitive, should not exceed 15 characters, and should not contain any special characters.

Description

Enter a description of the Database Server machine.

Release

Enter the release number you are installing, for example, E910.

Host Type

Select the type of Database Server that you are adding to the plan. Values are:

- 10 — IBM i

- 25 — Sun Solaris

- 30 — RS\6000

- 35 — Linux

- 50 — Microsoft Windows (Intel)

- 80— Client - Microsoft Windows

- 90 — Client - Microsoft Windows

Location

The Installation Planner populates this field by default, based on previous selections.

Primary User

The user to whom an email is sent once a package is deployed. The default for Primary User is JDE.

3. On the Data tab, complete the following field:

Field

Description

Data Source Type

Choose the type of data source. For example:

- I - IBM i

4. Click OK.

5. To add another Data Server, click Yes and repeat steps 1 through 4 to define another Data Server.

6. On Data Source, click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources.

7. On Location, select Yes to add another location, or click No to continue with Installation Planner.

16.10 Entering Shared Data Source Information

This section discusses:

- Section 16.10.1, "Specifying (Custom or Default) Shared Data Source Setup Information"

- Section 16.10.2, "Verifying the Data Source for Data Dictionary"

- Section 16.10.3, "Verifying the Object Librarian Data Source"

- Section 16.10.4, "Verifying the OWJRNL Data Source"

- Section 16.10.5, "Verifying the System Data Source"

16.10.1 Specifying (Custom or Default) Shared Data Source Setup Information

When you are prompted to enter the data source information for the shared data sources, to use the Release 9.1 data sources, click Take Defaults, or click OK to specifically enter the data source information.

See Also

For more information about System data source fields or fields for other data sources mentioned in this process, refer to Chapter 19, "Understanding Data Source Charts".

16.10.2 Verifying the Data Source for Data Dictionary

To verify the data source for Data Dictionary:

1. On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source.
The library name in the Library Name field is the Release 9.1 data dictionary library (DD910).

2. Click OK.

16.10.3 Verifying the Object Librarian Data Source

To verify the Object Librarian data source:

1. On Data Source Revisions, verify the accuracy of the settings for the Object Librarian data source.

2. Click OK.

16.10.4 Verifying the OWJRNL Data Source

To verify the OWJRNL data source:

1. On Data Source Revisions, verify the accuracy of the settings for the OWJRNL data source.

2. Click OK.

16.10.5 Verifying the System Data Source

To verify the System data source:

1. On Data Source Revisions, verify the accuracy of the settings for the System data source.

2. Click OK.
The Environment Selection screen appears.

See Also

For more information about System data source fields or fields for other data sources mentioned in this process, refer to Chapter 19, "Understanding Data Source Charts".

16.11 Setting Up Environments

By default, Release 9.1 configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 9.1 displays one or more of the following parameters, which you can customize in these tasks:

- Environments

- Data load options

- Languages

You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Release 9.1 displays a customization form for each parameter that you turn off.

1. On Environment Selection, clear the options for those parameters that you want to customize.

Note:
The parameters that are available vary depending on the options that you selected at the beginning of the planning process.

2. Click OK.

Note:
If you selected the default option for all parameters, skip to Section 16.12, "Setting Up Environment Data Sources".

Use the following tasks to customize each of the parameters listed above. Release 9.1 displays customization forms only for those parameters for which were cleared of the default options. Skip the tasks for those parameters that were selected.

3. Continue with the following relevant tasks:

- Section 16.11.1, "Selecting an Environment"

- Section 16.11.2, "Specifying Environment Data Load Parameters"

- Section 16.11.3, "Selecting Languages"

16.11.1 Selecting an Environment

The Select Environment form appears. Environments prefixed with J are required for the HTML Web Server.

To select an environment:

On Select Environments, double-click the environment that you want to define.

To set up multiple environments, choose and define them one at a time. This screen appears after the following tasks are completed.

16.11.2 Specifying Environment Data Load Parameters

If you cleared Default Data Load on the Environment Selection form, the Data Load Parameters form appears.

To specify environment data load parameters:

Note:
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 9.1 because data is automatically loaded by the Platform Pack Installer.
For additional details, refer to Section 6.1.2, "Loading Data (Demo Data and Production Data)".

16.11.3 Selecting Languages

To select languages:

1. On Language Selection, to set up a language for the selected environment, choose the appropriate language.

2. From the Row menu, click Select.

3. Repeat the above steps until all your languages have been selected.

4. Click OK.

16.12 Setting Up Environment Data Sources

Once the Environments have been set up, it is necessary to set up the data sources for those environments. If you created a custom environment, data source information is generated from the data source template provided with JD Edwards EnterpriseOne.

See Also

To modify this template, see the JD Edwards EnterpriseOne Configurable Network Computing Implementation Guide.

16.12.1 Selecting an Environment Data Source Setup Option

When you are prompted to set up data sources for the environment you just configured, click OK to manually enter the data sources, continue with the following task, or click Take Defaults to accept the Release 9.1 default data sources.

16.12.2 Setting Up the Data Source for Business Data

To set up the data source for business data:

1. On Data Source Revisions, verify the data source for your Business Data.

2. Click OK.

Caution:
The Central Objects data source must be Unicode. Select Advanced from the Form menu to verifyUnicode is checked.

3. Click OK.

16.12.3 Setting Up the Data Source for Central Objects

You should change the data source if Central Objects are not on an IBM i machine.

To set up the data source for central objects:

1. On Data Source Revisions, verify the information for your Central Objects data source.
If you are putting Central Objects on the IBM i, verify that the data library name is CO pathcode. For example, COPY910 or CODV910.

2. Click OK.

3. On Advanced Set-Up, because the central objects data source must be Unicode, verify the Unicode setting is checked.
For IBM i, ensure the AS/400 BLOB Support setting is checked.

16.12.4 Setting Up the Data Source for Control Tables

To set up the data source for control tables:

1. On Data Source Revisions, verify the accuracy of the Control Tables data source.

Field

Description

Data Source Name

Verify the name of the data source.

Server Name

Verify the name of the Enterprise Server.

Library Name

Enter the name of the library housing your Control Tables for the selected environment.

ODBC Data Source Name

Enter the name of the data source. For example, Control Tables - Test.

Note:
Control Tables data sources are specific to the environment and pathcode.

2. Click OK.

16.12.5 Verifying the Data Source for Versions

To verify the data source for versions:

1. On Data Source Revisions, verify the accuracy of the Versions data source.

2. Click OK.

Note:
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced Form must be checked.

16.13 Finalizing the Installation Plan

Installation Planner finalizes your installation plan automatically. A message appears to let you know that the installation plan is finalized.

When the plan is finalized:

- The status is set to 20, which signals that several adjustments to tables were made according to your plan.

- Create the OCM.

- Modify the jde.ini.

- The following tables are upgraded:

- Release Master table (F00945)

- Path Code Master table (F00942)

- Package Plan table (F98404)

- Machine Detail table (F9651)

- Language table (F984031), if you are installing an alternate language

To finalize the installation plan:

1. Click OK to exit the concluding message box and initiate the Planner Validation Report.

- If you chose the default processing option, Planner Validation Report automatically prompts you to run this report.

- If you did not choose the default processing option, on the tree view of your plan, click Validate to initiate the Planner Validation Report.

16.14 Concluding the Validation Planner Report

To conclude the validation planner report:

1. On Report Output Destination, choose On Screen or To Printer, and then click OK.

2. Review the report to confirm that all records were validated.

3. After reviewing the report, on the Batch Versions form, click Close.
For more information about Section 22.1, "Installation Planner Validation Report (R9840B)", refer to Section 22, "Working with Reports".

4. On Work With Installation Plans, click Expand to review the plan that you created.

5. Run Installation Workbench for this installation plan.
For more information about Installation Workbench, refer to Chapter 6, "Working With Installation Workbench".

16.15 Configuring Additional Servers

To configure any additional servers that you have added:

1. Create server map Library (SVM910) on additional Enterprise Servers.

2. After configuring your database and server, use Installation Workbench to allocate and configure software and resources.
When using the Installation Workbench for adding servers, the Table Conversion and the Specification Merge workbenches do not appear because they are not needed.

3. When adding a server plan for a HTML Web Server, using the P9654A program, you must add all environments prefixed with J to the Enterprise Server and generate a Server Map data source.

17 Creating a Language-Only Installation Plan

This section discusses:

- Section 17.1, "Understanding Language-Only Installation Plans"

- Section 17.2, "Reviewing Requirements for a Language Installation"

- Section 17.3, "Installing Languages on the Deployment Server"

- Section 17.4, "Running Installation Planner"

- Section 17.6, "Running Installation Workbench"

- Section 17.7, "Verifying Enterprise Server Requirements"

- Section 17.8, "Verifying Workstation Requirements"

- Section 17.9, "Completing the Language Installation"

- Section 17.10, "Building and Deploying Alternate Language Packages"

17.1 Understanding Language-Only Installation Plans

To make the language-only installation as easy and quick as possible, you should use the procedures in this chapter when installing an alternate language or multiple languages for the first time. These tasks will help you organize the pre-installation preparation required for a language-only installation:

- Install alternate languages at the same time that you install Release 9.1, or after completing a working installation .

- Implement a language-only plan only for installations in which a language has not been previously installed.

It is important that you complete all tasks in this chapter to achieve a successful language installation.

17.2 Reviewing Requirements for a Language Installation

To review the basic requirements for performing a language installation:

1. Review the language installation process.
The detailed information regarding the language installation process is found in Section 1.6, "Language Process Overview".

2. Review the disk space requirements.
Verify that the disk space requirements are available for each language and each environment that you are installing on the deployment and Enterprise Servers.

3. Review the directory structure.
The detailed information about directory structures is found in the Chapter 19, "Understanding JD Edwards EnterpriseOne Directory Structures" chapter of this guide.

17.3 Installing Languages on the Deployment Server

To install languages on the Deployment Server:

1. Obtain the JD Edwards EnterpriseOne language and run the setup.exe.

2. On JD Edwards Installation Manager, click the link for the language that you want to install.
In this example, the language installation image is for French.

3. On the Welcome screen, click Next.

4. On Client Workstation Installation Setup Type, complete these fields:

Field

Description

Select Setup Type

Ensure the radio button for your language is selected.

Install Path

The Installer provides a default path to the existing client installation on this machine:
c:\JDEdwards\910

You must verify that this drive and path is valid for your installation. You can use the browse function to locate the directory.

5. Click Finish.

The Client Workstation Install Progress displays the progress of the language installation.

When the installation finishes, the Oracle Deployment Server Setup form indicates whether the installation was successful.

6. On Installation Complete, click OK.

Note:
To access more than one language within the same package, you need to build a custom package that includes all available languages.

17.4 Running Installation Planner

Once you have installed languages on the Deployment Server, run Installation Planner. These tasks highlight the critical language-related stages of this operation.

- Section 17.4.1, "Accessing Installation Planner"

- Section 17.4.2, "Entering Information into Installation Planner"

- Section 17.4.3, "Selecting Custom or Default Parameters"

- Section 17.4.4, "Selecting an Environment"

17.4.1 Accessing Installation Planner

For details on accessing the Installation Planner, refer to the chapter of this guide entitled: Working with the Installation Planner.

Note:
If you choose a custom installation plan, you can choose which language to install for each environment. This section assumes you are defining a custom plan.

17.4.2 Entering Information into Installation Planner

To enter information into the Installation Planner:

1. On Installation Planner, enter the basic plan information.

2. In the Include Language area, select the Language Only option.

17.4.3 Selecting Custom or Default Parameters

To select custom or default parameters:

1. From Environment Selection, all environments and languages are the default values. Clear the options for Default Environment and Default Languages if you want to specify which language or languages to install for each environment.

17.4.4 Selecting an Environment

To select an environment:

Choose the environment for which you wish to install a language.

The Language Selection form appears.

17.5 Selecting a Language

To select a language:

1. On Language Selection, to set up a language for the selected environment, choose the appropriate language.

2. From the Row menu, click Select.

3. Repeat the above steps until all your languages have been selected.

4. Click OK.

17.6 Running Installation Workbench

After you create the language-only plan, you must run it through a series of workbenches in order to load the language tables to the appropriate data sources. The language installation process is the same for every database.

To run the Installation Workbench:

1. Go to Chapter 6, "Working With Installation Workbench".

2. Complete the procedures for Control Table Workbench and Specification Table Merge Workbenches.
The control tables, data dictionary, and central objects will be loaded by the Control Table Workbench and the Specification Table Merge Workbench.

17.7 Verifying Enterprise Server Requirements

To verify Enterprise Server requirements:

1. Verify that the Enterprise Server hardware and software meet all requirements.

2. Verify that the Enterprise Server disk space meets all requirements.

3. Verify that the jde.ini settings for local code set and code page values are set for your preferred language. These values are found in the National Language Support tables in Section 1.6, "Language Process Overview".

17.8 Verifying Workstation Requirements

To verify workstation requirements:

1. Verify that the workstation hardware and software meet all requirements.

2. Install the appropriate language character set to a workstation.

3. Complete the step to verify the JDE.INI settings on the Deployment Server for Interactive Runtime, Install, and Network Queues.

4. Complete the tasks in Chapter 8, "Installing the Development Clients for Developers and System Administrators".

5. Verify that the group and user profiles are set up properly.

17.9 Completing the Language Installation

Once you have verified that the Enterprise Server and workstation hardware and software meet your language install requirements, you can complete the installation.

See the JD Edwards EnterpriseOne Tools Package Management Guide for more information about how to transfer language specifications to the Enterprise Server.

17.10 Building and Deploying Alternate Language Packages

Once you have concluded the installation, it is time to build and deploy the alternate language packages. See Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for the details of including a language or creating language-only packages.

18 FTP on the IBM i

This chapter provides instructions on setting up FTP on your IBM i Enterprise Server for JD Edwards EnterpriseOne. Using FTP is an alternate method to transfer the unwrapped .jar file from a Microsoft Windows-machine to the IBM i machine.

This chapter includes the following tasks:

- Section 18.1, "Setting up FTP on the IBM i"

- Section 18.2, "Starting the FTP Server"

- Section 18.3, "Copying assembly.dat to the IBM i IFS Directory (optional)"

18.1 Setting up FTP on the IBM i

1. Use the AS\400 Operations Navigator to open your IBM i machine node and navigate to Network > Servers > TCP\IP.

2. If the DDM server is not already started, you can manually start it using the Operations Navigator. In the right-hand pane of the Operations Navigator, in the Server Name column, highlight DDM, right-click, and choose Start.

3. Configure the FTP server. In the right-hand pane of the Operations Navigator, in the Server Name column, highlight the FTP server, right click, and choose Properties.

4. On FTP Properties, select the Initial Formats tab.

5. With the Initial Formats tab selected, ensure the following checkboxes are enabled:

Checkbox

Description

File naming format

Path

Working directory

Use user's home directory

File listing format

UNIX listing format

6. Click OK to save the changes and exit the FTP Properties.

18.2 Starting the FTP Server

1. Use the AS\400 Operations Navigator to open your IBM i machine node and navigate to Network > Servers > TCP\IP.

2. In the right-hand pane of the Operations Navigator, highlight FTP, right click, and choose Start.

18.3 Copying assembly.dat to the IBM i IFS Directory (optional)

If you are not able to copy the install image from your Windows client to your IBM i because the assembly.dat file is too large, alternatively you can use FTP to transfer that file into the IFS directory.

On the Microsoft Windows client where you ran the IBM i Wrapper install:

1. Start a command window (Run | cmd), then enter this command:

ftp machine_name

where machine_name is the name of your IBM i machine.

Enter a valid IBM i user and password when prompted to do so.

2. To indicate you want to use the IFS instead of the standard file system on the IBM i, enter this command:

cd \

Note:
This command specifies you want to put files into the IFS without changing any system settings on your IBM i, as would be the case if you entered a quote site namefmt 1 command.

3. In Microsoft Windows Explorer, drill down to the assembly.dat file in your install image on the Microsoft Windows client.

For example, the assembly.dat file might be in a location similar to this:

d:\disk1\install\data\E910-3ffd45216a0d2fb17cd87deda05\9.1.000

4. In the command window type this command (but do not press Enter):

lcd

Note:
Do not press Enter at this point. Continue with the steps below to finish populating the lcd command.

5. Drag the location of the assembly.dat from Microsoft Windows Explorer results from Step 3 into the command window to append the lcd command begun in Step 4, and then press Enter to execute the lcd command.
Your completed command will look similar to this:

lcd d:\disk1\install\data\E910-3ffd45216a0d2fb17cd87deda05\9.1.000

6. In the command window type this command (but do not press Enter):

cd

Note:
Do not press Enter at this point. Continue with the steps below to finish populating the cd command.

7. In Microsoft Windows Explorer, copy the location of the assembly.dat on the Microsoft Windows box from the Address bar and paste the results to append the cd command.
Your completed command will look similar to this:

cd address_copied_from_Windows_Explorer

8. In the command window, enter this command:

bin

9. In the command window, enter this command:

put assembly.dat

10. Using Microsoft Windows Explorer, verify that the size and number of files match in the Microsoft Windows install image and the IBM i install image.

19 Understanding JD Edwards EnterpriseOne Directory Structures

The charts in this section illustrate the directory structures for JD Edwards EnterpriseOne on the Deployment Server, the Enterprise Server, and Workstations. You must understand these directory structures to verify that you installed or upgraded Release 9.1 correctly.

Assuming you use the recommended shared path names, the process does not delete or overlay your previous release. You will have the Release 9.1 directories in addition to your existing directories.

The recommended configuration is for all business functions to be mapped to the server. The only exception to this rule is a client development environment in which case all business functions should be mapped locally.

This chapter discusses:

- Section 19.1, "Deployment Server Directory Structure"

- Section 19.2, "Language Directory Structure"

- Section 19.3, "IBM i Libraries"

- Section 19.4, "Workstation General Directory Structure"

19.1 Deployment Server Directory Structure

After you install Release 9.1 on the Deployment Server, you should have the following directory structure:

JDEdwardsE910\CD Templates
JDEdwardsE910\CD Templates\Esu & Asu
JDEdwardsE910\CD Templates\Esu & Asu\planner
JDEdwardsE910\CD Templates\Esu & Asu\planner\Package
JDEdwardsE910\CD Templates\Esu & Asu\planner\Package\PKGNAME
JDEdwardsE910\cfgtoollogs
JDEdwardsE910\cfgtoollogs\cfgfw
JDEdwardsE910\cfgtoollogs\oui
JDEdwardsE910\Change Assistant
JDEdwardsE910\Change Assistant\Downloads
JDEdwardsE910\Change Assistant\Downloads\CopiedESUs
JDEdwardsE910\Change Assistant\Downloads\ESUs
JDEdwardsE910\Change Assistant\Downloads\logs
JDEdwardsE910\Change Assistant\SupportAssistant
JDEdwardsE910\client
JDEdwardsE910\database
JDEdwardsE910\database\Oracle
JDEdwardsE910\database\SQL
JDEdwardsE910\database\UDB
JDEdwardsE910\diagnostics
JDEdwardsE910\diagnostics\config
JDEdwardsE910\diagnostics\config\registration
JDEdwardsE910\path_code
JDEdwardsE910\path_code\bin32
JDEdwardsE910\path_code\include
JDEdwardsE910\path_code\ini
JDEdwardsE910\path_code\ini\sbf
JDEdwardsE910\path_code\java
JDEdwardsE910\path_code\java\sbfjars
JDEdwardsE910\path_code\lib32
JDEdwardsE910\path_code\make
JDEdwardsE910\path_code\obj
JDEdwardsE910\path_code\PACKAGE
JDEdwardsE910\path_code\PACKAGE\DATA
JDEdwardsE910\path_code\PACKAGE\DATACOMP
JDEdwardsE910\path_code\PACKAGE\path_codeFA
JDEdwardsE910\path_code\PACKAGE\path_codeFA\bin32
JDEdwardsE910\path_code\PACKAGE\path_codeFA\include
JDEdwardsE910\path_code\PACKAGE\path_codeFA\java
JDEdwardsE910\path_code\PACKAGE\path_codeFA\java\sbfjars
JDEdwardsE910\path_code\PACKAGE\path_codeFA\lib32
JDEdwardsE910\path_code\PACKAGE\path_codeFA\make
JDEdwardsE910\path_code\PACKAGE\path_codeFA\obj
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\actionbmps
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\AVI Files
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\FormLines
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\Icons
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\images
JDEdwardsE910\path_code\PACKAGE\path_codeFA\res\treebmps
JDEdwardsE910\path_code\PACKAGE\path_codeFA\source
JDEdwardsE910\path_code\PACKAGE\path_codeFA\spec
JDEdwardsE910\path_code\PACKAGE\path_codeFA\spec\runtimeCache
JDEdwardsE910\path_code\PACKAGE\path_codeFA\work
JDEdwardsE910\path_code\PACKAGE\path_codeFA\work\sbf
JDEdwardsE910\path_code\PACKAGE\path_codeFA\work\sbf\oas
JDEdwardsE910\path_code\PACKAGE\path_codeFA\work\sbf\oas\META-INF
JDEdwardsE910\path_code\res
JDEdwardsE910\path_code\res\actionbmps
JDEdwardsE910\path_code\res\AVI Files
JDEdwardsE910\path_code\res\FormLines
JDEdwardsE910\path_code\res\Icons
JDEdwardsE910\path_code\res\images
JDEdwardsE910\path_code\res\treebmps
JDEdwardsE910\path_code\source
JDEdwardsE910\path_code\spec
JDEdwardsE910\path_code\spec\runtimeCache
JDEdwardsE910\path_code\work
JDEdwardsE910\path_code\work\sbf
JDEdwardsE910\path_code\work\sbf\oas
JDEdwardsE910\path_code\work\sbf\oas\META-INF

Note:
In the preceding paths, the path_code portion is DV910, PD910, PS910, or PY910.

Note:
The PACKAGE\path_code directory contains the same sub-structure as this parent directory:
JDEdwards910\path_code

JDEdwardsE910\E1InstallerLibs
JDEdwardsE910\install
JDEdwardsE910\inventory
JDEdwardsE910\inventory\Actions21
JDEdwardsE910\inventory\Actions21\e1FileActions
JDEdwardsE910\inventory\Actions21\e1FileActions\10.2.0.3.0
JDEdwardsE910\inventory\Actions21\e1GeneralActions
JDEdwardsE910\inventory\Actions21\e1FileActions\10.2.0.3.0
JDEdwardsE910\inventory\Actions21\e1PackageActions
JDEdwardsE910\inventory\Actions21\e1PackageActions\10.2.0.3.0
JDEdwardsE910\inventory\Actions21\fileActions
JDEdwardsE910\inventory\Actions21\fileActions\11.2.0.2.0
JDEdwardsE910\inventory\Actions21\generalActions
JDEdwardsE910\inventory\Actions21\generalActions\10.2.0.9.0
JDEdwardsE910\inventory\Actions21\ntServicesActions
JDEdwardsE910\inventory\Actions21\ntServicesActions\10.2.0.6.0
JDEdwardsE910\inventory\Actions21\ntw32FoldersActions
JDEdwardsE910\inventory\Actions21\ntw32FoldersActions\10.2.0.3.0
JDEdwardsE910\inventory\Actions21\SpawnActions
JDEdwardsE910\inventory\Actions21\SpawnActions\10.1.0.3.4
JDEdwardsE910\inventory\Actions21\w32RegActions
JDEdwardsE910\inventory\Actions21\w32RegActions\10.2.0.1.0
JDEdwardsE910\inventory\backup
JDEdwardsE910\inventory\checkpoints
JDEdwardsE910\inventory\Clone
JDEdwardsE910\inventory\Components21
JDEdwardsE910\inventory\Components21\com.e1.bpm
JDEdwardsE910\inventory\Components21\com.e1.bpm\1.0.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.bpm\1.0.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.data
JDEdwardsE910\inventory\Components21\com.e1.deployment.data\1.0.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.data\1.0.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.development
JDEdwardsE910\inventory\Components21\com.e1.deployment.development\9.1.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.development\9.1.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.e1files
JDEdwardsE910\inventory\Components21\com.e1.deployment.e1files\9.1.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.e1files\9.1.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.oh4a
JDEdwardsE910\inventory\Components21\com.e1.deployment.oh4a\1.0.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.oh4a\1.0.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.planner
JDEdwardsE910\inventory\Components21\com.e1.deployment.planner\9.1.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.planner\9.1.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.deployment.top
JDEdwardsE910\inventory\Components21\com.e1.deployment.top\9.1.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.deployment.top\9.1.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.features
JDEdwardsE910\inventory\Components21\com.e1.features\1.0.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.features\1.0.0.0.0\resources
JDEdwardsE910\inventory\Components21\com.e1.foundation
JDEdwardsE910\inventory\Components21\com.e1.foundation\1.0.0.0.0
JDEdwardsE910\inventory\Components21\com.e1.foundation\1.0.0.0.0\resources
JDEdwardsE910\inventory\Components21\oracle.jdk
JDEdwardsE910\inventory\Components21\oracle.jdk\1.6.0.21.51
JDEdwardsE910\inventory\Components21\oracle.jdk\1.6.0.21.51\resources
JDEdwardsE910\inventory\Components21\oracle.swd.opatch
JDEdwardsE910\inventory\Components21\oracle.swd.opatch\11.2.0.0.2
JDEdwardsE910\inventory\Components21\oracle.swd.opatch\11.2.0.0.2\resources
JDEdwardsE910\inventory\Components21\oracle.swd.oui
JDEdwardsE910\inventory\Components21\oracle.swd.oui\11.2.0.2.0
JDEdwardsE910\inventory\Components21\oracle.swd.oui\11.2.0.2.0\resources
JDEdwardsE910\inventory\Components21\oracle.swd.oui.core
JDEdwardsE910\inventory\Components21\oracle.swd.oui.core\11.2.0.2.0
JDEdwardsE910\inventory\Components21\oracle.swd.oui.core\11.2.0.2.0\resources
JDEdwardsE910\inventory\ContentsXML
JDEdwardsE910\inventory\ContentsXML\ConfigXML
JDEdwardsE910\inventory\Dialogs21
JDEdwardsE910\inventory\Dialogs21\standardDialogs
JDEdwardsE910\inventory\Dialogs21\standardDialogs\10.2.0.1.0
JDEdwardsE910\inventory\Queries21
JDEdwardsE910\inventory\Queries21\areasQueries
JDEdwardsE910\inventory\Queries21\areasQueries\10.2.0.1.0
JDEdwardsE910\inventory\Queries21\e1DBQueries
JDEdwardsE910\inventory\Queries21\e1DBQueries\10.2.0.3.0
JDEdwardsE910\inventory\Queries21\e1FileQueries
JDEdwardsE910\inventory\Queries21\e1FileQueries\10.2.0.3.0
JDEdwardsE910\inventory\Queries21\e1GeneralQueries
JDEdwardsE910\inventory\Queries21\e1GeneralQueries\10.2.0.3.0
JDEdwardsE910\inventory\Queries21\e1PackageQueries
JDEdwardsE910\inventory\Queries21\e1PackageQueries\10.2.0.3.0
JDEdwardsE910\inventory\Queries21\fileQueries
JDEdwardsE910\inventory\Queries21\fileQueries\10.1.0.3.0
JDEdwardsE910\inventory\Queries21\generalQueries
JDEdwardsE910\inventory\Queries21\generalQueries\10.2.0.2.0
JDEdwardsE910\inventory\Queries21\w32RegQueries
JDEdwardsE910\inventory\Queries21\w32RegQueries\10.2.0.1.0
JDEdwardsE910\inventory\Queries21\WindowsGeneralQueries
JDEdwardsE910\inventory\Queries21\WindowsGeneralQueries\10.2.0.1.0
JDEdwardsE910\inventory\Scripts
JDEdwardsE910\inventory\Scripts\ext
JDEdwardsE910\inventory\Scripts\ext\jlib
JDEdwardsE910\inventory\Scripts\ext\lib
JDEdwardsE910\inventory\Templates
JDEdwardsE910\inventory\Templates\OPatch
JDEdwardsE910\inventory\Templates\oui
JDEdwardsE910\inventory\Templates\oui\bin
JDEdwardsE910\inventory\Templates\system
JDEdwardsE910\inventory\Templates\system\OC4J
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home\applications
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home\applications\webclient.ear
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home\applications\webclient.ear\webclient
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF
JDEdwardsE910\inventory\Templates\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes
JDEdwardsE910\jdk
JDEdwardsE910\jdk\bin
JDEdwardsE910\jdk\include
JDEdwardsE910\jdk\include\win32
JDEdwardsE910\jdk\jre
JDEdwardsE910\jdk\jre\bin
JDEdwardsE910\jdk\jre\bin\client
JDEdwardsE910\jdk\jre\bin\new_plugin
JDEdwardsE910\jdk\jre\bin\server
JDEdwardsE910\jdk\jre\lib
JDEdwardsE910\jdk\jre\lib\applet
JDEdwardsE910\jdk\jre\lib\audio
JDEdwardsE910\jdk\jre\lib\cmm
JDEdwardsE910\jdk\jre\lib\deploy
JDEdwardsE910\jdk\jre\lib\deploy\jqs
JDEdwardsE910\jdk\jre\lib\deploy\jqs\ff
JDEdwardsE910\jdk\jre\lib\deploy\jqs\ff\chrome
JDEdwardsE910\jdk\jre\lib\deploy\jqs\ff\chrome\content
JDEdwardsE910\jdk\jre\lib\deploy\jqs\ie
JDEdwardsE910\jdk\jre\lib\ext
JDEdwardsE910\jdk\jre\lib\fonts
JDEdwardsE910\jdk\jre\lib\i386
JDEdwardsE910\jdk\jre\lib\im
JDEdwardsE910\jdk\jre\lib\images
JDEdwardsE910\jdk\jre\lib\images\cursors
JDEdwardsE910\jdk\jre\lib\management
JDEdwardsE910\jdk\jre\lib\security
JDEdwardsE910\jdk\jre\lib\servicetag
JDEdwardsE910\jdk\jre\lib\zi
JDEdwardsE910\jdk\jre\lib\zi\Africa
JDEdwardsE910\jdk\jre\lib\zi\America
JDEdwardsE910\jdk\jre\lib\zi\America\Argentina
JDEdwardsE910\jdk\jre\lib\zi\America\Indiana
JDEdwardsE910\jdk\jre\lib\zi\America\Kentucky
JDEdwardsE910\jdk\jre\lib\zi\America\North_Dakota
JDEdwardsE910\jdk\jre\lib\zi\Antarctica
JDEdwardsE910\jdk\jre\lib\zi\Asia
JDEdwardsE910\jdk\jre\lib\zi\Atlantic
JDEdwardsE910\jdk\jre\lib\zi\Australia
JDEdwardsE910\jdk\jre\lib\zi\Etc
JDEdwardsE910\jdk\jre\lib\zi\Europe
JDEdwardsE910\jdk\jre\lib\zi\Indian
JDEdwardsE910\jdk\jre\lib\zi\Pacific
JDEdwardsE910\jdk\jre\lib\zi\SystemV
JDEdwardsE910\jdk\lib
JDEdwardsE910\jdk\lib\visualvm
JDEdwardsE910\jdk\lib\visualvm\etc
JDEdwardsE910\jdk\lib\visualvm\platform11
JDEdwardsE910\jdk\lib\visualvm\platform11\config
JDEdwardsE910\jdk\lib\visualvm\platform11\config\ModuleAutoDeps
JDEdwardsE910\jdk\lib\visualvm\platform11\config\Modules
JDEdwardsE910\jdk\lib\visualvm\platform11\core
JDEdwardsE910\jdk\lib\visualvm\platform11\core\locale
JDEdwardsE910\jdk\lib\visualvm\platform11\docs
JDEdwardsE910\jdk\lib\visualvm\platform11\lib
JDEdwardsE910\jdk\lib\visualvm\platform11\lib\locale
JDEdwardsE910\jdk\lib\visualvm\platform11\modules
JDEdwardsE910\jdk\lib\visualvm\platform11\modules\ext
JDEdwardsE910\jdk\lib\visualvm\platform11\modules\ext\locale
JDEdwardsE910\jdk\lib\visualvm\platform11\modules\locale
JDEdwardsE910\jdk\lib\visualvm\platform11\update_tracking
JDEdwardsE910\jdk\lib\visualvm\profiler3
JDEdwardsE910\jdk\lib\visualvm\profiler3\config
JDEdwardsE910\jdk\lib\visualvm\profiler3\config\Modules
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\deployed
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\deployed\jdk15
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\deployed\jdk15\windows
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\deployed\jdk16
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\deployed\jdk16\windows
JDEdwardsE910\jdk\lib\visualvm\profiler3\lib\locale
JDEdwardsE910\jdk\lib\visualvm\profiler3\modules
JDEdwardsE910\jdk\lib\visualvm\profiler3\modules\locale
JDEdwardsE910\jdk\lib\visualvm\profiler3\update_tracking
JDEdwardsE910\jdk\lib\visualvm\visualvm
JDEdwardsE910\jdk\lib\visualvm\visualvm\config
JDEdwardsE910\jdk\lib\visualvm\visualvm\config\Modules
JDEdwardsE910\jdk\lib\visualvm\visualvm\core
JDEdwardsE910\jdk\lib\visualvm\visualvm\core\locale
JDEdwardsE910\jdk\lib\visualvm\visualvm\modules
JDEdwardsE910\jdk\lib\visualvm\visualvm\modules\locale
JDEdwardsE910\jdk\lib\visualvm\visualvm\update_tracking
JDEdwardsE910\mediaobj
JDEdwardsE910\mediaobj\Composer
JDEdwardsE910\mediaobj\Composer\html
JDEdwardsE910\mediaobj\Composer\html\Images
JDEdwardsE910\mediaobj\Composer\Visio
JDEdwardsE910\mediaobj\ComposerCBT
JDEdwardsE910\mediaobj\ComposerCBT\Order_to_Cash
JDEdwardsE910\mediaobj\ComposerCBT\Procure_to_Pay
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Eapxxxxx
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Eapxxxxx\graphics
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Earxxxxx
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Earxxxxx\graphics
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Ecoxxxxx
JDEdwardsE910\mediaobj\ComposerCBT\ShowMe_Ecoxxxxx\graphics
JDEdwardsE910\mediaobj\ComposerCBT\Standard_Graphics
JDEdwardsE910\mediaobj\Distribution
JDEdwardsE910\mediaobj\Financials
JDEdwardsE910\mediaobj\htmlupload
JDEdwardsE910\mediaobj\Human Resources
JDEdwardsE910\mediaobj\Manufacturing
JDEdwardsE910\mediaobj\MISC
JDEdwardsE910\mediaobj\Misc Animations
JDEdwardsE910\mediaobj\Misc Images
JDEdwardsE910\mediaobj\Oleque
JDEdwardsE910\mediaobj\OMW
JDEdwardsE910\mediaobj\SelfService
JDEdwardsE910\mediaobj\Text
JDEdwardsE910\MISC
JDEdwardsE910\OneWorld Client Install
JDEdwardsE910\OneWorld Client Install\install
JDEdwardsE910\OneWorld Client Install\install\access
JDEdwardsE910\OneWorld Client Install\install\access\jdk
JDEdwardsE910\OneWorld Client Install\install\access\jdk\jre
JDEdwardsE910\OneWorld Client Install\install\access\jdk\jre\bin
JDEdwardsE910\OneWorld Client Install\install\access\jdk\jre\lib
JDEdwardsE910\OneWorld Client Install\install\access\jdk\jre\lib\ext
JDEdwardsE910\OneWorld Client Install\install\resource
JDEdwardsE910\OneWorld Client Install\Misc
JDEdwardsE910\OneWorld Client Install\Misc\SBFServer
JDEdwardsE910\OneWorld Client Install\Stage
JDEdwardsE910\OneWorld Client Install\Stage\Actions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\dbActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\dbActions\10.1.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\dbActions\10.1.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1FileActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1FileActions\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1FileActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1GeneralActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1GeneralActions\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1GeneralActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1ISeriesActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1ISeriesActions\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1ISeriesActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1PackageActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\e1PackageActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\fileActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\fileActions\11.2.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\fileActions\11.2.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\generalActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\generalActions\10.2.0.9.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\generalActions\10.2.0.9.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\jarActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\jarActions\10.2.0.0.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\jarActions\10.2.0.0.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\launchPadActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\launchPadActions\10.1.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\launchPadActions\10.1.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntServicesActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntServicesActions\10.2.0.6.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntServicesActions\10.2.0.6.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntw32FoldersActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntw32FoldersActions\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\ntw32FoldersActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\rgsActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\rgsActions\10.1.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\rgsActions\10.1.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\SpawnActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\SpawnActions\10.1.0.3.4
JDEdwardsE910\OneWorld Client Install\Stage\Actions\SpawnActions\10.1.0.3.4\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\unixActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\unixActions\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\unixActions\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32OcxRegActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32OcxRegActions\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32OcxRegActions\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32RegActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32RegActions\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\w32RegActions\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Actions\wingeneralActions
JDEdwardsE910\OneWorld Client Install\Stage\Actions\wingeneralActions\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Actions\wingeneralActions\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Components
JDEdwardsE910\OneWorld Client Install\Stage\Components\com.e1.devclient.top
JDEdwardsE910\OneWorld Client Install\Stage\Components\com.e1.devclient.top\1.0.0.0.0
JDEdwardsE910\OneWorld Client Install\Stage\Components\com.e1.devclient.top\1.0.0.0.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\com.e1.devclient.top\1.0.0.0.0\1\DataFiles
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.jdk
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.jdk\1.6.0.21.51
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.jdk\1.6.0.21.51\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.jdk\1.6.0.21.51\1\DataFiles
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.jre
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.jre\1.5.0.11.0
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.jre\1.5.0.11.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.jre\1.5.0.11.0\1\DataFiles
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.opatch
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.opatch\11.2.0.0.2
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.opatch\11.2.0.0.2\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.opatch\11.2.0.0.2\1\DataFiles
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui\11.2.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui\11.2.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui.core
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui.core\11.2.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui.core\11.2.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Components\oracle.swd.oui.core\11.2.0.2.0\1\DataFiles
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\e1Dialogs
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\e1Dialogs\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\e1Dialogs\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\standardDialogs
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\standardDialogs\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Dialogs\standardDialogs\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Disk1
JDEdwardsE910\OneWorld Client Install\Stage\Disk1\stage
JDEdwardsE910\OneWorld Client Install\Stage\ext
JDEdwardsE910\OneWorld Client Install\Stage\ext\jlib
JDEdwardsE910\OneWorld Client Install\Stage\ext\lib
JDEdwardsE910\OneWorld Client Install\Stage\globalvariables
JDEdwardsE910\OneWorld Client Install\Stage\Queries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\areasQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\areasQueries\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\areasQueries\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\dbQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\dbQueries\10.1.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\dbQueries\10.1.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1DBQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1FileQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1FileQueries\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1FileQueries\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1GeneralQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1GeneralQueries\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1GeneralQueries\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1ISeriesQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1ISeriesQueries\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1ISeriesQueries\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1PackageQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1PackageQueries\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\e1PackageQueries\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\fileQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\fileQueries\10.1.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\fileQueries\10.1.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\generalQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\generalQueries\10.2.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\generalQueries\10.2.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\netQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\netQueries\10.2.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\netQueries\10.2.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\NtServicesQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\NtServicesQueries\10.2.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\NtServicesQueries\10.2.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\rgsQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\rgsQueries\10.1.0.3.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\rgsQueries\10.1.0.3.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\unixQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\unixQueries\10.1.0.2.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\unixQueries\10.1.0.2.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\w32RegQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\w32RegQueries\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\w32RegQueries\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\Queries\WindowsGeneralQueries
JDEdwardsE910\OneWorld Client Install\Stage\Queries\WindowsGeneralQueries\10.2.0.1.0
JDEdwardsE910\OneWorld Client Install\Stage\Queries\WindowsGeneralQueries\10.2.0.1.0\1
JDEdwardsE910\OneWorld Client Install\Stage\shiphomeinfo
JDEdwardsE910\OneWorld Client Install\Stage\shiphomeinfo\summary
JDEdwardsE910\OneWorld Client Install\ThirdParty
JDEdwardsE910\OneWorld Client Install\ThirdParty\BPMBroker
JDEdwardsE910\OneWorld Client Install\ThirdParty\ORACLE
JDEdwardsE910\OneWorld Client Install\ThirdParty\VSRunTime
JDEdwardsE910\OneWorld Client Install\ThirdParty\WebDevFeature
JDEdwardsE910\OneWorld Client Install\ThirdParty\WebDevFeature\H4A7
JDEdwardsE910\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A
JDEdwardsE910\OPatch
JDEdwardsE910\OPatch\crs
JDEdwardsE910\OPatch\docs
JDEdwardsE910\OPatch\fmw
JDEdwardsE910\OPatch\jlib
JDEdwardsE910\OPatch\ocm
JDEdwardsE910\OPatch\ocm\generic.zip
JDEdwardsE910\OPatch\opatchprereqs
JDEdwardsE910\OPatch\opatchprereqs\opatch
JDEdwardsE910\OPatch\opatchprereqs\oui
JDEdwardsE910\oui
JDEdwardsE910\oui\bin
JDEdwardsE910\oui\bin\resource
JDEdwardsE910\oui\instImages
JDEdwardsE910\oui\jlib
JDEdwardsE910\oui\jlib\lib
JDEdwardsE910\oui\lib
JDEdwardsE910\oui\lib\win32
JDEdwardsE910\oui\schema
JDEdwardsE910\package_inf
JDEdwardsE910\package_inf\Feature_inf
JDEdwardsE910\Planner
JDEdwardsE910\Planner\bin32
JDEdwardsE910\Planner\bin32
JDEdwardsE910\Planner\data
JDEdwardsE910\Planner\include
JDEdwardsE910\Planner\ini
JDEdwardsE910\Planner\ini\sbf
JDEdwardsE910\Planner\java
JDEdwardsE910\Planner\java\sbfjars
JDEdwardsE910\Planner\lib32
JDEdwardsE910\Planner\make
JDEdwardsE910\Planner\obj
JDEdwardsE910\Planner\res
JDEdwardsE910\Planner\res\actionbmps
JDEdwardsE910\Planner\res\AVI Files
JDEdwardsE910\Planner\res\FormLines
JDEdwardsE910\Planner\res\Icons
JDEdwardsE910\Planner\res\images
JDEdwardsE910\Planner\res\treebmps
JDEdwardsE910\Planner\source
JDEdwardsE910\Planner\spec
JDEdwardsE910\Planner\spec\runtimeCache
JDEdwardsE910\Planner\work
JDEdwardsE910\Planner\work\sbf
JDEdwardsE910\SolutionExplorer
JDEdwardsE910\SolutionExplorer\+ Concept To Opportunity
JDEdwardsE910\SolutionExplorer\+ Concept To Opportunity\CustomWorks
JDEdwardsE910\SolutionExplorer\+ Concept To Opportunity\CustomWorks\Object Model Documentation
JDEdwardsE910\SolutionExplorer\+ Consumption To Reorder
JDEdwardsE910\SolutionExplorer\+ Demand To Available
JDEdwardsE910\SolutionExplorer\+ Demand To Available\MakeProduct
JDEdwardsE910\SolutionExplorer\+ Demand To Available\MakeProduct\Make Product Interview Questions_files
JDEdwardsE910\SolutionExplorer\+ Demand To Available\PlanSupplyChain
JDEdwardsE910\SolutionExplorer\+ Implementation Approach
JDEdwardsE910\SolutionExplorer\+ Manage The Business
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Activity Scripts
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Activity Scripts\Account and Report Script_files
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Activity Scripts\Process Payments Script_files
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Activity Scripts\Process Receivables Script_files
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Interview Questions
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Interview Questions\Account and Report Questions_files
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Interview Questions\Process Payments Questions_files
JDEdwardsE910\SolutionExplorer\+ Manage The Business\Interview Questions\Process Receivables Questions_files
JDEdwardsE910\SolutionExplorer\+ Order To Cash
JDEdwardsE910\SolutionExplorer\+ Order To Cash\_vti_cnf
JDEdwardsE910\SolutionExplorer\+ Procure To Pay
JDEdwardsE910\SolutionExplorer\+ Procure To Pay\_vti_cnf
JDEdwardsE910\SolutionExplorer\+ Procure To Pay\CRP Scripts procure to pay_files
JDEdwardsE910\SolutionExplorer\+ Procure To Pay\CRP Scripts procure to pay_files\_vti_cnf
JDEdwardsE910\SolutionExplorer\BM944072060102
JDEdwardsE910\SolutionExplorer\BMPxxxxxxxxxxxx
JDEdwardsE910\SolutionExplorer\JDExxxxxx
JDEdwardsE910\system
JDEdwardsE910\system\bin32
JDEdwardsE910\system\bin32\debug
JDEdwardsE910\system\Classes
JDEdwardsE910\system\Classes\buildDeployBSSV
JDEdwardsE910\system\Classes\ConsumerWEBXML
JDEdwardsE910\system\Classes\endorsed
JDEdwardsE910\system\Classes\lib
JDEdwardsE910\system\Classes\Orchestration
JDEdwardsE910\system\Classes\samples
JDEdwardsE910\system\Generator
JDEdwardsE910\system\IDA
JDEdwardsE910\system\include
JDEdwardsE910\system\include\connector
JDEdwardsE910\system\include\database
JDEdwardsE910\system\include\jdesaw
JDEdwardsE910\system\include\Metadata
JDEdwardsE910\system\include\netmessaging
JDEdwardsE910\system\include\perfmon
JDEdwardsE910\system\include\workflow
JDEdwardsE910\system\include\xml
JDEdwardsE910\system\includev
JDEdwardsE910\system\includev\unicode
JDEdwardsE910\system\JDK
JDEdwardsE910\system\JRE
JDEdwardsE910\system\lib32
JDEdwardsE910\system\libv32
JDEdwardsE910\system\Locale
JDEdwardsE910\system\Locale\Iconv
JDEdwardsE910\system\Locale\Uconvtab
JDEdwardsE910\system\Locale\xml
JDEdwardsE910\system\Locale\xml\hpux
JDEdwardsE910\system\Locale\xml\NT
JDEdwardsE910\system\Locale\xml\Solaris
JDEdwardsE910\system\Mobile
JDEdwardsE910\system\Mobile\Authentication
JDEdwardsE910\system\Mobile\JrnlSQLCode
JDEdwardsE910\system\Mobile\WebLogic
JDEdwardsE910\system\OC4J
JDEdwardsE910\system\OC4J\ant
JDEdwardsE910\system\OC4J\ant\bin
JDEdwardsE910\system\OC4J\ant\etc
JDEdwardsE910\system\OC4J\ant\etc\checkstyle
JDEdwardsE910\system\OC4J\ant\lib
JDEdwardsE910\system\OC4J\bin
JDEdwardsE910\system\OC4J\diagnostics
JDEdwardsE910\system\OC4J\diagnostics\config
JDEdwardsE910\system\OC4J\diagnostics\lib
JDEdwardsE910\system\OC4J\j2ee
JDEdwardsE910\system\OC4J\j2ee\home
JDEdwardsE910\system\OC4J\j2ee\utilities
JDEdwardsE910\system\OC4J\javacache
JDEdwardsE910\system\OC4J\javacache\lib
JDEdwardsE910\system\OC4J\javavm
JDEdwardsE910\system\OC4J\javavm\lib
JDEdwardsE910\system\OC4J\jdbc
JDEdwardsE910\system\OC4J\jdbc\lib
JDEdwardsE910\system\OC4J\jlib
JDEdwardsE910\system\OC4J\lib
JDEdwardsE910\system\OC4J\opmn
JDEdwardsE910\system\OC4J\opmn\lib
JDEdwardsE910\system\OC4J\rdbms
JDEdwardsE910\system\OC4J\rdbms\jlib
JDEdwardsE910\system\OC4J\sqlj
JDEdwardsE910\system\OC4J\sqlj\jlib
JDEdwardsE910\system\OC4J\toplink
JDEdwardsE910\system\OC4J\toplink\jlib
JDEdwardsE910\system\OC4J\webservices
JDEdwardsE910\system\OC4J\webservices\lib
JDEdwardsE910\system\OC4J\xqs
JDEdwardsE910\system\OC4J\xqs\lib
JDEdwardsE910\system\OC4J\xqs\tools
JDEdwardsE910\system\resource
JDEdwardsE910\system\resource\cmap
JDEdwardsE910\system\resource\truetype
JDEdwardsE910\systemcomp
JDEdwardsE910\ThirdParty
JDEdwardsE910\ThirdParty\BPMBroker

19.2 Language Directory Structure

The following table outlines the Release 9.1 software directory structure for the Release 9.1 language installation image. You must understand this directory structure to help you verify that the language was installed correctly.

Directory Name

Definition

\LANGUAGE

Name of language for JD Edwards EnterpriseOne language installation.

\Helps

Language help files.

\SolutionExplorer

Solution Explorer language files.

\SolutionExplorer\PLANNER

Planner path code.

\SolutionExplorer\PLANNER\DATA

Language database.

19.3 IBM i Libraries

After you transfer Release 9.1 software to the Enterprise Server and run Installation Workbench, you should have the following Enterprise Server libraries, where xxxx is the release to which you are installing, such as E910.

Library Type

Library Name

IFS

Definition

Install

JDEOW

Menus and executable programs

Host Application

E900SYS

E900SYS
classes

include

includea

includev

locale

resource

INI

output

queue

printqueue

OneWorld\Package

JD Edwards EnterpriseOne Foundation

Host Application

E900SYS

Packages

Package source, include, and spec files

Shared

DD910

Data Dictionary tables

OL910

Object Librarian tables

SVM910

Server Map tables

SY910

System tables

OWJRNL

Journaling

JDE910

EnterpriseOne log files

Environment

DV910 (Development)

TESTCTL

Control Tables and Data Dictionary tables

TESTDTA

Business Data tables

CODV910

Central Objects and Versions tables

DV910

Pathcode service programs

DV910

Parent package service programs

DV910\specfile

Pathcode specifications

PS910 (Pristine)

PS910CTL

Control Tables and Data Dictionary tables

PS910DTA

Business Data tables

COPS910

Central Objects and Versions tables

PS910

Pathcode service programs

PS910

Parent package service programs

PS910\specfile

Pathcode specifications

PD910 (Production)

PRODCTL

Control Tables and Data Dictionary tables

PRODDTA

Business Data tables

COPD910

Central Objects and Versions tables

PD910

Pathcode service programs

PD910FA

Parent package service programs

PD910\specfile

Pathcode specifications

PY910 (Prototype)

CRPCTL

Control Tables and Data Dictionary tables

CRPDTA

Business Data tables

COPY910

Central Objects and Versions tables

PY910

Pathcode service programs

PY910FA

Parent package service programs

PY910\specfile

Pathcode specifications

19.4 Workstation General Directory Structure

After you install Release 9.1 installation on a Workstation, you should have the following local directory structure:

\E910
\E910\Log
\E910\output
\E910\packages
\E910\PD910
\E910\PrintQueue
\E910\queues
\E910\system
\E910\PD910\bin32
\E910\PD910\spec
\E910\PD910\spec\JDE
\E910\queues\control
\E910\queues\outqueue
\E910\system\bin32
\E910\system\Classes
\E910\system\include
\E910\system\includev
\E910\system\lib32
\E910\system\libv32
\E910\system\locale
\E910\system\resource
\E910\system\Classes\samples
\E910\system\includev\unicode
\E910\system\locale\iconv
\E910\system\locale\uconvtab
\E910\system\locale\xml
\E910\system\resource\cidfont
\E910\system\resource\cmap
\E910\system\resource\encoding
\E910\system\resource\font
\E910\system\resource\iccprofile
\E910\system\resource\truetype
\E910\system\resource\font\pfm

20 Understanding Data Source Charts

This chapter discusses these data sources:

- Section 20.1, "Business Data"

- Section 20.2, "Central Objects"

- Section 20.3, "Control Tables"

- Section 20.4, "Data Dictionary"

- Section 20.8, "Local"

- Section 20.5, "Logic"

- Section 20.6, "Object Librarian"

- Section 20.7, "Language"

- Section 20.8, "Local"

- Section 20.9, "OWJRNL"

- Section 20.10, "Server Map"

- Section 20.11, "System"

- Section 20.12, "Versions"

20.1 Business Data

This chart lists the characteristics of the Business Data data source.

Field

Valid Value for Client Access

Data Source Name (list includes possible sources)

Business Data - PROD
Business Data - CRP

Business Data - TEST

Business Data - PS910

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name (list includes possible libraries)

PRODDTA
TESTDTA

CRPDTA

PS910DTA

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name (list includes possible databases)

Business Data - PROD
Business Data - TEST

Business Data - CRPDTA

Business Data - PS910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

LOB Data Source

Selected

IBM i BLOB Support

Blank

20.2 Central Objects

This chart lists the characteristics of the Central Objects data source.

Field

Client Access

Data Source Name (list includes possible sources)

Central Objects - PY910 (for CRP)
Central Objects - PS910 (for Prist)

Central Objects - PD910 (for Prod)

Central Objects - DV910 (for Dev)

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name (list includes possible libraries)

COPD910 (for Prod)
COPY910 (for CRP)

COPS910 (for Prist)

CODV910 (for Dev)

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name (list includes possible databases)

Central Objects - PY910
Central Objects - PS910

Central Objects - PD910

Central Objects - DV910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

LOB Data Source

Selected

IBM i BLOB Support

Blank

20.3 Control Tables

This chart lists the characteristics of the Control Tables data source.

Field

Client Access

Data Source Name (list includes possible sources)

Control Tables - Prod
Control Tables - CRP

Control Tables - PS910

Control Tables - Test

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name (list includes possible libraries)

PRODCTL
CRPCTL

PS910CTL

TESTCTL

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name (list includes possible databases)

Control Tables - Prod
Control Tables - CRP

Control Tables - PS910

Control Tables - Test

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

LOB Data Source

Selected

IBM i BLOB Support

Blank

20.4 Data Dictionary

This chart lists the characteristics of the Data Dictionary data source.

Field

Client Access

Data Source Name

Data Dictionary - 910

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name

DD910

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name

Data Dictionary - 910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

LOB Data Source

Selected

IBM i BLOB Support

Blank

20.5 Logic

This chart lists the characteristics of the Logic data source.

Field

Client Access

Data Source Name

Name of the machine where your database resides

Data Source Use

SVR

Data Source Type

I

Object Owner ID

Blank

Library Name

xMAP (where x is the release to which you are installing, such as 910)

Library List Name

RDB name of the IBM i
Note: Ensure the system value for QCCSID is 37.

To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name

machinename - 910 Server Map

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

IBM i BLOB Support

Selected

20.6 Object Librarian

This chart lists the characteristics of the Object Librarian data source.

Field

Valid Value for Client Access

Data Source Name

Object Librarian - 910

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name

OL910

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name

Object Librarian - 910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

IBM i BLOB Support

Blank

LOB Data Source

Selected

20.7 Language

This chart lists the characteristics of the Language data source, which applies to the Oracle tablespace on the Deployment Server.

Field

Valid Value for Oracle

Data Source Name (list includes possible sources)

Language
Language – 910

For example, French – 910.

Data Source Use

DB

Data Source Type

N

Object Owner ID (list includes possible owner IDs)

Blank

Library Name

Blank

Library List Name

Blank

Database Name (list includes possible databases)

Language
JDELanguage_F910

Server Name

Local

Platform

LOCAL

Use Table Owner

Blank

Use Julian Dates

Blank

Use Decimal Shift

Blank

Support for Updates

Blank

OCM Data Source

Blank

IBM i BLOB Support

Blank

20.8 Local

This chart lists the characteristics of the Local data source, which applies to the Oracle tablespace on the Deployment Server.

Field

Valid Value for Oracle

Data Source Name (list includes possible sources)

Local
JDELocal - DV910

JDELocal - PS910

JDELocal - PD910

JDELocal - PY910

Data Source Use

DB

Data Source Type

N

Object Owner ID (list includes possible owner IDs)

dbo

Library Name

Blank

Library List Name

Blank

Database Name (list includes possible databases)

JDELocal
JDEPlan910

JDECTL910

JDEDD910

JDESY910

JDEVL910

JDEOL910

JDEData910

Server Name

Local

Platform

LOCAL

Use Table Owner

Selected

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

LOB Data Source

Blank

20.9 OWJRNL

This chart lists the characteristics of the Journal data source.

Field

Valid Value for Client Access

Data Source Name (list includes possible sources)

OWJRNL

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name

OWJRNL

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name

OWJRNL

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

IBM i BLOB Support

Blank

20.10 Server Map

This chart lists the characteristics of the Server Map data source.

Field

Valid Value for Client Access

Data Source Name

machinename - 910 Server Map

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name

SVM910

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

Database Name

machinename - 910 Server Map

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Selected

IBM i BLOB Support

Blank

LOB Data Source

Selected

20.11 System

This chart lists the characteristics of the System data source.

Field

Valid Value for Client Access

Data Source Name (list includes possible sources)

System - 910

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name

SY910

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

DLL Name

Blank

Database Name (list includes possible databases)

System - 910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Selected

IBM i BLOB Support

Blank

LOB Data Source

Selected

20.12 Versions

This chart lists the characteristics of the Versions data source.

Field

Valid Value for Client Access

Data Source Name (list includes possible sources)

Versions - PD910
Versions - PY910

Versions - DV910

Versions - PS910

Data Source Use

DB

Data Source Type

I

Object Owner ID

Blank

Library Name (list includes possible libraries)

COPD910
COPY910

CODV910

COPS910

Library List Name

RDB name of the IBM i
Note: To find the IBM i RDB name, use the WRKRDBDIRE command.

DLL Name

Blank

Database Name (list includes possible databases)

Versions - PD910
Versions - PY910

Versions - DV910

Versions - PS910

Server Name

Name of the machine where your database resides

Platform

IBM i

Use Table Owner

Blank

Use Julian Dates

Selected

Use Decimal Shift

Selected

Support for Updates

Selected

OCM Data Source

Blank

IBM i BLOB Support

Blank

LOB Data Source

Selected

21 Major Technical Tables

This chapter lists the major technical tables in the Release 9.1 data sources. This chapter does not list any Release 9.1 application tables. All technical media storage objects (GTxxx) are listed at the end of this chart. Many tables exist in multiple data sources. Some tables exist in data sources not noted here.

Note:
The Local - pathcode data source refers only to local databases that are path code specific. In the chart below, Local - pathcode could represent more than one data source, depending on the number of path codes you use. Pathcode is one or more of the following path codes:

- PY910

- DV910

- PS910

- PD910

- DEP910

Note:
The Local data source refers only to the local database on the Deployment Server, which is used by the planner environment.

* Specific tables in the list below reflect language information, and contain a language preference code that is translated by JD Edwards EnterpriseOne.

Table

Data Source

Description

Purpose

F0004D*

Control Tables

UDC - Alternate Language

Contains the User Defined Code (UDC) key, language key, and text for headers in the F0004 table. Provides UDC type descriptions for alternate languages.

F0005D*

Control Tables

UDC - Alternate Language

Contains UDC key, language key, and text for detail in the F0005 table. Provides UDC value descriptions for alternate languages.

F00165*

Business Data - Data Dictionary - 910Object Librarian - 910 Business Data Local Data Dictionary Local Object Librarian Local

Media Objects storage

Stores text OLE references and image references. Stores glossary text and media objects for all languages.

F0092

System - 910
Planner - 910

System Local

Library List - User

Contains one record per user with initial menu, initial program, and whether to enable fast path.

F00921*

System - 910
Planner - 910

System Local

User Display Preferences

Contains one record per user with date format, date separator, DW prefix, and language preference.

F00922

System - 910
Planner - 910

System Local

User Display Preferences Tagfile

Contains one record per user with workstation configuration name. This table is used with the F00050 table.

F00924

System - 910
Planner - 910

System Local

User Install Packages

Contains one record per user for each authorized package.

F0093

System - 910
Planner - 910

System Local

Library List Control

Contains a list, by user, of authorized environments.

F0094

System - 910
Planner - 910

System Local

Library List Master file

Contains master file information for an environment.

F00941

System - 910
Planner - 910

System Local

Environment Detail - EO

Contains one record per environment, with release and path code.

F00942

System - 910
Planner - 910

System Local

Object Path Master file

Contains one record per path code with the data source for the specification files and the server path for the other development objects (.DLL, source, headers).

F00945

System - 910
Planner - 910

System Local

Release Master

Contains one record per release, with the data source for system tables and the environments server path.

F00946

System - 910
Planner - 910

System Local

Release Compatibility Map

Contains information used to map major release levels to determine forward and backward compatibility.

F00948

System - 910
Planner - 910

System Local

Release Data Source Map

Contains information used to map a specific type of data source to a release level, such as Object Librarian, data dictionary, or versions list data sources.

F00950

System - 910
System Local

Security Workbench table

Stores security attributes (one record for each user or group).

F00960

System - 910
System Local

Machine/Group Identification

Stores a list of all workstations that installed Release 8.9 to scheduled packages.

F83100*

System - 910
System Local

Data Title

Series of definitions of data titles. Each row is the definition or specification of the date title. Provides soft coded RDA text.

F83110*

System - 910
System Local

Column Headings

Gives each period number an associated description. Provides soft coded RDA text.

F9100

Control Table

Task Master

Lists Release 8.9 tasks (Solution Explorer only).

F9101

Control Table

Task Relationships

Groups tasks listed in the F9100 table in logical (parent/child) tree order (ActivEra only).

F9102

Control Table

Task Descriptions

Provides descriptions of tasks listed in the F9100 table (ActivEra only).

F9105

Control Table

Variant Description

Describes the attributes of variants listed in this table. A variant performs a series of designated tasks (nodes) within a tree order defined in the F9101 table (ActivEra only).

F9105D

Control Table

Alternate Variant Descriptions

Provides translated text for descriptions listed in the F9105 table (ActivEra only).

F9106

Control Table

Variant Detail

Defines which nodes (tasks) are run within a variant and the names of any tasks dynamically renamed within a variant (ActivEra only).

F9106D

Control Table

Alternate Variant Detail Descriptions

Provides translated text for descriptions listed in the F9106 table (ActivEra only).

F9010

Control Table

Environment Setup Answers

F9020

Control Table

ActivEra Qualifier Rules Header

Defines rule names used by ActivEra. Rules are applied to conditionally execute an individual task or task relationship (tree order).

F9022

Control Table

ActivEra Qualifier Rules Detail

Lists conditional statements within rules listed in the F9020 table (ActivEra only).

F9030

Control Table

Documentation Cross-reference

Stores indexes of HTML documents associated with specific tasks (ActivEra only).

F9050

Control Table

Rough-cut Answer Dependency

Defines the hierarchical means of eliminating system codes and subsequent applications which do not apply within a specified system configuration (ActivEra only).

F91100

System - 910

Favorites - Relationship Properties

Categorizes business views on a parent/child format.

F91100D*

System - 910

Favorites - All Descriptions

Stores alternate descriptions for different languages.

F91300

System - 910

Scheduled Job Master

F91310

System - 910

Scheduled Job Parameters

F91320

System - 910

Job Schedule

F91330

System - 910

Scheduled Job Override Printer Info

F91400

System - 910

Report Director Templates

Contains the design templates for reports that users can create.

F91410

System - 910

Report Director Templates Sequence Items

Helps users manipulate data sequencing.

F91420

System - 910

Report Director Template Smart Field Activation

Creates a list showing all data items belonging to a smart field template.

F91430

System - 910

Smart Field Template Criteria

Stores a subset of selection criteria.

F91500

System - 910

Application Header for Tip of the Day

Contains application names or tools names where tips reside.

F91510

System - 910

Tip Details for Tip of the Day

Stores tip texts and a key to modify the sequence.

F9200

Data Dictionary
Data Dictionary Local

Data Item Master

Contains the relational breakdown of data dictionary.

F9202*

Data Dictionary
Data Dictionary Local

Data Field Display Text

Contains display text for each data field for language, data item, and product code reporting. Used when data items descriptions requested. Data dictionary row and column text for all languages* *
The language preference code for data dictionary applies to text only. Text includes row and column headings, a compressed description, and glossaries.

F9203*

Data Dictionary
Data Dictionary Local

Data Item Alpha Descriptions

Contains alpha descriptions and compressed descriptions of data items. Used when data items descriptions requested. Similar to the F9202 table. Contains data dictionary alpha descriptions for all languages.

F9207

Data Dictionary
Data Dictionary Local

DD Error Message Information

Contains one record per error message.

F9210

Data Dictionary
Data Dictionary Local

Data Field Specifications

Contains detailed information (specifications) for each data item. This table is accessed whenever a data item needs to be identified.

F9211

Data Dictionary
Data Dictionary Local

Data Dictionary - Smart Fields

Contains information for Smart Fields.

F9212

Data Dictionary - 910 Data Dictionary Local

Smart Field Criteria - Setup Rules

F96021

System - 910

Software Package Build Header

Stores the detail information from the definition process of package build.

F9603

System - 910

Software Package Build Header

Stores information from the assembly process of package build.

F96210

System - 910
System Local

Package Build Validation Tables

F96211

System - 910
System Local

Package Build Validation Detail

F96215

System - 910
Planner - 910

System Local

Software Package Build Header History

Contains the history record of the F96021 record. It stores statuses of the package each time it is built.

F9622

System - 910
Planner - 910

System Local

Software Package Build Detail

Stores the option information from the definition process of package build. Each record is either the name of the specification file, the name of a .DLL file, the name of the compression directory, or the name of an object.

F96225

System - 910
Planner - 910

System Local

Software Package Build Detail History

Contains the history record of the software build program (P9622). Stores the status of the build on the operation of that record when the package is finished.

F9631

System - 910
Planner - 910

System Local

Software Package Detail

Stores the detail information for the assembly process of package build. Stores the object names, foundation name, data name, or helps name.

F9650

System - 910
Planner - 910

System Local

Machine Master

Holds the default information regarding all machines used by JD Edwards EnterpriseOne.

F9651

System - 910
Planner - 910

System Local

Machine Detail

Holds specific information about each machine defined in the machine master table by record type.

F9652

System - 910
Planner - 910

System Local

Deployment Group Header

Specifies groups that can be used by the Release 9.1 administrator for deploying packages.

F9653

System - 910
Planner - 910

System Local

Deployment Group Detail Definitions

Stores the users that belong to one or more groups that were defined in the deployment header file. In addition, groups of groups can be defined here.

F9654

System - 910
Planner - 910

System Local

Deployment Location Definitions

Enables definition of one or more locations for deployment. This table is used primarily in multitier deployment.

F9660

System - 910
Planner - 910

System Local

Task Breaks

F96600

System - 910
Planner - 910

System Local

Deployment Features

F96601

System - 910
Planner - 910

System Local

Deployment Registry

F96602

System - 910
Planner - 910

System Local

Deployment Shortcut

F96603

System - 910
Planner - 910

System Local

Deployment Execute

F96604

System - 910
Planner - 910

System Local

Deployment Third Party

F96605

System - 910
Planner - 910

System Local

Deployment Initialization

F96605T

System - 910
Planner - 910

System Local

Deployment Initialization

F96606

System - 910
Planner - 910

System Local

Deployment File Set

F966071

System - 910
Planner - 910

System Local

Deployment ODBC Data Source

F966072

System - 910
Planner - 910

System Local

Deployment ODBC Data Source Attributes

F9670

System - 910
Planner - 910

System Local

Software Update Master Table

F9671

System - 910
Planner - 910

System Local

Software Update Detail Table

F96710

System - 910
Planner - 910

System Local

Impact Analysis Results

F9672

System - 910
Planner - 910

System Local

Software Update Pathcode Information

F96761

System - 910
Planner - 910

System Local

Software Update Object Detail

F967611

System - 910
Planner - 910

System Local

Software Update Language Table

F9691100

System Local

Change Table - Favorites

Stores adds, changes, and deletes to favorites tables between releases.

F9691400

System Local

Change Table - Report Director Template Header

Stores adds/changes/deletes to the Report Director template header table between releases.

F9691410

System Local

Change Table - Report Director Template Sequence

Stores adds/changes/deletes to the Report Director Template Sequence table between releases.

F9691420

System Local

Change Table - Smart Field Activity

Stores adds/changes/deletes to the Smart Field Activity table between releases.

F9691430

System Local

Change Table - Smart Field Criteria

Stores adds/changes/deletes to the Smart Field Criteria table between releases.

F9746

System Local

UDC Merge table

Contains the UDC records changed or added from release to release. This table is used by the UDC merge program (R98741).

F960004

Control Tables - xxx Control Tables Local

UDC Type

F960005

Control Tables - xxx Control Tables Local

UDC Codes

F9755

Data Dictionary - 910 Data Dictionary Local

Data Item Master Changes by Release

Contains the data dictionary items changed or added from release to release. This table is used by the Data Dictionary merge program (R989200P).

F9757

Data Dictionary - 910 Data Dictionary Local

Data Item Alpha Description Changes by Release

Lists changes made to alpha descriptions of data items (F9203) between releases. This table is used in the data dictionary merge process.

F9759

Data Dictionary - 910 Data Dictionary Local

Error Message Pgm Call Changes By Release

Lists changes made to error messages (F9207) between releases. This table is used in the data dictionary merge process.

F9760

Data Dictionary - 910 Data Dictionary Local

Data Field Specification Changes By Release

Lists changes made to field specifications (F9210) between releases. This table is used in the data dictionary merges.

F980011

Central Objects - xxx Versions Local

Cross ' Reference Relationships

Lists cross-reference relationships for business views, event rules, and controls.

F980021

Central Objects - xxx Versions Local

Cross ' Reference Field Relationships

Lists cross-reference relationships for fields in an application.

F98101

System - 910
System Local

Imaging Constants

Determines whether you are doing third-party imaging.

F983051

Versions - xxx Versions Local

Versions List

Contains one record per version (batch or interactive). For interactive, it stores processing option values. For batch, this table holds data selection, sequencing, and other template overrides.

F982xx

System - 910
System Local

Planner - 910

Series (OMW)

F98306*

Central Objects - xxx Versions Local

Processing Option Text

Provides processing option text for all languages.

F9840

Version - 910
Planner - 910

Installation Plan Master table

Contains general information for the installation plan with one record per plan name (description and status).

F98401

Version - 910
Planner - 910

Data Source Plan Detail table

Lists data sources for each plan, and one record per plan record per data source associated with that plan.

F98402

Version - 910
Planner - 910

Host Plan Detail table

Lists the Enterprise Server and hosts for each plan (one record per plan, per server).

F984021

Version - 910
Planner - 910

Location Plan Detail table

Contains the last location for a plan.

F984022

Version - 910
Planner - 910

Replication Plan Detail table

Stores replicated plan for remote locations, publisher, and subscriber tables.

F98403

Version - 910
Planner - 910

Environment Plan Detail table

Lists environments for each plan. Holds flags for production data, demo data, and table conversions for an upgrade.

F984031*

Version - 910
Planner - 910

Language and Environment Plan Detail table

Lists language and the selected environments for each plan.

F98404

Version - 910
Planner - 910

Package Plan Detail table

Lists packages and package definitions for each environment.

F98405

Version - 910
Planner - 910

Table Conversion Scheduler

Lists table conversion information merged in Table Conversion Scheduler from Environment Planner and Table Conversion Planner. This table is similar to the F9843 table.

F984052

Version - 910
Planner - 910

Table Conversion - History Log

Stores the logs for table conversions, control table merges, and specification merges.

F9843

System - 910

Table Conversion - JDE Scheduler

Contains table conversions, control table merges, and specification merges for upgrades, updates, and coexistent installations.

F9843T

System - 910

F98511

System - 910
Planner - 910

REP Data Sources by Environment

Lists default data sources by environment. This table is used during installation.

F9860

Object Librarian
Object Librarian Local

Object Librarian Master table

Contains one record per object with description and object type.

F9861

Object Librarian
Object Librarian Local

Object Librarian - Status Detail

Contains one record per object, per location, per path code. Each object has a server location plus locations for each person who checks it out to his machine.

F986101

System - 910
Server Map

Planner - 910

System Local

Object Configuration Master

Contains all data sources for tables, batch applications, and business functions that run on the server. The only data sources not controlled through this file are the system data source in Release Master and the Development data source in object path master.

F98611

System - 910
Server Map

Planner - 910

System Local

Data Source Master

Holds data source definitions. One record per data source with type, database, machine name, and foundation .DLL.

F986110

System - 910
Server Map

Planner - 910

System Local

Contains one record for each job on the server with status information.

F986111

System - 910
Server Map

Planner - 910

System Local

Job Number Master

Contains the next numbers table for server jobs.

F986113

System - 910
Server Map

Planner - 910

System Local

Subsystem Job Master

Contains server job records, including status, location, and version.

F986115

System - 910
Server Map

Planner - 910

System Local

Table and Data Source Sizing table

Holds storage, sizing, and location parameters for Oracle, with some general information for all data sources.

F986116

System - 910
Server Map

Planner - 910

System Local

MVS table and Data Source Sizing

Holds storage, sizing, and location parameters for MVS. Similar to the F986115 table.

F98613

System - 910
Server Map

Planner - 910

System Local

Business View Environmental Server

Lists cached tables.

F986150

System - 910
System Local

Server Transfer Package Contents

Lists objects belonging to each server package. This table is used by the server package installation process (P986150).

F986151

System - 910
System Local

Server Package Transfer

Lists the servers and path codes to which a given server package will be transferred. This table is used by the server package install process (P986150).

F986152

System - 910
System Local

Server Package Master

Contains the master list of all service packages. This table is used by the server package install process (P986150).

F98616

System - 910
System Local

Printer

Lists the printer definitions, including logical name, physical name, and conversion program, one record per printer.

F986161

System - 910
System Local

Default Printer table

Lists default printer settings by user and environment.

F986162

System - 910
System Local

Paper Definition

Lists paper sizes defined for each printer, one record per printer.

F986163

System - 910
System Local

Printer Capability

Lists printer capabilities (paper orientation and size, type and location of printer) for each printer, one record per printer.

F986164

System - 910
System Local

Output Conversions

Lists printer output conversions defined for each printer, one record per printer.

F986165

System Shared

New Default Printer Table

Stores the default printer information including the user, environment, host name, printer name, and the status.

F986167

System - 910
System Local

Printer Security

Reserved for future use.

F9862

Object Librarian
Object Librarian Local

Object Librarian - Function Detail

Lists one record for each function contained in the source file.

F9863

Object Librarian
Object Librarian Local

Object Librarian - Object Relationships

Contains one record per business function per related object. This table is used when building business functions.

F9865

Object Librarian
Object Librarian Local

Form Information

Contains one record per interactive form, including online help information.

F98710

Central Objects Specifications

Table Header

Holds table-specific information for tables created in TDA (BOBSPEC).

F98711

Central Objects Specifications

Table Columns

Holds all column information for the table in TDA (DDCLMN).

F98712

Central Objects Specifications

Primary Index Header

TDA - Information pertaining to the primary index.

F98713

Central Objects Specifications

Primary Index Detail

TDA - All fields that make up the primary index.

F98720

Central Objects Specifications

Business View Specifications

Holds all business-view specific information from BDA.

F98740

Central Objects Specifications

Event Rules - Link

Stores header file for event rules.

F98741

Central Objects Specifications

Event Rules - Specification

Contains actual event rules detail for a form.

F98743

Central Objects Specifications

Data Structure Templates

Contains one record for each template, for example, Data Structure for Business Function.

F98744

Central Objects Specifications

Media Object

Contains media object text for tools.

F98745

Central Objects Specifications

Smart Field Named Mappings

Contains smart field named mappings.

F98750*

Central Objects Specifications

FDA Text Information

Contains form design text for all languages for any generated application.

F98751

Central Objects Specifications

FDA Specification Information

Contains specifications for an application.

F98752

Central Objects Specifications

FDA/SVR Header Information

Contains summary information about each application.

F98753

Central Objects Specifications

FDA/SVR Detail Information

Contains summary information about each form for each application.

F98760*

Central Objects Specifications

RDA Text Information

Holds records that contain the report design aid text for all languages.

F98761

Central Objects Specifications

RDA Specification Info

Holds records that contain report design aid setup information.

F98762

Central Objects Specifications

JDEBLC - Behavior Information

Contains business function specifications.

F9882

System - 910
Planner - 910

System Local

Checkout Log table

Logs all transactions that take place to objects.

F98825

System - 910

Package Deployment Scheduling

Contains information for deploying client packages, such as group user ID and package assignment.

F9883

System - 910

Release 9.1 Network Locations table

Contains information for deploying server packages, such as package assignments.

F9885

System - 910
System Local

Install Package Header

Contains one record per package.

F9886

System - 910
System Local

Install Package Detail

Contains one record per package per product code or object to be included in the package.

F9887

System - 910
System Local

Install Package Build History

Lists each time the package is built.

F9888

System - 910
Planner - 910

System Local

Merge Log

Contains temporary message logging for merges.

F98800D*

Control Tables

Process Master - Alternative Description

Contains multiple language information for the F98800 table.

F98800T

Control Tables

Process Master Supplemental Information

Categorizes Composer processes.

F98810D*

Control Tables

Activity Master - Alternative Description

Contains multiple language information for the F98810 table.

F98810

Control Tables

Activity Master

Contains workflow activity information.

F98811

Control Tables

Activity Specifications

Contains workflow activity specifications stored as event rules.

F98830

Control Tables

Process Activity Associations

Contains workflow activity relationships.

F98840

Control Tables

Organizational Structure Master

Contains the defining data for organizational models.

F98845

Control Tables

Organizational Structure Rule

Contains the data that ties workflows to organizational models.

F98860

Control Tables

Process Instance

Contains the instances of workflow processes.

F98865

Control Tables

Activity Instance

Contains the instances of workflow activities within processes.

F98881

System - 910
System - Local

Specification Merge Logging

Contains logging information generated from the Specification Merge for upgrade, update, and the Specification Merge and Object Librarian Merge reports.

F9889

System - 910
System - Local

Deployment Location Master

Lists records for each tier with system and help information. This table is used only for multitier deployment.

F98891

System - 910
System - Local

Deployment Location Path Code

Lists records with packages and help information. This table is used only for multitier deployment.

F98892

System - 910
System - Local

Package Deployment Scheduling

Lists scheduling information for a multitier environment.

F98950

Central Objects Specifications
System - Local

User Overrides table

Contains application version information: application, version, and user who entered it.

F98980

System - 910
System - Local

Font Override by Language

Lists languages with information on corresponding display fonts.

F98BLOB

System - 910

DB2 BLOB Support

F98CONST

System - 910
System - Local

Table of Constants

Lists constants for report design aid and form design aid.

F98DRENV

System - 910
System - Planner

Data Replication Environment Mapping table

Determines which path codes to update for data dictionary replication.

F98DRLOG

System - 910
Server Map

System - Planner

Data Replication Change Log

Contains one record for each replicated change. The table information is stored as a BLOB.

F98DRPCN

System - 910
Server Map

System - Planner

Data Replication Pending Change Notifications

Contains one record for each replicated change for each subscriber. Records are deleted as subscribers are notified.

F98DRPUB

System - 910
System - Planner

Data Replication Publisher

Lists definitions of published objects.

F98DRSUB

System - 910
System - Planner

Data Replication Subscribers

Defines each subscriber.

F98EVDTL

System - 910
System - Local

Event Detail file

Filters events displayed in Form Design Aid (FDA) or Universal Batch Engine (UBE) design.

F98EVHDR

System - 910
System - Local

Event Header file

Stores event description and event ID. This table is used for all event rules.

F98MOQUE

System - 910
System - Local

Media Object Queues

Contains path codes to locations of multimedia objects.

F98OWSEC

System - 910
System - Local

Release 9.1 Security

Contains the security tables that store the Release 9.1 user name and password for obtaining database user and password for certain data sources.

F98TMPL

System - 910
System - Local

Templates

F98VAR

System - 910
System - Local

Table of Variables

Contains commonly used event rule variables.

GT92002

Data Dictionary

Data Dictionary - Glossary Information

Contains column in data dictionary with descriptions of data dictionary items.

GT9860A

Object Librarian

Object Librarian Generic Text Structure

Contains notes for objects in the Object Librarian.

GT9862A

Object Librarian

Business Function Notes

Contains notes for business functions.

GT98DSA

Object Librarian

Data Structure Notes - Structure and Item

Contains notes for data structures.

GT98DSB

Object Librarian

Data Structure Notes - Structure and Item

Contains notes for data structures.

GT98TMPL

Object Librarian

Media Object Templates

Contains templates that can be used for any attachment.

22 Working with Reports

During the installation, upgrade, and cumulative update processes, JD Edwards EnterpriseOne creates reports that show detailed information about the plan and summarize the status of the environment builds. During upgrades and cumulative updates, additional reports summarize the status of tables merges.

This chapter discusses:

- Section 22.1, "Installation Planner Validation Report (R9840B)"
This report is for installation, upgrade, and cumulative update customers.

- Section 22.2, "Environment Database Creation Report (R98403)"
This report is for installation, upgrade and cumulative update customers.

- Section 22.3, "Index Recreation (R9698713)"
This report is for installation, upgrade and cumulative update customers.

- Section 22.4, "Pathcode Copy (R9800942)"
This report is for installation, upgrade and cumulative update customers.

22.1 Installation Planner Validation Report (R9840B)

Note:
This report is used by installation, upgrade, and cumulative update customers.

All processes use version XJDE0001 of this report.

The Installation Planner Validation report summarizes the status of the installation plan and verifies that the plan information is correct before you run the Installation Workbench

22.1.1 Setting Processing Options

The Extra Info tab contains these options:

Option

Value

Additional data source information flag

Enter Y to include additional information.

OCM Information Flag

Enter Y to see all Object Configuration Manager (OCM) information for the current data selection.
Enter D to select all default records.

Enter N to prevent OCM records from being displayed.

OCM Differences Flag

Enter Y to see OCM differences between the new environment and the previous environment.

Path Code Information Flag

Enter Y to display all path code information for the plan(s) in the data selection

Update the Plan Status (10 – 60)

Enter 30

22.1.2 How to Read the Report

Use the Installation Planner Validation report summary section to review basic information about the installation, upgrade, or cumulative update; the number of records validated; and the types of processes run.

Review the main body of the report to verify that each data source, machine, and package build in the plan was created successfully. To verify, each detail line should have the value Record Validated in the far right column.

The report includes the status of the following record types:

- Location

- Data sources (listed by database type)

- Environments

- Path codes

- Object Configuration Manager (OCM)

- Machines

- Table conversions

- Control table merges

- Specification table merges

- Packages

A summary should appear at the end of the report verifying that all records were validated and the plan status was updated to 30.

22.2 Environment Database Creation Report (R98403)

Release 9.1 creates an Environment Database Creation report for each environment that is part of your plan. For each environment, you can choose to load either production or demonstration data.

Users performing installations and upgrades should run version XJDE0001.

Users performing cumulative updates should run version XJDE0004.

Upgrade users should run XJDE0005 because the update process updates only generic text. When running against pristine data, these users should run version XJDE0024.

The environment database creation copies the System data source (previous release) to the System - 910 data source. The System data source is release specific. The report is read and errors are processed in the same way as they are for the regular Environment Database Creation.

22.2.1 Setting Processing Options

These processing options are the typical processing options for each version of the Environment Database Creation report.

22.2.1.1 Version XJDE0001 for Installations and Upgrades

The Environment Tab contains these options:

Option

Values

Enter the Environment for the database to be created.

Leave this field blank.

Enter the Data Source for the database to be created.

Leave this field blank.

Enter a 1 to load Production Data or a 2 to load Demonstration Data.

Enter 2. The default is 1.
If this report is called from another process, the system passes in this flag.

Enter the source Data Source for Loading of Data.

Enter OneWorld Local.
If this report is called from another process, the system passes in this flag.

Enter the Source Environment for the database to be copied from.

Leave this field blank.
If this report is called from another process, the system passes in this flag.

The Update Tab contains the following options:

Option

Value

Enter a 1 for Proof Mode or a 2 to create the Environment Database.

Enter 2.
The default is Proof Mode.

Enter a A to recreate existing tables in data sources that allow automatic table creation.

Leave this field blank.
The default is not to recreate tables.

Enter a 1 to only copy tables that exist in the source data source.

Leave this field blank.

Enter a Y to add records without clearing the target table.

Leave this field blank.
This is used for language tables. The default is to clear the target table.

The Print Tab contains these options:

Option

Value

Enter a 1 to only print exceptions.

Leave this field blank.
The default is to print all lines.

The Licensing Tab contains these options:

Option

Value

Enter a Y to create all tables or a N to create licensed tables only.

Leave this field blank.
The default is to create all tables.

Enter a Y to print all tables in the report or an N to print licensed tables only.

Leave this field blank.
The default is to print all tables.

22.2.1.2 Version XJDE0004 for Updates

The Environment Tab contains these options:

Option

Value

Enter the Environment for the database to be created.

Leave this field blank.

Enter the Data Source for the database to be created.

Leave this field blank.

Enter a 1 to load Production Data or a 2 to load Demonstration Data

Enter 1.
The default is to load production data. If this report is called from another process, the system passes in this flag.

Enter the source Data Source for Loading of Data.

Leave this field blank.
If this report is called from another process, the system passes in the data source.

Enter the Source Environment for the database to be copied from.

Leave this field blank.
If this report is called from another process, the system passed in the Source Environment.

The Update Tab contains these options:

Option

Value

Enter a 1 for Proof Mode or a 2 to create the Environment Database.

Enter 2.
The default is Proof Mode.

Enter a A to recreate existing tables in data sources that allow automatic table creation

Leave this field blank.
The default is not to recreate tables.

Enter a 1 to only copy tables that exist in the source data source

Leave this field blank.
The default is to copy all tables.

Enter a Y to add records without clearing the target table.

Enter N.
to indicate you do not want to add records without clearing the target table.

This is used for language tables. The default is to clear the target table.

The Print Tab contains this option:

Option

Value

Enter a 1 to only print exceptions.

Leave this field blank.
The default is to print all lines.

The Licensing Tab contains these options:

Option

Value

Enter a Y to create all tables or an N to create licensed tables only.

Leave this field blank.
The default is to create all tables.

Enter a Y to print all tables in the report or an N to print licensed tables only.

Leave this field blank.
The default is to print all tables.

22.2.1.3 Version XJDE0024 for Running Pristine Data

The Environment Tab contains these options:

Option

Value

Enter the Environment for the database to be created.

Leave this field blank.

Enter the Data Source for the database to be created.

Leave this field blank.

Enter a 1 to load Production Data or a 2 to load Demonstration Data.

Enter 2.
The default is to load production data. If this report is called from another process, the system passes in this flag.

Enter the source Data Source for Loading of Data.

Enter OneWorld Local.
If this report is called from another process, the system passes in the data source.

Enter the Source Environment for the database to be copied from.

Leave this field blank.
If this report is called from another process, the system passes in the Source Environment .

The Update Tab contains these options:

Option

Value

Enter a 1 for Proof Mode or a 2 to create the Environment Database.

Enter 2.
The default is Proof Mode.

Enter a A to recreate existing tables in data sources that allow automatic table creation.

Enter A.
The default is not to recreate tables.

Enter a 1 to only copy tables that exist in the source data source.

Leave this field blank.
The default is to copy all tables.

Enter a Y to add records without clearing the target table.

Leave this field blank.
This is used for language tables. The default is to clear the target table.

The Print Tab contains these options:

Option

Value

Enter a 1 to only print exceptions.

Leave this field blank.
The default is to print all lines.

The Licensing Tab contains the following options:

Option

Value

Enter a Y to create all tables or a N to create licensed tables only.

Leave this field blank.
The default is to create all tables.

Enter a Y to print all tables in the report or a N to print licensed tables only.

Leave this field blank.
The default is to print all tables.

22.2.1.4 How to Read the Report

Review the reports to make sure the environments were created and configured successfully. The report includes a status for each table:

- Tables that have been created correctly have a status of Success.

- Tables that had errors have a status of Failure.

- Tables can have a status of No Action.

The Environment Database Creation report does not have a cover page. The reports list the following properties of each table (object) created:

Object headings

Description

Syst Code

System Code. Shows the JD Edwards EnterpriseOne product code for the database listed in the Member Description column.

Object Name

Displays the alphanumeric name of the database.

Member Description

Displays the full name of the database being created.

Data Source

Displays the data source toward which this member points.

Crt Tbl

Create Table. Shows whether tables are being created for this database.

Copy Data

Shows whether the table was copied with data.

Rec Insrt

Record Insert. Displays the number of records inserted.

Rec Fail

Record Failure. Displays the number of records that failed.

Copied from Data Source

Displays whether the table was copied with data and the data source from which it was copied.

Status

Displays one of the following statuses for the table creation: Success, Failure, or No Action.

Source DS Warnings

Displays any errors or warnings associated with the source data source.

Target DS Warnings

Displays any errors or warnings associated with the target data source.

22.2.1.5 Errors and How to Resolve Them

A report occasionally lists a status of Failure for tables that are created successfully. These failures are generally due to problems creating indices and are not critical for the successful installation of the software.

During an upgrade or cumulative update, you could receive failures for some tables. To confirm successful table creation, verify that the following tables were created successfully:

- F0007Z1

- F00092

- F0086

- F03B11

- F03B14

- F03B112

- F060116

- F06106

- F08042

- F08330

- F0911

- F1501B

- F1721

- F1731

- F17111

- F30006Z1

- F3002Z1

- F3003Z1

- F3460Z1

- F39062

- F4077

- F4106

- F4111

- F41508

- F4600

- F4812H

- F5215

- F7302

- F986113

Reports frequently list a status of No Action for tables the system created successfully. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. These warnings are normal and you can ignore them. The most common reasons for the warnings are because the source and target data sources are the same or the table was created by a previously installed environment.

When the source and target are the same, the report lists the following warnings:

Source data source warning

Target data source warning

Source Same as Target

Existing table

This commonly occurs when the "copied from" data source is the same as the "target" data source (where the table is mapped), and often occurs for the following tables:

UDC tables

Menu tables

F0004 and F0005

F0082, F00821, F0083, and F0084

If you load multiple environments that share the same mappings (for example, DV910 and TS910), the first environment loaded (DV910 in this case) lists the tables with a Success status. The second environment (TS910) lists any tables already created during the first environment load with a status of No Action and a target data source warning of Existing Table.

The No Action status and Existing Table warning for the second (TS910) environment are normal. You can verify that any table with a target data source warning of Existing Table has been created successfully by verifying it was created while loading a previous environment.

22.3 Index Recreation (R9698713)

The R9698713 program is run from Batch Versions after an install or upgrade. It compares database indexes versus Release 9.1 index specifications in F98712 and F98713. If you run the program in Update mode, it recreates incorrect indexes.

22.4 Pathcode Copy (R9800942)

Environment Workbench runs the R9800942 program for each custom environment whose path code is to be copied from an existing path code. It copies the directory structure of the existing path code on the Deployment Server. It also copies package.inf and records in the package definition tables F9603, F9631, F96021 and F96215, replacing the path code names in those items.

23 Deinstalling the Software

This chapter includes these tasks:

- Section 23.1, "Understanding the Deinstallation"

- Section 23.2, "Deinstalling the Software from the Workstations"

- Section 23.3, "Deinstalling the Local OEE from the Deployment Server"

- Section 23.4, "Manual Cleanup of a Deinstalled Oracle Database on the Deployment Server"

- Section 23.5, "Using the OUI Installer to Deinstall JD Edwards EnterpriseOne from the Deployment Server"

- Section 23.6, "Dropping DB2\400 Libraries"

- Section 23.7, "Deinstalling the Platform Pack"

23.1 Understanding the Deinstallation

The installation and upgrade processes do not automatically remove any JD Edwards EnterpriseOne databases. You should have a database administrator (DBA) for your relational database management system (RDMS) manually remove any unused databases according to the list of databases and associated components, which are provided in this document.

The deinstallation program restricts you from deinstalling 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

ES Development

ES Pristine

23.2 Deinstalling the Software from the Workstations

You can remove previous JD Edwards EnterpriseOne installations from workstations by running the deinstallation program as described in the JD Edwards EnterpriseOne Development Client Installation Guide.

23.3 Deinstalling the Local OEE from the Deployment Server

Note:
Oracle products use the term "deinstall" to refer to removing an Oracle product.

To deinstall the local Oracle database:

1. Either export the local database tablespaces or deinstall JD Edwards EnterpriseOne using Start > Programs > Oracle - <Home_Name> > Oracle Installation Products > Universal Installer where <Home_Name> is the name that you gave the installation of EnterpriseOne on the Deployment Server.

2. Locate this file:
<Oracle_Home>\deinstall\deinstall.bat

3. Right click on the file that you located in Step 2 and select Run as administrator, where <Oracle_Home> is the directory where you installed the local Oracle database. For example, your directory might be:
c:\Oracle\E1Local

4. At the end of the deinstallation, verify that the Oracle_Home directory has been deleted (for example, c:\Oracle\E1local). If it still exists, you should attempt to manually delete it.

Caution:
Prior to any reinstall an Oracle local database on this same machine, the Oracle_Home directory (for example, c:\Oracle\E1local) must not exist. If you attempt to reinstall the local Oracle database and this directory still exists, it is likely that the new installation will fail.

Tip:
You may not be able to delete the Oracle_Home directory (for example, c:\Oracle\E1local) if a process has it locked. In that case, to determine which process(es) has it locked, run the steps in the section of this guide entitled: Section 3.11.5.4, "Process Explorer".

23.4 Manual Cleanup of a Deinstalled Oracle Database on the Deployment Server

If the deinstallation of the OEE database fails for some reason, you need to perform the manual steps in this procedure to completely remove the old installation before reinstalling the database.

1. Deinstall the Deployment Server.
Be sure the Deployment Server is deinstalled before attempting to deinstall the database. This should ensure that no EnterpriseOne tablespaces are imported (attached) to the EnterpriseOne database.

2. Delete the following registry keys:
\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_E1Local

\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_E1Local

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\(see Keys below)

Keys. Delete any keys with names that start with "Oracle" and contain "E1Local".

3. Delete this directory:
c:\Oracle\E1Local

If you cannot delete the E1Local subdirectory because a file in that directory is locked, follow these steps:

1. Determine which file is locked and which process has the lock on the file. A freeware program called Process Explorer can be helpful in determining this information. You can obtain a free copy of Process Explorer from this web site:
http://technet.microsoft.com/en-us/sysinternals

2. Either kill the locking process with Process Explorer or Microsoft Windows Task Manager or, if the process was started as a Microsoft Windows service, change the Startup Type to Manual and reboot the computer again.

3. Try again to delete the E1Local subdirectory.

4. Remove the 64-bit Oracle inventory entries.

1. With a text editor (such as Notepad), edit this file:
c:\Program Files\Oracle\inventory\ContentsXML\inventory.xml

2. Delete any lines that start with:
<HOME NAME="E1Local"

3. Save the file.

5. Remove the entry from the Windows PATH.

1. Navigate to Control Panel > System.

2. Click Advanced system settings on the left.

3. Click Environment Variables… near the bottom.

4. In the System variables box near the bottom, highlight Path and click the Edit… button.

5. In the Variable value field, delete this value:
c:\Oracle\E1Local\bin

Be sure to remove the semicolon as well.

6. Click OK.

6. Remove the ORACLE_HOME Windows environment variable.

1. Navigate to Control Panel > System.

2. Click Advanced system settings on the left.

3. Click Environment Variables… near the bottom.

4. In the System variables box near the bottom, highlight ORACLE_HOME and click Delete.

5. Click OK.

23.5 Using the OUI Installer to Deinstall JD Edwards EnterpriseOne from the Deployment Server

You can use the OUI installer to deinstall JD Edwards EnterpriseOne from the Deployment Server. To deinstall the local database, depending on your local database type, refer to the preceding sections of this guide entitled: Section 23.3, "Deinstalling the Local OEE from the Deployment Server".

To use the OUI installer to deinstall JD Edwards EnterpriseOne from the Deployment Server:

1. Log on to the Deployment Server as a user with Administrator rights.

Caution:
Ensure that the Administrator account name that you use does not contain any special characters.

2. If JD Edwards EnterpriseOne is running on the Deployment Server, stop it.
Use Task Manager to verify these processes are stopped:

- activConsole.exe

- jdenet_n.exe

- java.exe

If any of these processes are running, either wait for them to finish or kill them via Task Manager.

3. Go to Start > All Programs > Oracle - JDE_DEP910_Home > Oracle Installation Products > Universal Installer.

4. On Oracle Universal Installer: Welcome, select the Deinstall Products ... button.

5. On Inventory, with the Contents tab select, put a check mark next to the Oracle Homes for the Deployment Server Home.
For example, if you followed recommendation in this guide the Oracle Home for your Deployment Server is:

JDE_DEP910_HOME

6. Select the Remove button.

7. On Confirmation, verify that you want to deinstall the listed components and their dependent components and if so, select the Yes button.

The Remove dialog indicates the progress of the deinstall action.

8. When the deinstallation process completes, the Inventory is shown again. The products you selected for deinstallation should no longer be displayed in the inventory.

9. Select the Close button.

You are returned to the Oracle Universal Installer: Welcome screen.

10. On Oracle Universal Installer: Welcome, select the Cancel button to exit the Oracle Universal Installer.

23.6 Dropping DB2\400 Libraries

This section lists the DB2\400 libraries that must be manually dropped by a DBA. This is the list of libraries that were created by the JD Edwards EnterpriseOne 9.0 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation, or from a previous JD Edwards EnterpriseOne installation.

By design, these libraries are not automatically removed by the JD Edwards EnterpriseOne deinstallation program. You should have a DBA for your RDBMS manually remove any unused libraries listed in the table below.

JD Edwards EnterpriseOne Component

DB2\400 Library Name

Foundation

SY910
OL910

DD910

SVM910

OWJRNL

Production

COPD910
PRODDTA

PRODCTL

Pristine

COPS910
PS910DTA

PS910CTL

Development

CODV910
TESTDTA

TESTCTL

Prototype

COPY910
CRPDTA

CRPCTL

23.7 Deinstalling the Platform Pack

You should always use the JD Edwards EnterpriseOne OUI-based installation program to remove JD Edwards EnterpriseOne. If you manually remove the software, the deinstallation cannot be guaranteed to be complete and, as a result, subsequent reinstallation of JD Edwards EnterpriseOne may be hindered.

To run the JD Edwards EnterpriseOne Platform Pack Installer for the IBM i Enterprise Server:

1. Log on to the same Microsoft Windows machine where you initially ran the Platform Pack installer for IBM i. If you followed the recommendation, this will be the JD Edwards EnterpriseOne Deployment Server.

2. Locate the directory where you extracted the install images. If you followed the recommendation, the directory is:
c:\IBMPPack

3. In the extracted structure, locate the setup.exe file under the \install subdirectory, right-click on it, and select Run as Administrator.

4. On Oracle Universal Installer, Welcome, click the Deinstall Products… button.

5. Turn on the check box next to the Oracle Home for the Platform Pack and expand the node to show all installed components. For example, the Oracle Home might be named JDE_PPack910_Home.

Note:
At this step, you should select only the Oracle Home that is associated with this particular OUI. That is, the Oracle Home name that you select on this screen should match the Oracle Home name that you selected from Start > Programs.

6. Click the Remove… button.

7. On Confirmation, verify that you want to deinstall the listed components and their dependent components and if so, select the Yes button.

8. On User Input, you must enter the password for the account you used to run the install. For example, enter the password for QSECOFR. Then click on OK

9. Click the OK button.

The Remove dialog indicates the progress of the deinstall action.

10. When the deinstallation process complete, the Inventory is shown again. The products you selected for deinstallation should no longer be displayed in the inventory.

11. Select the Close button.

You are returned to the Oracle Universal Installer: Welcome screen.

12. On Oracle Universal Installer: Welcome, select the Cancel button to exit the Oracle Universal Installer.

13. Verify that the installation directory (Oracle Home) has been deleted. If it still exists, you can delete it.

A Understanding IBM i Databases

This appendix presents a diagram of the JD Edwards EnterpriseOne relationships with the IBM i databases.

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.