JD Edwards EnterpriseOne

Oracle VM Templates Express Installation Guide

Tools Release 9.1.4.4 and Applications Release 9.1.2 for the Oracle Database on Linux x86-64 Platforms

E54942-04

August 2014

JD Edwards EnterpriseOne Oracle VM Templates Express Installation Guide, Tools Release 9.1.4.4 and Applications Release 9.1.2 for the Oracle Database on Linux x86-64 Platforms

E54942-04

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

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

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

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

U.S. GOVERNMENT 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 on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 Understanding JD Edwards EnterpriseOne and Oracle VM Templates

- 1.1 Understanding This Guide

- 1.2 Understanding the Installation Process

- 1.2.1 Understanding the Deployment Server Installation

- 1.2.2 Understanding the Creation of the Enterprise, Database and HTML Web Server Virtual Machines

- 1.2.3 Understanding the Database Server for Non-Virtualized Databases such as Oracle Exadata or ODA

- 1.2.4 Understanding the Web Development Client Installation

- 1.3 Certifications (Formerly Known as Minimum Technical Requirements)

- 1.4 Working With the Customer Checklist

- 1.5 Working With the Pre-Install Worksheet

- 1.5.1 Environments Overview

- 1.5.2 Updating the Operating System and Applications

- 1.6 Disk Space Requirements

2 Before You Begin the Installation

- 2.1 Verifying Software and Hardware Requirements

- 2.2 Verifying the Disk Space Requirements

- 2.3 Host Name

- 2.4 Security Considerations

- 2.5 Overall Process Flow

3 Working with the Deployment Server

- 3.1 Understanding the Deployment Server

- 3.2 Local Oracle Enterprise Edition (OEE) Considerations

- 3.2.1 32-Bit Oracle Database Client (Required to Run EnterpriseOne)

- 3.2.2 EnterpriseOne Application P96717

- 3.2.3 Best Practices for OEE Performance

- 3.3 Obtaining and Preparing the Deployment Server Install Image

- 3.4 Working with JDBC Drivers on the Deployment Server

- 3.5 Installing the Deployment Server

- 3.5.1 Prerequisites

- 3.5.2 Installation Process Flow

- 3.5.3 Before Launching the Deployment Server Installer

- 3.5.4 Understanding Destination Paths

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

- 3.5.6 Examine the Local Database Installer Logs

- 3.5.7 Understanding the JD Edwards EnterpriseOne Deployment Server Installer

- 3.5.7.1 Understanding EnterpriseOne Files Location

- 3.5.7.2 Running the JD Edwards EnterpriseOne Deployment Server Installer

- 3.5.7.3 Mandatory Post Installation Tools Accelerator

- 3.6 Working with the Development Client Installation

- 3.6.1 Updating the oraparam.ini File

- 3.6.2 WebSphere Express Considerations

- 3.6.3 Add the Security Server Name to the Development Client jde.ini

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

- 3.8 Downloading and Installing the Latest Software (Optional Except for Planner Update, which is Recommended)

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

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

- 3.9 Troubleshooting Deployment Server Installation

- 3.9.1 Verify Local Planner Tablespaces are Not Attached

- 3.9.2 OEE Installer Logs

- 3.9.3 Configuration Files

- 3.9.4 Path Code Master (F98611)

- 3.9.5 Oracle Enterprise Edition

- 3.9.5.1 File Locations

- 3.9.5.2 Rebooting the Deployment Server

- 3.9.5.3 EnterpriseOne Access to the Local Oracle Database

- 3.9.5.4 Process Explorer

- 3.9.5.5 Verifying the Local Oracle Database Installation

- 3.9.5.6 Deployment Server Installation Problems

- 3.9.5.7 Runtime Problems

- 3.9.5.8 Administering the Local Oracle Database Using SQL Plus

- 3.9.5.9 Encrypting the Password of the Local Oracle Database

- 3.9.5.10 Decrypting the Password of the Local Oracle Database

- 3.9.5.11 Import and Export Tablespaces to the Local Oracle Database

- 3.9.5.12 Local Oracle Database Configuration

- 3.9.5.13 Deployment.inf and <Package_name>.inf

- 3.9.6 UBE Submission Failed on the Development Client

- 3.10 Configuring the Planner Databases

4 Working with Oracle VM Templates for JD Edwards EnterpriseOne

- 4.1 Implementing the Oracle Database With or Without Oracle VM Templates

- 4.2 Completing the Pre-Install Worksheet

- 4.3 Working with the Oracle VM Image Files for JD Edwards EnterpriseOne

- 4.4 Working with JD Edwards OVM Tools (config.sh Configuration Script)

- 4.4.1 Installing the JD Edwards OVM Tools

- 4.4.2 Creating the Directory Structure for the Oracle VM Templates for JD Edwards EnterpriseOne

- 4.4.3 Working with the Configuration Script

- 4.4.3.1 Manifest Check

- 4.4.3.2 Extract and Merge

- 4.4.3.3 Copy System

- 4.4.3.4 Server Configuration

- 4.4.3.5 JD Edwards Foundation Setup

- 4.4.3.6 JD Edwards Server Manager Setup

- 4.4.3.7 JD Edwards BIP Server Setup

- 4.4.3.8 JD Edwards Mobile Server Setup

- 4.4.3.9 JD Edwards AIS Server Setup

- 4.4.3.10 Completing the config.sh Script

- 4.4.3.11 Configuring for a Non-Virtualized or Exadata Database

- 4.4.3.12 Adding an Additional Enterprise Server (Standalone)

- 4.4.3.13 Adding an Additional HTML Server (Standalone)

- 4.4.3.14 Deploying an Additional Enterprise Server or HTML Server (Standalone) as a VM Template

5 Uploading Templates

- 5.1 Uploading a VM Template for JD Edwards Enterprise One Application Image

6 Working with VM Guests

- 6.1 Creating a VM Guest from the JD Edwards EnterpriseOne Application Template

- 6.2 Starting and Configuring the JD Edwards EnterpriseOne VM Guest Image

- 6.2.1 Boot the VM

- 6.2.2 Boot the VM for the First Time to Automatically Run the EOne_cfg.ksh Script

- 6.2.3 Checking the Configuration Log Files

7 Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server

- 7.1 Understanding the Platform Pack for a Non-Virtualized Database Server

- 7.2 Understanding the Connect String

- 7.3 Working with the Platform Pack Installer for a Non-Virtualized Database Server

- 7.3.1 Working with the zip File for the Platform Pack Installer

- 7.3.2 Working with the Response File for the Platform Pack Installer

- 7.3.3 Running the Platform Pack Installer for Non-Virtualized Database Servers

- 7.3.4 Working with Installer Log Files

- 7.3.5 Deinstalling the Platform Pack for Non-Virtualized Database Servers

8 Working With the Enterprise Server

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

- 8.2 Verifying the Release 9.1 Enterprise Server Installation Using PORTTEST

9 Starting the JD Edwards EnterpriseOne Servers

- 9.1 Starting the HTML Server

- 9.2 Starting the BI Publisher Server

- 9.3 Starting the Mobile Server

- 9.4 Starting the AIS Server

- 9.5 Starting Server Manager

10 Installing the Workstations for Developers and System Administrators

- 10.1 Workstation Installation

- 10.1.1 Overview of Workstation Installation

- 10.1.2 Prepare for Workstation Installation

- 10.1.3 Prerequisites

- 10.1.4 Configure the jde.ini File on the Deployment Server to Specify the Security Server

- 10.1.5 Modifying the Workstation JDE.INI on the Deployment Server for Languages (Optional)

- 10.2 Copying the Configured tnsnames.ora File

- 10.3 Copying the JDK to the Deployment Server

- 10.4 Understanding Workstation Installation Methods

- 10.4.1 Interactive Mode

- 10.4.1.1 Creating a Desktop Shortcut

- 10.4.1.2 Using a Shared Drive

- 10.4.2 Silent Mode

- 10.4.3 Push Mode

- 10.5 Understanding Third-Party Products

11 Post Installation Tasks

12 Deinstalling the Software

- 12.1 Understanding the Deinstallation

- 12.2 Deinstalling the Software from the Workstations

- 12.3 Deinstalling the Local OEE from the Deployment Server

- 12.4 Deleting Virtual machines for JD Edwards EnterpriseOne Servers

A Globalization Considerations

- A.1 National Language Setting Considerations

- A.2 NLS Considerations for Non Western European Users

- A.2.1 Non-Western European Database Language Considerations

B Documentation Resources

- B.1 Oracle VM Documentation

- B.2 Oracle Exalogic Documentation

- B.3 Oracle Enterprise Manager

- B.4 JD Edwards EnterpriseOne Installation Guide

- B.5 JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide

C Security and Demo Data Configuration

- C.1 Licensing Considerations

- C.2 Understanding Users for the Mobile Application

- C.3 Understanding Default Passwords for Database Users

- C.4 Considerations for Securing Database Users

- C.5 Securing the Miscellaneous Users

- C.6 Securing Package Build Users

- C.7 Securing the ESU Users

- C.8 Securing Other Users

- C.9 Securing the JDE User

- C.10 Adding a Security Override

- C.11 Changing the Admin Password with the P98OWSEC Security Application

- C.12 Changing the User Password in the Database

- C.13 Working with the Oracle Business Intelligence Publisher Schema Password

- C.13.1 Step 1: Modify the Schema Password from the Database

- C.13.2 Step 2: Modify the Data Source Connection Information from the WebLogic Administration Console

D Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode

- D.1 Understanding the Platform Pack in GUI Mode for RAC Database Servers

- D.2 Working with the Platform Pack Installer for a Non-Virtualized Database Server

- D.2.1 Working with the zip File for the Platform Pack Installer

- D.2.2 Running the Platform Pack Installer for Non-Virtualized Database Servers

- D.2.3 Working with Installer Log Files

- D.2.4 Deinstalling the Platform Pack for Non-Virtualized Database Servers

E Applying Patches

- E.1 Oracle Systems

- E.2 JD Edwards Applications, Clients, and Servers

F Managing Disk Images Used Within the EnterpriseOne VMs

- F.1 Creating a New Disk Image

- F.2 Updating the vm.cfg File to Add the New Disk Image

- F.3 Creating a Partition Table

- F.4 Creating a New Physical Volume with the New Disk Image

- F.5 Extending the Volume Group with the New Physical Disk

- F.6 Extending the Logical Volume with the New Volume Group

- F.7 Resizing the File System

- F.8 Logical Volume Manager Command Summary

G Default Port Listing Used Within the VMs for JD Edwards EnterpriseOne

Preface

Welcome to the JD Edwards EnterpriseOne Oracle VM Templates Express Installation Guide.

Audience

This document is intended for implementers and administrators who are responsible for performing a basic JD Edwards EnterpriseOne installation using Oracle VM templates for the Enterprise Server, Database Server and HTML Server.

Documentation Accessibility

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

Access to Oracle Support

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

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.

Indicates a link to a recording of the described feature. These recordings are in MP4 format so ensure that you have an appropriate player installed. Access to these recordings requires a valid Oracle account.

1 Understanding JD Edwards EnterpriseOne and Oracle VM Templates

This chapter contains the following topics:

- Section 1.1, "Understanding This Guide"

- Section 1.2, "Understanding the Installation Process"

- Section 1.3, "Certifications (Formerly Known as Minimum Technical Requirements)"

- Section 1.4, "Working With the Customer Checklist"

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

1.1 Understanding This Guide

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

The instructions in this guide also assume that Oracle VM software is already installed.

This guide contains only the procedures required for a typical base installation with predefined typical environments and databases. You can add on additional components after the Express Install by following procedures in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix, is available in the document on the Oracle Technology Network at this link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23313.pdf

This guide is designed for management information system (MIS) managers and installers. It outlines the procedures for installing Release 9.1. To successfully install Release 9.1, you must understand:

- Hardware and software requirements

- Database setup and management

- Enterprise platforms and operating systems

At a minimum, review these guides before beginning:

- JD Edwards EnterpriseOne Tools Foundation Guide

- JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide

- JD Edwards EnterpriseOne Tools System Administration Guide

- JD Edwards EnterpriseOne Tools Package Management Guide

- JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide

- JD Edwards EnterpriseOne Tools Security Administration Guide

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

For optimization recommendations for JD Edwards EnterpriseOne In-Memory Applications running on Oracle Exalogic and/or Oracle Exadata, refer to the JD Edwards EnterpriseOne Oracle VM Templates Express Installation Guide for Exalogic Platforms:

http://docs.oracle.com/cd/E16582_01/doc.91/e40602/title.htm

Tutorial:
Click here to view a recording of this feature or cut and paste the link below into your browser as a single line:
http://apex.oracle.com/pls/apex/f?p=44785:24:0::::P24_CONTENT_ID,P24_PREV_PAGE:7910,1

1.2 Understanding the Installation Process

This documentation explains the process used to install JD Edwards EnterpriseOne Applications and Tools Release software components for use with Oracle Virtual Machines using these five (5) steps:

1. Install Server Manager

Note:
You will need to download Server Manager from edelivery.oracle.com and follow the installation instructions in the Server Manager Guide.
The Oracle VM templates assume that Server Manager has been installed on the Deployment Server. The control files for the Server Manager Agents on the Oracle VM templates are updated and delivered to point to the Deployment Server.

2. Install Change Assistant

Note:
The Change Assistant install download is available on My Oracle Support on the Electronic Software Updates page.

3. Install the Deployment Server (see below for concurrent operations)

4. Create the Enterprise, Database and HTML Server Virtual Machines

Note:
For Release 9.1, the JD Edwards EnterpriseOne HTML Web Server is mandatory to run web-enabled JD Edwards EnterpriseOne applications, which includes all end-user applications and selected tools applications.
For Release 9.1, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.

5. Run the JD Edwards EnterpriseOne configuration script (EOne_cfg.ksh) which prompts you for values for your Oracle VM server names IP addresses. After the servers are created with valid values, you must re-run the script with the -syn switch to synchronize values for each server.

Caution:
This is an important step that is required to properly complete and synchronize the configuration of each VM server with valid values for your installation.

6. Install the workstations for developers and system administrators

Note:
You can concurrently install the Deployment Server and create the Enterprise Server, Database Server and HTML Web Server virtual machines. This can decrease the overall time it takes to complete the installation.

The supplied Deployment Server DVDs and templates for the Enterprise Server and the Database Server each contain a complete install of the three standard environments (PS910, PY910, and DV910) - with ESUs applied. The HTML Server template contains only the DV910 environment.

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

See Also:
Once you have completed the setup and applied fixes and modifications to your Prototype environment, you can copy the data, Central Objects, tested full package, and related records to your Production environment using the process described in the chapter entitled: Upgrading the Production Environment in the JD Edwards EnterpriseOne Applications Upgrade Guide for UNIX with Oracle, which is located on the Oracle Technology Network at this link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23319/title.htm

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

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

1.2.1 Understanding the Deployment Server Installation

Note:
The Oracle VM templates are used to create the Enterprise, Database and HTML Web Server virtual machines for JD Edwards EnterpriseOne. As is the case for all JD Edwards EnterpriseOne installations, the Deployment Server must be installed using a separate standalone installer on a Microsoft Windows machine.

The Deployment Server is the focus of the standard (non Oracle Virtual Template) Release 9.1 installation process. For non-production use with Oracle VM Templates, a Deployment Server is not required. You must have a Deployment Server in production environments or any environment in which you want to apply ESUs or perform Package Builds.

The installation program for the Deployment Server copies the Release 9.1 software and a language, if applicable, from the CD to the Deployment Server. From the Deployment Server, the Release 9.1 software is distributed to one or more workstations. Since the Deployment Server installer is separate from creating the Enterprise, Database, and HTML Server Virtual machines, you can run these installations concurrently to decrease the overall installation time.

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

1.2.2 Understanding the Creation of the Enterprise, Database and HTML Web Server Virtual Machines

The Oracle VM templates for the Enterprise Server and the Database Server virtual machines contain a complete installation of these three standard environments:

- PS910

- PY910

- DV910

Note:
Whereas previous releases of the Oracle VM templates for JD Edwards EnterpriseOne contained a PD910 environment, this release does not. Refer to the See Also below for information on how to create a Production environment.

See Also:
Once you have completed the setup and applied fixes and modifications to your Prototype environment, you can copy the data, Central Objects, tested full package, and related records to your Production environment using the process described in the chapter entitled: "Copying an Environment to Another Environment" in the JD Edwards EnterpriseOne Applications Installation Guide for UNIX with Oracle.

The Oracle VM template for the HTML Web Server virtual machine contains a complete installation of a single environment:

- JDV910

When you start these virtual machines for the first time, a script updates the database tables and control files on these servers with your machine names. This greatly reduces the overall install time for the servers. Since the Deployment Server installer is separate from creating the server virtual machines, these processes can be run concurrently.

1.2.3 Understanding the Database Server for Non-Virtualized Databases such as Oracle Exadata or ODA

Optionally you can choose to install the JD Edwards EnterpriseOne Database Server on a non-virtualized machine such as Oracle Exadata, Oracle RAC, Oracle Database Appliance (ODA), or any other database server. In that case, you would not install the VM template for the database server. Instead you would use a special version of the JD Edwards EnterpriseOne Platform Pack installer as described in the chapter of this guide entitled: Section 7, "Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server".

1.2.4 Understanding the Web Development Client Installation

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

1.3 Certifications (Formerly Known as Minimum Technical Requirements)

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Certifications (formerly known as 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

Refer to the Certifications tab on My Oracle Support and search for each of the JD Edwards components which you plan to install. Within each JD Edwards component that you want to install as an Oracle VM Template, search for the section within that component entitled: Virtualization Software.

For example, if you chose Certifications for the JD Edwards EnterpriseOne Enterprise Server, you would have these selections available for Virtualization Software:

1.4 Working With the Customer Checklist

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

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

This checklist helps to organize the required upgrade preparation:

- Review the Section called Environments Overview.

- Assess the network.

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

- Verify that the Oracle VM Server (OVS) host hardware and software meet minimum technical requirements.

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

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

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

1.5 Working With the Pre-Install Worksheet

A Pre-Install Worksheet is provided in this guide to gather information about your planned installation prior to installing the Oracle VM templates themselves. Using this worksheet decreases the chances for data entry errors and makes for a documented and repeatable process. Since the scripts used to create the Oracle VM templates are designed to execute only once, incorrect deployment will necessitate the deletion of the Oracle VM and require that the process be re-run. Refer to the section of this guide entitled: Section 4.2, "Completing the Pre-Install Worksheet".

This remainder of this section discusses these topics:

- Section 1.5.1, "Environments Overview"

- Section 1.5.2, "Updating the Operating System and Applications"

1.5.1 Environments Overview

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

Each environment shipped with Release 9.1 has a specific use. For more detail, refer to these sections in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix

- Understanding Environments

- Planner Environment (JDEPLAN)

- Pristine Environment (PS910)

- Deployment Environment (DEP910)

- Prototype Environment (PY910)

Note:
The Production environment is not shipped with Oracle Virtual Templates for JD Edwards EnterpriseOne.
Once you have completed the setup and applied fixes and modifications to your Prototype environment, you can copy the data, Central Objects, tested full package, and related records to your Production environment using the process described in the chapter entitled: Upgrading the Production Environment in the JD Edwards EnterpriseOne Applications Upgrade Guide for UNIX with Oracle, which is located on the Oracle Technology Network at this link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23319/title.htm

- Development Environment (DV910)

- Additional Considerations

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

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

1.5.2 Updating the Operating System and Applications

Caution:
It is the responsibility of the customer to update the installed and running VM templates for the Operating System and Application patches.

It is important to understand that the Oracle VM templates were created at a particular point and time and that after that they are not updated until they are recreated for a new release. This means that there likely have been patches and updates to the operating system and applications within the templates. Users should plan on updating the running images with OS patches and Application patches. Patches to the Oracle software delivered with the OVM 6 templates are available at this link:

https://support.oracle.com

For additional details on patches, refer to the section of this guide entitled: Appendix E, "Applying Patches".

Refer to the Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4 Readme part number V43874-01 for details on the exact OS and Applications contained within a Oracle VM template release.

1.6 Disk Space Requirements

The table below lists the disk spaces requirements for the individual components for all downloads available for the Oracle VM Templates for JD Edwards EnterpriseOne. You can use these requirements to size the disk space for your implementation.

Image Files or Template Name

Required Disk Space

JDE_OVM (JD Edwards OVM Tools)

108 KB

JDE_SYS (Linux operating system)

19 GB

JDE_EXA (Exalogic operating system)

JDE_ENT (Enterprise Server)

45 GB

JDE_DB (Database Server)

125 GB

JDE_WEB (HTML Server)

24 GB

JDE_BIP (BI Publisher Server)

49 GB

JDE_MBL (Mobile Server)

35 GB

JDE_AIS (Application Integration Services Server)

22 GB

Server Manager (Linux-based)

22 GB

2 Before You Begin the Installation

You should complete the tasks in this chapter before you begin the actual installation process. This chapter contains the following topics:

- Section 2.1, "Verifying Software and Hardware Requirements"

- Section 2.2, "Verifying the Disk Space Requirements"

- Section 2.3, "Host Name"

- Section 2.4, "Security Considerations"

- Section 2.5, "Overall Process Flow"

2.1 Verifying Software and Hardware Requirements

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

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

Note:
Make sure that you have taken and installed the latest Planner ESU from the Update Center on My Oracle Support. Failing to do so may prevent proper installation of the software.

Additionally, a new compiler requirement is added for Release 9.1. Before installing the Deployment Server, you should install a Microsoft Visual C++ compiler on it. The MTRs list supported C++ compilers on Microsoft Windows-based machines. Refer to Certifications (Formerly Known as Minimum Technical Requirements) in this guide.

2.2 Verifying the Disk Space Requirements

The amount of disk space you need for Release 9.1 software on the Deployment Server and OVS Host depends on many variables. In general, this release of OVM requires three times the base space requirement for each EnterpriseOne component. Configuring disk space is covered in this guide. Up-to-date disk space requirements for JD Edwards EnterpriseOne components are listed in the Release 9.1 Minimum Technical Requirements. Refer to Certifications (Formerly Known as Minimum Technical Requirements).

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

2.3 Host Name

The Oracle JD Edwards EnterpriseOne Application requires that Virtual Machine hostnames are not fully qualified with domain names. With the exception of the Enterprise Server, a maximum of 15 character mixed case alphanumeric name is allowed for names of these JD Edwards EnterpriseOne Servers:

- Enterprise Server (exception maximum of 13 characters)

- Database Server

- HTML Server

- BI Publisher Server

- Mobile Server

- Deployment Server

These names should correctly resolve using the local DNS. The configuration of these items is the responsibility of the local network and system administrators.

2.4 Security Considerations

The Oracle database users created for your JD Edwards EnterpriseOne Database Server have been set up with the default passwords (for example, JDE user has JDE for the password). You should change the passwords for the Oracle database users within the Oracle DBMS.

A minimal JD Edwards EnterpriseOne security definition has been shipped with your Database Server. Follow the instructions in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix to change the passwords within EnterpriseOne for JDE, DV910, PS910, and PY910 so they match any changes you make to the passwords for the Oracle Database users.

2.5 Overall Process Flow

One of the purposes of the following flow chart is to help you determine which processes can be done in parallel. Because the Deployment Server installation is the most time consuming installation in the entire process, the reason for having the Change Assistant and Server Manager installations at the beginning of the flow is so that after they installed you could be using those tools while the Deployment Server installation is running. That is, if applicable to your implementation, you could be using Change Assistant to download ESUs and software components and you could be deploying software components (such as Tools Releases) using Server Manager while the Deployment Server installer is running.

While there is no dependency between the steps shown in flow chart, you cannot run more than one installation (Change Assistant, Server Manager, and Deployment Server) at the same time on the same machine.

The following diagram (which spans two pages) illustrates the overall process flow for the entire JD Edwards EnterpriseOne installation process using Oracle VM templates.

Process Flow - Deployment Server and Foundation Servers (Part 1 of 2)

Process Flow - Optional Servers (Part 2 of 2)

3 Working with the Deployment Server

This chapter discusses:

- Section 3.1, "Understanding the Deployment Server"

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

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

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

- Section 3.5, "Installing the Deployment Server"

- Section 3.6, "Working with the Development Client Installation"

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

- Section 3.8, "Downloading and Installing the Latest Software (Optional Except for Planner Update, which is Recommended)"

- Section 3.9, "Troubleshooting Deployment Server Installation"

- Section 3.10, "Configuring the Planner Databases"

3.1 Understanding the Deployment Server

The Deployment Server for JD Edwards EnterpriseOne must reside on an Intel Pentium-based computer running Microsoft Windows. Optionally you can choose to install the Deployment Server into a virtual machine for Microsoft Windows. For non-production use with Oracle VM Templates, a Deployment Server is not required. You must have a Deployment Server in production environments or any environment in which you want to apply ESUs or perform Package Builds.

The JD Edwards EnterpriseOne software installation and upgrade programs enable you to create and maintain installation plans and deploy Release 9.1 to the Enterprise Servers and workstations.

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

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

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

- A local OEE database must exist before you can run the OUI-based Deployment Server installer. The JD Edwards program called InstallManager is used to start the installation of the local OEE database.
No separate end-user licensing is required for installation of the local OEE database. It should be noted, however, that the installed OEE database is not fully functional relative to the commercial versions of the Oracle databases that are available.

- Install the JD Edwards EnterpriseOne Deployment Share on the same machine as the Deployment Client or on a remote share.
The default is to install the Deployment Share and the Deployment Client on the same machine. If you choose to install on a remote share, the target machine can be Windows or Linux SAMBA based.

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

3.2 Local Oracle Enterprise Edition (OEE) Considerations

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

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

This section discusses these topics:

- Section 3.2.1, "32-Bit Oracle Database Client (Required to Run EnterpriseOne)"

- Section 3.2.2, "EnterpriseOne Application P96717"

- Section 3.2.3, "Best Practices for OEE Performance"

3.2.1 32-Bit Oracle Database Client (Required to Run EnterpriseOne)

You must install a 32-bit version of the Oracle database client and then copy your tnsnames.ora file to a subdirectory under the database client installation directory.

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

To install a 32-bit Oracle database client:

1. Download the 32-bit Oracle 11g database client from the Oracle Software Delivery Cloud (https://edelivery.oracle.com).

2. Install the database client.

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

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

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

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

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

3. Click the Advanced tab.

4. Click Environment Variables….

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

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

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

8. Click OK.

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

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

11. Close the Control Panel's System window.

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

x:\oracle\E1Local\NETWORK\admin\

To:

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

3.2.2 EnterpriseOne Application P96717

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

- Import Tablespace

- Export Tablespace

- Create Tablespace

- Drop Tablespace

3.2.3 Best Practices for OEE Performance

You should always verify that your Deployment Server machine meets the MTRs (refer to Section 1.3, "Certifications (Formerly Known as Minimum Technical Requirements)"). The local Oracle database performs best on hard drives that are not fragmented or full. Additionally, the following table lists some guidelines for minimum configurations.

Specification

Recommendation

RAM

2 GB minimum

Page File Size

Minimum setting should be two times the amount of memory

Disk Space Usage

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

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

Local Database Name

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

Failure to use the exact mixed case will lead to decreased performance of JD Edwards EnterpriseOne on the Deployment Server.

3.3 Obtaining and Preparing the Deployment Server Install Image

You install the Deployment Server Install image from DVD images obtained from the Oracle Software Delivery Cloud (https://edelivery.oracle.com).

To install from images downloaded from the Oracle Software Delivery Cloud:

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

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

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

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

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

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

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

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

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

3.4 Working with JDBC Drivers on the Deployment Server

The Deployment Server delivers the ojdbc5.jar for connecting to both the local and the enterprise Oracle databases

3.5 Installing the Deployment Server

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

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

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

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

Microsoft Windows 2008

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

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

Server

Mandatory Component

Optional Components

Deployment Server

Deployment Client
EnterpriseOne Files

Development environment
Prototype environment

Pristine environment

The installation process for the Deployment Server performs these functions:

- Installs the objects from the CDs.

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

- Updates the Microsoft Windows Registry.

Note:
You can concurrently run the Deployment Server installer and perform the creation of the Enterprise, Web and Database virtual machines.

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

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

This section describes these topics:

- Section 3.5.1, "Prerequisites"

- Section 3.5.2, "Installation Process Flow"

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

- Section 3.5.4, "Understanding Destination Paths"

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

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

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

3.5.1 Prerequisites

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

3.5.2 Installation Process Flow

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

3.5.3 Before Launching the Deployment Server Installer

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

Tip: Installation Methods

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

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

- From a downloaded and unzipped image of the installation DVDs that was obtained from the Oracle Software Delivery Cloud (https://edelivery.oracle.com).

3.5.4 Understanding Destination Paths

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

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

Oracle Home Path

Oracle Home Name

Comment

C:\JDEdwards\E910

JDE_DEP910_HOME

This is the Oracle Home of the Deployment Server

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

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

To use the InstallManager to install a local database:

1. Obtain the appropriate disk images from the Oracle Software Delivery Cloud (https://edelivery.oracle.com) for the local database you wish to install on your Deployment Server.

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

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

3. Locate the unzipped image for the Deployment Server installation DVDs.

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

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

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

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

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

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

3.5.6 Examine the Local Database Installer Logs

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

1. Examine the log file

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

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

where the syntax is:

- yyyy is the year

- mm is the month

- dd is the day of the month

- hh is the hour

- mm is the minutes

- ss is the seconds

- AM|PM is either AM or PM

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

2. Verify that the OEE services exist and are running

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

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

OracleServiceE1LOCAL

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

3.5.7 Understanding the JD Edwards EnterpriseOne Deployment Server Installer

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

This section describes:

- Section 3.5.7.1, "Understanding EnterpriseOne Files Location"

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

- Section 3.5.7.3, "Mandatory Post Installation Tools Accelerator"

3.5.7.1 Understanding EnterpriseOne Files Location

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

- Development

- Prototype

- Pristine

- Production

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

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

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

Using a Remote Machine as the Deployment Server

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

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

E:\JDEdwards\E910

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

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

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

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

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

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

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

3.5.7.2 Running the JD Edwards EnterpriseOne Deployment Server Installer

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

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

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

2. Locate the unzipped image for the Deployment Server installation.

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

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

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

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

5. This process opens a Microsoft Windows command window as shown in the below example.

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

6. On Welcome, select the Next button.

7. On Select Installation Type, you must select the Custom radio button for this installation type. This is required because it is mandatory for all four path codes to be loaded.

Note:
The Typical selection installs environments for Deployment Client (Planner), prototype, pristine and also installs JD Edwards EnterpriseOne files on the local machine. The Typical selection installs environments for Deployment Client (Planner), prototype, pristine and also installs JD Edwards EnterpriseOne files on the local machine. This selection will not work for this process.
The Custom selection lets you choose the specific environments you want to install on the deployment server. The deployment client (Planner) is always installed on the local machine. You may choose to install JD Edwards EnterpriseOne Files and environments on a remote machine. In that case, first you need to setup a mapped drive as described in the section of this guide entitled: Section 3.5.7.1, "Understanding EnterpriseOne Files Location". This selection is required for this process.

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

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

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

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

On Specify Home Details, complete these fields:

Field

Description

Name

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

Path

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

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

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

10. Select the Next button.

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

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

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

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

- Development Environment

- Prototype Environment

- Pristine Environment

Tip:
Use the Select All button to select all components.

Caution:
By default all environments are selected. However, since Oracle VM Templates for JD Edwards is not shipped with the Production Environment, you should manually deselect that checkbox, as shown in the preceding screen shot.

12. Click the Next button.

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

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

C:\JDEdwards\E910

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

Z:\

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

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

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

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

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

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

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

14. Select the Next button.

15. On Deployment Server for OVM, change the following values to match what you are using for your Virtual Machines for Enterprise Server, Database Server and Web Server:

- Location Name
Specify the same Deployment Location that you are using for the Database Server.

- Deployment Server Name
You should only change this value from the supplied value if you are installing to a Remote Share on a different machine. If that is the case, then supply the name of the Remote Share machine.

Caution:
On this screen only, you should not enter a fully qualified machine name. You should only enter server names without the domain. The values you enter for the Deployment Server Name on this screen are used to populate the Planner database, which for these fields has a restriction of 15 alphanumeric characters.

- Database Server
Specify the name of your Database Server.

- HTML Server
Specify the name of your HTML Server.

- Enterprise Server
Specify the name of your Enterprise Server.

16. Select the Next button.

17. On Oracle connect string, Enterprise database connect string, you can change the connect string value only if you are installing to a non-virtualized database, such as Exadata or ODA.

Caution:
If you are installing a virtual database using the Oracle VM templates for JD Edwards EnterpriseOne, you must accept the default value, which is ovsorcl. If you change this value for use with a virtualized Oracle database, all database server functions will fail.

18. Select the Next button.

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

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

20. Select the Next button.

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

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

22. Click the Install button.

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

23. When the installation of the Deployment Server finishes, the End of Installation screen is displayed.

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

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

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

3.5.7.3 Mandatory Post Installation Tools Accelerator

After the Deployment Server is installed, you must run the TLOVM001 Tools Accelerator. You will not be able to start services until you have run this accelerator. For details on locating this Tools Accelerator and a description of its functions, refer to the procedure in the section of this guide entitled: Section 3.10, "Configuring the Planner Databases".

3.6 Working with the Development Client Installation

After the Deployment Server is installed for Oracle VM Templates implementations, before you install the Development Client (also called the fat client), you must complete the procedures in this section entitled:

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

- Section 3.6.2, "WebSphere Express Considerations"

- Section 3.6.3, "Add the Security Server Name to the Development Client jde.ini"

3.6.1 Updating the oraparam.ini File

If you when you are installing the VM Template for the Enterprise Server, you did not give the requisite non-qualified name for the Deployment Server, you will need to modify the oraparma.ini file to include both the non-qualified name and the fully qualified name, as described in this procedure.

Prior to submitting UBEs on the Development Client, you must to manually update the oraparam.ini file on the Deployment Server using this procedure.

1. Navigate to this directory on the Deployment Server:
OneWorldClientInstall\Install

2. Use an ASCII editor to edit the oraparam.ini file.

3. Within the oraparam.ini file, search for this section:
[FileLocations]

4. Change the PackageInf setting to remove the segment \\DEPLOYMSTR\E910 as shown below:
from:

PackageInfs=\\<Your Deployment Server Name>\E910\\DEPLOYMSTR\E910\pacakge_inf

to:

PackageInfs=\\<Your Deployment Server Name>\E910 \pacakge_inf

5. Change the CurrentReleaseMasterPath setting to remove the segment \\DEPLOYMSTR\E910 as shown below:
from:

=\\<Your Deployment Server Name>\E910\\DEPLOYMSTR\E910

to:

=\\<Your Deployment Server Name>\E910

6. Save and close the oraparam.ini file.

3.6.2 WebSphere Express Considerations

If you do not have WebSphere Express installed on your Development Client, before you install the Development Client you must follow the procedure in this section or else the Install Features will fail.

1. Login to the Deployment Server.

2. Go to this directory:
X:/JDEdwards/E910_1/package_inf

3. Use an ASCII editor to open the DV910FA.inf file.

4. In the [Features] section, comment out this entry:
WEBDEVELF=\\<MachineName>\E910\package_inf\feature_inf\WEBDEVELF_1.INF

5. Save and close the DV910FA.inf file.

3.6.3 Add the Security Server Name to the Development Client jde.ini

After you have installed the Development Client, before you can log onto it, you must follow this procedure to add the Security Serve name to the Development Client jde.ini file.

1. On the Development Client machine, use an ASCII editor to open the jde.ini file.

2. In the [Security] section, locate this setting:
SecurityServer

3. Enter a valid value for the Security Server for your installation. For Oracle VM Template implementations, this value is the same name as your Enterprise Server machine name.

4. Save and close the jde.ini file.

3.7 Adding Additional Environments (Rerunning the Deployment Server Installer)

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

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

3.8 Downloading and Installing the Latest Software (Optional Except for Planner Update, which is Recommended)

This install image of Deployment Server and matching OVM machines was updated with the latest available ESUs and Tools Release at the Tools 9.1 Update 3 general availability time frame. While you do not need to install additional software changes unless you have a specific need for them, it is recommended and always a best practice to download the latest Planner Update. If you are not adding any Tools or ESU changes, you can skip to the section of this guide entitled: Section 3.9, "Troubleshooting Deployment Server Installation".

If you decide to update to get the latest software, you should use Change Assistant to download and install the latest Tools Release, Tools Release Patch, and Planner Update ESU from the JD Edwards EnterpriseOne Update Center.

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

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

This section discusses:

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

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

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

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

1. From the JD Edwards EnterpriseOne Update Center homepage, download the latest Tools Release Patch (for example, 9.1.1.0) and Tools Release documentation.

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

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

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

3.8.2 Installing the Latest Planner Update and Running the Special Instructions

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

To install the latest planner update:

1. From My Oracle Support, download the latest planner update for your Tools Release to the Deployment Server.

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

3. You must enter a valid JD Edwards EnterpriseOne user and password to initialize the Planner.
The shipped values are JDE for the user and JDE for the password.

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

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

Tip:
If the folder into which you expanded the Planner Update is empty, you should run the self-extracting executable (JMnnnnn.exe) again. When the Welcome screen comes up, click on Cancel to quit.

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

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

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

- SpecialInstrs.bat

- R98403XB XJDE0002

3.9 Troubleshooting Deployment Server Installation

This section discusses:

- Section 3.9.2, "OEE Installer Logs"

- Section 3.9.3, "Configuration Files"

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

- Section 3.9.5, "Oracle Enterprise Edition"

- Section 3.9.6, "UBE Submission Failed on the Development Client"

3.9.1 Verify Local Planner Tablespaces are Not Attached

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

jdedwards\e910\planner\data\DropPlannerDB.BAT

jdedwards\e910\planner\data\detach_metadata.bat

3.9.2 OEE Installer Logs

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

- x:\jdedebug.log

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

- x:\jde.log

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

- C:\ReconfigureMSDE.log

- \InstallLogs\attach_plannerdata.log

- \InstallLogs\attach_plannerspec.log

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

ConfigureDV910FAspec.log

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

DetachDV910FAspec.log

See Also

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

3.9.3 Configuration Files

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

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

- jde.ini

- jdbj.ini

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

- jde.ini

[DB SYSTEM SETTINGS]
Type=E
LOBFlag=Y

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

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

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

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

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

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

3.9.4 Path Code Master (F98611)

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

EMDBSY Value

Spec Type

Local DB Type

0

TAM

MSDE

1

XML

MSDE

2

TAM

SSE

3

XML

SSE

5

XML

Oracle

3.9.5 Oracle Enterprise Edition

This section discusses these topics:

- Section 3.9.5.1, "File Locations"

- Section 3.9.5.2, "Rebooting the Deployment Server"

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

- Section 3.9.5.4, "Process Explorer"

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

- Section 3.9.5.6, "Deployment Server Installation Problems"

- Section 3.9.5.7, "Runtime Problems"

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

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

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

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

- Section 3.9.5.12, "Local Oracle Database Configuration"

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

3.9.5.1 File Locations

This section discusses the location for these critical files:

- Section 3.9.5.1.1, "Oracle Installation Directory"

- Section 3.9.5.1.2, "OEE Logs"

- Section 3.9.5.1.3, "tnsnames.ora"

3.9.5.1.1 Oracle Installation Directory

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

C:\Oracle\E1Local

Note:
This location can be changed at installation time.

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

C:\Oracle\E1Local

Note:
This location can be changed at installation time.

3.9.5.1.2 OEE Logs

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

Log File

Location

Oracle import log for data

<E1_install_dir>\<pathcode>\Data\imp*.log

Oracle export log for data

<E1_install_dir>\<pathcode>\Data\exp*.log

Oracle import log for specifications

<E1_install_dir>\<pathcode>\Spec\imp*.log

Oracle export log for specifications

<E1_install_dir>\<pathcode>\Spec\exp*.log

Deployment Server and local Oracle database install logs

<E1_install_dir>\InstallLogs\*.log

Local Oracle database runtime

.\admin\E1Local\bdump

Local Oracle database listener

alert_e1local.log

Local Oracle database runtime and listener

.\NETWORK\ADMIN\*.log

Log for ReconfigureMSDE.exe

C:\ReconfigureMSDE.log

Local Oracle database install logs

c:\Program Files\Oracle\Inventory\logs

Log for OEESetup.exe

c:\OEEInstall.log

3.9.5.1.3 tnsnames.ora

The tnsnames.ora file is located in these directories:

..\Oracle\E1Local\NETWORK\ADMIN
..\E910\client

3.9.5.2 Rebooting the Deployment Server

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

3.9.5.3 EnterpriseOne Access to the Local Oracle Database

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

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

Local Oracle Database Account

Default Password

System

Generated and encrypted by the Deployment Server installer.

Sys

Generated and encrypted by the Deployment Server installer.

JDE

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

<tablespace_name>
For example:

- JDESY910

- JDEOL910

<tablespace_name>
For example:

- JDESY910

- JDEOL910

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

3.9.5.4 Process Explorer

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

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

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

To use Process Explorer:

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

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

3. Click the Search button.

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

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

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

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

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

3.9.5.5 Verifying the Local Oracle Database Installation

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

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

C:\Program Files\Oracle\Inventory\logs

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

3.9.5.6 Deployment Server Installation Problems

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

- The local Oracle database service OracleServiceE1LOCAL is running.

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

3.9.5.7 Runtime Problems

This section discusses:

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

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

- Section 3.9.5.7.3, "tnsnames.ora"

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

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

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

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

SQLPlus.exe system/admin@E1Local

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

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

3.9.5.7.3 tnsnames.ora

When the Deployment Server installer installs the local Oracle database (E1Local), the \bin directory is added to the start of the Windows PATH. If you have both the local Oracle database and the Oracle client installed (for example, if you are connecting to an Oracle database on a machine other than the Deployment Server), the local Oracle database version of the executables and tnsnames.ora are used. The Deployment Server installer will rename any tnsnames.ora file that it finds in the location below, and put a configured tnsnames.ora in this location.

<E1Local_installation_path>\network\admin

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

Note:
If the deployment server is in a different domain than the Database Server, the configured tnsnames.ora may not have the correct domain name for your Database Server. If not, you should edit the tnsnames.ora file in this location:
c:\oracle\E1local\network\admin

This tnsnames.ora must specify the correct domain name for the Database Server for the ovsorcl database. Copy and overlay the corrected tnsnames.ora file into this directory:

JDEdwards\E910\client

This tnsnames.ora file is used for JD Edwards EnterpriseOne Development Client install.

This configured tnsnames.ora must be copied to the network\admin directory under the 32-bit Client install for Oracle, and also into the ..\E910\client directory for use by Client Install.

3.9.5.8 Administering the Local Oracle Database Using SQL Plus

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

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

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

SQLPlus.exe JDESY910/JDESY910@E1Local

3.9.5.9 Encrypting the Password of the Local Oracle Database

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

SQLPlus.exe system/admin@E1Local

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

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

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

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

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

3. Be sure the E1Local database is selected.

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

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

6. Click OK.

7. Click OK.

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

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

3.9.5.10 Decrypting the Password of the Local Oracle Database

To decrypt the system account password:

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

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

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

3. Be sure the E1Local database is selected.

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

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

6. Reenter the new password and click OK.

7. Click OK.

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

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

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

3.9.5.11 Import and Export Tablespaces to the Local Oracle Database

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

For Planner Databases:

<E1_install_dir>\planner\data\attach_planner.bat

<E1_install_dir>\planner\data\detach_planner.bat

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

<E1_install_dir>\planner\Data\attach_metadata.bat

<E1_install_dir>\planner\Data\detach_metadata.bat

This section discusses:

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

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

3.9.5.11.1 Import Tablespace Script (attach_planner.bat)

To use the import tablespace script:

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

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

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

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

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

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

For example:

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

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

3.9.5.11.2 Export Tablespace Script (detach_planner.bat)

To use the export tablespace script:

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

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

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

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

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

For example:

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

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

3.9.5.12 Local Oracle Database Configuration

The <E1_install_dir>\OneWorld Client Install\install.ini file specifies that the OEE database will be installed by the Web Development client (workstation) installer.

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

Caution:
The ”,” character is required at the end of the line that specifies the OEESetup.exe.

The local Oracle database configuration requires that the Oracle DB installer be located in this directory:

<E1_install_dir>\OneWorld Client Installer\ThirdParty\ORACLE

3.9.5.13 Deployment.inf and <Package_name>.inf

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

- Deployment.inf

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

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

[Oracle Databases]
JDELocal_DV910=ORACLE
SPEC_DV910FA=ORACLE

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

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

3.9.6 UBE Submission Failed on the Development Client

If you cannot submit UBEs from the Development Client (also called the ”fat” client), it may be because you specified a fully qualified name instead of a non-qualified name for the Deployment Server.

Use this procedure to specify both a non-qualified and fully qualified name for the Job Queue entries.

1. Login to the Development Client.

2. Fastpath to P986130.

3. If you specified a fully qualified name during the Oracle VM Template installation, you will see entries for QBATCH and I-ACTIVE with the machine name as fully qualified machine name (for example: machine-name.domain.name)

4. Select the QBATCH entry and click the Copy icon.

5. On Job Queue Revisions, complete these fields:

- Host
Enter the non-qualified machine name without the domain name. This can be a maximum of 15 alphanumeric characters (no special characters).

- Job Queue
Enter QBATCH.

- Port
Enter the value 6016.

6. Click the OK button.

7. On the Work with Job Queue form, click the Find button and verify the entry is available.

3.10 Configuring the Planner Databases

The images for the installation of the Oracle VM Deployment Server include the Installation Plan created for you at Oracle. You do not need to create and run an Installation Plan for the PS910, PY910, and DV910 environments. However, there are some steps that normally run during an Installation plan that must be done on your Deployment Server. An Oracle Tools Accelerator has been provided to do these steps, and must be run at this point.

Note:
This step cannot be run until you have started the OVM Database Server or loaded the Non-Virtualized Database Server. This is required because this step updates tables in the Database Server.

Use this procedure to configure the Planner databases:

1. If you have not done so already, install the latest version of Change Assistant.

2. Set the Preferences in Change Assistant to store and find ESUs in your install location. For example:
c:\JDEdwards\E910\Change Assistant\Downloads

3. Start Change Assistant and deploy the Tools Accelerator TLOVM001_20_99.par, which is obtained from the location specified in the preceding step. This Tools Accelerator does the following:

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

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

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

4. Configures the Package Feature records

5. Configures the manifest records for these shipped packages:
- PS910FA

- PY910FA

- DV910FA

Caution:
If you do not install all four standard environments as recommended, the Tools Accelerator will fail at this point for each environments that is not installed. However, this does not prevent it from running correctly for the standard environments that you did install.

Note:
If you re-load the OVM database Server or non Virtualized Database Server, you must re-run this process.

4 Working with Oracle VM Templates for JD Edwards EnterpriseOne

This chapter contains the following topics:

- Section 4.1, "Implementing the Oracle Database With or Without Oracle VM Templates"

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

- Section 4.3, "Working with the Oracle VM Image Files for JD Edwards EnterpriseOne"

- Section 4.4, "Working with JD Edwards OVM Tools (config.sh Configuration Script)"

4.1 Implementing the Oracle Database With or Without Oracle VM Templates

The installation process allows you to deploy the JD Edwards EnterpriseOne database server either as an Oracle VM virtual machine or to a non-virtualized database server. You can choose to run the Oracle database as follows:

- VMs on a Linux x86 machine
You can deploy all Oracle VM templates, including the Oracle Database template, to a Linux x86 machine. This is fully support ed for both non-production environments, such as evaluation or testing, as well as production environments.

- Oracle Enterprise Database on a Non-Virtualized Machine
The non-virtualized database could be an Oracle Exadata, Oracle Database Appliance (ODA), Oracle Real Application Cluster (RAC), or other similar machine. In this case you would not use a VM template for the database, but instead you would install the database using a special version of the EnterpriseOne Platform Pack installer that is designed to work with the other base and optional Oracle VM Templates that are described in this guide. To use this installer refer to chapter of this guide entitled: Chapter 7, "Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server".

4.2 Completing the Pre-Install Worksheet

You can use the Pre-Install Worksheet in this section to gather information required to answer the questions for which you will be prompted by the template installer as it executes. Prior to installing any template, it is highly recommended that you complete the Pre-Install Worksheet with the requisite information. By doing so you will reduce the potential for errors due to incorrect data entry information.

Caution:
The scripts to configure the JD Edwards EnterpriseOne system are not tied to actual configuration of the system. That is, before you run the scripts you must know the IP address, hostname, and system configuration of the target machine in order to match to the expected configuration of JD Edwards EnterpriseOne. Filling out the Pre-Install Worksheet helps guarantee an accurate and valid configuration.

Caution:
The implementation of the JD Edwards EnterpriseOne delivered with the Oracle VM Templates has Demo data loaded in the DV910 environment. Refer to Appendix C, "Security and Demo Data Configuration" for additional details.

Tip:
Contact your network administrator to attain valid network settings for your network prior to creating new VM Guests.

The following image shows the Pre-Install Worksheet:

4.3 Working with the Oracle VM Image Files for JD Edwards EnterpriseOne

The JD Edwards EnterpriseOne Oracle VM (OVM) system implementation requires either an FTP or HTTP server to upload images files into the OVM repository. Once that configuration is in place, you can download the EnterpriseOne System and Application zip files from the Oracle Software Delivery Cloud (https://edelivery.oracle.com).

The JD Edwards EnterpriseOne OVM is delivered in these zip files and images:

- One (1) zip file containing JD Edwards EnterpriseOne OVM Tools for Template Extraction and Configuration

- One (1) System Image
This is the Linux 5.8 VM system.

- Seven (7) Application Images
These are the JD Edwards EnterpriseOne components:

1. Enterprise Server

2. Database Server

3. HTML Server

4. BI Publisher Server

5. Mobile Server

6. Application Interface Services (AIS) Server

7. Server Manager (Linux-based)

Disk Space Requirements:
For disk space requirements for each of the above-listed zip file or image, refer to the section of this guide entitled: Section 1.6, "Disk Space Requirements".

You can obtain the download files for the Oracle VM Templates for JD Edwards from the Oracle Software Cloud (https://edelivery.oracle.com. The following table lists all available download files for Oracle VM Templates for JD Edwards EnterpriseOne:

Image File Name

Description

Download Directory

V43846-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Deployment Server for Use with Express Installation 1 of 6

NA

V43847-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Deployment Server for Use with Express Installation 2 of 6

NA

V43848-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Deployment Server for Use with Express Installation 3 of 6

NA

V43849-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4- Deployment Server for Use with Express Installation 4 of 6

NA

V43850-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4- Deployment Server for Use with Express Installation 5 of 6

NA

V43851-01

JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Deployment Server for Use with Express Installation 6 of 6

NA

V43852-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 Enterprise Server 1 of 2

JDE_ENT

V43853-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 Enterprise Server 2 of 2

JDE_ENT

V43854-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - HTML Server (WebLogic Server 12.1.2.0)

JDE_WEB

V43855-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 1 of 7

JDE_DB

V43856-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 2 of 7

JDE_DB

V43857-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 3 of 7

JDE_DB

V43858-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 4 of 7

JDE_DB

V43859-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 5 of 7

JDE_DB

V44308-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 6 of 7

JDE_DB

V45140-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Database Server (Oracle Database 12.1.0.1) 7 of 7

JDE_DB

V43861-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and tools 9.1.4.4 - Oracle Linux 5.8 System

JDE_EXA

V43862-01

Oracle VM Template for JD Edwards EnterpriseOne - Oracle Exalogic 2.0.4.0.0 Base Guest Template for Exalogic Linux x86-64 (64 bit)

JDE_EXA

V43863-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Non Virtualized Database Server (Oracle Database 12.1.0.1)

NA

V43864-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BSSV and ADF Server (WebLogic Server 10.3.5) (1/2)

JDE_MBL

V43865-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BSSV and ADF Server (WebLogic Server 10.3.5) (2/2)

JDE_MBL

V43866-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BI Publisher Server 11.1.1.7.1 (1/5)

JDE_BIP

V43867-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BI Publisher Server 11.1.1.7.1 (2/5)

JDE_BIP

V43868-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BI Publisher Server 11.1.1.7.1 (3/5)

JDE_BIP

V43869-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BI Publisher Server 11.1.1.7.1 (4/5)

JDE_BIP

V43870-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - BI Publisher Server 11.1.1.7.1 (5/5)

JDE_BIP

V43871-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Application Interface Services Server (Weblogic Server 12.1.2.0)

JDE_AIS

V43872-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Server Manager (Weblogic Server 12.1.2.0) (1/4)

JDE_SM

V43873-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Server Manager (Weblogic Server 12.1.2.0) (2/4)

JDE_SM

V44309-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Server Manager (Weblogic Server 12.1.2.0) (3/4)

JDE_SM

V44310-01

Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Server Manager (Weblogic Server 12.1.2.0) (4/4)

JDE_SM

V43874-01

Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 Readme

NA

V43875-01

Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Configuration Utility and Manifest

JDE_OVM

4.4 Working with JD Edwards OVM Tools (config.sh Configuration Script)

This release the Oracle VM Templates for JD Edwards EnterpriseOne includes a set of tools to help with the configuration of the VM images in zip files that you downloaded as listed in the preceding section of this guide entitled: Section 4.3, "Working with the Oracle VM Image Files for JD Edwards EnterpriseOne".

This section describes these tasks:

- Section 4.4.1, "Installing the JD Edwards OVM Tools"

- Section 4.4.2, "Creating the Directory Structure for the Oracle VM Templates for JD Edwards EnterpriseOne"

- Section 4.4.3, "Working with the Configuration Script"

4.4.1 Installing the JD Edwards OVM Tools

The JD Edwards OVM tools (called JDE_OVM) are included in the VV43875-01.zip file. You should place this zip file on a work machine with adequate disk space for this zip and the total of each image you intend to install.

Disk Space Requirements:
For disk space requirements for each of the above-listed zip file or image, refer to the section of this guide entitled: Section 1.6, "Disk Space Requirements".

The V43875-01.zip file contains files which comprise the JDE_OVM tools that you can use to extract and configure the JD Edwards EnterpriseOne VM templates. In order to use the JDE_OVM tools, you must have these packages installed

- lvm2-2.02.88-8.100.3.el1 (only required for Exalogic)

- dialog-1.0.20051107-1.2.2

Note:
The dialog package is available from the Oracle Linux repository.

On a work machine on which you intend to install the JD Edwards OVM Tools and VM images:

1. Create a directory into which you will place the V43875-01.zip file which contains the JD Edwards OVM Tools. For example:
mkdir -p /OVS/configTest

2. Place the downloaded V43875-01-01.zip into the directory you created in the previous step.

3. Unzip the file using this command:
unzip V43875-01.zip

The unzip action should have created a directory named JDE_OVM.

4. Change directory to JDE_OVM, which should have been created in the previous step.
cd JDE_OVM

This directory should contain the following extracted files:

- config.sh

- Help.doc

- jdedwards.conf

- OVM7.mft

- setup.sh

4.4.2 Creating the Directory Structure for the Oracle VM Templates for JD Edwards EnterpriseOne

You will run the setup.sh script to create an empty but complete directory structure that supports all the VM templates supported by the current release. As it executes the script reads the manifest file (*.mft) for the current release and informs you which Oracle eDelivery part number files go into each directory. This helps you to obtain the required image files for your implementation and place them in the appropriate directory so that can be further configured and deployed by the JDE_OVM tools.

To create the directories for the Oracle VM Templates for JD Edwards EnterpriseOne, run this script:

setup.sh

This script creates directories for all the Oracle VM templates for JD Edwards EnterpriseOne, as shown in the right-most field in this example:

Caution:
Although the setup.sh creates the complete directory structure (which is empty at this point), you only need to download and configure the templates that you intend to use in your installation. You should not delete the directories the template directories that are created by the setup.sh script. These directories are shown in the graphic above and listed alphabetically here as well:

- JDE_AIS

- JDE_BIP

- JDE_DB
If you are planning for a non-virtualized database you should delete the JDE_DB directory or leave it empty (that is, you should not upload the database image into it). If this directory does not exist or does not contain a database Oracle VM image, then the config.sh runs in a mode that assumes a non-virtualized database and configures accordingly.

- JDE_ENT

- JDE_EXA

- JDE_MBL

- JDE_OVM

- JDE_SM

- JDE_SYS

- JDE_WEB

4.4.3 Working with the Configuration Script

You can use the config.sh configuration script to perform these functions:

- Verify the correct files exist in the correct locations

- Extract and merge multi-part files

- Copy system images

- Prompt for input of server names and IP address

- Configure and pair the System and Application images
Deploy the paired System and Application image files

This section describes these functions of the config.sh script:

- Section 4.4.3.1, "Manifest Check"

- Section 4.4.3.2, "Extract and Merge"

- Section 4.4.3.3, "Copy System"

- Section 4.4.3.4, "Server Configuration"

- Section 4.4.3.5, "JD Edwards Foundation Setup"

- Section 4.4.3.6, "JD Edwards Server Manager Setup"

- Section 4.4.3.7, "JD Edwards BIP Server Setup"

- Section 4.4.3.8, "JD Edwards Mobile Server Setup"

- Section 4.4.3.9, "JD Edwards AIS Server Setup"

- Section 4.4.3.10, "Completing the config.sh Script"

- Section 4.4.3.11, "Configuring for a Non-Virtualized or Exadata Database"

- Section 4.4.3.12, "Adding an Additional Enterprise Server (Standalone)"

- Section 4.4.3.13, "Adding an Additional HTML Server (Standalone)"

For an installation on an x86 Linux machine

1. Ensure the dialog-1.0.20051107-1.2.2 package exists on the machine on which you are running the config.sh script.

2. Ensure the lvm2-2.02.88-8.100.3.el1 package does not exist on the machine on which you are running the config.sh script.

3. Run the config.sh script with the -nodep startup parameter:
> config.sh -nodep

Note:
The display of a dialog menu requires a screen that supports a resolution of 120x48. Further, you must either have a connection package that supports screen scale or else you must the administrative console.

For an installation on an Exalogic machine

1. Ensure the dialog-1.0.20051107-1.2.2 package exists on the machine on which you are running the config.sh script.

Note:
The dialog package is available from the Oracle Linux repository.

2. Ensure the lvm2-2.02.88-8.100.3.el1 package exists on the machine on which you are running the config.sh script.

3. Run the config.sh script with no startup parameters:
> config.sh

The procedures in this section illustrates a typical execution of the config.sh script using a virtualized database (Oracle VM Template). This example assumes the values shown on the Example Pre-Install Worksheet shown below.

4.4.3.1 Manifest Check

This section describes the Manifest function of the config.sh script.

1. Launch the config.sh script.

2. The first function of the Manifest Check, which first checks the contents of the OMV7.mft file. Next it checks for the existence of the required of the directory structure that was created when you ran the setup.sh script.
Below is an example of a successful Manifest Check.

Note:
The preceding example of Manifest Check shows the directory structure with a path containing /OVS/configTest. This is a variable value that depends on the structure you have defined for your installation.

3. The preceding screen example shows the Manifest Check process has completed successfully. You can determine that the entire process completed successfully when you see the Manifest:1 Done message at the bottom of the screen.
Press the Enter key to continue with script processing.

4.4.3.2 Extract and Merge

After the Manifest Check, the config.sh script continues with the Extract and Merge functions.

1. The following screen shows the starting of the Extract All function.

The preceding screen example shows that the JDE_DB directory was checked. Since no image was located in that directory, the next step is to check the manifest to determine which files are required to build a database image. The first file (in this example V00007-01.zip) was found and therefore can be extracted as shown in the following screen example.

The above example indicates that all the part files for the database image have been located and unzipped. Subsequently these parts are able to be merged into the database image filed: E1_DB_DSK_9141.img.

Note:
The values for part number files and release version are variable and dependent on a particular release of the Oracle VM Templates for JD Edwards EnterpriseOne.

2. After all the part files are located, the merge of these parts into the image file begins, as shown in the following example:

This preceding examples shows that the image for the database (E1_DB_DSK_9141.img) was successfully merged and the process has moved on to the EnterpriseOne image, found the parts file for that image, unzipped the part files, and has started to merge them into the Enterprise Server image (E1_ENT_DSK_9141.img).

3. The following screen example shows the Extract and Merge process has completed successfully. You can determine that the entire process completed successfully when you see the Extract All: Done message at the bottom of the screen. You should not press the Enter key until you see this message. Depending on the performance of your machine, this process can take up to an hour or more.

Note:
In this example, note that there were no part files found for the E1_EXA_SYS_9144.img. If you were not installing this Oracle VM template for JD Edwards EnterpriseOne and therefore had not downloaded the image files, this may be normal for your installation.
Regardless, note that the normal behavior of the script is to display a Warning that required files were not found for a certain image, and then continue the process. You will need to be familiar with the intended topology of installed components and check the log afterwards to determine if the Warnings can be ignored for your installation, or if you need to obtain the required components and re-run the configuration.

4. When the process is complete as indicated by the Extract All: Done message, press the Enter key to proceed to the next step in the configuration script process.

4.4.3.3 Copy System

After the Extract and Merge completes, the config.sh script continues with the System Copy functions.

1. As shown in the following example, the config.sh script begins to the Copy System functions to pair System files with each JD Edwards EnterpriseOne application image that you downloaded and want to configure and install.

The above screen shot shows the start of the process to copy a system image file that is to be paired with each JD Edwards EnterpriseOne application image. In this example, the config.sh script previously determined that the only System image was for an x86 type system; therefore this is the image that it is copied. If the config.sh script had not previously detected an x86 System part file download and only detected an Exalogic System download, then it would have skipped the x86 System copy and begun with a copy of the Exalogic System. If both types of Systems were detected, the x86 System is set as the default and the script processing continues. In order to implement an Exalogic System, the Exalogic image must be the only image download that exists in the JDE_SYS directory.

As shown in the following screen shot, the copy of the System continues for each detected D Edwards EnterpriseOne application image that you downloaded and therefore intend to install and configure.

2. When the config.sh script displays the message Copy System: 0 Done, press the Enter key to continue.

4.4.3.4 Server Configuration

After the Copy System completes, the config.sh script continues with the Server Configuration functions, which include:

- Server Name

- IP Address

- Additional Server Configuration

1. On JDEdwards EnterpriseOne, Server(s) To Be Configured, at a minimum, you must choose to configure Line Item 1, which is a combination servers called the Foundation Server. This combined server group includes the JD Edwards EnterpriseOne servers for the Database, Enterprise Server, and HTML Server. This is the minimum viable combination of servers for JD Edwards EnterpriseOne using Oracle VM Templates.
The other line items in this list are for optional JD Edwards EnterpriseOne servers. The term "Standalone" refers to a server of the selected type that are additional to those included in the mandatory Foundation Server group. That is, you can choose to install multiple EnterpriseOne Servers if you want to separate logic and batch functions, and you can install multiple HTML servers for scaling and performance.

2. For purposes of the example in this guide, all servers will be configured (not including additional "Standalone" servers), as shown in the preceding screen shot.
To select servers to be configured, use the Up Arrow and Down Arrow keys to highlight a row. Once the row is highlighted, you can select the row by pressing the Space Bar. An [X] between the square brackets indicates the line item is selected.

3. Once you have selected each server that you want to configure, press the Enter key to proceed.

4.4.3.5 JD Edwards Foundation Setup

After you have selected the servers to configure, the config.sh script continues with the JD Edwards Foundation Setup.

For this setup, you to will need to provide this information for each server in the Foundation System:

- Server Name

- Server IP Address

- Starting Memory Size (in Megabytes)

- Number of CPUs Allocated to the Server

- Database Server Name

- Net Mask, Gateway, Domain, and one DNS Server

1. On JDEdwards Foundation Setup, confirm that the values that are detected for Line Items 1 and 8 are valid.

2. Use your Pre-Install Worksheet to enter values for each remaining Line Item.
Use the Up Arrow and Down Arrow keys to highlight a row for which you want to enter a value. When you reach the bottom of the screen it will automatically scroll to show remaining Line Items. Once you have entered all required values, press the Enter key to proceed.

Caution:
The entered values will be edited for syntax only. This mean if you enter a valid length server name but misspelled it, the value will still be accepted. At this point in the process the server name is not checked against a DNS server. The same is true of the IP address.

The following sequence of four (4) screens shows example values for a completed Foundation Setup.

Note:
The values shown in these screens are example values for purposes of this documentation (derived from the example Pre-Install Worksheet). Your values will be different.

Note:
The Memory allocation shown in this example is specified as 4096, which is measured in M bytes (therefore equals 4 GB).

Note:
If your installation uses a VM template for the Oracle database, the Database Service Name must be ovsorcl for configuration of Oracle VM templates for JD Edwards EnterpriseOne.
If your installation uses a non-virtualized or Exadata database, refer to the section of this guide entitled: Section 4.4.3.11, "Configuring for a Non-Virtualized or Exadata Database".

Caution:
If your configuration includes an Exalogic machine, at this step you must know the IP you will be using. You cannot later use the EMOC option to automatically select an IP.

Caution:
Do not attempt to manually change the location of the image files. This is set relative to where the JDE_OVM directories is located.

Use the Down Arrow key to scroll to the next page.

Use the Down Arrow key to scroll to the next page.

Use the Down Arrow key to scroll to the next page.

3. Once you have entered values for all fields to configure all three of the Foundation Servers, you should save the values by pressing the Tab key until the <OK> selection is highlighted, and then press the Enter key.

4. On the confirmation dialog, Save configure changes and continue?, use the Tab key to highlight the <Yes> selection and press the Enter key to confirm that you want to save the changes and continue.

5. After you have entered values for all the Foundation Servers, the config.sh script performs Configuration Check Results for these servers.
The results are displayed as shown in the example below. This example shows that the first set of values have passed the validation checks performed by the config.sh script. This validation is for syntax only, and does not guarantee connectivity as no networking checks are performed at this point in the process. In the following example, the value 56% at the bottom of the screen indicates that more information is available for these results. Use the Down Arrow key to scroll down to the next page of results.

6. On Configuration Check Results, verify that the first set of parameters pass the check. This is indicated by [OK] results in the square brackets.

7. Use the Up Arrow and Down Arrow keys to scroll through the complete set of results. The final results screen, indicating 100% complete, is shown below.

8. If the value for a field fails the syntax check, reports if a field fails the syntax check, the display will show ERROR in the square brackets. In this case, you should press the Return key to return to the setup screen. After you correct the value, press the Return key to accept the revised value and resume the syntax check. Verify the results are reported as [OK].

9. On Configuration Check Results, after you have confirmed the syntax check results are 100% complete and all values have a status of [OK], use the Tab key to highlight the <OK> selection at the bottom of the screen, and press the Enter button to continue.

4.4.3.6 JD Edwards Server Manager Setup

After you have successfully configured values for your Foundation Servers, if you have downloaded the Server Manager files and the files were detected by the Manifest Check, the config.sh script prompts you to configure this server.

1. On JDEdwards SM Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. These values should be recorded on your Pre-Install Worksheet.
The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

2. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

3. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

4. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

4.4.3.7 JD Edwards BIP Server Setup

If you have downloaded the BIP Server files and the files were detected by the Manifest Check, the config.sh script prompts you to configure this server.

1. On JDEdwards BIP Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. These values should be recorded on your Pre-Install Worksheet.
The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

2. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

3. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

4. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

4.4.3.8 JD Edwards Mobile Server Setup

If you have downloaded the Mobile Server files and the files were detected by the Manifest Check, the config.sh script prompts you to configure this server.

1. On JDEdwards Mobile Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. These values should be recorded on your Pre-Install Worksheet.
The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

2. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

3. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

4. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

4.4.3.9 JD Edwards AIS Server Setup

If you have downloaded the AIS Server files and the files were detected by the Manifest Check, the config.sh script prompts you to configure this server.

1. On JDEdwards AIS Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. These values should be recorded on your Pre-Install Worksheet.
The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

2. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

3. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

4. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

4.4.3.10 Completing the config.sh Script

When the final selected configuration is saved, the config.sh script mounts the System image file and the JD Edwards configuration file is written to the system. In addition the config.sh script performs the specified changes for the network configuration and passwords on the System image file.

The following shows an example of the System mounting the HTML application system and writing the configuration.

When all System and application paired images are mounted and the file written, the config.sh script ends and the user is returned to the command line.

The following shows the state of the system after the config.sh script has run. There are several log files (with .log extensions). Also the values for the settings of each server configuration is saved in a file with a .cfg extension. Any time you re-run the config.sh script it reads the values from these files.

You must pair each image that you wish to run as an Oracle VM template with a System image.

1. Change to the directory that contains the prepared image (the preparation is done by executing the config.sh script). For example:
cd JDE_ENT

2. Use this command to tar and zip the JD Edwards EnterpriseOne Foundation System and either the Enterprise Server or HTML Server Standalone images along with their respective vm.cfg files:
tar -czvf e1_XXX.tgz e1_x86_sys.img e1_XXX.img vm.cfg

where XXX is the application type (such as JDE_ENT or JDE_WEB) along with the release level. For example, to pair the Enterprise Server you would issue this command:

tar -czvf e1_ent_914.tgz vm.cfg E1_X86_SYS_9141.img E1_ENT_DSK_ 9141.img vm.cfg

This results in the zipped file named e1_ent_914. tgz that contains the paired files for the Foundation System and the Enterprise Server.

3. Move the zip file to a configured FTP or HTTP enabled location and deploy it as an Oracle VM Template for JD Edwards EnterpriseOne.

4. Repeat this process for each configured template that you have configured with the config.sh script and that you wish to deploy.

4.4.3.11 Configuring for a Non-Virtualized or Exadata Database

You can configure your OVM templates for JD Edwards EnterpriseOne system to use a non-virtualized database or an Exadata database system. In this configuration you must manually remove the JDE_DB directory that was created when you configured the Foundation System.

When you re-run the config.sh script you are prompted for required database values. These values are required to configure connections with the other JD Edwards EnterpriseOne applications that are deployed.

1. Note the values NULL and N/A in certain fields, as shown as above. These values are supplied if the config.sh script cannot locate the database directory (JDE_DB), which you should have manually deleted prior to re-running the script for purposes of configuring a non-virtual database.
On JDEdwards Foundation Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. The values you enter here are required to setup the database connections for the other Oracle VM templates in the JD Edwards EnterpriseOne deployment.

The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

2. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

3. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

4. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

4.4.3.12 Adding an Additional Enterprise Server (Standalone)

Optionally you can deploy additional Enterprise Servers as Oracle VM Templates for JD Edwards EnterpriseOne. You can use these additional servers to separate logic and batch jobs or you may want use extra servers for scaling.

1. Before you can deploy an additional Enterprise Server template, you must first configure and deploy the Foundation System. Then re-run the config.sh script.

2. On JDEdwards EnterpriseOne, use the Up Arrow and Down Arrow keys to highlight the line item for Enterprise Server (Standalone). Once the row is highlighted, you can select the row by pressing the Space Bar. An [X] between the square brackets indicates the line item is selected.

3. Once you have selected Enterprise Server (Standalone), use the Tab key to highlight the OK selection and press the Enter key to proceed.

4. On JDEdwards EnterpriseOne Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. The values you enter here are required to setup the database connections for the other Oracle VM templates in the JD Edwards EnterpriseOne deployment.
The values shown in the following screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

5. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

6. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

7. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

Note:
The system uses the information from the Foundation setup to rewrite the System image in the JDE_ENT directory with the new EnterpriseOne setup. You must manually pair and deploy this new Foundation System image with this new Standalone Enterprise Server as described in the following section in this guide entitled: Section 4.4.3.14, "Deploying an Additional Enterprise Server or HTML Server (Standalone) as a VM Template".

Caution:
The process of configuring an additional Enterprise Server as a VM template does not configure the JD Edwards EnterpriseOne CNC table with the information for this new server.

4.4.3.13 Adding an Additional HTML Server (Standalone)

Optionally you can deploy additional HTML Servers as Oracle VM Templates for JD Edwards EnterpriseOne. You can use these additional servers for scaling.

1. Before you can deploy an additional HTML Server template, you must first configure and deploy the Foundation System. Then re-run the config.sh script.

2. On JDEdwards EnterpriseOne, use the Up Arrow and Down Arrow keys to highlight the line item for HTML Server (Standalone). Once the row is highlighted, you can select the row by pressing the Space Bar. An [X] between the square brackets indicates the line item is selected.

3. Once you have selected HTML Server (Standalone), use the Tab key to highlight the OK selection and press the Enter key to proceed.

4. On JDEdwards EnterpriseOne Setup, use the Up Arrow and Down Arrow keys to navigate through each setting and enter valid values. The values you enter here are required to setup the database connections for the other Oracle VM templates in the JD Edwards EnterpriseOne deployment.
The values shown in the above screen shot assume the values that from the Example Pre-Install Worksheet used in this guide.

5. After you have entered values for each setting, use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.
The config.sh script then performs a syntax check of the values and displays the Configuration Check Results. For example:

6. On Configuration Check Results, use the Up Arrow and Down Arrow keys to scroll through all the selections to verify that the results are [OK] for each setting.

7. Use the Tab key to highlight the <OK> selection, and then press the Enter key to accept the values.

Note:
The system uses the information from the Foundation setup to rewrite the System image in the JDE_WEB directory with the new EnterpriseOne setup. You must manually pair and deploy this new Foundation System image with this new HTML Enterprise Server as described in the following section in this guide entitled: Section 4.4.3.14, "Deploying an Additional Enterprise Server or HTML Server (Standalone) as a VM Template".

Caution:
The process of configuring an additional HTML Server as a VM template does not configure the JD Edwards EnterpriseOne CNC table with the information for this new server.

4.4.3.14 Deploying an Additional Enterprise Server or HTML Server (Standalone) as a VM Template

Once you have created an additional Enterprise Server or HTML Server as a Standalone as described in the preceding sections, use this procedure to pair and deploy the images with the JD Edwards EnterpriseOne Foundation System that was also updated during those procedures.

To tar and zip the JD Edwards EnterpriseOne Foundation System and the Standalone files together:

1. Change to the directory of the application you wish to build. For example:
Enterprise Server

cd JDE_ENT

or

HTML Server

cd JDE_WEB

2. Use this command to tar and zip the JD Edwards EnterpriseOne Foundation System and either the Enterprise Server or HTML Server Standalone images along with their respective vm.cfg files:
tar -czvf e1_XXX.tgz e1_x86_sys.img e1_XXX.img vm.cfg

where XXX is the application type, such as JDE_ENT or JDE_WEB along with the release level. For example, issuing this command:

tar -czvf e1_ent_914.tgz vm.cfg E1_X86_SYS_9141.img E1_ENT_DSK_9141.img vm.cfg

results in the zipped file e1_ent_914.tgz which contains the paired files for the Foundation System and the Enterprise Server (Standalone), as illustrated in the following screen shot:

3. At this point you can move the zip file to a configured FTP or HTTP enable location and deploy it as an Oracle VM Template for JD Edwards EnterpriseOne.

5 Uploading Templates

Before you can upload the EnterpriseOne templates, you must configure an OVM repository.

1. On Oracle VM Manager, on the Repositories tab, highlight the VM Templates node in the left pane and in the right pane click the Upload icon (blue downward arrow).

2. On Import VM Template, use the pulldown to enter the URL of the FTP server and the file to be uploaded. Enter each pair of the EnterpriseOne system image and one of the application images.

1. Server
Use the pulldown to select the target machine on which you want to import the VM Templates.

2. VM Template URLs
Enter the URLs to the FTP machine for each pair of JD Edwards EnterpriseOne VM Templates as listed in the table below.

These files can be uploaded individually or as explained previously they can be gzipped with the -czvf option into a single file for uploading. The example shows multiple files; however you can upload a single file as well.

JD Edwards EnterpriseOne Template

Upload Files

Enterprise Server

E1_X86_SYS_914.img
E1_ENT_DSK_914.tgz

vm.cfg

Database Server

E1_X86_SYS_914.img
E1_DB_DSK_914.tgz

vm.cfg

Caution:

The size of the Database Server image is approximately 11 GBs; depending on your network this image could take several hours to upload.

HTML Server

E1_X86_SYS_914.img
e1_wb_914.tgz

vm.cfg

BI Publisher Server

E1_X86_SYS_914.img
E1_OVR_DSK_914.tgz

vm.cfg

Mobile Server

E1_X86_SYS_914.img
E1_MBL_DSK_914.tgz

vm.cfg

Server Manager

E1_X86_SYS_914.img
E1_SM_DSK_914.tgz

vm.cfg

AIS Server

E1_X86_SYS_914.img
E1_AIS_DSK_914.tgz

vm.cfg

3. Click the OK button to begin the import.
You can select the Jobs tab to check the progress of the import as shown in the following sample.

When the import successfully completes, the Oracle VM Manager shows the JD Edwards VM Template in the Job Summary section. The following sample shows the imported templates for JD Edwards EnterpriseOne HTML and Enterprise Servers.

Note:
The name of the template is derived from the vm.cfg file bundle within the application images.

Once all three pairs of JD Edwards EnterpriseOne servers are imported, you can proceed to the next section to create VM Guests.

5.1 Uploading a VM Template for JD Edwards Enterprise One Application Image

Before you can upload the EnterpriseOne templates, you must configure an OVM repository.

1. On Oracle VM Manager, on the Repositories tab, highlight the VM Templates node in the left pane and in the right pane click the Upload icon (blue downward arrow).

2. On Import VM Template, use the pulldown to enter the URL of the FTP server and the file to be uploaded. Enter each pair of the EnterpriseOne system image and one of the application images.

1. Server
Use the pulldown to select the target machine on which you want to import the VM Templates.

2. VM Template URLs
Enter the URLS to the FTP or HTTP machine for each of the JD Edwards EnterpriseOne VM templates. Upload the files separately or as a single file which has been tar'ed and gzipped together. The below table lists the files that comprise each JD Edwards EnterpriseOne server.

JD Edwards EnterpriseOne Template

Upload Files

Enterprise Server

E1_X86_SYS_914.img
E1_ENT_DSK_914.tgz

vm.cfg

Database Server

E1_X86_SYS_914.img
E1_DB_DSK_914.tgz

vm.cfg

Caution:

The size of the Database Server image is approximately 11 GBs; depending on your network this image could take several hours to upload.

HTML Server

E1_X86_SYS_914.img
e1_wb_914.tgz

vm.cfg

BI Publisher Server

E1_X86_SYS_914.img
E1_OVR_DSK_914.tgz

vm.cfg

Mobile Server

E1_X86_SYS_914.img
E1_MBL_DSK_914.tgz

vm.cfg

AIS Server

E1_X86_SYS_914.img
E1_AIS_DSK_914.tgz

vm.cfg

Server Manager

E1_X86_SYS_914.img
E1_SM_DSK_914.tgz

vm.cfg

3. Click the OK button to begin the import.
You can select the Jobs tab to check the progress of the import as shown in the following sample.

When the import successfully completes, the Oracle VM Manager shows the JD Edwards VM Template in the Job Summary section. The following sample shows the imported templates for JD Edwards EnterpriseOne HTML and Enterprise Servers.

Note:
The name of the template is derived from the vm.cfg file bundle within the application images.

Once all three pairs of JD Edwards EnterpriseOne servers are imported, you can proceed to the next section to create VM Guests.

6 Working with VM Guests

This chapter discusses these topics:

- Section 6.1, "Creating a VM Guest from the JD Edwards EnterpriseOne Application Template"

- Section 6.2, "Starting and Configuring the JD Edwards EnterpriseOne VM Guest Image"

6.1 Creating a VM Guest from the JD Edwards EnterpriseOne Application Template

In order to get a functional VM Guest, you must use the procedure in this section to clone each template that you imported.

1. On Oracle VM Manager, on the Repositories tab, select the JD Edwards EnterpriseOne template that you want to clone.

2. Click the Clone or Move icon.

3. On the Close or Move Template<name> popup, in the left pane select the radio button for this option:

- Create a clone of this Template (Click 'Next' to continue)

4. Click the Next button.

5. On the second Close or Move Template<name> popup, complete these fields:

- Clone to a:
Click the Virtual Machine radio button.

- Clone Count
Set the count value to 1.

- Clone Name
Enter a name for the clone. For example, E1_ENT_914_SVR.

- Target Server Pool
Use the pulldown to select a target server pool. For example, dnptovm200_server_pool.

- Description
Enter a description for the clone.

Note:
The Advanced Clone Options are not used for JD Edwards EnterpriseOne OVM.

6. Click the OK button.

With the Repositories tab selected, the Job Summary in the lower pane indicates the status and progress of the template cloning. In the upper left pane, Lock icons are displayed indicating that all files in the Repository are locked for changes. The Oracle VM Manager is still functional, but no changes to the Repository are allowed during cloning process.

7. Check the progress of the cloning process by selecting the Jobs tab. This may take several hours depending on the type of disk configuration you have.

8. Verify that when the cloning process completes that the new clone shows up as a new VM guest in the server pool as shown in the following example.

9. Repeat the cloning process for each of the EnterpriseOne templates:

- Enterprise Server

- Database Server

Note:
If you are not implementing the database server with an Oracle VM Template, and instead are using a non-virtualized database, you can will not have a virtualized database server to clone.

- HTML Server

- BI Publisher Server

Note:
This is an optional step that is only required if you are implementing the JD Edwards EnterpriseOne OneView Reporting (OVR) application on a BIP server.

- Mobile Server

Note:
This is an optional step that is only required if you are implementing the JD Edwards EnterpriseOne Mobile application on a BSSV server.

- AIS Server

Note:
This is an optional step that is only required if you are implementing the JD Edwards EnterpriseOne AIS server.

- Server Manager

Note:
This is an optional step that is only required if you are implementing the JD Edwards EnterpriseOne Server Manager.

10. For applicable servers (see Note below), restart the Server Manager agent by executing the restartAgent script in this directory:
/u01/jdedwards/jde_home/SCHFA/bin/restartAgent

Note:
This step is not applicable to the BIP or Mobile servers (and Server Manager itself) because they do not use Server Manager agents.

11. After all three Templates for JD Edwards EnterpriseOne are cloned and the Server Manager agents are restarted you can proceed to the next section to start the VMs and configure the Virtual NIC and network.

Caution:
During the initial startup of the JD Edwards EnterpriseOne server templates, it is very important that properly configure the Virtual NIC and the network as described in the following section of this guide.

6.2 Starting and Configuring the JD Edwards EnterpriseOne VM Guest Image

After you have cloned all the JD Edwards EnterpriseOne templates in the VM Guest, you can start and configure the VMs using these steps:

1. Boot the VM
Refer to the section entitled: Section 6.2.1, "Boot the VM".

2. Log in as the root user and boot the VM for the first time to automatically run the EOne_cfg.ksh script.
Refer to the section entitled: Section 6.2.2, "Boot the VM for the First Time to Automatically Run the EOne_cfg.ksh Script"

3. After the VM boots, check the /var/log configuration logs.
Refer to the section entitled: Section 6.2.3, "Checking the Configuration Log Files"

You must perform these steps for each of the three JD Edwards EnterpriseOne servers: Enterprise, Database, and HTML

6.2.1 Boot the VM

Use this procedure to boot the VM.

1. On Oracle VM Manager, open the Servers and VM tab and select the Server pool and then the host machine on which the VM guest is configured.

2. Click the Start icon (green triangle).
The VM Guests status will change from Stopped to Starting and then Running.

6.2.2 Boot the VM for the First Time to Automatically Run the EOne_cfg.ksh Script

Logged on as the root user, when you boot the VM for the first time the, the system automatically runs the EOne_cfg.ksh script to complete the server configuration using the parameters you entered using the config.sh script.

1. On Oracle VM Manager, with the Servers and VMs tab selected, while the VM guest is starting, select the Console icon to connect to the starting VM machine for the highlighted VM. In this example, that VM is E1_ENT_SVR.

The start up messages are displayed on the console.

2. Login into the VM as the root user. The root user account has been configured to determine what type of EnterpriseOne application image and also the associated hostname and IP and upon successful login displays that information.

6.2.3 Checking the Configuration Log Files

Use this procedure to check the configuration log files. These log files were creating when the VM was booted for the first time. At that time the system ran the EOne_cfg.ksh script passing the -syn option.

1. Change to this directory:
/var/log

2. The table below lists the log files that are available for each JD Edwards EnterpriseOne VM template. For each template you installed, you should inspect the log files to verify that they installed correctly.

JD Edwards EnterpriseOne VM Template

Log File(s)

Oracle Database

update_dba_cfg.log
update_dba_emca.log

gen_sql.log

exe_gen_sql.log

Enterprise Server

EOne_update_jde_ini.log

HTML Server

EOne_update_wls_cfg.log

BI Publisher (BIP) Server

EOne_update_ovr_cfg.log

Mobile Server

EOne_update_mbl_cfg.log

Application Interface Services (AIS) Server

EOne_update_ais_cfg.log

Server Manager

EOne_update_sm_cfg.log

7 Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server

This chapter describes using the Oracle Universal Installer for the Platform Pack in silent mode to install the JD Edwards EnterpriseOne Database Server components on a non-virtualized database server such as Oracle Exadata or Oracle Database Appliance (ODA).

Note:
If your non-virtualized database is not an Oracle Exadata or ODA machine, you can use the OUI in GUI mode as described in the appendix of this guide entitled: Appendix D, "Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode".

This method assumes you are not installing the VM template for the JD Edwards EnterpriseOne database server, and that the installation of these components on a non-virtualized database server will be used with the Oracle VM templates for JD Edwards EnterpriseOne that utilizes the complementary components described in this guide.

Note:
This method can also be used on a Linux box with or without ASM, as desired.

This chapter discusses these topics:

- Section 7.1, "Understanding the Platform Pack for a Non-Virtualized Database Server"

- Section 7.2, "Understanding the Connect String"

- Section 7.3, "Working with the Platform Pack Installer for a Non-Virtualized Database Server"

7.1 Understanding the Platform Pack for a Non-Virtualized Database Server

When setting up the JD Edwards EnterpriseOne Database Server components on non-virtualized database servers that are to be used with JD Edwards EnterpriseOne Oracle VM templates, the connect string must match across all instances of the templates. The standard value is ovsorcl. If you change this value, you must make the corresponding change when instantiating database connectivity for every OVM template using the JD Edwards OVM Tools described in the section of this document entitled: Section 4.4, "Working with JD Edwards OVM Tools (config.sh Configuration Script)".

Note:
The Platform Pack installs artifacts for the DV910, PS910, and PY910 environments. It does not install the PD910 environment.

7.2 Understanding the Connect String

You must know the name of the Oracle instance on the server on which you are running the Platform Pack installer. To determine this name, run the following command:

srvctl status database -d ovsorcl

For example, the output will look similar to this:

Instance ovsorcl1 is running on node mymachine1
Instance ovsorcl2 is running on node mymachine2

In this example, if you are running on mymachine1, you need to set your environment variable ORACLE_SID to ovsorcl1. Otherwise the data pump commands (impdp) in the database load scripts will fail. However, when you are editing the Silent Install response file, you should supply the connect string ovsorcl (or the value you have definied to be used across all VM Templates for JD Edwards EnterpriseOne) so that EnterpriseOne Services can use the RAC performance.

Caution:
To ensure you have your environment variable set correctly, run this command before proceeding (substitute your password for system in place of xxx):
sqlplus system/xxx (do not supply the @connectstring)

If you cannot successfully connect to your local database without supplying the connect string, your load scripts will fail. Review the preceding notes.

7.3 Working with the Platform Pack Installer for a Non-Virtualized Database Server

This section discusses:

- Section 7.3.1, "Working with the zip File for the Platform Pack Installer"

- Section 7.3.2, "Working with the Response File for the Platform Pack Installer"

- Section 7.3.3, "Running the Platform Pack Installer for Non-Virtualized Database Servers"

- Section 7.3.4, "Working with Installer Log Files"

- Section 7.3.5, "Deinstalling the Platform Pack for Non-Virtualized Database Servers"

7.3.1 Working with the zip File for the Platform Pack Installer

The zip file for the Platform Pack Installer for a non-virtualized database server is included in the Media Pack for JD Edwards EnterpriseOne VM Templates, which is available from the Oracle Software Delivery Cloud:

https://edelivery.oracle.com/

Create a directory on the non-virtualized database server (which is a machine such as Oracle Exadata or ODA) that the oracle user can update. For example:

/u01/Exadata

Then run this command to set appropriate permissions on the created directory:

chmod -R 775 /u01/Exadata

7.3.2 Working with the Response File for the Platform Pack Installer

An interactive install of the database using the Oracle Universal Installer (OUI) is not supported on non-virtualized database servers such as Oracle Exadata or ODA. Therefore, you must run the OUI installer in silent mode, which is driven by parameters that you set in a response (.rsp) file. This section describes the appropriate settings that you must set within this file.

Note:
If your non-virtualized database is not an Oracle Exadata or ODA machine, you can use the OUI in GUI mode as described in the appendix of this guide entitled: Appendix D, "Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode"

1. Use an editor such as vi to open the OVMDB.rsp file that is located inside the \Exadata directory that is created when the installer zip file is unzipped.

2. Edit the OVMDB.rsp response file to set valid parameters for your installation. Each section of the response file has comments to describe valid values. The entries that must be changed are at the top of the response file before the ###*###*### eye catcher.
The following figures contain the Pre-Install Worksheet for Database Installation in Silent Mode -- Response File. This Worksheet describes each section that you must modify or verify to be valid for your installation on a non-virtualized database server. Use the Worksheet to enter valid values for your installation.

3. Once edit, you should save and close the OVMDB.rsp response file.

Pre-Install Worksheet

Database Installation in Silent Mode - OVMDB.rsp Response File

Section Name

Value

Comment

ACCEPT_LICENSE_AGREEMENT

Valid values are true or false.
The shipped version of the OVMDB.rsp has this value set to false.

You must change this to true in order for the installation to be able to proceed.

UNIX_GROUP_NAME

Specify the UNIX group to be set for the inventory directory. Set this to the group name for the oracle user.
The default value is oinstall.

ORACLE_HOME

Specify the path where you want the installer to place the scripts and dump files.
For example, a valid home name might be:

/u01/app/oracle/JDEOVM/e910

Important: When setting ORACLE_HOME ensure the folder is empty and there is not another Oracle product installed in that folder.

ODA Considerations. For ODA you can put the scripts and dump files onto the shared disk space. For example:

/cloudfs/JDEOVM/e910

If using the shared disk space you can specify ovsorcl as your ORACLE_SID environment variable.

ORACLE_HOME_NAME

Specify the name of the Oracle Home.
The installer uses this name to create folders and services.

For example, a valid ORACLE_HOME_NAME might be:

JDEOVM_E910_1

Important: This name must be unique. Ensure you do not use an ORACLE_HOME_NAME that has already been defined on the server you are using.

connectString

Specify the Oracle connect string.
The standard Oracle connect string for the OVM templates is ovsorcl. If you enter a different value here, you must make the corresponding change when instantiating the OVM templates using the JD Edwards EnterpriseOne OVM Tools described in the chapter of this guide entitled: Chapter 4, "Working with Oracle VM Templates for JD Edwards EnterpriseOne".

JDEMODEN

Specify the mode as Install (0) or Upgrade (1).
You must choose Install mode (0) so that the installer will create and load the Business Data and Control Tables.

Do not choose Upgrade mode because in this mode the installer does not create or load the Business Data and Control Tables.

The default value is Install (0).

sysadmUser

Specify the name of the Oracle sysadmin.
You cannot specify sys as the user.

sysadmPwd

Specify the password for the Oracle sysadmin. This is a required value.

slOVMvalues

Specify a string list of location, machine names, and values that are required for use with JD Edwards EnterpriseOne VM templates.
The machine names should not be qualified.

The syntax for the string is:

slOVMvalues={"Location","deployment_server","html_ server","enterprise_server","ASM_YES_NO","BIP_YES_NO", ,"BIP_server","sys_password"}

where

Location is the location name for Package Deployment. For example, Corporate.

deployment_server is the machine name of the Deployment Server. This name must be specified in Upper Case. For example, CUSTVMDEP.

html_server is the machine name of the HTML Server. For example, custvmhtml.

enterprise_server is the machine name of the Enterprise Server. For example, custent.

ASM YES or NO is used to specify whether your database server is using Oracle Automatic Store Management (Oracle ASM). Valid values are YES or NO.

BIP YES or NO determines if you want to load the repository for Oracle BI Publisher. Valid values are YES or NO.

BIP_server is the machine name of your BIP server. This is only required if you specified YES to BIP YES or NO.

sys_password is the password for the sys user. This is only required if you specified YES to BIP YES or NO.

Caution: The import of the SQL procedures in the BI Publisher Repository will fail if you do not supply the correct sys password.

Here is an example of a valid command string, which must be contiguous with no spaces or line feeds:

slOVMvalues={"Corporate","CUSTVMDEP","custvmhtml","custvment","YES","YES","custvmbip","mypassword"}

orclTblDir

ASM Considerations. If you are using ASM, this value specifies the ASM disk group for the tables. The default value is: DATA.
Non-ASM. Specify the path to the directory where the Oracle tablespaces are to be created. You should change the default value to a valid value for your environment. For example:

/u01/jdedwardsppack/ORCL/Tables

orclIdxDir

ASM Considerations. If you are using ASM, this value specifies the ASM disk group for the indexes. The default value is DATA.
Non-ASM. Specifies the path to the directory where the Oracle indexes are to be created. You should change the default value to a valid value for your environment. For example:

/u01/jdedwardsppack/ORCL/Indexes

iRunScripts

Specify whether to deploy the scripts for the user to run later, or to run the scripts as part of the installation.
0 = Edit and deploy the scripts; you must run the scripts manually after the installer completes.

1 = Edit and deploy the scripts and dump files; the scripts are run automatically by the installer.

The default value is 1.

dbMach

Specify the SCAN listener or host name for the database server. You should change the default value to a valid value for your environment.

gbl_secure_Password

Specify the complex password to be used for all accounts created by the installer.
You should leave this value as DEFAULT until you bring up all servers in the JD Edwards EnterpriseOne system. You can then change the passwords in your database and in your JD Edwards EnterpriseOne administration.

Important: For all versions of Oracle VM Templates for JD Edwards EnterpriseOne prior to and including the GA release of the Oracle VM Templates for JD Edwards EnterpriseOne Tools Release 9.1.4.4 and Applications Release 9.1.2, you must manually edit this response file to rename this setting:

From: gbl_secure_Password="DEFAULT"

To: securePwd="DEFAULT"

bPrecreateTbsp

Specify whether you are precreating tablespaces where valid values are:

- true
Use this value if you want to precreate the tablespaces before running the install scripts.

- false
Use this value if you do not want to precreate the tablespaces. In this case, the installer scripts will create the tablespaces.

The default value is false.

7.3.3 Running the Platform Pack Installer for Non-Virtualized Database Servers

To run the Platform Pack installer for non-virtualized database servers (such as Oracle Exadata and ODA):

1. Verify these values are set:

- ORACLE_SID

- ORACLE_HOME

- ORACLE_BASE

2. Ensure the value $ORACLE_HOME/bin is in the PATH environment variable.

3. Change directory to the Exadata/install folder.

4. Use this command syntax to run the installer. For the response file, you must specify the full path to the location of the Platform Pack installer image for non-virtualized database servers. For example:
./runInstaller -silent -responseFile /u01/Exadata/OVMDB.rsp

Caution:
You will not be able to start services until you have run the TLOVM001 Tools Accelerator on the Deployment Server. This is previously documented in the section of this guide entitled: Section 3.5.7.3, "Mandatory Post Installation Tools Accelerator".

7.3.4 Working with Installer Log Files

Upon completion, the installer reports success or failure for the Oracle database scripts. To verify the status of the install, you should:

1. Check the logs in your install location in this directory:
ORCL/logs

Tip:
It especially important that you check and verify the Import* logs.

2. Check the logs in the Oracle inventory location, which by default is:
/u01/app/oraInventory/logs

This directory contains these log files:

- silentInstallxxx.log

- oraInstallxx

- installActionsxxx

Note:
The following error will appear in the install logs:

update PD910.F983051 set vrmkey='UNIT9057' where vrmkey = 'DEPLOYMSTR'
*
ERROR at line 1:
ORA-00942: table or view does not exist

Ignore this error. The PD environment is no longer deployed, and this statement should not have been run. This error will not impact the success of the install.

7.3.5 Deinstalling the Platform Pack for Non-Virtualized Database Servers

Use this procedure to deinstall the Platform Pack for non-virtualized databases servers (such as Oracle Exadata and ODA).

1. Navigate to your install location.

2. Change directory to ORCL.

3. Run this script:
drop_db.sh

4. Navigate to the oui folder within your install location.

5. Change directory to bin.

6. Use this command to run the OUI installer in silent mode to deinstall the Platform Pack for non-virtualized database servers.
./runInstaller -deinstall -silent REMOVE_HOMES={"/u01/JDEOVM/e910"} ORACLE_HOME_NAME="JDEOVM_E910"

8 Working With the Enterprise Server

This chapter contains the following topics:

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

- Section 8.2, "Verifying the Release 9.1 Enterprise Server Installation Using PORTTEST"

8.1 Starting and Shutting Down Network Services on the Enterprise Server

The network services are automatically started when you run the RunOneWorld.sh startup script using these steps:

1. Log on to the Enterprise Server as jde910.

2. Change to this directory:
cd $SYSTEM/bin32

3. Run the RunOneWorld.sh startup script using this command:
./RunOneWorld.sh

4. Check the status of the services by running the netwm program.

Note:
You should always shut down services before shutting down a VM Guest. When a VM Guest is shutdown and restarted, the Server Manager Agent may need to be manually restarted by logging in as jde910 and running the restartAgent script.
To shutdown services, repeat the above steps substituting EndOneWorld.sh for RunOneWorld.sh.

For example, your console might look like this when running the RunOneWorld.sh startup script:

[root@custent ~]# su - jde910

$ cd $SYSTEM/bin32
$ ./RunOneWorld.sh
Wed Jun 10 18:33:14 EDT 2011   Starting JD Edwards OneWorld on custent
Wed Jun 10 18:33:16 EDT 2011   JD Edwards OneWorld startup complete.
$ netwm
Initializing JDEIPC
About to setupWorkManagementStruct
setupWorkManagementStruct ok
getJDENetWorkManagement ok
********************
1 net processes
********************
pid-2926  start-Wed  Jun 10 18:33:14 2011 dport-6015 sport-6015 in-0  out-0   total-0
********************
4 kernel processes
********************
pid-2927        parent-2926     start-Wed Jun 10 18:33:17 2011  kdef-13         requests-0      outstanding-1   UserCount-0
pid-2934        parent-2926     start-Wed Jun 10 18:33:18 2011  kdef-30         requests-0      outstanding-0   UserCount-0
pid-2935        parent-2926     start-Wed Jun 10 18:33:19 2011  kdef-4  requests-0      outstanding-1   UserCount-0
pid-2937        parent-2926     start-Wed Jun 10 18:33:20 2011  kdef-4  requests-0      outstanding-0   UserCount-0
$

8.2 Verifying the Release 9.1 Enterprise Server Installation Using PORTTEST

Note:
When running PORTTEST after installing the Enterprise Server, the test returns a failure message. This is because it is not able to access the F0902 table at this time, (the format of the F0902 table changes during the Table Conversion Workbench). Ignore any errors relating to accessing the F0902 table. For example:
Select all on table F0902 failed - rcode=0

Once the Workbench tasks are all complete, and the Enterprise Server is configured, rerun PORTTEST.

To verify the Enterprise Server installation using PORTTEST:

1. Log on to the Enterprise Server as jde910.

2. To verify that Release 9.1 is installed correctly on the Enterprise Server, enter these commands:
cd $SYSTEM/bin32

porttest userid password environment

where userid is a valid Release 9.1 user ID, password is the user password, and environment is the environment you want to verify.

For example:

porttest JDE JDE DV910

These parameters are case-sensitive. Enter this command for each environment.

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

Tip:
If PORTTEST fails to run, for diagnostic assistance refer to the chapter entitled: ”Using the PORTTEST Checklist” in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix.

9 Starting the JD Edwards EnterpriseOne Servers

This chapter discusses these tasks:

- Section 9.1, "Starting the HTML Server"

- Section 9.2, "Starting the BI Publisher Server"

- Section 9.3, "Starting the Mobile Server"

- Section 9.4, "Starting the AIS Server"

- Section 9.5, "Starting Server Manager"

9.1 Starting the HTML Server

The HTML Server is started using these scripts:

- startNodeManager.sh

- startWebLogic.sh

- startManagedWebLogic.sh

While logged on to the HTML Server as the oracle user, you can submit these commands to run with nohup and in the background by executing the following commands:

cd /u01/Oracle/Middleware/user_proj ects/domains/base_domain/bin
nohup ./startNodeManager.sh & tail -f nohup.out

Watch this log until you see this message:

INFO: Plain socket Listener started on port

Press ”Control + C” to break out of the tail command and then execute the following commands:

cd /u01/Oracle/Middleware/user_projects/domains/base_domain/bin
./startWebLogic.sh

Watch this log until you see this message:

... <Server started in RUNNING mode>

Logon to your WebLogic Server Admin Console at this URL:

http:/<your WebLogic server>:7001/console

From the WebLogic Server Admin Console, go to the Environment and select the Servers option. The Summary of Servers screen is displayed. Select the Control tab and click the html_server row click the start button.

The log will display on the screen and prompt you to enter the user name and password, whose values should be documented in the Pre-Install Worksheet. Once WebLogic has been configured with a new password you can update the boot.properties file for nohup and background processing. For instructions on changing and setting up boot.properties files, refer to the JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, Section 4.4 at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/toc.htm

Monitor the log until you see this message:

INFO: Successfully stated the management agent listerner on port 14502

Alternately, you can start the html_server through the WebLogic Administration Console or from Server Manager.

Note:
You should always shut down services before shutting down a VM Guest. When a VM Guest is shutdown and restarted, the Server Manager Agent may need to be manually restarted by logging in as the oracle user and running the startup steps.
To shutdown services, log in as oracle and cd to the bin directory as above, and run the following scripts:

/stopManagedWebLogic.sh html_server

./stopWebLogic.sh

For more information on using WebLogic with JD Edwards EnterpriseOne see JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/toc.htm

9.2 Starting the BI Publisher Server

The BI Publisher Server is started using these scripts:

- startNodeManager.sh

- startWebLogic.sh

- startManagedWebLogic.sh

1. While logged on to the BI Publisher Server as the oracle user, you can submit these commands to run with nohup and in the background by executing the following commands:

cd /u01/Oracle/Middleware/wlserver_10.3/server/bin
nohup ./startNodeManager.sh & tail -f nohup.out

2. Watch this log until you see this message:
INFO: Plain socket Listener started on port

3. Press ”Control + C” to break out of the tail command and then execute the following commands:

cd /u01/Oracle/Middleware/user_projects/domains/bifoundation_domain /bin
./startWebLogic.sh

4. The system prompts you for the password for the WebLogic Administrator; you must enter a valid password to continue. You should have this value recorded on your Pre-Install Worksheet. Refer to the section of this guide entitled: Section 4.2, "Completing the Pre-Install Worksheet".

5. Watch this log until you see this messages as shown below indicating the server started in RUNNING mode:

6. Logon to the WebLogic Server Administrative Console and start the BI Publisher Application, as shown in the following example

Caution:
Do not use this script to start the BI Publisher:
startManagedWebLogic.sh

You must use the WebLogic Server Administrative Console to start the BI Publisher because there are configuration settings that are only available using this method.

9.3 Starting the Mobile Server

The Mobile Server is started using these scripts:

- startNodeManager.sh

- startWebLogic.sh for the BSSV Server

- startWebLogic.sh for the ADF Server

1. While logged on to the Mobile Server as the oracle user, you can submit these commands to run with nohup and in the background by executing the following commands:

cd /u01/Oracle/Middleware/wlserver_10.3/server/bin
nohup ./startNodeManager.sh & tail -f nohup.out

2. Watch this log until you see this message:
INFO: Plain socket Listener started on port 5556

3. Press ”Control + C” to break out of the tail command and then execute the following commands:

cd /u01/Oracle/Middleware/user_projects/domains/bssv_domain/bin
./startWebLogic.sh

4. The system prompts you for the password for the WebLogic Administrator; you must enter a valid password to continue. You should have this value recorded on your Pre-Install Worksheet. Refer to the section of this guide entitled: Section 4.2, "Completing the Pre-Install Worksheet".

5. Watch this log until you see this messages as shown below indicating the server started in RUNNING mode:

6. In the messages indicating the AdminServer_bssv is started, note on which port the server is listening. In the above example, the port is 10.245.161.12:8001.

7. Press ”Control + C” to break out of the tail command and then execute the following commands:
cd /u01/Oracle/Middleware/user_proj ects/domains/adf_domain/bin

nohup ./startWebLogic.sh & tail -f nohup.out

8. Watch this log until you see this messages as shown below indicating the ADF server started in RUNNING mode:

9. In the messages indicating the AdminServer_adf is started, note on which port the server is listening. In the above example, the port is 10.245.161.12:7001.

10. Press ”Control + C” to break out of the tail command.

11. Logon to the BSSV WebLogic Administrative Console and start the BSSV application, as shown in the following example:

12. Logon to the ADF Administrative Console and start the ADF application, as shown in the following example:

Caution:
Do not use this script to start the BSSV or ADF application:
startManagedWebLogic.sh

You must use the WebLogic Server Administrative Console to start the BSSV and ADF applications because there are configuration settings that are only available using this method.

9.4 Starting the AIS Server

The AIS Server is started using these scripts:

- startNodeManager.sh

- startWebLogic.sh

- startManagedWebLogic.sh

1. While logged on to the AIS Server as the oracle user, you can submit these commands to run with nohup and in the background by executing the following commands:

cd /u01/Oracle/Middleware/user_projects/domains/AIS_domain/bin
nohup ./startNodeManager.sh & tail -f nohup.out

2. Watch this log until you see this message:
INFO: Plain socket Listener started on port 5556

3. Press ”Control + C” to break out of the tail command and then execute the following commands:

cd /u01/Oracle/Middleware/user_proj ects/domains/AIS_domain/bin
./startWebLogic.sh

4. The system prompts you for the password for the WebLogic Administrator; you must enter a valid password to continue. You should have this value recorded on your Pre-Install Worksheet. Refer to the section of this guide entitled: Section 4.2, "Completing the Pre-Install Worksheet".

5. Watch this log until you see this messages as shown below indicating the server started in RUNNING mode:

6. From the WebLogic Server Admin Console, go to the Environment tab and select the Servers option.
The Summary of Servers screen is displayed.

7. Select the Control tab and highlight the AIS_server row

8. Click the Start button and confirm the AIS server is started.
The log will display on the screen and prompt you to enter the user name and password, whose values should be documented in the Pre-Install Worksheet. Once WebLogic has been configured with a new password you can update the boot.properties file for nohup and background processing. For instructions on changing and setting up boot.properties files, refer to the JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, Section 4.4 at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/toc.htm

Monitor the log until you see this message:

INFO: Successfully stated the management agent listerner on port 14502

Alternately, you can start the AIS Server through the WebLogic Administration Console or from Server Manager.

Note:
You should always shut down services before shutting down a VM Guest. When a VM Guest is shutdown and restarted, the Server Manager Agent may need to be manually restarted by logging in as the oracle user and running the startup steps.
To shutdown services, log in as oracle and cd to the bin directory as above, and run the following scripts:

/stopManagedWebLogic.sh ais_server

./stopWebLogic.sh

For more information on using WebLogic with JD Edwards EnterpriseOne see JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/toc.htm

9.5 Starting Server Manager

Server Manager is started using these scripts:

- startNodeManager.sh

- startWebLogic.sh

1. While logged Server Manager as the oracle user, you can submit these commands to run with nohup and in the background by executing the following commands:

cd /u01/Oracle/Middleware/user_projects/domains/SM_domain/bin
nohup ./startNodeManager.sh & tail -f nohup.out

2. Watch this log until you see this message:
INFO: Plain socket Listener started on port

3. Press ”Control + C” to break out of the tail command and then execute the following commands:

cd /u01/Oracle/Middleware/user_proj ects/domains/SM_domain/bin
./startWebLogic.sh

4. Enter the Weblogic user weblogic and the default password ovsadminE1.

5. Watch this log until you see this message:
... <Server started in RUNNING mode>

6. Logon to your WebLogic Server Admin Console at this URL:
http:/<your WebLogic server>:7001/console

7. Launch the WebLogic Administration Console.

8. From the WebLogic Server Admin Console, log in with the weblogic user and ovsadminE1 password.

9. Go to the Environment and select the Servers option. The Summary of Servers screen is displayed.

10. On Summary of Servers, select the Control tab and click on and highlight this row:
SMC_Server_EOne_ManagementConsole_Console

11. Click the Start button.
Server manger is now running and you can access it at this URL:

http://<server name>:8999/manage

12. Logon to Server Manager with the User ID jde_admin and the password jde_admin.
Once WebLogic has been configured with a new password you can update the boot.properties file for nohup and background processing. For instructions on changing and setting up boot .properties files, refer to the JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, in the section entitled: Create boot.properties to Start and Stop Servers. at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/prep_wls_e1_web_server.htm#EOHLU124

13. Monitor the log until you see this message:
INFO: Successfully stated the management agent listener on port 14502

Note:
You should always shut down services before shutting down a VM Guest. When a VM Guest is shutdown and restarted, the Server Manager Agent may need to be manually restarted by logging in as the oracle user and running the startup steps.
To shutdown services, log in as oracle and cd to the bin directory as above, and run the following scripts:

/stopManagedWebLogic.sh sm_server

./stopWebLogic.sh

For more information on using WebLogic with JD Edwards EnterpriseOne see JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide Release 9.1 for UNIX, at the following link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23434/toc.htm

10 Installing the Workstations for Developers and System Administrators

This chapter contains the following topics:

- Section 10.1, "Workstation Installation"

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

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

- Section 10.4, "Understanding Workstation Installation Methods"

- Section 10.5, "Understanding Third-Party Products"

10.1 Workstation Installation

This section discusses these topics:

- Section 10.1.3, "Prerequisites"

- Section 10.1.2, "Prepare for Workstation Installation"

- Section 10.1.3, "Prerequisites"

- Section 10.1.4, "Configure the jde.ini File on the Deployment Server to Specify the Security Server"

- Section 10.1.5, "Modifying the Workstation JDE.INI on the Deployment Server for Languages (Optional)"

10.1.1 Overview of Workstation Installation

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

The workstations for developers and system administrators are Microsoft Windows-based machines. Refer to the Certifications (Formerly Known as Minimum Technical Requirements) for specifically-supported versions of Microsoft Windows.

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

See Also:

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

- JD Edwards EnterpriseOne Development Client Installation and Configuration Guide

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

10.1.2 Prepare for Workstation Installation

To prepare for the installation of Release 9.1 on individual workstations you must:

- Modify the workstation JDE.INI on the Deployment Server (refer to Section 10.1.4, "Configure the jde.ini File on the Deployment Server to Specify the Security Server".

- Optionally, if you are using languages, you must further modify the JDE.INI on the Deployment Server (refer to Section 10.1.4, "Configure the jde.ini File on the Deployment Server to Specify the Security Server"

- The JD Edwards EnterpriseOne system administrator must create a user profile for every user before that user can log on to Release 9.1.

- Copy the configured tnsnames.ora from the oracle\E1local directory to the \client directory on the Deployment Server, as specified in the next section of this guide entitled: Section 10.2, "Copying the Configured tnsnames.ora File".

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

Note:
Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for additional details on installing the Web Development Client.

10.1.3 Prerequisites

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

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

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

During workstation installation, connectivity is required for:

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

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

For example:

\\deployment_server_name\E910\PD910\package

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

For example:

\\deployment_server_name\E910\client

10.1.4 Configure the jde.ini File on the Deployment Server to Specify the Security Server

Prior to installing the Web Development Client used for development, you must modify the jde.ini file on the Deployment Server to specify the Security Server. These files on this server are used by the Web Development Client installation program. If these files are not configured properly, the Web Development Client that is installed from the Deployment Server will not be able to connect to the requisite JD Edwards EnterpriseOne servers.

1. Edit the jde.ini file in this directory on the Deployment Server:
\\<deployment_server>\e910\OneWorld Client Install\Misc

2. Locate this setting:
SecurityServer=

3. Add a valid value for your installation for the Security Server so the configured setting is:
SecurityServer=your_server_name

4. Save the configured jde.ini file on the Deployment Server.

10.1.5 Modifying the Workstation JDE.INI on the Deployment Server for Languages (Optional)

Note:
This is an optional task if you are using languages on your Web Development Client.

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

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

DBCSNoTruncErr=1

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

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

\JDEdwards\E910\OneWorld Client Install\Misc

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

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

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

- [INTERACTIVE RUNTIME]
For the language you are installing, enter:

Initial_Language_Code = x

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

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

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

2. Save and close the file.

10.2 Copying the Configured tnsnames.ora File

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

To copy the configured tnsnames.ora file:

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

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

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

10.3 Copying the JDK to the Deployment Server

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

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

2. Refer to Certifications (Formerly Known as Minimum Technical Requirements)to determine the correct JDK required for this installation.

3. Locate and download the appropriate JDK from the Sun web site:
http://www.oracle.com/us/sun/index.htm

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 Development Client unless instructed to do so by JD Edwards EnterpriseOne support.

4. Save the JDK to a temporary directory.

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

6. Click Next.

7. Select Accept and click Next.

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

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

10. Deselect both Browse Registration options.

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

12. When the process is complete, click Finish.

10.4 Understanding Workstation Installation Methods

You can select from three methods to deploy Release 9.1 and to launch the workstation installation program:

- Interactive Mode

- Silent Mode

- Push Mode

10.4.1 Interactive Mode

This section discusses:

- Creating a Desktop Shortcut

- Using a Shared Drive

10.4.1.1 Creating a Desktop Shortcut

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

\JDEdwards\E910\OneWorld Client Install

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

To create a desktop shortcut:

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

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

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

4. Skip to the next task immediately following entitled: Using a Shared Drive, and begin with Step 2 of that task.

10.4.1.2 Using a Shared Drive

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

To use a shared drive:

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

OneWorld Client Install

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

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

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

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

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

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

- Select Setup Type
Select Development or Production objects.

Note:
You should only select the Development option if you intend to develop Release 9.1 applications.

- Install Path
Select the drive and directory in which to install the package. For example, this is the typical path for Release 9.1:

c:\E910

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

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

7. Reboot if necessary.

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

Note:
When you open Release 9.1 after installing the client workstation, or upgrading to Release 9.1, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click OK.

10.4.2 Silent Mode

JD Edwards EnterpriseOne can also be installed to the workstation by the silent mode, which is optional. The silent installation mode lets you specify the installation path by command-line arguments instead of entering them on the Workstation Installation forms. As a result, submit the silent installation from the command line or through any scheduling service (such as Microsoft Windows schedulers) that you have installed.

Verify that you are connected to this shared drive on the Deployment Server:

\JDEdwards\E910

To work with silent mode:

1. From the Start menu, select Run.

2. Click the Browse button.

3. Locate the \JDEdwards\E910\OneWorld Client Install directory on the Deployment Server, select SETUP.EXE, and then click the Open button.

4. In the Run box, append the required parameters to setup.exe so that the command line conforms to this structure:
setup.exe -S -P packagename -D installpath

where packagename is a valid package name and installpath is the installation path on the workstation where Release 9.1 should be installed (for example, c:\E910).

You also can include the following optional parameters:

-t Typical

Using the typical parameter installs the development objects.

-t Compact

Using the compact parameter does not install the development objects.

-r

Using the -r parameter indicates you want to uninstall the previous installation before continuing. The results of the uninstallation appear in c:\jdeinst.log.

Caution:
If the specified installation path already exists, the directory structure contents are overwritten.

5. To run the command line, click the OK button.
During a silent installation, Release 9.1 Client Installation appears in the Microsoft Windows taskbar.

6. Verify a successful installation by viewing the c:\jdeinst.log file.

Note:
When you open Release 9.1 after installing the client workstation, or upgrading to Release 9.1, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click the OK button.

10.4.3 Push Mode

Push mode is described in the JD Edwards EnterpriseOne Tools Package Management Guide.

10.5 Understanding Third-Party Products

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

Microsoft Internet Explorer provides:

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

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

11 Post Installation Tasks

After you have installed the JD Edwards EnterpriseOne Deployment Server, Enterprise Server, Database Server, and HTML Web Server, you may wish to perform some of these tasks:

- Working with Sign-on Security

- Applying an Oracle Business Accelerator

- Building and Testing Packages

- Installing Languages

- Creating a Language-Only Plan

- Adding a Server to an Existing Configuration

- Setting up Microsoft Windows Security on Deployment Server

- Using Adobe SVG Viewer on Web Clients

- Building Task Word Search Tables

- Configuring JD Edwards EnterpriseOne for use with Vertex

- Enabling CRM

- Enabling Verity Search Capability

- Copying an Environment to Another Environment

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

These tasks are described in detail in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix, which is available in the document on the Oracle Technology Network at this link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23313.pdf

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

Security Considerations

Your implementation of the JD Edwards EnterpriseOne Oracle VM templates should follow the guidelines recommended in the JD Edwards EnterpriseOne Tools Security Administration Guide, which is available at this link:

http://docs.oracle.com/cd/E24705_01/doc.91/e24258/toc.htm

This implementation of the JD Edwards EnterpriseOne Oracle VM templates complies with the Oracle security guidelines as described in the documents at these links:

Oracle Database

http://docs.oracle.com/cd/E16655_01/index.htm

Oracle WebLogic Server

http://docs.oracle.com/middleware/1212/

Oracle ADF Mobile Server

http://docs.oracle.com/cd/E37975_01/index.htm

Oracle BI Publisher

http://docs.oracle.com/cd/E28280_01/bi.htm

12 Deinstalling the Software

This chapter includes these tasks:

- Section 12.1, "Understanding the Deinstallation"

- Section 12.2, "Deinstalling the Software from the Workstations"

- Section 12.3, "Deinstalling the Local OEE from the Deployment Server"

- Section 12.4, "Deleting Virtual machines for JD Edwards EnterpriseOne Servers"

12.1 Understanding the Deinstallation

The installation and upgrade processes do not automatically remove any JD Edwards EnterpriseOne databases. You should have a database administrator (DBA) for your relational database management system (RDMS) manually remove any unused databases according to the list of databases and associated components, which are provided in this document.

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

Server

Mandatory Component

Optional Components

Deployment Server

JD Edwards EnterpriseOne Files

Production Environment
Prototype Environment

Development Environment

Pristine Environment

Enterprise Server

JD Edwards EnterpriseOne Foundation

ES Production
ES Prototype

ES Development

ES Pristine

12.2 Deinstalling the Software from the Workstations

You can remove previous JD Edwards EnterpriseOne installations from workstations by running the deinstallation program as described in the JD Edwards EnterpriseOne Development Client Installation Guide.

12.3 Deinstalling the Local OEE from the Deployment Server

Note:
Oracle products use the term ”deinstall” to refer to removing an Oracle product.

To deinstall the local Oracle database:

1. Either export the local database tablespaces or deinstall JD Edwards EnterpriseOne using Start > Programs > Oracle - <Home_Name> > Oracle Installation Products > Universal Installer where <Home_Name> is the name that you gave the installation of EnterpriseOne on the Deployment Server.

2. Locate this file:
<Oracle_Home>\deinstall\deinstall.bat

3. Right click on the file that you located in Step 2 and select Run as administrator, where <Oracle_Home> is the directory where you installed the local Oracle database. For example, your directory might be:
c:\Oracle\E1Local

4. At the end of the deinstallation, verify that the Oracle_Home directory has been deleted (for example, c:\Oracle\E1local). If it still exists, you should attempt to manually delete it.

Caution:
Prior to any reinstall an Oracle local database on this same machine, the Oracle_Home directory (for example, c:\Oracle\E1local) must not exist. If you attempt to reinstall the local Oracle database and this directory still exists, it is likely that the new installation will fail.

Tip:
You may not be able to delete the Oracle_Home directory (for example, c:\Oracle\E1local) if a process has it locked. In that case, to determine which process(es) has it locked, run the steps in the section of this guide entitled: Section 3.9.5.4, "Process Explorer".

12.4 Deleting Virtual machines for JD Edwards EnterpriseOne Servers

When uninstalling the VM Guest with this release of OVM, select the VM guest that you want to delete and select the delete icon (the red X) from the command menu. The user will be prompted to delete the disk images associated with theVM guest.

Use these steps for each VM guest you want to deinstall:

1. Access the Oracle VM Manager.

2. On Oracle VM Manager, with the Servers and VMs tab selected and with the Server Pools node expanded to your pool, highlight the VM guest you want to delete and click the Delete icon (red X).

3. On Delete Confirmation, select the checkbox for the virtual disk that you want to delete.

4. Click the OK buttonn to complete the deletion of the selected disk.

Note:
Up to this point in this procedure, only the VM guest is deleted. Continue with the following steps to delete the VM template.

5. On Oracle VM Manager, with the Repositories tab selected and with the VM Templates node selected, highlight the VM template you want to delete, and click the Delete icon (red X).

6. On Delete Confirmation, select the checkbox for the virtual disk that you want to delete.

7. Click the OK button to complete the deletion of the selected disk.

A Globalization Considerations

This appendix discusses these topics:

- Appendix A, "National Language Setting Considerations"

- Appendix A, "NLS Considerations for Non Western European Users"

A.1 National Language Setting Considerations

This section discusses National Language Settings Considerations for the JD Edwards EnterpriseOne preconfigured implementation that is delivered through an Oracle Virtual Machine (OVM). The OVM database image includes:

- Oracle Enterprise Linux 2.6.18-8.1.15.3.1.el5xen

- Oracle 11g R1 (11.1.0.7.0) database

Both the operating system and database are configured as Western European. The Oracle Unicode database is configured to use national character set AL16UTF16 with a database character set of WE8MSWIN1252. This preconfigured OVM image is available for global use as a certified J.D. Edwards EnterpriseOne environment and includes full customer support.

Many NLS database parameters can be configured to meet specific customer business needs. Certain NLS parameters cannot be changed or may only be altered with some additional effort. Changes to database parameters should only be made by an Oracle DBA who can weigh the specific implications and considerations of each modified parameter.

Use the SQL query that follows to determine the current database NLS settings:

"SELECT * FROM NLS_DATABASE_PARAMETERS;"

The following table describes NLS character set values

Parameter

Description

OVM Value

Notes

NLS_CHARACTERSET

Database Character Set

WE8MSWIN1252

The Database Character Set value is set during database creation. This value can be altered post database installation with certain limitations. Review the Oracle® Database Globalization Support Guide 11g Release 1 (11.1) B28298-02, ”Character Set Migration” chapter for more information.
Use of the WE8MSWIN1252 value for non-Western European users is possible. In such a case the database is treated as multilingual.

NLS_NCHAR_CHARACTERSET

National Character Set

AL16UTF16

The National Character Set value is set during database creation. This database value cannot be altered post database installation. Only an AL16UTF16 setting is supported for the Oracle J.D.Edwards EnterpriseOne database.

Refer to the JD Edwards Installation Guide entitled:

JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix. This guide is available on the Oracle Technology Network at this link:

http://docs.oracle.com/cd/E24902_01/doc.91/e23313.pdf

The referenced installation guide lists recommendations that are different than those delivered with this OVM image. Values for non-Western European language NLS_CHARACTERSET are shown in Figure C-1. Note this figure is for reference only and does not imply that a modification needs to be made to the OVM image to correctly function with J.D. Edwards EnterpriseOne.

The following image shows an excerpt from the JD Edwards EnterpriseOne 9.1 Installation Guide for Unix:

For non-Western European users the disparity in the NLS_CHARACTERSET parameter value of the OVM database from the above listed table is supported by JD Edwards EnterpriseOne. That is, the database is simply treated as multilingual. You should be certain to follow all of the other language configuration recommendations found in the referenced guide (JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix). For example, you should use the specified settings for configuration of NLS_LANG and the JDE.INI LocalCodeSet.

The following information is included to provide a better understanding of how the NLS Parameters are defined and how each value is used with the Oracle Database and Oracle Clients when used with JD Edwards EnterpriseOne.

The table shown directly below (which spans three pages) is an excerpt (Table 3-2 NLS Parameters) from the Oracle Database Globalization Support Guide 11g Release 1 (11.1) B28298-02. The NLS database parameters cited here can be altered to meet your specific business needs. Again, changes to database parameters should only be made by an Oracle DBA who can weigh the specific implications and considerations of each modified parameter.

This table describes NLS Parameters (excerpt Table: ”Oracle Database Globalization Support Guide 11g”):

Parameter

Description

Default

Scope:I = Initialization Parameter File E = Environment Variable A = ALTER SESSION

NLS_CALENDAR

Calendar system

Gregorian

I, E, A

NLS_COMP

SQL, PL/SQL operator comparison

BINARY

I, E, A

NLS_CREDIT

Credit accounting symbol

Derived from NLS_TERRITORY

E

NLS_CURRENCY

Local currency symbol

Derived from NLS_TERRITORY

I, E, A

NLS_DATE_FORMAT

Date format

Derived from NLS_TERRITORY

I, E, A

NLS_DATE_LANGUAGE

Language for day and month names

Derived from NLS_LANGUAGE

I, E, A

NLS_DEBIT

Debit accounting symbol

Derived from NLS_TERRITORY

E

NLS_ISO_CURRENCY

ISO international currency symbol

Derived from NLS_TERRITORY

I, E, A

NLS_LANG
See Also: ”Choosing a Locale with the NLS_LANG Environment Variable”

Language, territory, character set

AMERICAN_AMERICA. US7ASCII

E

NLS_LENGTH_SEMANTICS

How strings are treated

BYTE

I, E, A

NLS_LIST_SEPARATOR

Character that separates items in a list

Derived from NLS_TERRITORY

E

NLS_MONETARY_CHARACTERS

Monetary symbol for dollar and cents (or their equivalents)

Derived from NLS_TERRITORY

E

NLS_NCHAR_CONV_EXCP

Reports data loss during a character type conversion

FALSE

I, A

NLS_NUMERIC_CHARACTERS

Decimal character and group separator

Derived from NLS_TERRITORY

I, E, A

NLS_SORT **

Character sort sequence

Derived from NLS_LANGUAGE

I, E, A

NLS_TERRITORY

Territory

Derived from NLS_LANG

I, A

NLS_TIMESTAMP_FORMAT

Timestamp

Derived from NLS_TERRITORY

I, E, A

NLS_TIMESTAMP_TZ_FORMAT

Timestamp with time zone

Derived from NLS_TERRITORY

I, E, A

NLS_DUAL_CURRENCY

Dual currency symbol

Derived from NLS_TERRITORY

I, E, A

Caution:
Rebuilding JD Edwards EnterpriseOne Indexes. Changes to the NLS_SORT parameter from the 'as delivered' BINARY value require that you rebuild JD Edwards EnterpriseOne indexes. That is, you must drop indexes and primary keys and then use UBE R9698713 to rebuild the indexes.

A.2 NLS Considerations for Non Western European Users

All Oracle client configurations should be configured to use the appropriate NLS_SORT and NLS_LANG (host environment) parameters. Oracle client machines would include each of the following:

- Enterprise Server

- HTML (Web) Server

- Deployment Server

- WIN32 developer workstations

- Any bolt-on server which connects to the EnterpriseOne database (for example, an AIA server)

Start SQL*Plus from each Oracle client machine. To view your active NLS_SORT parameter, use this SQL statement:

"SELECT * FROM NLS_SESSION_PARAMETERS WHERE PARAMETER = 'NLS_SORT';"

Ensure that the NLS_SORT parameter is consistent between all machines and equivalent to the value on the database machine. In cases where the value differs from the database machine set the NLS_SORT database value as a host environment variable.

The NLS_LANG host environment variable should be set for the language you are using. For example, if your primary language is Japanese the NLS_LANG host environment variable should be set to JAPANESE_JAPAN.JA16SJIS on all Oracle client machines. As before this change should be performed on the Enterprise Server, OAS (Web) Server, Deployment Server, and WIN32 Developer workstations.

A.2.1 Non-Western European Database Language Considerations

The NLS_LANGUAGE parameter on the Oracle client is used to display Oracle database client error messages. While the NLS_LANGUAGE value on the server declares the language used for server error messages in the alert.log and trace files. Aside from defining this setting, one must install the appropriate Oracle database language translations.

For information about configuring and adding language translations to the current database, see ”Configuring Oracle Database Globalization Support” in the Oracle Database Installation Guide 11g Release 1 (11.1) for Linux Guide.

B Documentation Resources

This appendix contains links to documentation resources for Oracle and Oracle JD Edwards EnterpriseOne product infrastructure.

B.1 Oracle VM Documentation

Oracle VM enables you to deploy operating systems and application software within a supported virtualization environment. Refer to this link for additional information:

http://www.oracle.com/technetwork/documentation/vm-096300.html

B.2 Oracle Exalogic Documentation

Oracle Exalogic is an integrated hardware and software system designed to provide a complete platform for a wide range of application types and widely varied workloads. Exalogic combines Oracle Fusion Middleware software and industry-standard Sun hardware. Refer to this link for additional information:

http://docs.oracle.com/cd/E18476_01/index.htm

B.3 Oracle Enterprise Manager

Oracle Enterprise Manager provides a comprehensive management solution for Oracle WebLogic Server, Oracle Fusion Middleware, and non-Oracle middleware technology. Refer to this link for additional information:

http://www.oracle.com/technetwork/oem/soa-mgmt/soa-mgmt-085552.html

B.4 JD Edwards EnterpriseOne Installation Guide

The JD Edwards EnterpriseOne Installation Guide for Unix with an Oracle Database is designed for management information system (MIS) managers and installers. It outlines the procedures for installing JD Edwards EnterpriseOne Release 9.1.

See Appendix B of this guide, entitled: Oracle RAC with ASM Configuration, for a description of a method to install EnterpriseOne Database Server on a machine other than a VM. This appendix provides information required in order to install JD Edwards EnterpriseOne on Oracle Real Application Clusters (Oracle RAC) with Automatic Store Management (Oracle ASM) configuration.

http://docs.oracle.com/cd/E24902_01/doc.91/e23313.pdf

B.5 JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide

This document provides instructions for installing and running Oracle WebLogic 10.3.5.0.

http://docs.oracle.com/cd/E24902_01/doc.91/e23434.pdf

C Security and Demo Data Configuration

For JD Edwards EnterpriseOne, the demo data that is loaded in the DV910 environment has configuration for both the Mobile Server and One View Reporting applications.

This appendix describes these topics:

- Section C.1, "Licensing Considerations"

- Section C.2, "Understanding Users for the Mobile Application"

- Section C.3, "Understanding Default Passwords for Database Users"

- Section C.4, "Considerations for Securing Database Users"

- Section C.5, "Securing the Miscellaneous Users"

- Section C.6, "Securing Package Build Users"

- Section C.7, "Securing the ESU Users"

- Section C.8, "Securing Other Users"

- Section C.9, "Securing the JDE User"

- Section C.10, "Adding a Security Override"

- Section C.11, "Changing the Admin Password with the P98OWSEC Security Application"

- Section C.12, "Changing the User Password in the Database"

- Section C.13, "Working with the Oracle Business Intelligence Publisher Schema Password"

C.1 Licensing Considerations

The Oracle VM Templates for JD Edwards EnterpriseOne may include demonstration data and sample content, including but not limited to applications, forms, reports, report templates, EnterpriseOne Pages, One View Reporting artifacts, Watch Lists, data queries, portlets or other types of supplementary content. Usage of this content is governed by your applicable license agreement with Oracle, as described in the ”Agreement terms for Oracle Linux, Oracle VM Server and Oracle VM Manager” under ”Section D: Terms for Use of Other Oracle Programs” which is accessible on the Oracle Software Delivery Cloud at this link:

https://edelivery.oracle.com/EPD/GetUserInfo/get_form?caller=LinuxWelcome

C.2 Understanding Users for the Mobile Application

For use with the Mobile application, the P98OWSEC application was used to add the following users with access to the demo data:

- EMSMGR

- MPA07

- MRSS06

Caution:
Although the above users are added, they are disabled by default. You must enable these users in order to use the associated demo data for the Mobile or OVR applications.

C.3 Understanding Default Passwords for Database Users

The Oracle VM templates installation includes the following database users, which are set with default passwords. The expiration for these database users is reset during the configuration of the Oracle VM for the Database Server.

- PS910DTA

- PS910CTL

- PS910

- TESTDTA

- TESTCTL

- DV910

- CRPDTA

- CRPCTL

- PY910

- DD910

- OL910

- SVM910

- SY910

- DEVUSER

- APPLEAD

- JDEDBA

- JDE

- OVR_BIPLATFORM

- OVR_MDS

C.4 Considerations for Securing Database Users

Refer to ”Working with Database Security” in the JD Edwards EnterpriseOne Applications Installation Guide for UNIX with Oracle. This section details how to override the path code user for use with the Installation workbench. The same procedure can be used on the Enterprise Server to change the password settings.

C.5 Securing the Miscellaneous Users

For working with the EnterpriseOne VM templates, it is recommended that you disable (lock) certain users at the database level. If you configure Enterprise Manager for your Oracle 11g database, you can use it to lock these users. Otherwise, you can use the following sqlplus statements:

alter user APPLEAD account lock;
alter user PRODUSER account lock;
alter user DEVUSER account lock;
alter user JDEDBA account lock;

C.6 Securing Package Build Users

It is recommended that you secure your users for EnterpriseOne package builds. To change the password for the PS910, PY910 and DV910 users:

1. Add a security override for the user.

2. Change the password with the EnterpriseOne P98OWSEC security application.

3. Change the password on the database.

C.7 Securing the ESU Users

It is recommended that you secure your users that can apply EnterpriseOne ESUs. To change the password for the PS910DTA, CRPDTA and TESTDTA users:

1. Add a security override for the user.

2. Change the password with the EnterpriseOne P98OWSEC security application.

3. Change the password on the database.

C.8 Securing Other Users

It is recommended that you secure other JD Edwards EnterpriseOne users, which include PS910CTL, CRPCTL, TESTCTL, DD910, OL912, SVM910 and SY910user. To do so, you should change the password on the database.

C.9 Securing the JDE User

It is recommended that you secure the JDE user for EnterpriseOne using these steps:

1. Change the password with the EnterpriseOne P98OWSEC security application.

2. Change the password on the database.

3. Edit the jde.ini file.

The [SECURITY] section of the jde.ini file would appear as shown in the following example:

C.10 Adding a Security Override

To add a Security Override for a user:

1. Logon to the P98OWSEC application.

2. On Work With User Security, locate and select the JDE user for the DEFAULT data source.

3. Select the Form exit and choose Add System User.

4. Click the Find icon to display the current list of System users, as shown in the example below.

5. On Work With System Users, click the Add icon.

6. On System User Revisions, complete the fields for the user you want to add. In the above example, the fields are completed for the DV910 user.

7. Click the Save icon.

8. Click the Find icon again to confirm the added user is displayed in the list of System users list. For example, if you just added the DV910 user the list would be as shown in the following example:

9. From the P98OWSEC screen click the Add icon to add the new system user to JDE.

The Security Revisions screen is displayed.

10. On Security Revisions, select the JDE user for the User ID.

Select the Data Source for the user, which in this case is Central Objects - DV910. Then select the System User to match Data Sources in this case the DV910 user. In this case for adding the DV910 user, the completed form is shown above.

As shown in the example above, when you return to the P98OWSEC screen a row is displayed for the newly-added JDE user for DV910.

11. On Work With User Security, enter the user in this case the DV910 in the User ID /Role text box for the P98OWSEC application.

12. Click the Find icon.

13. On Security Revisions, click the Add icon and enter the user, which in this case is DV910, enter DEFAULT for the Data Source, and enter the user for the SYSTEM user, which in this case is DV910.
As shown in the following example, when you return to the P98OWSEC a row is displayed for the newly-added user, which in this case is DV910.

This completes setup a security override.

C.11 Changing the Admin Password with the P98OWSEC Security Application

To change the Admin password with the JD Edwards EnterpriseOne P98OWSEC security application:

1. Log in to the EnterpriseOne system as the JDE user.

2. Fast path to the P98OWSEC|W98OWSECF application.

3. On Administration Password Revisions, locate and select the user ID that you want to change. In this example, the selected user ID is PRODDTA.

4. On Administration Password Revisions, enter the new password and verify it.

5. Exit the security application to save your changes.

C.12 Changing the User Password in the Database

To change the user password in the database, execute the following SQL statement as the sysdba user on the ovsorcl database:

alter <user> sys identified by <new password>;

Substitute the <user> with the user id and <new password> with the new password.

C.13 Working with the Oracle Business Intelligence Publisher Schema Password

There are two database schemas associated with Oracle Business Intelligence Publisher (BI Publisher), MDS and BIPLATFORM. These schemas are created with a prefix during the Repository Creation Utility (RCU) process.

There are two steps to change these passwords:

- Section C.13.1, "Step 1: Modify the Schema Password from the Database"

- Section C.13.2, "Step 2: Modify the Data Source Connection Information from the WebLogic Administration Console"

C.13.1 Step 1: Modify the Schema Password from the Database

To modify the schema password from the database:

1. Use sqlplus to log on to the database as the sysdba user.

2. Enter the following commands to update the password:

alter user prefix_MDS identified by <new_password>;
alter user prefix_BIPLATFORM identified by <new_password>;
commit;

C.13.2 Step 2: Modify the Data Source Connection Information from the WebLogic Administration Console

To modify the data source connection information from the WebLogic Administration Console:

1. Log on to the WebLogic Administration Console.

2. Select Data Sources from Services.

3. From the list of Data Sources, click on the name the mds-owsm data source in order to display the Settings.

4. On Settings for mds-owsm, select the Connection Pool tab.

5. Click the Lock and Edit button.

Caution:
Ensure the schema that you are editing (prefix_MDS or prefix_BIPLATFORM), if they have different password.

6. Enter the new password in the Password and Confirm Password fields.

7. Repeat Steps 3 through 6 above for both of these data sources:
EPMSystemRegistry

bip_datasource

8. Click the Activate Changes button.

9. You must restart all servers for the changes to take affect.

D Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode

This appendix describes using the Oracle Universal Installer (OUI) for the Platform Pack in GUI mode to install the JD Edwards EnterpriseOne Database Server components on a non-virtualized database server.

Note:
If your non-virtualized database is an Oracle Exadata or ODA machine, you cannot use the OUI in GUI mode. Instead you must install in silent mode as described in the chapter of this guide entitled: Chapter 7, "Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server".

This method assumes you are not installing the VM template for the JD Edwards EnterpriseOne database server, and that the installation of these components on a non-virtualized database server will be used with the Oracle VM templates for JD Edwards EnterpriseOne that utilizes the complementary components described in this guide.

This appendix discusses these topics:

- Section D.1, "Understanding the Platform Pack in GUI Mode for RAC Database Servers"

- Section D.2, "Working with the Platform Pack Installer for a Non-Virtualized Database Server"

D.1 Understanding the Platform Pack in GUI Mode for RAC Database Servers

If you are using Oracle Real Application Clusters (RAC) to drive your database, you must set an environment variable ORACLE_SID to the instance on the database machines using this procedure:

1. Determine the name of the instance on the database machines by running this command:
srvctl status database -d ovsorcl

Note:
When setting up the JD Edwards EnterpriseOne Database Server components on non-virtualized database servers that are to be used with JD Edwards EnterpriseOne Oracle VM templates, the connect string must match across all instances of the templates. The standard value is ovsorcl. If you change this value, you must make the corresponding change when instantiating database connectivity for every OVM template using the JD Edwards OVM Tools described in the section of this document entitled: Section 4.4, "Working with JD Edwards OVM Tools (config.sh Configuration Script)".

2. Find your server name on the output of the status command and use that instance name. For example ovsorcl1.

3. Set the environment variable to this instance name. For example:
export ORACLE_SID=ovsorcl1

Caution:
Failure to do this will cause the load scripts to fail.

D.2 Working with the Platform Pack Installer for a Non-Virtualized Database Server

This section discusses:

- Section D.2.1, "Working with the zip File for the Platform Pack Installer"

- Section D.2.2, "Running the Platform Pack Installer for Non-Virtualized Database Servers"

- Section D.2.3, "Working with Installer Log Files"

- Section D.2.4, "Deinstalling the Platform Pack for Non-Virtualized Database Servers"

D.2.1 Working with the zip File for the Platform Pack Installer

The zip file for the Platform Pack Installer for a non-virtualized database server is included in the Media Pack for JD Edwards EnterpriseOne VM Templates, which is available from the Oracle Software Delivery Cloud:

https://edelivery.oracle.com/

You should unzip the Platform Pack installer on your non-virtualized database server. Then run give ownership to your Oracle account. For example:

chmod -R 775 Exadata

chown -R oracle:oinstall Exadata

D.2.2 Running the Platform Pack Installer for Non-Virtualized Database Servers

To run the Platform Pack installer for non-virtualized database servers in GUI mode (not available for Exadata or ODA):

1. Change directory to the Exadata/install folder.

2. Run the install using this command
./runInstaller

3. On Welcome, click the Next button.

4. On Select Installation Type, click this radio button:
Database

This selection installs the components that match the OVM Enterprise Server template.

5. Click the Next button.

6. On Specify Home Details, complete these fields:

- Name
Enter a name for this installation. For example:

JDEOVM6_910

- Path
Enter the location where you want the installer to place the database dump files and scripts. For example:

/u01/app/oracle/JDEOVM/e910

7. Click the Next button.

8. On Would you like to Install or Upgrade EnterpriseOne?, click the first radio button that is entitled:
Install

Install EnterpriseOne

Choose this option for OVM

Caution:
You must choose Install otherwise the Business Data and Control Tables will not get loaded.

9. Click the Next button.

10. On Database Options, complete these fields:

- Database Type
You can accept the default value, which is Oracle.

- Hostname / SCAN listener
Enter the unqualified hostname or Single Client Access Name (SCAN) for the database server. For example, denlcmlx3.

- Secure Password
For use with Oracle VM Templates, you must accept the DEFAULT value for this field.

Note:
The Secure Password is used for all database users created by the installer. The default password is the same as the database user name. For example, user name = JDE, password = JDE. The value for the password cannot be longer than 10 characters.

11. Click the Next button.

12. On Password Strength, for use with Oracle VM templates you must use the DEFAULT password; therefore you must accept the default value of No.

Note:
The installer program does not force you to change your password for a Weak value.

13. Click the Next button.

14. The installer presents the above screen as a security precaution. That is, it is important to note the security implication when you agree to proceed with the installation using the default password values that are required and specified in the preceding screen. These values are only required to complete the installation after which it is strongly recommended that you immediately change these passwords after installation as described in the appendix of this guide entitled: Appendix C, "Security and Demo Data Configuration".
To ensure you understand and agree to these terms, the installer defaults to a No value. In order to proceed and successfully complete the installation, you must explicitly change the value from No to Yes, as shown below:

Caution:
As noted on this screen, by choosing Yes you are acknowledging that by accepting the default passwords (which is required to completed the install) you are exposing your system to potential security concerns. As previously noted, after installation you should immediately change the passwords on your installed system as described in the appendix of this guide entitled: Appendix C, "Security and Demo Data Configuration".

15. Click the Next button.

16. On Warning, Test data will be laid down for PS and DV Environments, the following warning is displayed:
Demonstration data is included as part of this product which is not intended to be used in production systems. Care must be taken that systems/processes/servers containing the demonstration data are not exposed to untrusted environments where an attacker might be able to use their knowledge of the data to launch an attack against the systems/processes/servers.

17. After you have read, understood, and accepted the stated security risk, click the Next button.

18. On Target Server Names, complete these fields:

- Deployment Location
Enter the Deployment Location. For example, Corporate.

This value is used for package builds of JD Edwards EnterpriseOne.

- Deployment Server
Enter the name of the Deployment Server. This name must be all upper case and non-qualified. For example: CUSTVMDEP.

- HTML Server
Enter the name of the HTML Server. This name must be all lower case and non-qualified. For example: custvmhtml.

- Enterprise Server
Enter the name of the Enterprise Server. This name must be all lower case and non-qualified. For example: custvment.

- Are you using Automated Storage Management YES / NO
If you are using Oracle ASM on your database server, enter a value of YES.

- Create Oracle BIP Server YES or NO
If you want the Platform Pack installer to create an Oracle BI Publisher Server for JD Edwards EnterpriseOne, enter a value of YES.

- Oracle BI Publisher Server
If you specified YES in the previous field to create an Oracle BI Publisher Server, enter the name of the server. This name must be all lower case and non-qualified. For example: custvmbip.

- Password for SYS user
Enter the password for your Oracle SYS user on the database server.

19. Click the Next button.

20. On Warning Test data ill be laid down for PS and DV Environments, the warning informs you that the installation delivers test data that is not intended to be used in production environments. The primary purpose of this test data is for use by EnterpriseOne support when diagnosing issues you may have with the software. Because this data is not used in any production environment, it should not pose a security threat. Regardless, it is strongly recommended that as a best practice you secure your system as soon as possible after installing by changing your JDE and Database passwords. Refer to as described in the appendix of this guide entitled: Appendix C, "Security and Demo Data Configuration".

21. Click the Next button.
If you choose ASM = YES on the previous Target Server Names screen, refer to: "Oracle Database Information - ASM = YES".

If you choose ASM = NO on the previous screen, refer to: "Oracle Database Information - ASM = NO".

Oracle Database Information - ASM = YES

Note:
The above screen and these steps are applicable if you chose ASM = YES on the Target Server Names screen in Step 18.

On Oracle Database Information, complete these fields:

- Connect String
When setting up the JD Edwards EnterpriseOne Database Server components on non-virtualized database servers that are to be used with JD Edwards EnterpriseOne Oracle VM templates, the connect string must match across all instances of the templates. The standard value is ovsorcl. If you change this value, you must make the corresponding change when instantiating database connectivity for every OVM template using the JD Edwards OVM Tools described in the section of this document entitled: Section 4.4, "Working with JD Edwards OVM Tools (config.sh Configuration Script)".

- SYSTEM User
You must accept the default values for this field, which is system. Do not specify this value as sys.

- SYSTEM Password
Enter the password for your SYSTEM user.

- Have you pre-created tablespaces?
Use the radio buttons to select whether you have pre-created your Oracle tablespaces. If you choose No, the Platform Pack installer will execute scripts to create the tablespaces. If you choose Yes, you must have already created the tablespaces prior to running the Platform Pack installer.

- ASM disk group for tables
Enter the ASM Disk Group name(s) that will be used for your JD Edwards EnterpriseOne database tables. For example, DISK_GROUP1.

- ASM disk group for Indexes
Enter the ASM Disk Group name(s) that will be used for your JD Edwards EnterpriseOne database indexes. For example, DISK_GROUP2.

- Run Scripts Option
Use the pulldown to select when you want the Platform Pack installer to automatically run the database scripts, or whether you want the installer to only deliver the scripts so you can run them manually. By choosing to manually run the scripts you can choose to further edit and/or run them sequentially.

Proceed to the Step 23.

22. Oracle Database Information - ASM = NO

Note:
The above screen and these steps are applicable if you chose ASM = NO on the Target Server Names screen in Step 18.

On Oracle Database Information, complete these fields:

- Connect String
For purposes of running the Platform Pack installer, the value for this field must be ovsorcl. This is required to match the values specified in JD Edwards EnterpriseOne tables and also in jde.ini files on the Enterprise Server.

- SYSTEM User
You must accept the default values for this field, which is system. Do not specify this value as sys.

- SYSTEM Password
Enter the password for your SYSTEM user.

- Have you pre-created tablespaces?
Use the radio buttons to select whether you have pre-created your Oracle tablespaces. If you choose No, the Platform Pack installer will execute scripts to create the tablespaces. If you choose Yes, you must have already created the tablespaces prior to running the Platform Pack installer.

- Table tablespace Directory
Enter the mount point for the tablespaces of your JD Edwards EnterpriseOne database tables. For example:

/u01/jdedwardsppack/ORCL/Tables

- Index tablespace Directory
Enter the mount point for the tablespaces of your JD Edwards EnterpriseOne database indexes. For example:

/u01/jdedwardsppack/ORCL/Indexes

- Run Scripts Option
Use the pulldown to select when you want the Platform Pack installer to automatically run the database scripts, or whether you want the installer to only deliver the scripts so you can run them manually. By choosing to manually run the scripts you can choose to further edit and/or run them sequentially.

23. Click the Next button.

24. On Summary, review and verify your installation choices.

25. Click the Install button.

The Platform Pack installer displays a progress screen. Also at the bottom of the screen, a message displays the location of the log file for this installation.

Click the Stop installation ... button if you want to cancel the installation before it completes. Otherwise, the installer displays the following screen when it completes.

26. On End of Installation, verify the Platform Pack installation was successful. You should verify the OUI log files which are located in the path shown in the Please remember ... section. Also check the Oracle load logs which are located in this directory:
/u01/jdedwardsppack/e910/ORCL

Tip:
It especially important that you check and verify the Import* logs.

Note:
The above location is also where you will find this database script, which can be run manually:
InstallOracleDatabase.sh

D.2.3 Working with Installer Log Files

Upon completion, the installer reports success or failure for the Oracle database scripts. To verify the status of the install, you should:

- Check the logs in your install location in this directory:
ORCL/logs

- Check the logs in the Oracle inventory location, which by default is:
/u01/app/oraInventory/logs

This directory contains these log files:

- silentInstallxxx.log

- oraInstallxx

- installActionsxxx

D.2.4 Deinstalling the Platform Pack for Non-Virtualized Database Servers

Use this procedure to deinstall the Platform Pack for non-virtualized databases servers (such as Oracle Exadata and ODA).

1. Navigate to your install location.

2. Change directory to ORCL.

3. Run this script:
drop_db.sh

4. Navigate to the oui folder within your install location.

5. Change directory to bin.

6. Use this command to run the OUI installer in silent mode to deinstall the Platform Pack for non-virtualized database servers.
./runInstaller -deinstall -silent REMOVE_HOMES={"/u01/JDEOVM/e910"} ORACLE_HOME_NAME="JDEOVM_E910"

E Applying Patches

All software components for Oracle JD Edwards templates for Oracle VM environments are fully supported by Oracle Support. Patches are available for these categories of products:

- Section E.1, "Oracle Systems"

- Section E.2, "JD Edwards Applications, Clients, and Servers"

E.1 Oracle Systems

Products in the Oracle Systems category include:

- Oracle VM

- Oracle Linux

- Oracle Fusion Middleware (WebLogic Server)

- Oracle Database (such as 11g and 12c)

- BI Publisher Server

- Application Developer Framework

To obtain patches for Oracle Systems:

1. Go to My Oracle Support at this link:
https://support.oracle.com/

2. Once you have signed into My Oracle Support, the following screen is displayed:

3. Click the tab for Patches & Updates.

4. Click the link for Product Family (Advanced) and complete the fields as appropriate for your Oracle Systems product.

E.2 JD Edwards Applications, Clients, and Servers

Products in this category include:

- JD Edwards EnterpriseOne Applications

- JD Edwards EnterpriseOne Enterprise Server

- JD Edwards EnterpriseOne HTML Server

- JD Edwards EnterpriseOne BI Publisher Server

- JD Edwards EnterpriseOne Mobile Server

- JD Edwards EnterpriseOne Deployment Server

- JD Edwards EnterpriseOne Development Client

Patches for products in this category are available on the JD Edwards Update Center at this link:

https://updatecenter.oracle.com/apps/WebSearch/updatecenter.jsp?

To navigate to the Update Center from My Oracle Support:

1. Go to My Oracle Support at this link:
https://support.oracle.com/

2. Once you have signed into My Oracle Support, the following screen is displayed:

3. Click the tab for Patches & Updates.

4. In the left pane, expanded the section entitled: Patching Quick Links.

5. In the top section entitled: Software and Patch Search Sites, click the link for JD Edwards.
Your browser will display a pop-up window directing you to the JD Edwards EnterpriseOne Update Center as shown in the following screen:

F Managing Disk Images Used Within the EnterpriseOne VMs

You can use the Linux Logical Volume Manager (LVM) to manage disk images used within the JD Edwards Virtual Machines (VM). The procedures in this appendix demonstrates how to extend the current disk file system by creating a new disk image, creating a physical volume, and then adding the physical volume to the existing logical volume.

This appendix discusses these topics:

- Section F.1, "Creating a New Disk Image"

- Section F.2, "Updating the vm.cfg File to Add the New Disk Image"

- Section F.3, "Creating a Partition Table"

- Section F.4, "Creating a New Physical Volume with the New Disk Image"

- Section F.5, "Extending the Volume Group with the New Physical Disk"

- Section F.6, "Extending the Logical Volume with the New Volume Group"

- Section F.7, "Resizing the File System"

- Section F.8, "Logical Volume Manager Command Summary"

Caution:
It is highly recommended that you backup the JD Edwards EnterpriseOne application image file before executing the procedures in this appendix.

F.1 Creating a New Disk Image

The current verions of the JD Edwards EnterpriseOne VM templates are delivered as a single disk image paired with a single disk system image to create a fully functioning application. A configure file named vm.cfg is also included with each set of images, and is used to provide instruction to the VM Server on such things as number of Virtual CPU, memory, and certain file locations.

To create a new disk image:

1. Use the Linux disk command ls to show the content of a application directory.

2. Create the new disk image that will be used in the VM application by executing the dd command to create an empty file. The following shows an example command string to create an empty 10GB file named disk2.img.
dd if=/dev/zero of=disk2.img bs=1 count=1024 seek=10GB

See Also

- For more information refer to the Linux man pages for the dd command.

F.2 Updating the vm.cfg File to Add the New Disk Image

To update the vm.cfg file to add the new disk image that you created in the previous section:

1. You need to update the vm.cfg file with the name and location of the new image. In the example below, the new disk (disk2.img) image is added as the last line in the disk section with the designation of hdc.
'file:/OVS/development/system58/disk2.img,hdc,w',1

2. Save the updated vm.cfg file.

3. You can review available disk space on the system prior to adding the new disk image by running the df -h command.

4. Start the VM using the xm create to create the new disk image in the VM.

Note:
The following example uses the command xm create from the command line. Alternately you can use the OVM Manager to start the VM from the OVM GUI console.

xm create vm.cfg

5. Once the VM is up and running, sign into the 'root' user account.

See Also

- Refer to the Oracle VM Server User Guide for more details on the content of the vm.cfg file.

F.3 Creating a Partition Table

To make the disk image usable, you must create a partition table. This is done using the fdisk command.

To create a partition table:

1. Verify that the new disk image (in the example in this guide disk2.img) has been attached to the running VM, and the name of the new file device (hdc) by running the fdisk -l command from the command line as shown below.

2. To create a partition table, instead of using the -l option, replace it with the disk device. For example, in the example used in this guide is hdc.
fdisk /dev/hdc

3. Next, at the prompts from the fdisk command, enter the following command letters to create primary partition #1:

n
p
1
<enter>
<enter>

4. This process created a new device hdc1 which is the first partition on the hdc disk device. Since this new disk will be part of a logical volume, the disk type must be set to 8e which indicates that this partition is for Linux LVM. While still within the fdisk command prompts, enter the following commands.

t
8e

5. The next command writes these changes out to the disk images and exits the fdisk program.

w

See Also

- For more information refer to the Linux man pages for the fdisk command.

F.4 Creating a New Physical Volume with the New Disk Image

After you create a partition table as described in the previous procedure, the disk.image is now ready to become a physical device that can be added to a logical volume.

To create a new physical volume with the new disk image:

1. Execute the pvcreate command as shown below:
pvcreate /dev/hdc1

See Also

- For more information refer to the Linux man pages for the pvcreate command.

F.5 Extending the Volume Group with the New Physical Disk

To extending the volume group with the new physical disk:

1. You must determine the name of the volume group to which the disk will be added by using the vgscan command. In the below example, the name of the volume group is VolGroup00.

2. Using the volume group name found in the previous step, extend the volume group by using the vgextend command. The below example uses VolGroup00 as the volume group name.
vgextend VolGroup00 /dev/hdc1

See Also

- For more information refer to the Linux man pages for the vgextend command.

F.6 Extending the Logical Volume with the New Volume Group

As you did with the volume group, you must also extend the logical volume. To do so, you need to determine the logical volume name using the lvscan command. In this example, the logical volume name is LogVol01.

1. Determine the logical volume name using the lvscan command. In this example, the logical volume name is LogVol01.

2. Using the name of the logical volume returned by the lvscan command, extend the logical volume using the following command. In this example, the name of the logical volume is LogVol01.
lvextend -l +100%FREE /dev/VolGroup00/LogVol01

Note:
The second command parameter of +100%FREE instructs the program to use all of the free space available on the new disk image. To use less than 100%, you would use a numerical value.

See Also

- For more information refer to the Linux man pages for the vgextend command.

F.7 Resizing the File System

The final process is to resize the file system to enlarge the current LVM files system based on the size of the new disk image being added.

To resize the file system:

1. Enter the resize2fs command:
resize2fs /dev/VolGroup00/LogVol01

2. Verify that the new disk image has been added by issuing the df -h command.

Upon verification, you have successfully added a new disk image to you JD Edwards VM image.

See Also

- For more information refer to the Linux man pages for the resize2fs command.

F.8 Logical Volume Manager Command Summary

This section provides a summary of the Logical Volume Manager commands using in this guide.

- [fdisk]
This is the disk utility command.

To add a number 1 primary partition, use this syntax where subsequent values are entered at the command prompts:

fdisk /dev/hdc
n
p
1
<enter>
<enter>

While still in the prompts for the preceding fdisk commands, to change the type of disk to LVM:

t
8e

While still in the prompts for the preceding fdisk commands, to permanently save the changes to the disk:

w

- [pvcreate]
Use this utility to initialize a disk or partition for use by LVM. For example:

pvcreate /dev/hdc1

- [vgscan]
Use this command to scan all disks for volume groups and rebuild caches (returns names).

- [vgextend]
Use this command to add physical volumes to a volume group. For example:

vgextend VolGroup00 /dev/hdc1

- [lvscan]
Use this command to scan all disks for Logical Volumes (returns names). For example:

- [lvextend]
Use this command to extend the size of a logical volume. For example:

lvextend -l +100%FREE /dev/VolGroup00/LogVol01

- [resize2fs]
Use this command to resize the file system. For example:

resize2fs /dev/VolGroup00/LogVol01

G Default Port Listing Used Within the VMs for JD Edwards EnterpriseOne

The VM templates for JD Edwards EnterpriseOne have several pre-configured ports. It is important that you are aware of these ports are so you can make informed decisions on whether to change those ports or leave the default values. If you want to change ports you should check the configuration and installation documents for the affected software.

- Database Configuration
http://docs.oracle.com/cd/E16655_01/index.htm

- JD Edwards Enterprise One Configuration
http://docs.oracle.com/cd/E24705_01/index.htm

- Weblogic Server 12 Configuration
http://docs.oracle.com/cd/E24329_01/index.htm

- Weblogic Server 11 Configuration
http://docs.oracle.com/cd/E23943_01/index.htm

The following table lists the default ports used by each of the VM templates for JD Edwards EnterpriseOne servers.

Server Template

Default Port

Comment

Database

1521

The Database Server uses this port to communicate with the other JD Edwards EnterpriseOne servers.

Enterprise Server

1521

The Enterprise Server uses this port to communicate with the database server.

6016

This port is used for E1 communication as specified by serviceNameListen from the JDE.INI file using these rules:

- If enablePredefinedPorts is 1 then the next port is serverNameListen+1 until maxNetProcesses is reached.

- If enablePredefinedPorts is 0 then the next port whatever the OS allocates

14501
14502

The Enterprise Server uses these ports to communicate with Server Manager.

HTML Server

1521

The HTML Server uses this port to communicate with the database server.

6016

The HTML Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameConnect in the JDE.INI file.

6080

The HTML Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameListen in the JDE.INI file.

8080

The WebLogic Server function of the HTML Server uses this port to communicate with JD Edwards EnterpriseOne.

5556

The WebLogic Server function of the HTML Server uses this port for the WebLogic node manager.

7001

The WebLogic Server function of the HTML Server uses this port for WebLogic Administrator control.

1527

The WebLogic Server function of the HTML Server uses this port for the Derby database that is built-into WebLogic.

14501
14502

The HTML Server uses these ports to communicate with Server Manager.

BIP Server

1521

The BIP Server uses this port to communicate with the database server.

6016

The BIP Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameConnect in the JDE.INI file.

6080

The BIP Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameListen in the JDE.INI file.

9556

The WebLogic Server function of the BIP Server uses this port for the WebLogic node manager.

9704

The WebLogic Server function of the BIP Server uses this port for the BIP application.

7001

The WebLogic Server function of the BIP Server uses this port for WebLogic Administrator control.

Note: The BIP Server is not under control of Server Manager, therefore no port is required for that purpose.

Mobile Server

1521

The Mobile Server uses this port to communicate with the database server.

6016

The Mobile Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameConnect in the JDE.INI file.

6080

The Mobile Server uses this port to communicate with JD Edwards EnterpriseOne. The value derived from the serviceNameListen in the JDE.INI file.

5556

The WebLogic Server function of the Mobile Server uses this port for the WebLogic node manager.

7001

The WebLogic Server function of the Mobile Server uses this port for ADF Administrator control.

7005

The WebLogic Server function of the Mobile Server uses this port for ADF Server communication.

8001

The WebLogic Server function of the Mobile Server uses this port for BSSV Administrator control.

8006

The WebLogic Server function of the Mobile Server uses this port for BSSV Server communication.

14501
14502

The Mobile Server uses these ports to communicate with Server Manager.

AIS Server

1521

The AIS Server uses this port to communicate with the database server.

8080

The AIS Server uses this port to communicate with the HTML Server.

5556

The WebLogic Server function of the AIS Server uses this port for the WebLogic node manager.

7001

The WebLogic Server function of the AIS Server uses this port for WebLogic Administrator control.

8090

The WebLogic Server function of the AIS Server uses this port for the AIS applications.

14501
14502

The AIS Server uses these ports to communicate with Server Manager.

Server Manager

5556

The WebLogic Server function of Server Manager uses this port for the WebLogic node manager.

5556

The WebLogic Server function of Server Manager uses this port for the WebLogic node manager.

7001

The WebLogic Server function of Server Manager uses this port for WebLogic Administrator control.

8999

The WebLogic Server function of Server Manager uses this port for the Server Manager application.

14501

Server Manager uses this port for the Server Manager application.

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.