1. Deployment Server Reference Guide for Microsoft Windows
  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. The supported Application Servers 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 for Applications)

  • WASH4A (WebSphere Server for Applications)

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

For instructions on how to install Web Clients for both Application Servers and their features: WLSH4A and WASH4A, as well as the installation of the applications server for WebLogic or WebSphere, refer to the JD Edwards EnterpriseOne Development Client Installation Guide.

Note: These instructions assume that all required prerequisites for running EnterpriseOne on the Deployment Server have been 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.