Running Multiple Instances of JD Edwards EnterpriseOne on Windows

You can run multiple instances of JD Edwards EnterpriseOne on a Windows 2000 server. You might do so to test a new service or to upgrade to a new version of JD Edwards EnterpriseOne. You do not need to install a separate machine to run multiple instances of JD Edwards EnterpriseOne, so long as you follow a series of recommended steps.

Each instance of JD Edwards EnterpriseOne must have a unique identifier. You set the value of this identifier in the CLSID parameter of the server JDE.INI file. To generate the identifier, you run the uuidgen program.

For each new instance of JD Edwards EnterpriseOne, you modify the values of parameters in the JDE.INI file on the server. Each value for each JD Edwards EnterpriseOne instance must be unique. This table presents the server jde.ini file parameters that require modification, the purpose of each, and example values for each:

Section of server JDE.INI file

Parameter

Purpose

Example Value

[DEBUG]

DebugFile=

Name of the log file that contains debugging data.

z:\JDEdwards\E920_2\log\jdedebug.log

[DEBUG]

JobFile=

Name of the log file that contains log data.

z:\JDEdwards\E920_2\log\jde.log

[INSTALL]

StartServicePrefix=

Prefix that is used for names of the JD Edwards EnterpriseOne network and queue services.

Instance 2

[INSTALL]

B9=

Base directory of the JD Edwards EnterpriseOne installation.

z:\JDEdwards\E920_2

[JDEIPC]

StartIPCKeyValue=

Integer that indicates an arbitrary starting point in memory for interprocess communications. For multiple instances of JD Edwards EnterpriseOne, differences between the values of the parameter must be at least 1000.

6000

[JDEIPC]

CLSID=

Unique string generated by the NT guidgen program. The string identifies each instance of JD Edwards EnterpriseOne.

1E0CF350-AF81-11D0-BD7B-0000F6540786

[JDENET]

serviceNameListen=

The TCP/IP port number used by the server to receive communication packets from workstations.

6005

[JDENET]

serviceNameConnect=

The TCP/IP port number used by the server to send communications packets to servers.

6005

You are not required to install network and queue services for an existing JD Edwards EnterpriseOne instance unless you change the location of the system\bin32 directory for the new instance. For example, you might decide to put the directory on a new disk.

To move or rename a directory for EnterpriseOne instance after you install its services, you must uninstall the network service and uninstall the IPC Automation Server (ipcserv.exe). You can then move or rename the JD Edwards EnterpriseOne directory and reinstall the network service. The IPC Automation Server automatically reinstalls itself when it is first used.

After you have installed services for each JD Edwards EnterpriseOne installation, you must modify the workstation JDE.INI file so that the values of these parameters match those that you set up in the server JDE.INI file:

  • serviceNameListen=

  • serviceNameConnect=