JD Edwards EnterpriseOne

Deployment Server Reference Guide for Enterprise Systems

Tools Release 9.1.x and Applications Release 9.0 or 9.1 for IBM i

E24430-09

June 2015

JD Edwards EnterpriseOne Deployment Server Reference Guide for Enterprise Systems, Tools Release 9.1.x and Applications Release 9.0 or 9.1 for IBM i

E24430-09

Copyright © 2011, 2015, 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 Introduction

- 1.1 Understanding This Guide

- 1.2 Understanding the Tools Release on the Deployment Server

- 1.3 Understanding Server Manager and This Guide

- 1.4 Accessing Minimum Technical Requirements

- 1.5 Microsoft Windows Security

- 1.6 Minimizing Locked Files

2 Installing a Tools Release on the Deployment Server

- 2.1 Backing Up Your Existing System

- 2.2 Downloading Tools Release 9.1 for the Development Client

- 2.3 Understanding Destination Paths

- 2.4 Installing a JD Edwards Tools Release on a Deployment Server Using the Oracle Universal Installer (OUI)

- 2.5 Tools Release Installer Logs

- 2.6 Using Tools Accelerator TL910001 to Create and Map New Tables

3 Setting Up a Development Client Installer on the Deployment Server

- 3.1 Understanding the JD Edwards Clients (Development and Web)

- 3.2 Understanding the Oracle Universal Installer

- 3.3 Creating the Web Development Feature

- 3.4 Creating an Installation Package

- 3.5 Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server

- 3.5.1 Copy the JDBC Drivers

- 3.5.2 Copy the tnsnames.ora file

- 3.6 Updating the Database Drivers in the JDBJ.ini File

- 3.7 Copying the JDK to the Deployment Server (OH4A Only)

- 3.8 Updating the InstallManager.htm File

- 3.9 Updating the oraparam.ini File

- 3.10 Setting Up Local Database Installers

- 3.10.1 Additional OEE Setup

- 3.10.2 SSE Setup

4 Working With the Client Full Package

- 4.1 Understanding the Client Full Package

- 4.2 Creating the Client Full Package

5 Working
With SnapShot on the Deployment Server

- 5.1 Understanding SnapShot

- 5.2 Prerequisites

- 5.3 Using Snapshot on the Deployment Server

- 5.3.1 Starting SnapShot

- 5.3.2 Saving a SnapShot

- 5.3.3 Restoring a SnapShot

- 5.3.4 Deleting a SnapShot

- 5.4 Manually Backing Up Files and Settings

- 5.5 Set Logging for SnapShot Using the Registry

- 5.6 Troubleshooting

- 5.6.1 Examining the Log File

- 5.6.2 Remedial Actions

- 5.6.2.1 Examples of Healthy Environments

- 5.6.2.2 Simple Fixes

- 5.6.2.2.1 Missing Version Information

- 5.6.2.2.2 Missing Saved Version

6 Rebuilding Business Functions for Vertex Header Files (for Vertex users only)

7 Building Application Business Functions

8 Re-Linking Business Functions

A Working With Multiple Tools Release Foundations

- A.1 Understanding Multiple Foundation Code on the Enterprise Server

- A.1.1 Working With Tools Releases on the Enterprise Server

- A.1.1.1 Creating an IFS Directory

- A.1.1.2 Editing the JDE.INI

- A.1.1.3 Deleting the Subsystem Entry

- A.1.1.4 Creating a Subsystem for the Service Pack

- A.1.1.5 Verifying that the Library List is Set Up Correctly

- A.1.1.6 Linking Business Functions to Service Packs

- A.1.2 Registering an Existing Enterprise Server with Server Manager

- A.1.3 Understanding PORTTEST

- A.1.3.1 Running the PORTTEST

- A.1.3.2 Starting the Services

- A.2 Understanding Multiple Foundation Code on the Deployment Server

- A.2.1 Installing Multiple Tools Releases on the Deployment Server

- A.2.2 Adding a New Machine Record for the New Tools Release

- A.2.3 Modifying the Existing Machine Record to Remove Environments

- A.3 Working with Packages for Multiple Foundations

- A.4 Working with the Development Client

- A.5 Editing the Development Client jde.ini File

- A.6 Setting up the Multiple jde.ini Files on the Deployment Server

B Manual Cleanup of a Deinstalled Oracle Database

C Data by Pathcode

- C.1 Datasource Name Generation

- C.2 Package Build Considerations

- C.3 Additional Spec Datasource Settings in the jdbj.ini

- C.4 Summary of Possible Administrator Changes

D Working
With SnapShot on the Deployment Server (Base Release of Tools Release 9.1)

- D.1 Understanding SnapShot

- D.2 Prerequisites

- D.3 Using Snapshot on the Deployment Server

- D.3.1 Starting SnapShot

- D.3.2 Saving a SnapShot

- D.3.3 Restoring a SnapShot

- D.3.4 Deleting a SnapShot

- D.4 Manually Backing Up Files and Settings

- D.5 Set Logging for SnapShot Using the Registry

Preface

Welcome to the Deployment Server Reference Guide. This guide is new for JD Edwards EnterpriseOne Tools Release 9.1. In prior releases, some of the content was contained in a now-deprecated guide entitled: JD Edwards EnterpriseOne Tools Release Reference Guide.

Note:
This guide has been updated for JD Edwards EnterpriseOne Tools Release 9.1 Update 2. For details on documentation updates, refer to the JD Edwards EnterpriseOne Tools Net Change Guide.

Audience

This guide is intended for system administrators and technical consultants who are responsible for installing 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, which is 876932.1, or by using this link:

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

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

This guide contains references to JD Edwards EnterpriseOne Enterprise Server and HTML Web Server (JAS) 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 Introduction

This chapter discusses:

- Section 1.1, "Understanding This Guide"

- Section 1.2, "Understanding the Tools Release on the Deployment Server"

- Section 1.3, "Understanding Server Manager and This Guide"

- Section 1.4, "Accessing Minimum Technical Requirements"

- Section 1.5, "Microsoft Windows Security"

- Section 1.6, "Minimizing Locked Files"

1.1 Understanding This Guide

This guide describes the JD Edwards EnterpriseOne Deployment Server with Tools Release 9.1 and Applications Release 9.0 or 9.1. This Deployment Server Reference Guide supersedes the guides from previous JD Edwards EnterpriseOne tools releases most recently known as the Tools Release Reference Guide, and before that the Tools Release Installation Guide. All information in this guide is relevant to actions unique to and performed on the Deployment Server. This includes setup of the Development Client, which is deployed from the Deployment Server.

1.2 Understanding the Tools Release on the Deployment Server

You must use the JD Edwards EnterpriseOne Tools Release installer to install any tools release on the Deployment Server. A new version of the installer is available for Tools Release 9.1; this installer is an Oracle Universal Installer (OUI). Tools release versions previous to 9.1 use a different installer as documented in the applicable Tools Release Reference Guide for each tools release.

Tools Release 9.1 may be installed on base Application Release levels 9.0 or 9.1 as well as applicable minor tools releases on those releases.

You should always check the Oracle Technology Network for revisions to this guide subsequent to the initial release, which coincides with the General Availability of JD Edwards EnterpriseOne Tools Release 9.1.

Note:
The JD Edwards Applications Release 9.1 is installed on the Deployment Server using a separate installer. Refer to "Chapter 3, Installing the Deployment Server," in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guides. To access the guides, refer to the Installation and Upgrade Documentation Library at this link:
http://docs.oracle.com/cd/E24902_01/nav/installation.htm

1.3 Understanding Server Manager and This Guide

Note:
Management of JD Edwards EnterpriseOne Tools Release 8.96 or earlier must be done using the tools provided with those releases. Server Manager cannot be used to manage any JD Edwards EnterpriseOne tools release prior to 8.97.

For more information, see the JD Edwards EnterpriseOne Server Manager Guide:

The JD Edwards EnterpriseOne Server Manager tool provides:

- Web Based System Management
You can securely access and manage your JD Edwards EnterpriseOne installation from anywhere using a standard web browser.

- Remote Deployment and Upgrades
You can install, uninstall, and update your JD Edwards EnterpriseOne servers regardless of their physical location or platform.

- Remote Operational Control
You can start and stop any of your JD Edwards EnterpriseOne servers, Oracle J2EE application servers, or supported third party J2EE application servers directly from the Management Console.

- Secure Administrative Tasks
Server Manager permits you to specify which existing JD Edwards EnterpriseOne users have access to the Management Console, control which JD Edwards EnterpriseOne servers the user may view, and specify which administrative tasks the user may perform on those servers.

- Configuration Management
Server Manager provides a web-based interface for managing the configuration of all managed servers. The application presents each configuration item along with integrated help describing the configuration setting.

Note:
Beginning with the availability of Server Manager, it is strongly advised that all changes to configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, etc.) for any JD Edwards EnterpriseOne server managed by Server Manager be accomplished using only the Management Console interface of Server Manager. In addition to providing usability improvements, using Server Manager reduces the risk of introducing configuration errors by providing dropdowns that contain only valid values where applicable. Further, the tool provides a useful Audit History for any modifications made to configurations using Server Manager.

- Configuration Comparison
You can use Server Manager to compare the configuration of two or more servers to identify configuration differences. You can compare configurations through the Management Console application regardless of the platform or location of the actual JD Edwards EnterpriseOne server. You can also compare individual servers with the default configuration of the corresponding server groups to which the servers belong.

- Audit History

Server Manager maintains a history of changes made to the managed servers. This includes a history of each configuration change, each server start and stop, and each tools release update, including the user that performed the change or operation. The Management Console application provides mechanisms to query and view the audit history that is maintained.

- Integrated EnterpriseOne Software Management
Use Server Manager to centrally maintain all your JD Edwards EnterpriseOne server tools releases, including the ability to copy the software to the remote server machines.

- Logical Server Grouping
Server Manager allows you to group servers with a similar purpose. These groups can include any of the server types such as Enterprise Server, HTML Web Server, and so on. A default, or template, configuration is maintained for each server group.

- Application Release Independence
Server Manager is delivered with every JD Edwards EnterpriseOne Tools Release 8.97 and greater and is compatible with any supported JD Edwards EnterpriseOne application release beginning with Application Release 8.9 through the currently supported release. No electronic software updates (ESUs) are required to support Server Manager.

- Self-Contained Installation
The installation of Server Manager delivers all components that are required by the Management Console application. There are no third party requirements regardless of your existing or intended middleware topology (for example, Oracle Application Server, WebSphere Application Server, or no application server).

- Tools Release Independence
Newer versions of the Server Manager application will continue to support the management of earlier tools releases back to the initial general availability release of JD Edwards EnterpriseOne Tools Release 8.97.

1.4 Accessing Minimum Technical Requirements

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Minimum Technical Requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

http://www.oracle.com/corporate/contracts/index.html

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

JD Edwards EnterpriseOne Current MTR Index [ID 747323.1]

Within the MTR index, search for the section entitled: Deployment Server and Server Manager.

Note:
Local Database. Applications Release 9.1 supports only the Oracle Enterprise Edition (OEE) as the local database. It does not support Microsoft SQL Server 2005 Express Edition (SSE); however, Applications Release 9.0 supports both OEE and SSE.

1.5 Microsoft Windows Security

When installing, uninstalling/deinstalling, or running any JD Edwards EnterpriseOne product on Microsoft Windows operating systems, be sure to follow the below guidelines. This includes saving or restoring or deleting snapshots of EnterpriseOne using the Snapshot program. Not following these guidelines may cause unexpected errors to occur.

1. Registry and directory permissions
Be sure that the user account into which you are signing into Microsoft Windows is in the Administrators group or a similar group that provides permissions to write to and read from registry hives (for example, HKEY_LOCAL_MACHINE\SOFTWARE) and disk subdirectories (c:\Windows) that are restricted from standard Windows users.

2. "Run as administrator"
If Microsoft's User Access Control (UAC) is turned on, right-click on a program's icon or shortcut and select "Run as administrator." If a shortcut is configured to automatically "Run as administrator," you do not need to right-click and select "Run as administrator."

Note:
Tools Release 9.1 Update 2. An exception to this rule is the Tools Release 9.1 Update 2 and higher releases of SnapShot.exe. These versions of SnapShot are designed to automatically attempt to start with the elevated permissions. If you are not signed into Microsoft Windows with an administrative account, you will be prompted to enter the credentials for an administrative account when SnapShot starts.

If a file that you need to edit and then save is located in a directory with access restricted by UAC, you will need to right-click on your text editor program's icon, select "Run as administrator," and open the file from within the editor. If you do not follow those steps and UAC is turned on, you may not be able to save the modified file.

3. Remote Desktop connections
When connecting to a remote Microsoft Windows computer using Microsoft's Remote Desktop, run Remote Desktop with the "/admin" flag. Not running with this setting may cause subtle, hard-to-explain errors in the program. You can do this using these steps:

1. Right-click on the Remote Desktop shortcut.

2. Select properties.

3. Click on the Shortcut tab.

4. At the end of the Target field, add a space, a forward slash, and "admin" (without the quotes) to the end of the Target. The screen shot sample below illustrates this setting:

1.6 Minimizing Locked Files

To minimize the possibility that the Tools Release installer or SnapShot might fail due to locked files, follow these guidelines:

1. Exit from all running programs. You can use Microsoft Windows Task Manager to verify that the programs are stopped. In particular, be sure that EnterpriseOne, JDeveloper, and SQL Developer are stopped, but other programs may also need to be stopped. Exceptions to this rule include the database service(s) which should be running.

2. Verify that no files in the Deployment Server's installation directory or subdirectories are open in any file editors.

3. Verify that neither the installation directory nor any of its subdirectories are open in Microsoft Windows Explorer.

4. Verify that no Command Prompt window has as its current working directory either the Deployment Server's installation directory or any of its subdirectories.

2 Installing a Tools Release on the Deployment Server

This section discusses:

- Section 2.1, "Backing Up Your Existing System"

- Section 2.2, "Downloading Tools Release 9.1 for the Development Client"

- Section 2.3, "Understanding Destination Paths"

- Section 2.4, "Installing a JD Edwards Tools Release on a Deployment Server Using the Oracle Universal Installer (OUI)"

- Section 2.5, "Tools Release Installer Logs"

- Section 2.6, "Using Tools Accelerator TL910001 to Create and Map New Tables"

2.1 Backing Up Your Existing System

The tools release download replaces the System directory and its subdirectories on the Deployment Server. Therefore, before you begin you should make a backup of the existing directory structure.

On the Deployment Server, make a copy of these directories:

/System

/Systemcomp

/OneWorld Client Install

Note:
If the following files exist when installing or reinstalling Tools Release 9.1, they will NOT be replaced by new files in the downloaded tools release:

- All files in this directory:
\System\oc4j\j2ee\home\applications\webclient.ear\webclient\web-inf\classes

- \OneWorld Client Install\InstallManager.htm

- \OneWorld Client Install\install\oraparam.ini

For an initial installation of Tools Release 9.1 onto a Deployment Server that has a tools release prior to 9.1, you will probably need to modify the \OneWorld Client Install\InstallManager.htm file. See the instructions in Section 3.8, "Updating the InstallManager.htm File".

2.2 Downloading Tools Release 9.1 for the Development Client

This section contains the instructions for downloading and running the Tools Release 9.1 installer for the Development Client. You must download this code to a Microsoft Windows-based Deployment Server.

1. From the Oracle Software Delivery Cloud (http://edelivery.oracle.com), locate and download the Tools Release 9.1 for the Client Platform to your Windows-based Deployment Server.
It is recommended that you download the <filename>.par file to a Microsoft Windows temp directory. Do not save the executable anywhere within the JD Edwards Deployment Server's installation directory structure.

2. Once the <filename>.par is downloaded onto your Deployment Server, extract the contents.

Note:
WinZip or 7-Zip can be used to extract the contents.

2.3 Understanding Destination Paths

Each Oracle product that is installed on a machine is installed into what is termed an Oracle Home directory or path. This is a directory that contains most of 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 Oracle Enterprise Edition (OEE) database engine on the Deployment Server, by default the Oracle Home path will be:

c:\Oracle\E1Local

The value E1Local cannot be changed, but you may specify another drive and/or directory instead of c:\Oracle. The Oracle Home name for the OEE database is E1Local. SSE does not install into an Oracle Home 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.

If you are using OEE and, following the above examples, you would now have two Oracle Homes:

1. The first Oracle Home is the Oracle Home of the OEE database; it has these properties:

1. Oracle Home Path
C:\Oracle\E1Local

2. Oracle Home Name
E1Local

2. The second Oracle Home is the Oracle Home of the Deployment Server; it has these properties:

1. Oracle Home Path
C:\JDEdwards\E910

2. Oracle Home Name
JDE_DEP910_HOME

Tip:
It is recommended that you use the above names when installing OEE and Tools Release 9.1.

During the installation of an Applications Release 9.1 Deployment Server or a Tools Release 9.1, OUI will copy the files from the installer to subdirectories under the Oracle Home path and then perform the necessary configurations. In addition, it places a copy of OUI into the Oracle Home Path.

OUI also creates a submenu of items in the Start / All Programs menu. This submenu is named "Oracle - <Oracle_Home_Name>" where <Oracle_Home_Name> is the name that the user specified during the installation. This submenu will include a link to the EnterpriseOne Solution Explorer and another submenu for Oracle Installation Products. Oracle Installation Products includes a link to the copy of OUI that is in the Oracle Home Path. Although you can run other copies of OUI to deinstall (remove) the EnterpriseOne Deployment Server, it is safest to deinstall using the link in Start / All Programs / Oracle - <Oracle_Home_Name> / Oracle Installation Products / Universal Installer.

2.4 Installing a JD Edwards Tools Release on a Deployment Server Using the Oracle Universal Installer (OUI)

Use this procedure to install a JD Edwards tools release on a Deployment Sever using the Oracle Universal Installer (OUI).

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. From the location where you extracted the installer in the section of this guide entitled: Section 2.2, "Downloading Tools Release 9.1 for the Development Client", use this program to launch the installer:
\Disk 1\ToolsRelease\install\setup.exe

Caution:
Be sure to follow the guidelines in the preceding sections of this guide entitled:

- Section 1.5, "Microsoft Windows Security"

- Section 1.6, "Minimizing Locked Files"

3. On the Welcome screen, click the Next button to begin.

4. On Specify Home Details, you must select the Oracle Home path and name for the existing Deployment Server.

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 2.3, "Understanding Destination Paths".

Caution:
If you are installing Tools Release 9.1 and an Oracle Home for the Deployment Server does not already exist (for example, you are installing Tools Release 9.1 for the first time on a E900 Deployment Server), you can enter any name that you want but the path must match the path of the installed Deployment Server.
If an Oracle Home for the Deployment Server already exists (for example, you are reinstalling Tools Release 9.1 or you are installing the tools release on a E910 Deployment Server), you must select the existing Oracle Home name for the Deployment Server.

- 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 where the JD Edwards EnterpriseOne Deployment Server was installed. For example, the path would be:

C:\JDEdwards\E910

5. Click the Next button.
If you get the following warning prompt, click the Yes button.

The Tools Release panel displays.

6. On Tools Release, Service Pack Version, click the Next button to install the new tools release on the Deployment Server or to a specified mapped deployment drive.
If JD Edwards EnterpriseOne Files are installed on a remote Deployment Server, you should specify the mapped drive. For example:

Z:\

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.

7. Select the Next button.

8. On Summary, verify the list of items to be installed is correct.
If there is insufficient disk space available to complete the installation on the Deployment Server, an error message is displayed.

9. Select the Install button.

The JD Edwards EnterpriseOne Tools Release installer displays a panel showing the ongoing status of the installation.

10. When the installation of the tools release 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 always check the logs before you attempt to run the Deployment Server.

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

11. On End of Installation, click the Exit button.

2.5 Tools Release Installer Logs

This table lists the Tools Release installer logs.

Path/File

Description

C:\JDEdwards\E910\cfgtoollogs\oui

Path that contains OUI logs for the installation of the JD Edwards EnterpriseOne tools release.
C:\JDEdwards\E910 is the Oracle Home path that you specified during the installation.

C:\Program Files (x86)\Oracle\Inventory\Logs

Master path that contains logs for all runs of OUI installing 32-bit products to any Oracle Home on the machine. Upon completion of OUI, the logs for the current run of OUI are copied to this path:
C:\JDEdwards\E910\cfgtoollogs\oui

C:\DeCompressStatus.log

Records results of decompressing CAB files.

2.6 Using Tools Accelerator TL910001 to Create and Map New Tables

You can use Change Assistant to download a Tools Accelerator from the JD Edwards Update Center. This accelerator creates and maps the 14 new tables required for enhancements included in 9.1.0.0. You run this accelerator from the Deployment Server. It is estimated that running this accelerator could save you about 30 minutes of manual instructions.

For further information on deploying accelerators see knowledge document, Oracle Business Accelerators for JD Edwards EnterpriseOne 9.0 or 9.1 Installation Guide. The 9.0 version of the guide is document ID 705506.1, and is available in the document at this link on My Oracle Support:

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocTitle=Oracle%20Business%20Accelerators%20for%20JD%20Edwards%20EnterpriseOne%209.0%20Installation%20Guide,%20Revised&bmDocID=705506.1&bmDocType=REFERENCE&bmDocDsrc=KB&viewingMode=1143&from=BOOKMARK%29%29

The 9.1 version of the guide will be posted to My Oracle Support when it becomes available.

This Automated Special Instructions accelerator will perform the special instructions for the Bugs within the ESU that contains Bug 13009881. It must be run for each environment for the Path Code(s) to which you applied the ESU.

Caution:
You can use this process only the first time you install JD Edwards Tools Release 9.1 on the Deployment Server.

To locate this accelerator at the JD Edwards EnterpriseOne Update Center, use these search criteria:

- Type: JD Edwards EnterpriseOne

- Release: 9.0 or 9.1, depending on the release you want (the 9.1 version may not be immediately available with the general availability of Applications Release 9.1)

- Search for Name: TL910001

3 Setting Up a Development Client Installer on the Deployment Server

This chapter discusses these topics:

- Section 3.1, "Understanding the JD Edwards Clients (Development and Web)"

- Section 3.2, "Understanding the Oracle Universal Installer"

- Section 3.3, "Creating the Web Development Feature"

- Section 3.4, "Creating an Installation Package"

- Section 3.5, "Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server"

- Section 3.6, "Updating the Database Drivers in the JDBJ.ini File"

- Section 3.7, "Copying the JDK to the Deployment Server (OH4A Only)"

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

- Section 3.9, "Updating the oraparam.ini File"

- Section 3.10, "Setting Up Local Database Installers"

3.1 Understanding the JD Edwards Clients (Development and Web)

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. For example, in Tools Release 9.1 the supported version is WAS 7.0)
Tools Release 9.1 Update 2.3

Support for WAS 8.5 is added making this value H4A85.

This chapter describes the first time setup of the JD Edwards EnterpriseOne Development Client installer and installation package on an EnterpriseOne Deployment Server. 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.

For instructions on how to install Web Clients for both Application Servers: OH4A and H4A7/H4A85, as well as the installation of WAS 7/8.5 Express or WAS 7/8.5 for Developers, refer to the JD Edwards EnterpriseOne Development Client Installation Guide.

3.2 Understanding the Oracle Universal Installer

As of Tools Release 9.1, the Development Client is installed using the Oracle Universal Installer (OUI). In addition, the Web Client is installed as a package feature using OUI. When you run the 9.1 Tools Release installer on the Deployment Server, it copies the OUI installers for the Development Client and Web Client to the correct location on the Deployment Server. The location of the Development Client installer is:

\\<deployment server name>\<release>\OneWorld Client Install

Underneath this directory are the following. Only noteworthy files and directories are listed. Those under ThirdParty may or may not exist depending on which features are defined.

- InstallManager.exe
The program that the user runs to install the local database and the Development Client.

- Installmanager.htm
This HTML file is read by InstallManager.exe and contains commands to display a Graphical User Interface (GUI) and allows the user to select actions to carry out. The contents may be edited (to some extent) by the EnterpriseOne administrator.

- OracleLogo.gif
This bitmap file contains the Oracle logo that is displayed by the InstallManager.exe program.

- \install
This subdirectory contains the setup.exe program, which is the actual OUI installation program for the Development Client. It is run from the InstallManager.exe program. This directory also contains the oraparam.ini file, which contains parameters used by the setup.exe program.

- \stage
This subdirectory contains configuration files used by setup.exe during the installation.

- \MISC
This subdirectory contains a template jde.ini file and one or more <pathcode>.ini files. During the installation of the package the <pathcode>.ini file corresponding to the pathcode in the package that the user selects is merged with the jde.ini template file to create the jde.ini that is copied to the c:\Windows directory on the target machine.

- \ThirdParty
This subdirectory contains any additional programs that may need to be installed on the target machine. Examples include a database installer and an installer for OH4A, H4A7, or H4A85.

- \ThirdParty\WebDevFeature
This subdirectory contains the various available JD Edwards EnterpriseOne Web Client installers.

- \ThirdParty\WebDevFeature\OH4A
This subdirectory contains the installer and necessary files for the OH4A Web Client. A corresponding directory for H4A7 and/or H4A85 may also exist.

- \ThirdParty\WebDevFeature\OH4A\install
This subdirectory contains the setup.exe program, which is the actual OUI installation program for the OH4A Web Client. It is run as a feature from the Development Client installer. This directory also contains the oraparam.ini file which contains parameters that the setup.exe program uses.

- \ThirdParty\WebDevFeature\OH4A\stage
This subdirectory contains configuration files that tell setup.exe what to do during the installation.

- \ThirdParty\WebDevFeature\OH4A\JDBC
This subdirectory contains JDBC drivers that the Web Client uses to connect to databases. All of the OH4A, H4A7, and H4A85 Web Client installers have this directory. For instructions to set this up, refer to the section of this guide entitled: Section 3.5, "Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server".

- \ThirdParty\WebDevFeature\OH4A\JDK
This subdirectory contains a Java Development Kit (JDK) that the OH4A Web Client uses. This is needed by only the OH4A Web Client installer.

- \ThirdParty\WebDevFeature\H4A7
This subdirectory contains all files for the H4A7 installer. A corresponding directory for OH4A and/or H4A85 may also exist.

- \ThirdParty\WebDevFeature\H4A7\install
This subdirectory contains the setup.exe program, which is the actual OUI installation program for the H4A7 Web Client. It is run as a feature from the Development Client OUI installer. This directory also contains the oraparam.ini file which contains parameters that setup.exe uses.

- \ThirdParty\WebDevFeature\H4A7\stage
This subdirectory contains configuration files used by setup.exe during the installation.

- \ThirdParty\WebDevFeature\H4A7\JDBC
This subdirectory contains JDBC drivers that the Web Client uses to connect to databases. All of the OH4A, H4A7, and H4A85 Web Client installers have this directory. For instructions to set this up, refer to the section of this guide entitled: Section 3.5, "Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server".

- Note:
Tools Release 9.1 Update 2.3 The remaining bullet points in this list are applicable to WAS 8.5 which is supported beginning with Tools Release 9.1, Update 2.3.

- \ThirdParty\WebDevFeature\H4A85
This subdirectory contains all files for the H4A85 installer. A corresponding directory for OH4A and/or H4A7 may also exist.

- \ThirdParty\WebDevFeature\H4A85\install
This subdirectory contains the setup.exe program, which is the actual OUI installation program for the H4A85 Web Client. It is run as a feature from the Development Client OUI installer. This directory also contains the oraparam.ini file which contains parameters that setup.exe uses.

- \ThirdParty\WebDevFeature\H4A85\stage
This subdirectory contains configuration files used by setup.exe during the installation.

- \ThirdParty\WebDevFeature\H4A85\JDBC
This subdirectory contains JDBC drivers that the Web Client uses to connect to databases. All of the OH4A, H4A7, and H4A85 Web Client installers have this directory. For instructions to set this up, refer to the section of this guide entitled: Section 3.5, "Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server".

Note:
Any combination (or all) of the Web Client installers may exist on the Deployment Server; however, an installation package may contain only one Web Client installer (as a feature). Likewise, only one Web Client may be installed on a Development Client.
The installers do not prevent you from installing more than one type of Web Client on a Development Client, but unexpected results may occur if you attempt this.

3.3 Creating the Web Development Feature

Complete this task to create a Web Client Installation Feature for your version of the application server. This feature must be included in the installation package before it is deployed to the Web Client machine.

1. On the Deployment Server, log on to the Deployment environment (for example, DEP910 for Applications Release 9.1).

2. From Solution Explorer, FastPath to P9623.

3. On Work With Features, click the Add button.

4. On Feature Based Deployment Directory, click the Next button.

5. On Feature Information, complete these fields:

- Feature
Enter a meaningful name for the feature. For example, if you are using OAS:

WEBDEVOAS

If you are using WAS, an example would be:

WEBDEVWAS

You can specify any name for the feature.

Tip:
Alternatively, you can provide the WAS Express version number (for example, either 7 or 85) in the name.

- Feature Type
Enter the value 1.

- Description
Enter a description. For example:

Web Development Objects (OH4A) for OAS

or

Web Development Objects (H4A) for WebSphere Express

You can specify any name for the description.

- Required
Ensure this option is selected.

- Additional Install Processes
Ensure this option is selected.

6. Click the Next button.

7. On Additional Install Processes, complete these fields:

- Execute Before Install/Execute After Install
The Development Client installer for Tools Release 9.1 does not use either of these flags. The behavior is to run the feature's installer after installing the Development Client.

- Third Party
Enter the name of the feature that you entered earlier. For example, if you are using OAS:

WEBDEVOAS

If you are using WAS, an example would be

WEBDEVWAS

You can specify any name for the feature.

- Description
Enter a description. For example:

Web Development Objects (OH4A) for OAS

or

Web Development Objects (H4A) for WebSphere Express

You can specify any name for the feature.

- Executable Name
Enter this value:

setup.exe

- Source Path
Enter the path to the installation executable.

For OH4A, the path would be:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\install

For H4A7, the path would be:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A7\install

Tools Release 9.1 Update 2.3

For H4A85, the path would be:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A85\install

8. Click the Save button.

9. Click the Next button.

10. On Features Summary, click the End button.

3.4 Creating an Installation Package

This task describes how to add a Web Client Installation Feature to an installation package.

1. On the Deployment Server, run EnterpriseOne.

2. From the Package and Deployment Tools menu (GH9083), choose Package Assembly (P9601).

3. Choose an assembled package that you want to deploy to the Development Client, and click Package Revisions from the Row Exit menu, or click Add to create a new package.

Caution:
Do not attempt to add a feature to an existing package that has already been built. When you deactivate a built package, EnterpriseOne deletes the package.

4. Click Features.

5. On the Features Component screen, click Browse.

6. On the Feature Component Selection screen, click Find.

7. Choose the Web Client Installation Feature for the Application Server you are using.

Caution:
Do not include a feature for more than one of the Web Client installers (OH4A, H4A7, or H4A85) in a single installation package. If you use more than one application server in your environment, create a separate package for each feature.

8. Click Select.
A check mark displays to the left of the component.

9. Click Close.

10. On the Feature Component screen, click Close.

11. On Package Component Revisions, click OK.

12. Choose the package you just modified, and click Activate/Inactive in the Row Exit menu.

13. Click Define Build in the Row Exit menu.

14. On the Work with Package Build Definition screen, click Add.

15. Navigate through the Package Build Definition screens by clicking Next.

16. On the Build Features screen, click the Build Feature INFs check box.

17. Complete the Build Definition process.

18. On Work With Package Build Definition, click Submit Build in the Row Exit menu.

3.5 Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server

Required JDBC drivers and the tnsnames.ora file are automatically downloaded from the Deployment Server to the Development Client during the installation of the Development Client. To set up this process, the administrator must first obtain the required JDBC drivers for the supported platforms and databases as well as the tnsnames.ora file, if connecting to an Oracle database, and copy them to the Deployment Server as described in this procedure.

This section describes these tasks:

- Section 3.5.1, "Copy the JDBC Drivers"

- Section 3.5.2, "Copy the tnsnames.ora file"

3.5.1 Copy the JDBC Drivers

To copy the JDBC drivers:

1. On the Deployment Server, create a \JDBC subdirectory under the folder that contains the Web Client installation program. For example:
\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\JDBC

or

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A7\JDBC

Tools Release 9.1 Update 2.3

or

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A85\JDBC

Note:
If you have to copy the JDBC files to a different directory for some reason, you have to add an entry to the oraparam.ini file for the OH4, H4A7, or H4A85 installer to indicate the location of that JDBC directory. Edit the oraparam.ini file located in this directory:
\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\Install

or

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A7\Install

Tools Release 9.1 Update 2.3

or

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A85\Install

Add this entry to the [FileLocations] section of the oraparam.ini file:

JdbcPath=<Path_to_JDBC_files>

For example,

[FileLocations]
JdbcPath=\\depsvr2\E910\My_JDBC

Note:
If you leave this entry out, the OH4A, H4A7, or H4A85 installer will look for the JDBC directory up one level from the setup.exe program for OH4A, H4A7, or H4A85.

2. Refer to the section of this guide entitled: Section 1.4, "Accessing Minimum Technical Requirements" for information on where to obtain the JDBC drivers.
The required JDBC drivers for each platform are listed below:

Database

Required Driver

Comments

SQL Server 2005

sqljdbc4.jar

Microsoft provides a type 4 JDBC driver with full support at no additional charge. Download the JDBC driver directly from Microsoft's website.
Use the installation documentation that comes with the download to install the JDBC driver into a temporary location.

Oracle

ojdbc5.jar

The JDBC driver for Oracle will automatically be downloaded to your system when you install an Oracle database client or server. If you install a different driver, the system may not function properly.

UDB/DB2

db2jcc.jar and db2jcc_license_cu.jar

The JDBC driver for DB2/UDB is delivered with DB2/UDB server or client installation. Both files need to be present.

DB2/400 for IBMi

jt400.jar

The DB2/400 driver for the IBMi platform is delivered with the DB2/400 database installation.

3. Obtain the JDBC drivers and copy them to the JDBC directory you created in the first step.
When the Web Client is deployed to a target machine, these drivers are automatically installed into the following directory:

<Client Install Path>\misc

3.5.2 Copy the tnsnames.ora file

The tnsnames.ora file is required only if the Development Client will connect to an Oracle database. However, if the tnsnames.ora file is not copied to the correct directory on the Deployment Server, the user will receive an error message during the Web Client installation process.

To copy the tnsnames.ora file:

1. Obtain the tnsnames.ora file from an Oracle database configured to run with JD Edwards EnterpriseOne.

2. If the Web Client will use an Oracle database installed locally on the Development Client machine, you must use the following steps to ensure that the tnsnames.ora file has an entry to allow the Web Client to connect to the local database:

1. Edit the tnsnames.ora file.

2. If an entry for E1Local does not already exist, add this to the file:

E1LOCAL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = E1Local)
))

3. Save the tnsnames.ora file.

3. Copy the tnsnames.ora to this directory on the Deployment Server:
\\<deployment server name>\<release>\Client

When the Web Client is installed on a target machine, this file is automatically installed to the following directory:

For OH4A:

<Client Install Path>\system\oc4j\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes

For H4A7 or H4A85:

<Client Install Path>\JAS\EA_JAS_80.ear\webclient.war\WEB-INF

3.6 Updating the Database Drivers in the JDBJ.ini File

The Web Client installer updates the JDBJ.ini file with settings for the databases to which the Web Client will connect based on the JDBC database drivers found in this directory:

<Client Install Path>\misc

As noted in the preceding section of this chapter entitled: Section 3.5.1, "Copy the JDBC Drivers", these JDBC database drivers are copied from this directory:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\<OH4A_or_H4A7_or_H4A85>\JDBC

Note:
If you copy additional database drivers into the <Client Install Path>\misc directory after installing OH4A, H4A7, or H4A85, you will need to update the list of drivers in the JDBJ.ini file.

To update the database drivers in the JDBJ.ini file:

1. Edit the JDBJ.ini file, which is typically found in this directory on your JD Edwards Development Client machine:
For OH4A:

<Client Install Path>\system\oc4j\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes

For H4A7 and H4A85:

<Client Install Path>\JAS\EA_JAS_80.ear\webclient.war\WEB-INF\classes

2. Locate the section: [JDBj-JDBC DRIVERS] and comment (add a hash or pound sign '#' at the beginning of the line) to disable any drivers that are not needed and uncomment (remove any hash or pound signs '#' at the beginning of the line) to enable any drivers that are needed.
The following table lists the database driver names for the types of databases that EnterpriseOne supports.

Database

Setting in [JDBj-JDBC DRIVERS]

Oracle

ORACLE=oracle.jdbc.driver.OracleDriver

IBM AS/400 DB

AS400=com.ibm.as400.access.AS400JDBCDriver

SQL Server 2005

SQLSERVER=com.microsoft.sqlserver.jdbc.SQLServerDriver

UDB

UDB=com.ibm.db2.jcc.DB2Driver

3.7 Copying the JDK to the Deployment Server (OH4A Only)

As with the JDBC drivers, you must store the correct version of JDK in a defined directory on the Deployment Server. The JDK is then automatically downloaded to the Web Client during the installation of the OH4A Web Client. (For H4A7 and H4A85, the JDK is installed when you install WebSphere Express or WebSphere for Developers.) To set up this process, the administrator must first obtain the required JDK from Oracle and copy this application to the Deployment Server as described in the following procedure.

Note:
These instructions refer to a JDK (Java Developers Kit) -- not a JRE (Java Runtime Environment). These terms refer to distinctly different products that should not be confused. A JDK contains a JRE plus other components. A specific JDK is an MTR that is required by the Web Client.

1. On the Deployment Server, create a directory called \JDK under the folder that contains the Web Client installation program. For example:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\JDK

2. Refer to the section of this guide entitled: Section 1.4, "Accessing Minimum Technical Requirements" for a link to the MTRs which specify the required JDK.

3. Locate and download the appropriate JDK from the Oracle web site:
www.oracle.com

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

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

4. Save the JDK to a temporary directory.

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

6. Click Next.

7. Select Accept and click Next.

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

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

10. Deselect both Browse Registration options.

11. Click Install.
The installation process takes several minutes

12. When the process is complete, click Finish.

Note:
If you have to copy the JDK files to a different directory for some reason, you have to add an entry to the oraparam.ini file for the OH4A installer to indicate the location of that JDK directory. Edit the oraparam.ini file located in this directory:
\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\Install

Add this entry to the [FileLocations] section of the oraparam.ini file:

JdkPath=<Path_to_JDK_files>

The path should be the parent directory of the \bin directory that holds the javac.exe program. Be sure this path can be reached by the installer as it runs on the target Web Client machine. For example, if the javac.exe resides in \\depsvr2\E910\My_JDK\bin, enter the following in the [FileLocations] section of the oraparam.ini file:

JdkPath=\\depsvr2\E910\My_JDK

Note:
If you do not add the entry described in the preceding note, the OH4A installer looks for the JDK directory up one level from the setup.exe program for OH4A.

3.8 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.9 Updating the oraparam.ini File

The OUI installer reads installation parameters from the oraparam.ini file. This file resides with the OUI executable called setup.exe in this directory:

\\<deployment server name>\<release>\OneWorld Client Install\install

When initially updating a Deployment Server to Tools Release 9.1, the oraparam.ini file is not updated from the existing install.inf file. Therefore, you must manually update some settings in the oraparam.ini file as described in this section.

The oraparam.ini file follows the standard format of ini files for Microsoft Windows: it contains sections with names inside square brackets ( [ ] ) and key/value pairs. The keys and their values are separated by equals signs ( = ).

If the following section or keys do not exist in your oraparam.ini, you must add them along with the values indicated. Be sure that any paths can be reached by the OUI program that is running on the machine where the Development Client is being installed; that is, do not use local paths -- use paths of this form:

\\<deployment server name>\<release>\xxx

Section

Key

Value Description

Value Example

[Oracle]

DEFAULT_HOME_LOCATION

Default Oracle Home path into which Development Client will be installed. Users can change this path at installation time.

E910

[Oracle]

DEFAULT_HOME_NAME

Default Oracle Home name of path into which Development Client will be installed. Users can change this path at installation time.

JDE_E910_Client

[FileLocations]

PackageInfs

Path to package.inf files.

\\depsvr2\E910\package_inf

[FileLocations]

currentReleaseMasterPath

Path including deployment server and share.

\\depsvr2\E910

[FileLocations]

JdbcPath

Optional - Used when installing OH4A, H4A7, or H4A85
- Path to JDBC files

- If not specified, installer looks for a directory called JDBC; this directory is expected up one level from the directory containing the setup.exe file for OH4A, H4A7, or H4A85.

\\depsvr2\E910\My_JDBC

[FileLocations]

JdkPath

Optional - Used when installing OH4A
- Path to JDK files

- If not specified, installer looks for a directory called JDK; this directory is expected up one level from the directory containing the setup.exe for OH4A.

\\depsvr2\E910\My_JDK

[Attributes]

DataByPathCode

Optional - Used when installing OH4A, H4A7, or H4A85 to create the datasource name that points to local data
=1 means that local data is specific to individual pathcodes.

=0 means that local data is shared among all installed pathcodes.

For details, see the appendix of this guide entitled Appendix C, "Data by Pathcode".

1

[Attributes]

LocalDS

Optional - Used when installing OH4A, H4A7, or H4A85 to create the datasource name that points to local data
For details, see the appendix of this guide entitled  Appendix C, "Data by Pathcode".

OneWorldLocal

3.10 Setting Up Local Database Installers

The Development Client requires a database to be installed onto the same machine on which the Development Client is to be installed. You can choose the database based on the Applications Release of E1 and "bitness" of the Windows operating system that your users are using. Do not take the following information for granted - you should always check the MTRs for the most current official information.

- Applications Release 9.1 / 64-bit Windows 7
64-bit Oracle Enterprise Edition 11gR2 (OEE)

- Applications Release 9.0 / 64-bit Windows 7
64-bit Oracle Enterprise Edition 11gR2 (OEE)

Microsoft SQL Server 2005 Express Edition (SSE; SP3 is required if installing on Windows 7)

- Applications Release 9.0 / 32-bit Windows XP
32-bit Oracle Enterprise Edition 10gR2 (OEE)

Microsoft SQL Server 2005 Express Edition (SSE; may use any service pack)

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

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

This program allows the user to install a local database or the E1 Development Client. By default, the InstallManager.htm file is shipped from Oracle configured to install OEE.

This section describes these topics:

- Section 3.10.1, "Additional OEE Setup"

- Section 3.10.2, "SSE Setup"

3.10.1 Additional OEE Setup

The main installation program for OEE is OEESetup.exe. Upon initial installation of Tools Release 9.1, this directory is created:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\ORACLE

The installation delivers these files in the above directory:

- OEESetup.exe

- deinstall.bat.tmpl

- deinstall_E1Local.rsp.tmpl

- settings.ini

The above files can be used for both 32- and 64-bit versions of the database and for 11gR2 and 10g versions.

You must manually copy the E1Local cloned database to this directory:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\ORACLE

This cloned database can be downloaded from the Oracle Software Delivery Cloud site or the JD Edwards Update Center. Available versions of the database include 32- and 64-bit. You should choose the bitness of database that is applicable to your end-user versions of Microsoft Windows.

Inside the zip files that you download are files containing the cloned database. These internal files are called E1Local.cab, E1Local2.cab, through E1Local15.cab. The names are the same for both 32- and 64-bit versions of the database, so be sure to keep them separated.

If some users require 32-bit and others require 64-bit versions of the database, follow these steps:

1. Create a copy of this directory:

\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\ORACLE

Name the new directory appropriately for the bitness, for example, ORACLE64.

Place the OEESetup.exe and related files (listed at the beginning of this section) into that directory.

2. Download the appropriate version of the E1Local cloned database from the Oracle Software Delivery Cloud or the JD Edwards Update Center.

3. Expand the downloaded zip files and put the contents into the directory you created in Step 1 (for example, ORACLE64). The contents should include 15 cab files that are prefixed with E1Local.

4. Edit this file:
\\<deployment server name>\<release>\OneWorld Client Install\InstallManager.htm

5. Locate this line near the bottom of the file:
<a class="sectionItem" id="LaunchLink" link="ThirdParty\ORACLE\OEESetup.exe" href="InstallManager.htm">Oracle Local Database</a>

6. Change the line to point to the correct directory and update the text that will appear on the screen:
<a class="sectionItem" id="LaunchLink" link="ThirdParty\ORACLE64\OEESetup.exe" href="InstallManager.htm">64-Bit Oracle Local Database</a>

Note:
The database will be installed in the directory specified in the [Bootstrap] section and OracleBasePath key in the settings.ini file.

7. Save and close the InstallManager.htm file.

Note:
The only differences between the installation files for the 32- and 64-bit versions of the database are in the CAB files and their contents. The non-CAB files (for example, OEESetup.exe, settings.ini, etc.) are the same for both versions of the database.

3.10.2 SSE Setup

If you want users to install SSE as the local database for the Development Client, you must change the installer option in the InstallManager.htm file to point to the SSE database installer. You should also refer to the complete instructions on editing the InstallManager.htm file in the section of this guide entitled: Section 3.8, "Updating the InstallManager.htm File".

To setup the InstallManager.htm file to install the SSE local database for the Development Client:

1. Using an editor such as Microsoft Notepad, edit this file:
\\<deployment server name>\<release>\OneWorld Client Install\InstallManager.htm

2. Locate this line near the bottom of the file:
<a class="sectionItem" id="LaunchLink" link="ThirdParty\ORACLE\OEESetup.exe -i" href="InstallManager.htm">Oracle Local Database</a>

3. Change the line to point to the correct directory and installation program for SSE:
<a class="sectionItem" id="LaunchLink" link="ThirdParty\SSE\DotNetSSESetup.exe" href="InstallManager.htm">SSE Local Database</a>

4. Save and close the InstallManager.htm file.

Follow these steps to download the installer for the database and the installer for the .NET Framework from Microsoft.

Note:
If the JD Edwards EnterpriseOne MTRs specify a higher version of the database, use the MTRs in the following instructions.

1. Download the Microsoft SQL Server Express 2005 SP3 installer:

1. Go to the Microsoft Download Center:
http://www.microsoft.com/downloads

2. In the search field near the top of the screen, enter "SQL Server 2005 Express Edition SP3" and click the magnifying glass icon.

3. Click on the link titled "SQL Server 2005 Express Edition SP3".

4. Next to the file called SQLEXPR.EXE, click the Download button.

5. Save the file to your local machine. It is recommended that you put the download in a specific location on the drive with the most space in a directory such as:
D:\SSE

2. The .NET Framework contains new Windows files that applications such as SSE can use. Oracle highly recommends that you install at least version 4.0 of Microsoft's .NET Framework. To download its installer:

1. Go to the Microsoft Download Center:
http://www.microsoft.com/downloads

2. In the menu bar at the top of the screen, click on "Downloads A-Z" and type "N" and NET".

3. Click on the link titled "Microsoft .NET Framework 4 (Web Installer)".

4. Next to the file called dotNetFx40_Full_setup.exe, click the Download button.

5. Save the file to your local machine in the folder created above. For example, D:\SSE.

3. The main installation program for SSE is called DotNetSSESetup.exe. It runs the .NET Framework and SSE installers. Upon initial installation of Tools Release 9.1, the following files should reside in \\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\SSE:

- DotNetSSESetup.exe

- settings.ini

4. Copy both the .NET Framework and SSE installers that you downloaded from Microsoft into this directory:
\\<deployment server name>\<release>\OneWorld Client Install\ThirdParty\SSE

Note:
The DotNetSSESetup.exe program is normally run from the InstallManager.exe program, but it can be run from the command line. If you need to run DotNetSSESetup.exe for some reason, you can run it from a command prompt with the argument -h to see a list of the available arguments.

4 Working With the Client Full Package

This section discusses:

- Section 4.1, "Understanding the Client Full Package"

- Section 4.2, "Creating the Client Full Package"

4.1 Understanding the Client Full Package

The package build and assembly process includes many critical tasks that must be successfully completed to correctly install packages. See JD Edwards EnterpriseOne Tools Package Management Guide for details on building, assembling, and deploying packages. That guide lists most of these tasks and gives step-by-step instructions for completing them.

It is necessary to build a Full Client and Server Package when upgrading to the Tools Release 9.1. If this tools release has an enterprise server download, you must first upgrade the enterprise servers before you upgrade the workstations. If the enterprise servers are not upgraded first, they may not be able to properly receive and process requests from workstations that are upgraded.

4.2 Creating the Client Full Package

To create the client full package:

1. Sign on to EnterpriseOne.

2. Go to GH9083.

3. Select Package Assembly.

4. Select Add.

5. On the Welcome screen select Next.

6. Enter the Package name, Description and Pathcode, Select Next.

7. If the package is using the Defaults then select End, otherwise you can use the form icons to perform the functions in this procedure.

8. Activate the package.

9. Select Define Build.

10. On the Welcome screen select Next.

11. Select Client and Server, select Next.

12. Select the Client, select Next.

13. Select End if you want to take the defaults.

14. Activate the package.

15. Select Submit Build to build the package.

16. When the package build is complete, deploy the package to the client workstations or make it Approved for Install Manager for the client workstations.

5 Working
With SnapShot on the Deployment Server

Note:
Tools Release 9.1 Update 2. This entire chapter is revised to support a significantly enhanced version of SnapShot that is available with Tools Release 9.1 Update 2 and higher. For the version of SnapShot that was included with the base release of JD Edwards EnterpriseOne Tools Release 9.1, refer to the appendix of this guide entitled: Appendix D, "Working With SnapShot on the Deployment Server (Base Release of Tools Release 9.1)".

This section discusses these topics:

- Section 5.1, "Understanding SnapShot"

- Section 5.2, "Prerequisites"

- Section 5.3, "Using Snapshot on the Deployment Server"

- Section 5.4, "Manually Backing Up Files and Settings"

- Section 5.5, "Set Logging for SnapShot Using the Registry"

- Section 5.6, "Troubleshooting"

5.1 Understanding SnapShot

The SnapShot program manages multiple instances of JD Edwards EnterpriseOne Deployment Servers or Development Clients on a single machine. Using this program you can save and restore copies of an installed Deployment Server or Development Client. For instructions on using SnapShot with the Development Client, refer to the JD Edwards EnterpriseOne Development Client Installation Guide.

Below is an example of SnapShot managing multiple tools releases including B7333 (DV7333) and two installations of E910 (E910_DV and E910_PD).

The preceding image shows the JD Edwards main SnapShot window. The main features of this window, from top to bottom, include:

- Close (icon)
The Close icon is located in the upper right hand corner. Click this icon to exit SnapShot.exe.

- System (icon)
The System icon is located in the upper left hand corner. Click on this icon or right-click on the title bar to display a drop-down menu that contains "About EnterpriseOne SnapShot…." Selecting this item displays version and build information about SnapShot as shown below:

- Existing Version
The Existing Version area contains these fields and buttons:

- Version
The Version field lists the existing installed Deployment Server. Initially, this is the release specified in the installed package. After you save and then restore a SnapShot, this field will be the name that you gave the SnapShot when you saved it.

- Location
The Location field shows the JD Edwards EnterpriseOne installation directory.

- Save
Use the Save button to save the installed JD Edwards EnterpriseOne to a SnapShot.

- Rename
Use the Rename Environment button to rename the path code and environment names of the installed JD Edwards EnterpriseOne. This function is not available on the Deployment Server.

- Saved Versions
The Saved Versions area contains a field that lists saved versions (also called SnapShots). The example in this image shows the following versions: DV7333 and E910_PD.

- Restore
Use the Restore button to restore a saved version (SnapShot) to a runnable JD Edwards EnterpriseOne installation.

- Delete
Use the Delete button to remove a saved version (SnapShot).

- Log File
The Log File area displays the log file path and name.

- Close
Use the Close button to exit SnapShot.exe.

5.2 Prerequisites

Before saving or restoring a JD Edwards EnterpriseOne installation using SnapShot, be sure that:

- You are signed into Microsoft Windows using an account with sufficient privileges (for example: read, write, execute) to the registry and to the JD Edwards EnterpriseOne installation and saved directories.

- All JD Edwards EnterpriseOne programs are closed.

- No applications (for example, Windows Explorer) have a file or subfolder open in either the installation or the saved directory or one of their subdirectories.

- The SnapShot.exe that you are running is not in either the installation or the saved directory or one of their subdirectories.

- The database(s) that both the JD Edwards EnterpriseOne installation and the saved SnapShot use is installed and running.

- Ensure that the Oracle product JDeveloper is not running.

Additional considerations:

- Before installing a new Deployment Server into a new Oracle Home, make sure you do not have any previous versions in the Existing Version field of SnapShot. All versions must be saved and should appear in the Saved Versions field.

5.3 Using Snapshot on the Deployment Server

To use SnapShot with multiple releases of the JD Edwards EnterpriseOne applications, you must use the most current version of SnapShot when switching between different releases of JD Edwards EnterpriseOne. For example, if you install the foundation code for both JD Edwards EnterpriseOne Applications Release 9.1 and Applications Release 8.12, you must use the version of SnapShot corresponding to the most current JD Edwards EnterpriseOne tools release, in this case, Tools Release 9.1.

This section describes these tasks:

- Section 5.3.1, "Starting SnapShot"

- Section 5.3.2, "Saving a SnapShot"

- Section 5.3.3, "Restoring a SnapShot"

- Section 5.3.4, "Deleting a SnapShot"

5.3.1 Starting SnapShot

Caution:
Be sure to follow the guidelines in the preceding sections of this guide entitled:

- Section 1.5, "Microsoft Windows Security"
As noted in this section, with the Tool Release 9.1 Update 2 and later version of SnapShot, you do not have to right click on the SnapShot.exe icon and select "Run as administrator." This is because these versions of SnapShot.exe are designed to automatically attempt to start with the elevated permissions. If you are not signed into Windows with an administrative account, you will be prompted to enter the credentials for an administrative account.

- Section 1.6, "Minimizing Locked Files"

The SnapShot utility is delivered with the installation of both the JD Edwards EnterpriseOne Deployment Server and the Development Client workstations. It is located in this directory:

<JDE_dep_server_or_dev_client_installation_directory>\System\Bin32

To run the most current version of SnapShot for multiple releases, you must copy the SnapShot.exe program to a directory outside the Deployment Server installation directory. For example, the installation directory might be c:\E910. If you attempt to run SnapShot from within the Deployment Server installation directory (for example, c:\E910) the application will display an error message.

Tip:
You can create a shortcut to SnapShot.exe, but you still must copy SnapShot.exe to a location outside the original installation directory where it was delivered.

5.3.2 Saving a SnapShot

To save a SnapShot:

1. On the main SnapShot window, click the Save button.

2. On Make a New SnapShot, complete this field:

- SnapShot Name
Enter a name for the SnapShot that will be saved. You may choose any name with the exceptions that the name cannot be empty and it cannot contain a backslash ( '\' ). A recommended scheme is to make it release specific, for example, Xe, B9, or E910.

- New Folder Name
SnapShot does not rename or move the installed directory on the Deployment Server; therefore, you cannot change the value in the New Folder Name field.

3. Click the OK button.
SnapShot saves a snapshot of the Deployment Server.

5.3.3 Restoring a SnapShot

To restore a SnapShot:

1. On the main SnapShot window and in the Saved Versions section, highlight the saved instance that you want to restore.

2. Click the Restore button.
SnapShot restores the selected instance of JD Edwards EnterpriseOne and makes it active.

5.3.4 Deleting a SnapShot

To delete a SnapShot:

1. On the main SnapShot window and in the Saved Versions section, highlight the instance that you want to delete.

2. Click the Delete button.
SnapShot completely removes the saved instance from the JD Edwards EnterpriseOne Deployment Server.

5.4 Manually Backing Up Files and Settings

Once you have saved a SnapShot for the Deployment Server, it is a good idea to manually backup the files to ensure that your settings for that Deployment Server are secure.

The files and subdirectories that need to be backed up are found in the folder of each saved snapshot. You should backup these files and subdirectories only while the SnapShot.exe program is not running. These files contain the information necessary to restore registry values and settings for each SnapShot.

5.5 Set Logging for SnapShot Using the Registry

The version of SnapShot that is shipped with Tools Release 9.1 Update 2 and later always outputs the maximum amount of logging information. Furthermore, by design there is no way to turn off logging. You can specify the name and location of the log file that is generated by adjusting a single registry setting.

Caution:
Changes made to the Microsoft Windows registry happen immediately, and no backup is automatically made. Do not edit the Windows registry unless you are confident about doing so.
Microsoft has issued the following warning with respect to the Registry Editor:

"Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk."

By default, the SnapShot log is located in the temp directory of the Microsoft Windows user. This is the directory pointed to by the TEMP environment variable. You can determine the value of this TEMP variable in a number of ways including:

1. Control Panel > System

2. In a command prompt window, enter this command:
echo %TEMP%

3. In the Address Bar of Windows Explorer, enter this string:
%TEMP%

The default log file name is SnapShot_<date-time>.log.

Both the directory and name of the SnapShot log can be specified by editing the registry; however, the date-time stamp will always be inserted immediately before the period.

To change the log file directory and/or name:

1. Open the registry by clicking on Windows Start button and entering regedit in the search field.

2. Navigate to this node:
\HKEY_LOCAL_MACHINE\Software\Wow6432Node\JDEdwards\Snapshot

The first time that you run SnapShot, it creates a value (shown on the right-hand pane in regedit) called LogFileName with the default value SnapShot.log. You can change this value or, if it does not exist yet, you can add the value with name LogFileName, type string value, and the directory and/or file name of your choice.

3. The rules listed below are used for determining the final log file directory and name based on the value of LogFileName:

- In all cases, the date and time that SnapShot.exe is run will be inserted immediately before the period in the extension of the file name.

- If the value of LogFileName does not contain any backslashes, the name represents only the file name. The value of the Windows TEMP variable will be used as the directory.

- If the value of LogFileName contains backslashes but does not start with a drive letter or a backslash, everything up to the last backslash represents a subdirectory or hierarchy of subdirectories below the directory designated by the Windows TEMP variable. Everything after the last backslash is the file name.

- If the value of LogFileName starts with a backslash, it represents a subdirectory below the root directory of the drive (that is, directory "\"). The drive letter is derived from the drive specified in the Windows TEMP variable.

- If the value of LogFileName starts with a letter followed by a colon and backslash, the letter is considered the drive letter where the log will reside. Any other applicable rule in the preceding rules above then apply.

The following are examples of values of the LogFileName registry entry and the resulting log file path and name. In these examples, the assumed value of the TEMP variable is C:\Users\John\AppData\Local\Temp and assumes the log was created on June 5, 2012, at 3:46:9 PM.

Value for LogFileName

Resulting Log File

SnapShot.log

C:\Users\John\AppData\Local\Temp\SnapShot_2012-6-5_15-46-9.log

MyFile.txt

C:\Users\John\AppData\Local\Temp\MyFile_2012-6-5_15-46-9.txt

MyTempDir\MyFile.txt

C:\Users\John\AppData\Local\Temp\MyTempDir\MyFile_2012-6-5_15-46-9.txt

MyTempDir\MyFile.txt

C:\MyTempDir\MyFile_2012-6-5_15-46-9.txt

D:\MyTempDir\MyFile.txt

D:\MyTempDir\MyFile_2012-6-5_15-46-9.txt

4. Save the changes and exit the registry.

5.6 Troubleshooting

If SnapShot encounters a problem when trying to perform an action, it is designed to attempt to rollback the actions performed up to the point of failure. This means that during a save operation, SnapShot attempts to restore the JD Edwards EnterpriseOne instance back to a runnable state. If a failure occurs during a restore action, SnapShot attempts to resave the JD Edwards EnterpriseOne snapshot so you can correct the problem and then retry the action.

Caution:
If a second error occurs when SnapShot is attempting to rollback changes, the error will likely result in either a non-runnable instance of JD Edwards EnterpriseOne or a saved snapshot that is corrupt. In either case, you will probably need to reinstall JD Edwards EnterpriseOne.

This section describes these topics:

- Section 5.6.1, "Examining the Log File"

- Section 5.6.2, "Remedial Actions"

5.6.1 Examining the Log File

When an error is encountered in SnapShot, the first thing that you should do is to carefully examine any on screen error messages for an indication of what went wrong and why. If you are not able to determine the cause and possible resolution of an error by examining the error message on the screen, examine the log file. As shown in the preceding screen example, the location and name of the log file is specified in the Log File section near the bottom of the main SnapShot window.

Above is an example of a SnapShot log file. When troubleshooting within the SnapShot log file, you should scan the Type column for a status of ERR, which indicates an error. If the error message itself is insufficient to isolate the cause of the problem, examine the messages immediately before and after the error for hints as to the root cause.

5.6.2 Remedial Actions

This section describes these topics:

- Section 5.6.2.1, "Examples of Healthy Environments"

- Section 5.6.2.2, "Simple Fixes"

5.6.2.1 Examples of Healthy Environments

This section illustrates a healthy JD Edwards EnterpriseOne installation and saved snapshot directories and registry settings.

The preceding shows the installation directory of a healthy JD Edwards EnterpriseOne instance.

In the preceding example screen, note that when you save a snapshot of the JD Edwards EnterpriseOne installation, the highlighted files and subdirectory shown above are created. Here are brief descriptions of the new files and subdirectory.

- STARTMENU*.*
The subdirectory that is prefixed with STARTMENU is the folder in the Start menu for the original installation.

- DESKTOP*.*
The file that starts with DESKTOP is the shortcut to JD Edwards EnterpriseOne that was on the desktop of the workstation.

- jde.ini
The jde.ini file is the same file that was in the c:\Windows directory.

- RegKeys*.*
The files that are prefixed with RegKeys are binary files that contain the saved registry entries.

The preceding image shows the registry entries for a healthy JD Edwards EnterpriseOne Deployment Server installation.

The preceding image shows the registry keys for a saved JD Edwards EnterpriseOne snapshot.

5.6.2.2 Simple Fixes

Not all issues can be resolved by simple steps. However this section describes a few simple fixes for these conditions:

- Section 5.6.2.2.1, "Missing Version Information"

- Section 5.6.2.2.2, "Missing Saved Version"

5.6.2.2.1 Missing Version Information

If the Existing Version fields are empty when you run SnapShot.exe and you are certain that a JD Edwards EnterpriseOne instance is active, it is likely that this file is missing:

c:\Windows\jde.ini

If you happened to save a copy of the jde.ini file when you last saved a snapshot of this installation, you can copy that jde.ini file into the c:\Windows directory and rerun SnapShot.exe.

5.6.2.2.2 Missing Saved Version

If a saved snapshot is not listed in the Saved Versions field and you know that the saved snapshot exists, some registry entries are probably missing or pointing to the wrong directory.

To resolve this issue, perform these steps:

1. Edit the registry with regedit.exe.

2. Create a subkey under this path:
\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JDEdwards\SnapShot

The name that you give for the subkey should be the name of the saved snapshot.

3. Click on the subkey that you just created.

4. Create a string value called SaveDir.

5. Set the value data for this to the directory where the saved snapshot is stored.

6. Create a second string value called InstallDir.

7. Set the value data for this to the installation directory (that is, the directory in which the saved snapshot will be restored).

The following image illustrates properly configured registry entries.

6 Rebuilding Business Functions for Vertex Header Files (for Vertex users only)

This applies to customers who use the Vertex Quantum Payroll Tax and Vertex Sales Tax Q Series (formerly Quantum for Sales and Use Tax) applications with JD Edwards EnterpriseOne.

These are the business functions that you may need to rebuild after applying Tools Release 9.1.

Business Function

Description

B0700058

Establish connection to Vertex

B0000182

Initialize environment for vendor business functions

B0000183

Free environment for vendor business function

B7300004

Retrieve Quantum GeoCodes

B7300002

Validate Quantum GeoCodes

B7300012

Retrieve Quantum software information

X00TAX

Calculate and edit tax amounts

For more information about using Vertex Quantum applications with ERP, see Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications in the JD Edwards EnterpriseOne Applications Release Installation Guide or JD Edwards EnterpriseOne Applications Release Upgrade Guide, for Applications Release 9.0 or 9.1, as applicable.

Note:
Refer to the Section 1.4, "Accessing Minimum Technical Requirements" to verify the supported versions of Vertex which vary according to platform.

7 Building Application Business Functions

If you are upgrading your IBM i to JD Edwards EnterpriseOne Release 9.1 with Tools Release 9.1, you must make modifications to the jde.ini file. These changes are required to enable successful builds of applications business functions on the IBM i machine.

You must add the following bold sections to your existing jde.ini setting on your IBM i JD Edwards EnterpriseOne Enterprise Server.

[BSFN BUILD]
LinkLibraries=JDEUNICODE JDELIB JDEKRNL OWVER V_VERIFY XERCESWRAP

Note:
In your jde.ini file, you should enter this command line for CRTSRVPGM.

[AS400]
CRTSRVPGM=CRTSRVPGM SRVPGM(%ls/%ls) MODULE(%ls/*ALL)
BNDSRVPGM(JDEUNICODE JDELIB JDEKRNL OWVER V_VERIFY
XERCESWRAP) EXPORT(*ALL) OPTION(*DUPPROC *DUPVAR *UNRSLVREF)
ALWLIBUPD(*YES) TGTRLS(*CURRENT)

Note:
You should enter the above command line as a single contiguous string.

8 Re-Linking Business Functions

After you have used Server Manager to install your Tools Release to an IBM i-based Enterprise Server, as in previous JD Edwards EnterpriseOne Tools Releases, you must re-link the Business Functions.

For each path code, re-link the business functions located in the associated IBM i library. The program LINKBSFN is delivered with the installation of each Tools Release to simplify this process. The following commands must be executed against each full package for a specified path code.

1. Run LINKBSFN against the full package of the path code.
LINKBSFN

After you have entered the LINKBSFN command, press F4 to display the system prompt. Enter the package library name for the first parameter and the path code for the second parameter.

2. Wait until the previous step completes successfully before continuing to the next step. Repeat this step for every package and path code you are updating.

A Working With Multiple Tools Release Foundations

As a best practice, you should always set up multiple tools release foundations, including a test environment for applying tools release fixes. This helps ensure that a stable environment exists before you promote fixes to your production environment. You can also use this same principle and procedure to set up multiple foundations of major tools releases, such as Tools Release 9.1 and Tools Release 9.2 (when applicable).

The procedures described in this document enable customers to target specific environments when they install a tools release. For example, customers can keep the production environment running on the existing foundation and apply the new tools release to all other environments. This configuration enables them to perform tests on the new foundation code without impacting the production environment. When they complete the testing, they can then apply the new tools release to production.

By completing the tasks below, you can configure your JD Edwards EnterpriseOne systems to handle many foundations on a single enterprise server. These tasks require that you reconfigure pathcodes and jde.ini files to set up multiple foundations, but once the initial tasks are completed, the new configuration requires very little maintenance.

Before you begin the installation, consider these factors:

- The multiple foundation setup uses one security server process per port.

- If you have multiple Enterprise Servers at different tools release levels, make sure each of them is pointing to the correct security data sources.

- If you have multiple foundations or multiple Enterprise Servers at different tools release levels, a dual maintenance of users and passwords is required.

- Before beginning installation of the Tools Release 9.1, check the associated readme.txt file for late-breaking information and requirements.

This appendix consists of the following tasks:

- Section A.1, "Understanding Multiple Foundation Code on the Enterprise Server"

- Section A.2, "Understanding Multiple Foundation Code on the Deployment Server"

- Section A.3, "Working with Packages for Multiple Foundations"

- Section A.4, "Working with the Development Client"

- Section A.5, "Editing the Development Client jde.ini File"

- Section A.6, "Setting up the Multiple jde.ini Files on the Deployment Server"

A.1 Understanding Multiple Foundation Code on the Enterprise Server

To install multiple foundations, you must first install and configure new system code on the Enterprise Server. This section includes these topics:

- Section A.1.1, "Working With Tools Releases on the Enterprise Server"

- Section A.1.2, "Registering an Existing Enterprise Server with Server Manager"

- Section A.1.3, "Understanding PORTTEST"

Note:
If your JD Edwards EnterpriseOne configuration includes multiple servers running JD Edwards EnterpriseOne host code (for example, additional application servers or data servers), then you will need to apply the procedures for installing multiple foundations to each server. For this type of configuration to work successfully:

- Make sure that the port settings for the [JDENET] section in the jde.ini match between all servers running the same foundation.

- Ensure the new services are running on all servers.

- Run PORTTEST successfully on all servers for all foundation releases that you have installed.

A.1.1 Working With Tools Releases on the Enterprise Server

Refer to the JD Edwards EnterpriseOne Server Manager Guide as described in the section of this guide entitled: Section 1.3, "Understanding Server Manager and This Guide".

This section discusses these topics:

- Section A.1.1.1, "Creating an IFS Directory"

- Section A.1.1.2, "Editing the JDE.INI"

- Section A.1.1.3, "Deleting the Subsystem Entry"

- Section A.1.1.4, "Creating a Subsystem for the Service Pack"

- Section A.1.1.5, "Verifying that the Library List is Set Up Correctly"

- Section A.1.1.6, "Linking Business Functions to Service Packs"

A.1.1.1 Creating an IFS Directory

Create a new IFS directory for storing the JDE logs for the new service pack by entering the following command:

MD DIR(logdirectory)

where logdirectory is the name of the IFS directory for storing the JDE logs. For example, your directory name might be PSE910SP.

A.1.1.2 Editing the JDE.INI

This section discusses editing the JDE.INI on an IBM i server.

Note:
Do not use the A98OWMNU option to access the JDE.INI. This option takes you to the Production JDE.INI, not the service pack JDE.INI.

1. Edit the JDE.INI you just copied by entering the following command:
WRKMBRPDM FILE(syslib/INI)

where syslib is the name of the new system library. For example, B9SPSYS.

2. Enter Option 2 to Edit the file.

3. Locate the [DEBUG] and [INSTALL] sections in the JDE.INI, and change the paths in each of the entries below to point to the new IFS directory and Library respectively:

[DEBUG]
DebugFile=logdirectory/JDEDEBUG
JobFile=logdirectory/JDE.LOG
JDETSFile=logdirectory/JDETS.LOG

[INSTALL]
DefaultSystem=syslib

4. Locate the [JDEIPC] section and change the startIPCKeyValue. This value should be an unused start key not within the IPC range of another instance. For example, if the IPC value of another instance is 5000, then you should set the startIPCKeyValue to 7000.

[JDEIPC]
startIPCKeyValue=7000

5. Locate the [JDENET] section, and find the port settings for serviceNameList and serviceNameConnect. For each entry, add 100 to the number. For example, if the settings are both 6013, change them to 6113.

[JDENET]
serviceNameListen=6113
serviceNameConnect=6113

6. In the [SECURITY] section, either clear security or edit DefaultEnvironment to reference a valid environment that accesses the new Tools Release.

7. Replace all references to the production environment (for example, PD9) with a valid environment that will access the new service pack (for example, PD812).

A.1.1.3 Deleting the Subsystem Entry

The service pack installation creates an entry for the new service pack under the existing subsystem. This is not necessary, as a new subsystem will be created for the new service pack.

1. To delete the entry, type the following command:
WRKSBSD SBSD(syslib/*ALL)

2. Enter Option 4 next to the entry that includes the new syslib and delete the entry.

A.1.1.4 Creating a Subsystem for the Service Pack

1. Ensure you are signed on as QSECOFR before performing these steps.

2. Add the SYSTEM library to your library list.
ADDLIBLE syslib

3. Enter these commands, depending on your Tools Release:
CHGCMD CMD(CRTOWSBS) PGM(*LIBL/CRTOWSBS)

CRTOWSBS SUBSYSTEM(subsystemname) SYSLIB(syslib)

where subsystemname is the name of the new subsystem for the newly installed Tools Release. For example, PSE9101SP.

Note:
The CALL PGM command requires four parameters, and the last three parameters should be the new SYSTEM library.

A.1.1.5 Verifying that the Library List is Set Up Correctly

Sign onto your IBM i as ONEWORLD. To ensure the library list is set up correctly, verify that it contains the newly created SYSTEM library. For example, E910PSYS.

A.1.1.6 Linking Business Functions to Service Packs

For each JD Edwards EnterpriseOne path code you want associated with the new service pack, re-link the business functions located in the associated IBM i library. The following commands must be executed against each full package for a specified path code:

1. Run LINKBSFN against the pathcode's full package. Type LINKBSFN, then press F4 to display the system prompt. Enter the package library name for the first parameter and the pathcode for the second parameter.

2. Wait until the previous step completes successfully before continuing to the next step.

3. Repeat this step for every package and pathcode you are updating.

A.1.2 Registering an Existing Enterprise Server with Server Manager

Any Enterprise Server running Tools Release 8.97 and greater should be registered with Server Manager. For details, refer to the section entitled: "Register or Create a JD Edwards Enterprise Server as a New Managed Instance" in the JD Edwards EnterpriseOne Server Manager Guide.

A.1.3 Understanding PORTTEST

To ensure that the new tools release is properly installed on the Enterprise Server, complete the following task to run PORTTEST on all environments accessing the new tools release.

Note:
If Security Server is on, then JD Edwards EnterpriseOne services must be running before PORTTEST can be run.

This section contains the following topics:

- Section A.1.3.1, "Running the PORTTEST"

- Section A.1.3.2, "Starting the Services"

A.1.3.1 Running the PORTTEST

This section discussing running the PORTTEST application on an IBM i Enterprise Server.

1. Sign on to the IBM i as ONEWORLD.

2. On Current Release 9.1 Versions, select the newly installed instance of JD Edwards EnterpriseOne.

3. Go to the Release 9.1 Menu by entering the following commands:
ADDLIBLE JDEOW

GO JDEOW/A98OWMNU

4. Choose option 4 to run PORTTEST.

5. Repeat the PORTTEST command for each environment accessing the new service pack

A.1.3.2 Starting the Services

This section discusses how to manage Services on an IBM i Enterprise Server.

1. Sign on to the IBM i as OneWorld.

2. On Current Release 9.1 Versions, select the newly installed instance of JD Edwards EnterpriseOne.

3. Enter these commands:
ADDLIBLE JDEOW

GO JDEOW/A98OWMNU

4. Choose option 6 to end JDE server.

5. Choose option 7 to clear the IPC.

6. Start the Enterprise Server using these options:

1. Choose option 5 to start the JDE server.

2. Choose option 8 to display active jobs.

7. Verify that the entry NETWORK is running with a PGM-MONITOR in SELW status.

8. Verify that the entry SENTINEL is running with a PGM-MONITOR in SIGW status.

Note:
Until you perform a net request, the CPU is 0 (zero).

A.2 Understanding Multiple Foundation Code on the Deployment Server

This chapter discusses:

- Installing Multiple Tools Releases on the Deployment Server

- Adding a New Machine Record for the New Tools Release

- Modifying the Existing Machine Record to Remove Environments

A.2.1 Installing Multiple Tools Releases on the Deployment Server

1. Sign on to the Deployment server using the JDE user ID.

2. Make sure that all JD Edwards EnterpriseOne processes (for example, Solution Explorer) are not running.

3. On the Deployment server, navigate to this directory:
z:\JDEdwards\E910

where z: is the drive on which the JD Edwards EnterpriseOne host code is installed.

4. In the E910 directory, create a directory called
System_TR_Original

where TR_Original is the release number of the tools release currently installed. For example, System_894_M1.

5. From the \JDEdwards\E910 directory, copy (not move) the following directories to the new System directory (System_TR_Original) that was just created. This will serve as backup or rollback location for the previous release.
System

SystemComp

OneWorld Client Install

Caution:
Ensure you do not move these directories; they are required in both locations. This is because the installer needs to save a copy of the jdbj.ini and jas.ini files so you can relocate them in the new system directory.

Note:
If you get a warning message, it indicates files are locked. You need to ensure that JD Edwards EnterpriseOne or any other application is not running and causing a lock on any file.

6. If the Deployment Server is directly connected to the Internet, run the installation using one of these two methods to acquire the tools release:

1. Change Assistant

2. Directly from the Update Center

In either case it is recommended to save the downloaded executable to a temporary directory and run it later from there.

7. When you run the downloaded executable, you will receive a dialog indicating that the files are extracting.

8. On Installation Complete, click OK.
The program installs the new System, SystemComp, and OneWorld Client Install files and directories onto the Deployment Server.

9. In the E910 directory, create another new directory called System_TR_New where TR_New is the release number of the tools release being installed. For example, System_91_A1.

10. Move the newly installed System, SystemComp, and OneWorld Client Install files and directories into the new directory:
\JDEdwards\E910\System_TR_New

For example, \JDEdwards\E910\System_91_A1.

11. Restore the original directories by copying the System, SystemComp, and OneWorld Client Install directories from System_TR_original to the base installation directory x:\JDEdwards\E910.

12. Locate the jde.ini in this location:
\JDEdwards\E910\System_TR_New\OneWorld Client Install\Misc

13. Modify the above-located jde.ini to change the port to that on which you wish to run the multiple foundation. For example, valid ports might be 6014, 6015, etc.

A.2.2 Adding a New Machine Record for the New Tools Release

1. On the Deployment Server, log on to the deployment environment.

2. From the Fast Path menu, run P9654A.

3. On Work with Locations and Machines, click Find and expand the location tree.

4. Click Enterprise Servers and then click Add.

5. On Enterprise Server Revisions, complete the following fields:

Field

Description

Machine Name

Enter the name of your existing primary Enterprise Server.

Description

Enter a description for the machine.

Release

Enter E910.

Host Type

Click the visual assist button and select the type of Enterprise Server.

Port Number

This should match the port number previously set in the new tools release
jde.ini

Database Type

Click the visual assist button and select the type of database being used on the Enterprise Server.

Installation Path

Enter the installation library in which Release 9.1 is installed on the Enterprise Server. For example:
SYSLIB

6. Click OK.

7. On Work with Locations and Machines, click Find and expand the tree.

8. Expand the Enterprise Server, click the newly added machine and click Select.

9. On Enterprise Server Revisions, click the Environments form exit.

10. On Machine Environments Revision, add the environments which you want to access with the new tools release. You can add the environments either by typing their names into the grid or by selecting them using the visual assist.

11. Click OK twice to return to Work with Locations and Machines.

A.2.3 Modifying the Existing Machine Record to Remove Environments

1. On the Deployment Server, log on to the deployment environment.

2. From the fast path menu, run P9654A.

3. On Work with Locations and Machines, click Find and expand the location tree.

4. Expand Enterprise Servers, click the initial Enterprise Server machine record and click Select.

5. On Enterprise Server Revisions form, click the Environments form exit.

6. Delete all the environments that you added in the previous section.
This should leave you with only those environments that you have defined to access the production tools release (for example, PD910).

7. Click OK twice.

A.3 Working with Packages for Multiple Foundations

Deploying the new tools release is easily done using the Package Build application by using a non-default foundation. Use these steps to create and include a new foundation for the multi-foundation tools release.

1. Sign on to the Deployment Server using the JDE user ID.

2. Sign on to EnterpriseOne using the JDE user ID into the Deployment (DEPXXX) environment.

3. Launch the Package Assembly application from menu GH9083.

4. On Package Component Revisions, select the Multi-foundation Update Package and enter a valid value for the Parent Package.

5. On Foundation Component Selection, search for and select the new update package you specified in the previous screen.

6. On Foundation Item Revisions, complete these fields:

Item

Value

Description

Foundation Name

TR_NewVersion

Enter a unique name of the foundation.
For example, 896_A1.

Description

TR New Version

Enter a description corresponding to the new foundation name.

Service Pack Number

TR New Number

Enter an arbitrary tools release number where the maximum string value is four characters.
For example: 896A.

Release

E1 Release

Use visual assist to appropriately select the EnterpriseOne release level.

Platform Type

99 – Client

Enter Client because the foundation is to be deployed to the development client workstation.

Build Type

20 – Optimize

You must select optimize as the build type.

Foundation Build Status

30 – Build is Available

You must identify the package build as available.

Date Built

Installed Date

Enter the date the tools release was installed.

Time of Build

Time of Installation

You can enter any time.
Typically you should enter the approximate time the installation was performed.

Foundation Machine Key

Deployment Server Name

Enter the UNC name of the deployment server.

Foundation Path

path

Enter the relative path to the new system folder.
Be sure to include the front –\– and the System directory at the end. For example:

\E910\System_TR_New\System

7. Click OK to save the Foundation Item Revision information.

8. On Foundation Item Revisions, select the browse button.

9. On Foundation Component Selection, select the Multi-foundation Update Package by clicking the first column of the selected row.
Ensure that the checkmark displays in the first column of the selected row record.

10. Click Add to create a new foundation to be used.

11. On Package Component Revisions, verify that the Multi-foundation Update Package you added is displayed in the Foundation field and click OK.

12. On Package Build Revisions, select the Compression Options tab and select your compression options.

13. Click End to complete the Package Assembly process.

14. Proceed to build and deploy the package.

A.4 Working with the Development Client

Use the procedure in this section to set up your Development Client.

1. On the GH9083 menu, launch the Package Build application.

2. Create an update package by selecting Package Assembly and then Add.

3. On the Work With Features, select Add.

4. On Feature Based Deployment Director, click Next.

5. On Feature Information, complete these fields:

Field

Description

Feature Type

Enter a valid value for this feature type.

Description

Enter a description for the machine.

Feature Installation Options

Select your feature installation options by checking the appropriate check boxes.

Components

Verify this check box is selected:
Additional Install Processes

6. Click Next.

7. On Package Assembly, Additional Install Processes, complete these fields:

- Feature
Enter a meaningful name for the feature. For example, if you are using OAS:

WEBDEVOAS

If you are using WAS, an example would be

WEBDEVWAS

You can specify any name for the feature.

- Feature Type
Enter the value1.

- Description
Enter a description. For example:

Web Development Objects (OH4A) for OAS

or

Web Development Objects (H4A) for WebSphere Express

You can specify any name for the description.

- Required
Ensure this option is selected.

- Additional Install Processes
Ensure this option is selected.

8. Click Save.

9. Click Next.

10. Continue with the rest of the package assembly; there is no need to select any objects.

11. Define the package and, when prompted, make sure to select:
Build Feature Inf

12. Submit the package, which creates the new feature .inf for Web Development.
The newly created feature .inf file is located in the package.inf directory.

Note:
For any subsequent package builds for the non-default foundation for which you want to include webdev feature, you can use the package that you created with this procedure.

A.5 Editing the Development Client jde.ini File

Note:
If you are using Snapshot, you do not need to manually edit the jde.ini file to manage multiple clients for multiple foundations, as described in this procedure.

This section describes editing the jde.ini file for a Development Client.

In order for the Release 9.1 clients to access the new tools release, you must edit the jde.ini file on each client to point to the new directory.

Complete the following task on all Release 9.1 clients that have path codes that will access the new tools release.

Note:
You will be unable to access multiple tools releases with a single client. To access multiple tools releases, you will need to install a different client for each tools release. This will require using the Snapshot application to save each client before installing the next one.

1. On the Release 9.1 workstation, open Microsoft Windows Explorer, and navigate to your Microsoft Windows directory. For example:
cd c:\WINDOWS

2. Open the jde.ini file.

3. Locate the [JDENET] section, and edit the port settings for serviceNameListen and serviceNameConnect. Change these entries to match those of the server jde.ini file for the new tools release.

[JDENET]
serviceNameList=portNumber
serviceNameConnect=portNumber

where portNumber is the same port number you entered in the jde.ini file on the Enterprise Server.

A.6 Setting up the Multiple jde.ini Files on the Deployment Server

You may need to set up multiple jde.ini files on the Deployment Server to address the requirement for the Development Client to access different pathcodes and ports for different application releases of JD Edwards EnterpriseOne. For details, refer to the appendix of this guide entitled: Appendix C, "Data by Pathcode".

B Manual Cleanup of a Deinstalled Oracle Database

If the deinstallation of the OEE database fails for some reason, to completely remove the old installation before reinstalling the database, you need to perform manual steps that are listed in the appendix of the JD Edwards EnterpriseOne Development Client Installation Guide entitled Manual Cleanup of a Deinstalled Oracle Database.

C Data by Pathcode

When a Development Client is installed, it may be configured so that each pathcode on the client has its own local database or for all pathcodes to share the same local database. Initially, JD Edwards EnterpriseOne is set up for each pathcode on a Development Client to have its own database. This section describes how to configure these scenarios.

This appendix discusses these topics:

- Section C.1, "Datasource Name Generation"

- Section C.2, "Package Build Considerations"

- Section C.3, "Additional Spec Datasource Settings in the jdbj.ini"

- Section C.4, "Summary of Possible Administrator Changes"

C.1 Datasource Name Generation

The Development Client installation creates entries in the registry based on values in the Development Client installer oraparam.ini file located at:

\\<deployment server>\<release>\OneWorld Client Install\install\oraparam.ini

The entries in the oraparam.ini are:

[Attributes]
DataByPathCode=0|1
LocalDS=Local (this can be any string; the default value is "Local")

The registry entries on the Development Client machine after the Development Client is installed are located under:

HKEY_LOCAL_MACHINE\Software\Jdedwards\OneWorld\install.ini\<releasenumber>

In the above location, the registry key values are assigned:

DataByPathCode=0|1LocalDS=some_string

Using these values, the OH4A, H4A7, or H4A85 installer creates these datasource entries that point to the EnterpriseOne specs stored in a local database:

1. Entry in the jdbj.ini used by the web client:

[JDBj - SPEC DATA SOURCE]
name=

2. Entry in the jde.ini used by the Development Client:

[LOCALWEB]

Spec Datasource=

For OH4A, the jdbj.ini file is located in this directory on the Development Client machine:

<installpath>\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes\jdbj.ini

For H4A7 and H4A85, the jdbj.ini is located in this directory on the client machine:

<installpath>\JAS\EA_JAS_80.ear\webclient.war\WEB-INF\jdbj.ini

The rules for generating the spec datasource name in the jdbj.ini and jde.ini are based on the values of the DataByPathCode and LocalDS in the [Attributes] section of oraparam.ini, which is located in this directory of the Development Client installer:

OneWorld Client Install\install

In hierarchical order, the rules are:

1. DataByPathCode is 0 or missing
This condition indicates a shared local database. The datasource name will be "OneWorld Local" regardless of the value of LocalDS.

The following table shows the parameters used to create a datasource name that points to a local database:

ini File

Settings

oraparam.ini

DataByPathcode=0 or missing
LocalDS is missing

jdbj.ini

[JDBj - SPEC DATA SOURCE]
name=OneWorld Local

jde.ini
(Development Client machine)

[LOCALWEB]
Spec Datasource=OneWorld Local

2. DataByPathCode is 1 and LocalDS is Missing
This condition indicates separate databases and LocalDS is missing. The datasource name will be "Local" followed by a hyphen and then the pathcode.

ini File

Settings

oraparam.ini

DataByPathcode=1
LocalDS is missing

jdbj.ini

[JDBj - SPEC DATA SOURCE]
name=Local - <pathcode>

jde.ini
(Development Client machine)

[LOCALWEB]
Spec Datasource=Local - <pathcode>

3. DataByPathCode is 1 and LocalDS is Set
This condition indicates separate databases and LocalDS is set. The datasource name will be the value of LocalDS followed by a hyphen and then the pathcode.

ini File

Settings

oraparam.ini

DataByPathcode=1
LocalDS=Local

jdbj.ini

[JDBj - SPEC DATA SOURCE]
name=Local - <pathcode>

jde.ini
(Development Client machine)

[LOCALWEB]
Spec Datasource=Local - <pathcode>

Caution:
The OH4A, H4A7, and H4A85 installers look for exact strings to replace. Therefore, you should not change these strings manually; you must allow the installer to change them.
String in the JDE.ini template:

- #Spec Datasource=OneWorld Local

String in the jdbj.ini template:

- ;name=OneWorld Local

C.2 Package Build Considerations

The package build process uses a value in the c:\Windows\jde.ini on the build machine when building a full package to determine the directory structure that will be created on target workstations when the package is installed. This key and setting are:

[INSTALL]
DataByPathCode=0|1

The directory structure that is formed by the package build based on this setting is stored in the inf file for the package.

The following table shows what the directory structure would look like when the built package is installed on a workstation using these example values:

- Installation Directory
c:\E910

- Pathcodes
DV910

PY910

Note:
These values are only examples; additional pathcodes could be included.

DataByPathCode

Directory Structure

Comment

DataByPathCode=0

c:\E910\JDEData

Contains database shared among all pathcodes

c:\E910\DV910

c:\E910\PY910

DataByPathCode=1
This is the default value for package build.

c:\E910\DV910\JDEData

Contains database for DV910

c:\E910\PY910\JDEData

Contains database for PY910

Caution:
The value of the DataByPathCode key in the [INSTALL] section of the jde.ini on the machine(s) on which any packages are built MUST match the value of the DataByPathCode key in the [Attributes] section of the oraparam.ini in \OneWorld client Install\install directory for the Development Client installer.

C.3 Additional Spec Datasource Settings in the jdbj.ini

As noted in the preceding sections of this appendix, the name of the Spec Data Source stored in the jdbj.ini is determined based on the values of the DataByPathCode and LocalDS keys in the oraparam.ini file. Additional entries in the jdbj.ini complete the definition of the datasource. These entries are copied to the jdbj.ini by the OH4A, H4A7, or H4A85 installer and come from the [DB SYSTEM SETTINGS - SECONDARY] section of the Development Client jde.ini.

The following table shows the mapping between Entries in the jde.ini and jdbj.ini.

jde.ini

jdbj.ini

DB SYSTEM SETTINGS - SECONDARY

JDBj - SPEC DATA SOURCE

Type

databaseType

DatabaseInstance

databaseInstance

During the installation of the Development Client, the jde.ini file for all the Development Clients is created according to specific rules. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express for details.

C.4 Summary of Possible Administrator Changes

The following table describes the only changes that the administrator might need to make to affect the definition of the datasource for the local database.

File

Setting

Comment

\\<deployment server name>\<release>\OneWorld Client Install\misc\jde.ini

[DB SYSTEM SETTINGS - SECONDARY]
Type
DatabaseInstance=

Type defines the type of the local database.
DatabaseInstance defines the instance name of the local database.

[INSTALL]DataByPathCode

0 = share database among pathcodes
1 = separate databases for each pathcode

This setting is only used when building a full package.

\\<deployment server name>\<release>\OneWorld Client Install\misc\<pathcode>.ini

[DB SYSTEM SETTINGS - SECONDARY]
Type
DatabaseInstance

Any values in this file override their respective values in this file:
\\<deployment server name>\<release>\OneWorld Client Install\misc\jde.ini

Type defines the type of the local database.

DatabaseInstance defines the instance name of the local database.

\\<deployment server name>\<release>\OneWorld Client Install\install\oraparam.ini

[Attributes]DataByPathCode
LocalDS

0 = share database among pathcodes
1 = separate databases for each pathcode

This o ptional datasource prefix is only used if DataByPathCode=1.

D Working
With SnapShot on the Deployment Server (Base Release of Tools Release 9.1)

Note:
Tools Release 9.1 Update 2. This appendix is applicable to the version of SnapShot that was included with the base release of JD Edwards EnterpriseOne Tools Release 9.1.

This section discusses these topics:

- Section D.1, "Understanding SnapShot"

- Section D.2, "Prerequisites"

- Section D.3, "Using Snapshot on the Deployment Server"

- Section D.4, "Manually Backing Up Files and Settings"

- Section D.5, "Set Logging for SnapShot Using the Registry"

D.1 Understanding SnapShot

The SnapShot program manages multiple instances of JD Edwards EnterpriseOne Deployment Servers or Development Clients on the same machine. Using this program you can save and restore copies of an installed Deployment Server or Development Client. For instructions on using SnapShot with the Development Client, refer to the JD Edwards EnterpriseOne Development Client Installation Guide.

Below is an example of SnapShot managing multiple tools releases including Xe, 8.11 SP1, and 9.0 (B9PD).

D.2 Prerequisites

This is a list of general considerations for using SnapShot:

- Make sure that you do not have a JDE.INI file open when you save or restore SnapShot.

- Make sure that you do not have the ODBC Data Source Administrator open when restoring a SnapShot.

- Make sure before installing a new Deployment Server into a new Oracle Home, you do not have any previous versions in the Existing Version field of SnapShot. All versions must be saved and should appear in the Saved Versions field.

- When saving a SnapShot of the Deployment Server, it is required that the New Folder Name field be identical to the existing location due to the sharing of the folder on the Deployment Server. This also allows the proper use of the Previous Planner ODBC during the upgrade process. The ODBC points to the jdeplan.mdb folder from the previous JD Edwards EnterpriseOne application release (for example, Xe or ERP8.0). Therefore, the folder name must NOT be changed. If the snapshot folder is not correct, the upgrade would fail to access the previous release database.

D.3 Using Snapshot on the Deployment Server

Caution:
Before using SnapShot on the Deployment Server, ensure that JDeveloper is not running.

To use SnapShot with multiple releases of the JD Edwards EnterpriseOne applications, you must use the most current version of SnapShot when switching between different releases of JD Edwards EnterpriseOne. For example, if you install the foundation code for both JD Edwards EnterpriseOne Applications Release 9.1 and Applications Release 8.12, you must use the version of SnapShot corresponding to the most current JD Edwards EnterpriseOne tools release, in this case, Tools Release 9.1.

This section describes these tasks:

- Section D.3.1, "Starting SnapShot"

- Section D.3.2, "Saving a SnapShot"

- Section D.3.3, "Restoring a SnapShot"

- Section D.3.4, "Deleting a SnapShot"

D.3.1 Starting SnapShot

Caution:
Be sure to follow the guidelines in the preceding sections of this guide entitled:

- Section 1.5, "Microsoft Windows Security"

- Section 1.6, "Minimizing Locked Files"

The SnapShot utility is delivered with the installation of both the JD Edwards EnterpriseOne Deployment Server and the Development Client workstations. It is located in this directory:

<JDE_dep_server_or_dev_client_installation_directory>\System\Bin32

To run the most current version of SnapShot for multiple releases, you must copy the SnapShot.exe program to a directory outside the Deployment Server installation directory. For example, the installation directory might be c:\E910. If you attempt to run SnapShot from within the Deployment Server installation directory (for example, c:\E910) the application will display an error message.

Tip:
You can create a shortcut to SnapShot.exe, but you still must copy SnapShot.exe to a location outside the original installation directory where it was delivered.

D.3.2 Saving a SnapShot

To save a SnapShot:

1. On JD Edwards | SnapShot, click the Save button.

2. On Make a New SnapShot, complete these fields:

- SnapShot Name
Enter a name for the SnapShot that will be saved. You may choose any name, but a recommended scheme is to make it release specific, for example, Xe, B9, or E910.

- New Folder Name
SnapShot does not rename or move the installed directory on the Deployment Server; therefore, do not change this value.

3. Click the OK button.
SnapShot saves a snapshot of the Deployment Server.

D.3.3 Restoring a SnapShot

To restore a SnapShot:

1. On JD Edwards | SnapShot, in the Saved Versions section, highlight the saved instance you want to restore.

2. Click the Restore button.
SnapShot makes the selected instance active.

D.3.4 Deleting a SnapShot

To delete a SnapShot:

1. On JD Edwards | SnapShot, in the Saved Versions section, highlight the instance you want to delete.

2. Click the Delete button.
SnapShot completely removes the instance from the Deployment Server.

D.4 Manually Backing Up Files and Settings

Once you have saved a SnapShot for the Deployment Server, it is a good idea to manually backup the files to ensure that your settings for that Deployment Server are secure.

The files that need to be backed up are found in the root folder of each saved snapshot. You should backup these files only while the SnapShot.exe program is not active. These files contain the information necessary to restore registry values and settings for each SnapShot.

The files to backup are listed below:

- jde.ini

- regkeys*.dat

- package.inf

D.5 Set Logging for SnapShot Using the Registry

Logging is controlled by adjusting registry settings that control SnapShot.

Caution:
Changes made to the Microsoft Windows registry happen immediately, and no backup is automatically made. Do not edit the Windows registry unless you are confident about doing so.
Microsoft has issued the following warning with respect to the Registry Editor:

"Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk."

To set the logging for SnapShot using the registry:

1. Open the Registry by navigating to Run > Regedit.

2. Navigate to this node:
\HKEY_LOCAL_MACHINE\Software\Wow6432Node\JDEdwards\Snapshot

3. To enable logging, change the LoggingEnabled key value to 1 (where a value of 0 is off). If this key does not exist, create it as a REG_SZ type.

4. Change the LoggingLevel to a value between 1 and 5, where 1 provides the least amount and 5 provides the most amount of logging details. If this key does not exist, create it as a REG_SZ type.

5. Save the changes and exit the Registry.
Logs will be located in the directory from which the SnapShot.exe program is being executed.

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.