Understanding Running Multiple Instances of JD Edwards EnterpriseOne
You might want to run multiple instances of JD Edwards EnterpriseOne on an IBM i server for these reasons:
To test a new service pack.
To upgrade to a new version of JD Edwards EnterpriseOne.
Note: You cannot use JD Edwards EnterpriseOne Planner to help you set up data for multiple instances of JD Edwards EnterpriseOne. Be prepared to manually copy data and to set up new Object Configuration Manager (OCM) mappings for each new instance.
A JD Edwards EnterpriseOne instance on the IBM i server is uniquely identified by these objects:
JD Edwards EnterpriseOne system directory (integrated file system, or IFS) and library (QSYS file system).
Path codes (IFS and QSYS file systems).
Use of selected .ini file settings.
The JDE.INI settings that you use to uniquely define a JD Edwards EnterpriseOne instance are summarized in this table:
Section in server JDE.INI file |
Parameter |
Purpose |
|---|---|---|
[INSTALL] |
DefaultSystem= |
The name of the JD Edwards EnterpriseOne System library. This value must be unique for each JD Edwards EnterpriseOne instance. |
[JDEIPC] |
StartIPCKeyValue= |
The value of the first interprocess communication (IPC) ID of a range of keys, which JDEIPC uses for shared memory. This value, plus the value of the maxNumberofResources parameter, defines the range of IPC IDs that the software uses for an instance of JD Edwards EnterpriseOne. |
[JDENET] |
ServiceNameListen= |
The TCP/IP port number that the server uses for receiving communications packets from workstations and other JD Edwards EnterpriseOne servers. |
[JDENET] |
ServiceNameConnect= |
The TCP/IP port number that the server uses for sending communications packets to workstations or other JD Edwards EnterpriseOne servers. |
[DBSYSTEM SETTINGS] |
Default Env= |
The default environment for an instance of JD Edwards EnterpriseOne. |
[DB SYSTEM SETTINGS] |
Default PathCode= |
The data source for an instance of JD Edwards EnterpriseOne. |
[DB SYSTEM SETTINGS] |
Library= |
The database library that stores the system tables used by JD Edwards EnterpriseOne at startup. |
Similarly, to apply JD Edwards EnterpriseOne security throughout multiple instances, you use these items to uniquely identify an instance:
OCM mappings.
Database.
JD Edwards EnterpriseOne user profile (the owner and default user ID under which JD Edwards EnterpriseOne jobs start).
Selected settings in the JDE.INI file.
The JDE.INI settings that you use to uniquely define a JD Edwards EnterpriseOne instance when you are applying security throughout multiple instances are summarized in this table:
Section in server JDE.INI file |
Parameter |
Purpose |
|---|---|---|
[DEBUG] |
DebugFile |
Specifies the location of the jdedebug.log file. |
[DEBUG] |
JobFile |
Specifies the location of the jde.log file. |
[DEBUG] |
JDTSFile |
Specifies the location of the lock manager trace file on the IBM i. |
[DB SYSTEM SETTINGS] |
Database |
Specifies the name of the database in which the system tables reside. |
[SECURITY] |
DataSource |
Specifies the name of the JD Edwards EnterpriseOne data source that contains the security tables and is used for user validation. |
To create an instance of JD Edwards EnterpriseOne on the IBM i, complete these tasks:
Copy needed libraries and directories and modify the values of selected parameters in the .ini library.
To create an instance of JD Edwards EnterpriseOne on the IBM i, you copy these objects:
System library
System directory
Path code library
Path code directory
Apply security to multiple instances of JD Edwards EnterpriseOne, if you desire to do so.
If you want to apply security to multiple instances of JD Edwards EnterpriseOne, complete the steps in these task. If you do not want to apply security to multiple instances, proceed to the steps for creating a JD Edwards EnterpriseOne subsystem and starting a JD Edwards EnterpriseOne service.
Create a new JD Edwards EnterpriseOne subsystem identification.
On the IBM i platform, a subsystem is a logical process that is used to run system jobs, whether they are JD Edwards EnterpriseOne or other application jobs. JD Edwards EnterpriseOne network and kernel jobs run under the IBM i subsystem, which we ship with a default description. You can use this description without modification when you are running a single instance of JD Edwards EnterpriseOne on the IBM i server.
If you decide to run multiple instances of JD Edwards EnterpriseOne, you need to create a new subsystem with a unique description for each instance of JD Edwards EnterpriseOne that you create. To create a new JD Edwards EnterpriseOne subsystem description, you use the CRTOWSBS command.