Preparing for Development Client Installation

To prepare for the installation of Release 9.2 on Development Clients, you must modify the Development Client JDE.INI on the Deployment Server and the JD Edwards EnterpriseOne system administrator must create a user profile for every user before that user can log on to Release 9.2. You must also copy the configured tnsnames.ora from the oracle\E1local directory to the \client directory on the Deployment Server, as specified in the next section of this chapter entitled: Working With Development Client Installation

Note: Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for additional details on installing the Development Client.

Prerequisites

• Before installing Release 9.2 on a Development Client used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in the Minimum Technical Requirements (MTRs). Refer to the section of this guide entitled: Accessing Certifications. Also refer to the appropriate Microsoft documents for installation information.

• The names of the Deployment Server, Enterprise Server, and the Development Client cannot exceed 15 characters in length.

• IPv4 Requirement

  The Development Client requires Microsoft Windows IPv4 for connectivity. It cannot function with IPv6. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle WebLogic Server (WLS) and WebSphere Application Server (WAS) Express details.

Note: You must have full administrator privileges to install Release 9.2 on the Microsoft Windows 7-based Development Clients. For details, refer to the JD Edwards EnterpriseOne Development Client Installation Guide on the Oracle Technology Network (OTN).

During Development Client installation, connectivity is required for:

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

  \oneworld

• Read access to the subdirectories located under this directory:

  \pathcode\package

  For example:

  \\deployment_server_name\E920\PD920\package

• Read/write access to this directory on the primary Deployment Server:

  \client

  For example:

  \\deployment_server_name\E920\client

• Refer to the JD Edwards EnterpriseOne Deployment Server Reference Guide for Enterprise Systems for Microsoft Windows in Setting Up a Development Client Installer on the Deployment Server for these topics:

  • Understanding the JD Edwards Clients (Development and Web)

  • Understanding the Oracle Universal Installer

  • Creating the Web Development Feature

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

  • Updating the Database Drivers in the JDBJ.ini File

  • Copying the JDK to the Deployment Server

  • Updating the InstallManager.htm File

  • Updating the oraparam.ini File

  • Setting Up Local Database Installers

• Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle WebLogic Server (WLS) and WebSphere Application Server (WAS) Express for these topics:

  • Understanding the Development Client Installation

    This section describes Understanding Installation Steps and Understanding Destination Paths.

  • Installing WebSphere Express 7.0 or WebSphere for Developers 7.0

  • Installing the Local Database

  • Installing the Development Client

  • Working With SnapShot on the Development Client

  • Deinstalling the Development Client

  • Removing the Local Database

  • Troubleshooting the Installation Process

  • Installing a Development Client from the Command Line

  • Manual Cleanup of a Deinstalled Development Client

  • Manual Cleanup of a Deinstalled Oracle Database

  • Installing Multiple Pathcodes