1. Deployment Server Reference Guide for UNIX
  2. Understanding the JD Edwards Clients (Development and Web)

Understanding the JD Edwards Clients (Development and Web)

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

Note:

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

  • Web Client

    Components that run in a web browser.

  • Development Client

    Composed of standard Windows components and Web Client.

The Web Client part of the Development Client runs inside an Application Server, with the user interface displayed in a browser. For Tools Releases prior to 9.2.9, the supported Application Servers installed on the Development Client machine are:

  • Oracle WebLogic Server (WLS)

  • IBM WebSphere Application Server (WAS)

The version of the Web Client is known by either of these names:

  • WLSH4A (WebLogic Server HTML for Applications)

  • WASH4A (WebSphere Server HTML for Applications)

Note: If you are not using WLSH4A or WASH4A, you can ignore references to it in the subsequent sections.

Prior to Tools Release 9.2.9, the Application Server such as WebLogic or WebSphere was installed on the Development Client computer to run the Web Client in a browser. With Tools Release 9.2.9, EnterpriseOne connects to a remote Application Server (such as, WebLogic or WebSphere) installed on a separate server known as a Development HTML Server.

The information needed to connect to this remote Development HTML Server is configured by the EnterpriseOne administrator in the jde.ini on the Deployment Server. This jde.ini is copied to the Development Client machine during installation of the EnterpriseOne Development Client software

This chapter describes the setup of the JD Edwards EnterpriseOne Development Client installer and installation package on an EnterpriseOne Deployment Server. This setup on the Deployment Server must be done before a user can install a JD Edwards EnterpriseOne Development Client on a workstation. The installation package specifies the components to install and may or may not include the Web Client.

If you are on Tools Releases prior to 9.2.9, you can find instructions on how to install Web Clients for both Application Servers and their WLSH4A and WASH4A features, as well as the installation of the WebLogic and WebSphere Application Servers in the JD Edwards EnterpriseOne Development Client Installation Guide.

Note: These instructions assume that all prerequisites for running EnterpriseOne on the Deployment Server are installed.
Note: The EnterpriseOne Deployment Server requires that the E1Local Oracle database be installed on the Deployment Server machine. Some Tools Releases also require that the E1Local Oracle database be installed on the Development Clients as well. Starting with Tools Release 9.2.5.0, the E1Local Oracle database will not be used on the Development Clients and can be uninstalled. It is important to note that the database is still required on the Deployment Server.

Installation of the JD Edwards Deployment Server provides installers for these components that can be installed on a Development Client:

  • Development Client
  • WLSH4A (Tools Releases prior to 9.2.9)
  • WASH4A (Tools Releases prior to 9.2.9)

These installers are based on the Oracle Universal Installer (OUI) which is used to install several JD Edwards EnterpriseOne and non-JD Edwards Oracle products such as Oracle databases and Oracle Middleware.

The JD Edwards EnterpriseOne administrator must perform a small number of configuration steps to prepare these installers for running on EnterpriseOne workstations.