Configuring the Web Client (Tools Release 9.2.9)

Prior to Tools Release 9.2.9, EnterpriseOne connected to an Application Server such as WebLogic or WebSphere 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 Application Server is configured by the EnterpriseOne administrator in the jde.ini template on the Deployment Server. This jde.ini is copied to the Development Client machine during installation of the EnterpriseOne Development Client software.

To specify the connection information in the <E1_dep_svr_install_directory>\OneWorld Client Install\misc\jde.ini template, update these values in the [LOCALWEB] section:
Key Value Comments

webhostname

<Development HTML Server's name> Fully qualified name (includes domain) or IP address of Development HTML Server. If useSSL (seen below) is 1, then the server name must exactly match the name on the web browser’s SSL certificate.
webport <Development HTML Server’s port>

Port number on which Development HTML Server listens

useSSL 1 or 0

1 = webport value is an https port

0 = webport value is an http port

If this setting is omitted, the default value is 1.

Note: [LOCALWEB] AppServerInstalled is set automatically in the jde.ini on the Development Client during installation. Do not change it manually.
Note: If there are any firewalls between the Development Client(s) and the Development HTML Server(s) designated in the LOCALWEB section, the webport must be open to allow communication between the server(s) and Development Client(s). The ports must also be open for the serviceNameListen value in the [JDENET] section of the Development Client JDE.INI and the BPMBroker value (default of 9876) in the registry under the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\JDEdwards\BPMBroker\port