8 Installing the Development Clients for Developers and System Administrators

This chapter includes these topics and tasks:

• Section 8.1, "Understanding Development Client Installation"

• Section 8.2, "Preparing for Development Client Installation"

• Section 8.3, "Working With Development Client Installation"

• Section 8.4, "Understanding User Profiles and Languages"

8.1 Understanding Development Client Installation

Release 9.1 software for Development Clients is first installed on the Deployment Server, and then deployed from the Deployment Server to Development Clients for developer and system administrator workstations.

The Development Clients are Microsoft Windows-based machines. Refer to the Oracle Certifications for specifically-supported versions of Microsoft Windows.

Note:

The JD Edwards EnterpriseOne installation delivers pre-built packages that are ready for use as delivered.

In order for the Development Client to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and Development Clients, in addition to the procedures to verify and modify the JDE.INI on the Development Clients and the JDE.INIjde.ini on the Enterprise Server.

See Also

• Refer to Section 1.6, "Language Process Overview" for more information about how you enable multilingual installations on Development Clients.

• JD Edwards EnterpriseOne Development Client Installation and Configuration Guide

• JD Edwards EnterpriseOne Tools Package Management Guide

8.2 Preparing for Development Client Installation

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

Note:

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

Prerequisites

• Uninstall the previous software version on each Development Client before installing the new version. See Chapter 26, "Deinstalling the Software" for more information about uninstalling previous releases of JD Edwards EnterpriseOne.

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

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

• IPv4 Requirement

  The Development Client requires Microsoft Windows IPv4 for connectivity. It cannot function with IPv6. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide details.

Note:

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

During Development Client installation, connectivity is required for:

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

  \oneworld

• Read access to the subdirectories located under this directory:

  \pathcode\package

  For example:

  \\deployment_server_name\E910\PD910\package

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

  \client

  For example:

  \\deployment_server_name\E910\client

• Refer to the Deployment Server Reference Guide in Setting Up a Development Client Installer on the Deployment Server for these topics:

  • Understanding the JD Edwards Clients (Development and Web)

  • Understanding the Oracle Universal Installer

  • Creating the Web Development Feature

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

  • Updating the Database Drivers in the JDBJ.ini File

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

  • Updating the InstallManager.htm File

  • Updating the oraparam.ini File

  • Setting Up Local Database Installers

• Refer to the Development Client Installation Guide for these topics:

  • Understanding the Development Client Installation

    This section describes Understanding Installation Steps and Understanding Destination Paths.

  • Installing WebSphere Express 7.0 or WebSphere for Developers 7.0

  • Installing the Local Database

  • Installing the Development Client

  • Working With SnapShot on the Development Client

  • Deinstalling the Development Client

  • Removing the Local Database

  • Troubleshooting the Installation Process

  • Installing a Development Client from the Command Line

  • Manual Cleanup of a Deinstalled Development Client

  • Manual Cleanup of a Deinstalled Oracle Database

  • Installing Multiple Pathcodes

8.3 Working With Development Client Installation

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

Caution:

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

This section discusses these topics:

• Section 8.3.1, "Creating a Desktop Shortcut"

• Section 8.3.2, "Using a Shared Drive"

• Section 8.3.3, "Understanding Third-Party Products"

8.3.1 Creating a Desktop Shortcut

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

\JDEdwards\E910\OneWorld Client Install

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

To create a desktop shortcut:

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

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

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

4. Skip to the next task entitled: Using a Shared Drive.

8.3.2 Using a Shared Drive

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

To use a shared drive:

1. Double-click InstallManager.exe to start the Release 9.1 installation manager.

   The InstallManager.exe file is located in this folder:

   OneWorld Client Install
   

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

3. On Client Workstation Setup, click Next.

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

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

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

   Tip:

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

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

   Field	Description
   Select Setup Type	Select Development or Production objects. You should only select the Development option if you intend to develop Release 9.1 applications. Note: Select the Development option only if you intend to develop JD Edwards EnterpriseOne applications.
   Install Path	Select the drive and directory in which to install the package. For example, this is the typical path for Release 9.1: c:\E910

   
   

6. To install the package, click Finish.

   InstallManager shows the status of the installation process through a series of forms.

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

7. Reboot if necessary.

   Caution:

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

8.3.3 Understanding Third-Party Products

A local Oracle Enterprise Edition (OEE) is required for Release 9.1 Development Clients. The OUI installer for the Development Client installs OEE and the Development client separately. Refer to the Development Client Installation Guide.

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

Microsoft Internet Explorer provides:

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

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

8.4 Understanding User Profiles and Languages

Note:

Release 9.1 supports group preferences for user profile Development Client configuration and environment assignment.

For user and group profiles, you should use the preloaded users to perform the installation process. The system administrator needs to create a user profile before the user can log on to Release 9.1.

All users are assigned a language preference code within the user profile. The language preference code field specifies which language is presented on the applicable form or report. You can set up your users and groups when determining how groups are to be organized and what preferences each group shared to have.

For languages, the JDE.INI on the Windows-based Deployment Server are updated automatically. For multiple language usage, both the Enterprise Server and Development Client JDE.INIjde.ini need to be modified for the preferred language being installed.

Existing user profile configurations are set up after the upgrade process finishes. You should add any new environments to these users as needed.

See Also

• JD Edwards EnterpriseOne Tools System Administration Guide for more detailed information about setting up group profiles and how to use them, as well as for information about defining user display preferences.