Running Multiple Instances of the JD Edwards EnterpriseOne Enterprise Server

To run multiple instances of the JD Edwards EnterpriseOne enterprise server:

1. The system administrator should create a new user ID that owns the new JD Edwards EnterpriseOne instance.

   Create the user ID using the appropriate administration tool, such as smit, smh, admintool, or useradd.

   Note: Although you can run multiple instances of the JD Edwards EnterpriseOne server using the same UNIX or Linux user ID, it is not recommended. The software depends on certain environment variables to function correctly, and these variables are easier to manage under different user IDs.

2. Sign on using the new user ID.

3. Copy the .profile files from the home directory of the original user ID to the home directory of the new user ID.

4. Change the .profile file for the new user ID to reference the new directory path in which you will create the new JD Edwards EnterpriseOne instance.

   For example:

   Original .psft file:

   if [ -f /u01/JDEdwards/E910/SharedScripts/enterpriseone.sh ] ; then . /u01/JDEdwards/E910/SharedScripts/enterpriseone.sh
   

   New .profile file:

   if [ -f /u02/JDEdwards/E910/SharedScripts/enterpriseone.sh ] ; then  . /u02/JDEdwards/E910/SharedScripts/enterpriseone.sh
   

5. Create the directory in which the new JD Edwards EnterpriseOne instance will reside.

   For example, type these:

   mkdir -p /u02/JDEdwards/E910
   

6. Copy the system directory, the ini directory, and at least one path code directory from the original instance of JD Edwards EnterpriseOne to the new directory path.

   These sample commands accomplish this:

   cp -R /u01/JDEdwards/E910/system /u02/JDEdwards/E910
   cp -R /u01/JDEdwards/E910/ini /u02/JDEdwards/E910
   cp -R /u01/JDEdwards/E910/DV910 /u02/JDEdwards/E910
   

   Note: The path code directories for any environments that you intend to use for this second instance of JD Edwards EnterpriseOne must be copied to the new directory. You cannot share path code directories between two or more instances of JD Edwards EnterpriseOne, as this sharing will corrupt specification files.

7. Create an empty log directory under the new path using a command such as this:

   mkdir -p /u02/JDEdwards/E910/log
   

8. In the new JDE.INI file, change all references to the original directory name to the new directory name, including the [INSTALL], [DEBUG], and [BSFN BUILD] sections.

   For example:

   [DEBUG]
   DebugFile=/u02/JDEdwards/E910/log/ jdedebug.log
   JobFile=/u02/JDEdwards/E910/log/jde.log
   
   [INSTALL]
   B9=/u02/JDEdwards/E910
   
   [BSFN BUILD]
   BuildArea=/u02/JDEdwards/E910/packages
   

9. Change the new JDE.INI file to reference a port number and starting IPC key that are different from the original JD Edwards EnterpriseOne instance.

   The values are defined by these parameters; but the numbers are only examples:

   [JDENET]
   serviceNameListen=6009
   serviceNameConnect=6009
   
   [JDEIPC]
   startIPCKeyValue=9000
   

10. From the client workstation JDE.INI file, change the serviceName parameters to match those of the server JDE.INI file.

11. Ensure you are signed on using the new user ID.

12. Perform a fresh installation of the Server Manager Agent on the Enterprise Server machine. This is required since the earlier Server Manager Agent, which is managing the original Enterprise Server, is running with a different UserId and cannot be used to manage the newly created Enterprise Server.

13. Once the Installation of the Server Manager Agent is completed, the Server Manager Agent will be running and will start showing up in the Server Manager Console.

14. The newly created Enterprise Server can be registered in the new Server Manager Agent and can be used for managing the new Enterprise Server (Configuration, Logs, Runtime Metrics, etc).

15. This completes the setup required from the Server Manager side for managing the new Enterprise Server.