Configuration Requirements for JD Edwards EnterpriseOne Enterprise Server

Use the requirements in this section to plan the installation and configuration of the JD Edwards EnterpriseOne Enterprise Server. These requirements apply only to the JD Edwards EnterpriseOne Enterprise Server. You must meet these requirements before you proceed with your JD Edwards EnterpriseOne Enterprise Server installation and configuration.

Information about how to install JD Edwards EnterpriseOne Enterprise Server version 9.1.x is published at JD Edwards EnterpriseOne Tools Documentation Library.

For requirements that apply to all data services, see Chapter 1, Planning for Oracle Solaris Cluster Data Services, in Oracle Solaris Cluster Data Services Planning and Administration Guide .

The following configuration requirements apply:

• UNIX user and group – The UNIX user and group that are used to install, operate, and manage the JD Edwards EnterpriseOne Enterprise Server must exist on all cluster nodes where the corresponding resource for the Enterprise Server is configured to come online. When you run the Oracle Universal Installer, a user is created (for example, jde910) on that node. This user starts the application and the user must exist on every cluster node. You can choose to manually create a jde user on every node or run the installer, which creates the jde910 user on the node.

• File systems – The file systems used to store the required binaries and data for the JD Edwards EnterpriseOne Enterprise Server must be configured on highly available local file systems. If you choose to install the binaries on local storage, install and keep them identical on all the cluster nodes. The JDE.INI file must reside on a highly available local file system, which must be accessible where the corresponding resource for the JD Edwards EnterpriseOne Enterprise Server comes online.

  If you are setting up the JD Edwards EnterpriseOne Enterprise Server in a multi-instance configuration, a local file system, or a global file system, the Enterprise Server installation should be located on network attached storage (NAS) that is accessible to all nodes running the server.

  If you are setting up multiple instances of the JD Edwards EnterpriseOne Enterprise Server in a multi-instance or a multi-master configuration, each instance should be installed as a different user. For JD Edwards EnterpriseOne Enterprise Server version 9.1.x installed through the Platform Pack installer, you can choose to create a user account for the jde910 user. If your configuration is on a local file system, the installation user can be the same for all instances.

• Environment variables – In addition to the required environment variables that are explained in the JD Edwards EnterpriseOne Installation Guide, you must set up some variables after you configure the Enterprise Server. For instructions, see Step 5 of How to Install JD Edwards Enterprise Server Software.

• Database tier dependency – If the database tier is deployed on the same global cluster, the resource for the JD Edwards EnterpriseOne Enterprise Server must define a strong resource dependency to the resources for the database instance and database listener. This ensures that the JD Edwards EnterpriseOne Enterprise Server will try to start only when the corresponding database is already operational. This configuration is required for a successful startup of the JD Edwards EnterpriseOne Enterprise Server. If the Oracle database is not managed through Oracle Solaris Cluster, you can also configure the database tier dependency by using the data service delivered as part of the Oracle External Proxy resource.

• Database client network connection – The database client used by the JD Edwards EnterpriseOne Enterprise Server configuration must be configured to connect to the network address that is managed by the cluster framework for the corresponding database server.

• JDE.INI attribute changes – The following attributes must be changed in the JDE.INI file:

  1. Base Datasource should have the logical host resource hostname configured for the JD Edwards EnterpriseOne Enterprise Server resource. For a multiple-master configuration, this is the per-node logical host resource hostname. For example, the setting in the JDE.INI file looks similar to the following:

     Base Datasource = LH-rs-hostname – 910 Server Map

     The LH-rs-hostname is the hostname of the per-node logical host resource.

  2. The listenOnSpecificIP setting in the JDE.INI file should be set to 1:

     listenOnSpecificIP=1

  3. The SecurityServer attribute under the [SECURITY] section should match the hostname or IP address of the logical host resource configured for the JD Edwards EnterpriseOne Enterprise Server resource. For a multiple-master configuration, this is the per-node logical host resource hostname or IP address. For example, the setting in the JDE.INI file looks similar to the following:

     SecurityServer=192.1.2.36

     The IP address of the per-node logical host resource hostname configured for the JD Edwards EnterpriseOne Enterprise Server is 192.1.2.36.

  4. The PrimaryNode attribute under the [CLUSTER] section should match the hostname or IP address of the logical host resource configured for the JD Edwards EnterpriseOne Enterprise Server resource. For a multiple-master configuration, this is the per-node logical host resource hostname or IP address. For example, the setting in the JDE.INI file looks similar to the following:

     PrimaryNode=192.1.2.36

     The IP address of the per-node logical host resource hostname configured for the JD Edwards EnterpriseOne Enterprise Server resource is 192.1.2.36.