Administering JD Edwards EnterpriseOne on a Windows Cluster

Configuration of MSCS has changed with Oracle's JD Edwards EnterpriseOne 8.9. This information is only valid beginning with JD Edwards EnterpriseOne 8.9 and should not be used with previous releases. For more information about how to install and set up a Microsoft cluster, see the appropriate Microsoft documentation.

This section discusses how to:

• Upgrade JD Edwards EnterpriseOne in a Windows cluster environment.

• Set up JD Edwards EnterpriseOne on a Windows cluster.

• Create a static IP address for the JD Edwards network name.

• Test JD Edwards EnterpriseOne connections on the cluster.

• Set Advanced Options for JD Edwards EnterpriseOne resources.

• Set failover and failback parameters.

• Troubleshoot a Windows cluster.

Prerequisites

Before you complete the tasks in this section:

• Partition the disk array to logically divide the software components. Typically, you will set up these partitions:

  • A partition that contains the cluster software.

  • A partition that contains the JD Edwards EnterpriseOne software.

  • A partition that contains the database management system (DBMS) software and database if these reside on the cluster system.

• If you will be using Microsoft clustering in conjunction with a DBMS, such as Oracle Fail Safe, SQL Server, or UDB DB2, consult the installation documentation for the appropriate DBMS before installing Windows enterprise server.

• Configure the network, which includes setting up connections among servers, workstations, and printers.

  Note. Microsoft cluster server software only supports TCP/IP. Microsoft cluster server software does not support the use of Dynamic Host Configuration Protocol (DHCP) for the assignment of IP addresses.

  Although you need only one network card in each node, you should use two cards to ensure redundancy. One network card will communicate with the public network, and the second card will connect between nodes. This setup enables the cluster to remain active when the primary node loses the network connection. If you use only one network card, when a node loses the network connection that node also loses the connection to other nodes in the cluster.

• If the database and Oracle's JD Edwards EnterpriseOne are both running on the cluster, they can be configured to run on separate nodes. To accomplish this, separate JD Edwards EnterpriseOne resources and database resources into different groups. Also, be sure that JD Edwards EnterpriseOne and the database do not share disk resources. JD Edwards EnterpriseOne resources will need to be in the same group as the cluster network name and cluster IP address. This can be the cluster group.

  When the JD Edwards EnterpriseOne and database groups are in separate groups, the database group must be online before bringing the JD Edwards EnterpriseOne resources online.

  If you do not require JD Edwards EnterpriseOne and database resources to run on separate nodes, place all database and JD Edwards EnterpriseOne resources in the cluster group.

See Also

Starting the Windows Enterprise Server in the JD Edwards EnterpriseOne Installation Guide

Managing Server Jobs

Upgrading JD Edwards EnterpriseOne in a Windows Cluster Environment

If you are already running JD Edwards EnterpriseOne in a cluster but are upgrading to JD Edwards EnterpriseOne 8.9 or later, you must change the cluster configuration for the cluster to operate properly. JD Edwards EnterpriseOne 8.9 and later releases require use of an IP address, and a network name separate from the cluster IP address and network name.( In previous releases, we used the cluster network name and IP address for the JD Edwards EnterpriseOne enterprise server name.)

Since the cluster name exists in JD Edwards EnterpriseOne ini files and tables, the recommended solution is to rename the cluster and create new resources for the JD Edwards EnterpriseOne group using the old cluster name and a different IP address. This requires changing the static IP address associated with the old cluster name to avoid an IP address conflict. Consult the Microsoft documentation on renaming a cluster. After the cluster is renamed, continue with these instructions.

Setting Up JD Edwards EnterpriseOne on a Windows Cluster

This task explains how to set up JD Edwards EnterpriseOne on a Windows cluster. This example is for a two node cluster.

Note. JD Edwards EnterpriseOne executables (such as runube) running from a command line on a Windows Cluster server node on Microsoft Windows 2003 and later releases, return the node name instead of the cluster name for the enterprise server name. This happens because the executable is not a defined resource in Windows Cluster Services. This creates an issue when trying to retrieve the job in JD Edwards EnterpriseOne.

To resolve this problem, add the following setting to the jde.ini file of the enterprise server. You can add this setting to any location, but we recommend adding it after the [DEBUG] section:

[CLUSTER]

PrimaryNode=Cluster Name

To set up JD Edwards EnterpriseOne on a Windows cluster:

1. Consult the JD Edwards MTRs to determine the appropriate Windows OS level. Install the OS on each node. Use member servers and not domain controllers.

2. Install Microsoft Cluster Server (MSCS) software on each node using an account that has administrator authority.

   Refer to the appropriate Microsoft documentation for specific instructions on the installation of MSCS.

3. Access the cluster to verify the installation of MSCS.

4. Install JD Edwards EnterpriseOne on the disk designated for JD Edwards EnterpriseOne enterprise server. All nodes will share a single copy of JD Edwards EnterpriseOne. The name used for the enterprise server will be the JD Edwards EnterpriseOne network name and used by JD Edwards EnterpriseOne to reference the cluster.

5. On the node which currently owns the JD Edwards EnterpriseOne disk, install the network service, open a DOS command window. Change the directory location to the system/bin32 directory for JD Edwards EnterpriseOne.

6. Type jdesnet –I.

   A message will be returned stating that the service was installed.

7. Exit the command prompt and open services.

8. Right click the JD Edwards Network Service and select Properties.

9. Click This Account and change the account to a valid domain account that is in the local administrators group.

10. In the server jde.ini, verify that all references to the enterprise server are set to the JD Edwards EnterpriseOne Network name.

11. Open cluster administrator.

12. Right click the cluster name, and select New, Group.

13. Type in a group name for JDE EnterpriseOne1 (i.e. JDEGROUP) and a description.

14. Click Next.

15. Add the required nodes to the preferred owners list.

16. Click Finish.

17. When the cluster group is successfully created, click OK.

18. Right click the cluster administrator screen and select New, then Resource.

    Three resources will need to be created to complete the setup. The first resource is the IP address resource for JD Edwards EnterpriseOne.

19. Type a name and description for the JD Edwards EnterpriseOne IP address. Resource type is the IP Address. The group name should be the group just created

20. Click Next.

21. Verify that all required nodes are preferred owners.

22. Click Next.

    The next screen defines dependencies. The IP resource should not have any dependencies.

23. Click Next.

24. Add the IP address and subnet mask.

25. Select Public from the available list, and select Enable NetBios for this address.

26. Click Finish.

    A pop-up should appear verifying successful configuration of the resource.

27. To set up the Network Name resource, right-click the cluster administrator screen and select New — Resource.

28. Fill in the name with the JD Edwards EnterpriseOne Network name you have chosen. Add a description, select Network Name from the available list and select the group you created earlier

29. Click Next.

30. Verify that all required nodes are preferred owners.

31. Click Next.

    The next screen defines dependencies. The Network Name should have the IP address as a dependency

32. Click Next.

    Specify the Network Name in the Name field.

33. Select the DNS registration check box. Do not select the Enable Kerberos Authentication check box.

34. Click Finish. The program should display a message verifying successful configuration of the resource

35. Click OK.

Adding JD Edwards EnterpriseOne Network Resources to the Group

To add the JD Edwards EnterpriseOne network resources to the cluster group:

1. From the Cluster Administrator main menu, select File, New, Resource.

2. On New Resource, complete these fields for the JDE network resources, and then click Next.

   • Name

   • Description

   • Resource Type

     Select Generic Service from the list.

   • Group Name

     Select the JDE EnterpriseOne group.

   Note. Do not select the option to Run this resource in a separate Resource Monitor.

3. On Possible Owners, verify that the possible owners match the preferred owners, and then click Next.

4. On Dependencies, select the JD Edwards EnterpriseOne physical disk resource and the cluster network name, click Add, and then click Next.

   You establish this dependency to ensure that the resources are available when the network service starts. Network and queue resources will not function if the drive is unavailable.

5. On Generic Service Parameters, complete these steps, and then click Next:

   • Type the JDE network service name as it appears in the NT Services applet.

   • Leave the Startup Parameters field blank.

   • Select the check box for Use Network Name.

6. On Registry Replication, click Finish.

7. On Cluster Administration, click OK.

Starting and Stopping the JD Edwards EnterpriseOne Resources on the Cluster

In a cluster environment, use Cluster Administrator to start and stop JD Edwards EnterpriseOne network and queue services. JD Edwards EnterpriseOne resources should be started and stopped in the same order as in the Windows Services applet: start the network service first and then the queue service. When stopping, stop the queue service first and then the network service.

To start and stop the JD Edwards EnterpriseOne resources on the cluster:

1. To start network or queue services or both services, in Cluster Administrator, right-click the JD Edwards EnterpriseOne resource and select Online.

2. To stop network or queue services or both services, in Cluster Administrator, right-click the JD Edwards EnterpriseOne resource and select Offline.

Testing JD Edwards EnterpriseOne Connections on the Cluster

JD Edwards EnterpriseOne network and queue services must be set up before you can test connections on the cluster.

To test JD Edwards EnterpriseOne connections on the cluster:

1. Sign on to Windows.

2. Using Cluster Administrator, verify that all JD Edwards EnterpriseOne resources are online for the JD Edwards EnterpriseOne group.

3. To verify that JD Edwards EnterpriseOne is installed correctly on the cluster server, enter these commands to run porttest:

   cd \JDEdwards\ddp\xxxx\System\Bin32
   porttest userID password environment

   Where xxxx is the specific release of JD Edwards EnterpriseOne (for example, 900), userID is a valid JD Edwards EnterpriseOne user, password is the password for that user, and environment is the environment you are verifying. These parameters are case-sensitive. Enter the porttest command for each environment.

   The porttest program initializes a user and an environment, assuming that JD Edwards EnterpriseOne is correctly installed and configured. The program should display messages indicating the selection of records out of a JD Edwards EnterpriseOne table. If it does not, review the jde_####.log file specified in the jde.ini file on the enterprise server.

4. Sign on to a JD Edwards EnterpriseOne workstation, and then run a batch application.

   For example, submit the Business Unit Master All Companies report (R0006P). Verify that the report processed successfully on the UBE server.

5. Using the Cluster Administration tools, stop JD Edwards EnterpriseOne on the first node by right-clicking the node name and selecting Cluster Service.

   All groups will failover to the second node.

6. Verify that all resources are online on the second node, and repeat these steps.

Setting Advanced Options for JD Edwards EnterpriseOne Resources

To set advanced options for JD Edwards EnterpriseOne resources:

1. From the Cluster Administrator main menu, open the group that contains the resource you want to modify.

2. Select a resource, and then select Properties from the File menu.

3. Select the Advanced tab, and then select one of these options:

   • Do Not Restart

   • Restart

     If you want to disable failover, select Do Not Restart.

4. Review the values on the form. For more information about these values, see the appropriate Microsoft clustering documentation.

Setting Failover and Failback Parameters

To set failover and failback parameters:

1. From the Cluster Administrator main menu, select the appropriate group, and then select Properties from the File menu.

2. Select the Failover tab, and review these fields:

   • Threshold

     This field determines the number of failovers attempted by MSCS.

   • Period

     This field determines the period of time during which MSCS attempts failovers.

3. Select the Failback tab and review these options:

   • Prevent Failback

   • Allow Failback

     The setting for this option can be immediate or during a set period of time.

For more information about these parameters, see the appropriate Microsoft clustering documentation.

Troubleshooting Windows Clustering

This section includes these troubleshooting tasks:

Changing an IP Address

After moving the cluster equipment to another area, we had to change the IP address for cluster nodes and any virtual machines connected to them. In order to perform this task, we had to uninstall Microsoft Cluster Services (MSCS), which required the removal of all resources and groups already defined. It also required uninstalling database management system (DBMS) cluster software, which included SQL Server Cluster Manager and Oracle Failsafe. The final steps were uninstalling MSCS, changing the physical IP address in the nodes, reinstalling MSCS using the new IP address for the virtual machine, and reinstalling SQL Server Cluster Manager and Oracle Failsafe.

Reinstalling MSCS

If you have already installed a version of Microsoft Cluster Server (MSCS) software and you need to uninstall it, you must use the Add/Remove Programs tool to uninstall MSCS.

Creating a Static IP Address for the JD Edwards Network Name

Starting with JD Edwards EnterpriseOne 8.9, you must create a network name for JD Edwards. The network name is used for the enterprise cluster server name. If you are installing a cluster aware DBMS, it also requires one or more static IP addresses.

Note. Microsoft cluster server software only supports TCP/IP. Microsoft cluster server software does not support the use of Dynamic Host Configuration Protocol (DHCP) for the assignment of IP addresses.

Although each node only requires one network card, Microsoft recommends using two network cards as a backup. One network card will communicate with the public network, and the second card will connect between nodes. This setup enables the cluster to remain active when the primary node loses the network connection. If you use only one network card, when a node loses the network connection, that node also loses the connection to other nodes in the cluster.

If the database and JD Edwards EnterpriseOne are both running on the cluster, they can be configured to run on separate nodes. To accomplish this, separate JD Edwards EnterpriseOne resources and database resources into different groups. Also ensure that JD Edwards EnterpriseOne and the database do not share disk resources. JD Edwards EnterpriseOne resources should be in a group other than the cluster group. JD Edwards EnterpriseOne resources will have their own network name and IP address.

When the JD Edwards EnterpriseOne and database groups are in separate groups, the database group must be online before bringing the JD Edwards EnterpriseOne resources online.

If you do not require JD Edwards EnterpriseOne and database resources to run on separate nodes, place all database and JD Edwards EnterpriseOne resources in the same cluster group.

If you use Oracle, SQLServer, or IBM UDB cluster services, the cluster might experience dependencies on database resources. Consult the appropriate Oracle, SQLServer, or IBM UDB documentation for more information.

Testing JD Edwards EnterpriseOne Connections on the Cluster

Complete this task to test the JD Edwards EnterpriseOne connection.

Note. JD Edwards EnterpriseOne network and queue services must be set up before you can test connections on the cluster.

To test a JD Edwards EnterpriseOne Connection:

1. Sign on to Windows.

2. Using Cluster Administrator, verify that all JD Edwards EnterpriseOne resources are online for the JD Edwards EnterpriseOne group.

3. To verify that JD Edwards EnterpriseOne is installed correctly on the cluster server, enter these commands to run porttest:

   • cd \jdedwardsoneworld\ddp\xxxx\System\Bin32

     where xxxxis the specific release of JD Edwards EnterpriseOne, for example, E900.

   • porttest userID password environment

     Where userID is a valid JD Edwards EnterpriseOne user, password is the password for that user, and environment is the environment you are verifying.

   Note. These parameters are case-sensitive.

   If JD Edwards EnterpriseOne is installed and configured correctly, the porttest program initializes a user and an environment. The program should display messages indicating the selection of records out of a JD Edwards EnterpriseOne table. If it does not, review the jde_####.log file that was specified in the jde.ini file on the enterprise server.

4. Sign on to a JD Edwards EnterpriseOne workstation, then run a batch application.

   For example, submit the Business Unit Master List - All Companies report (R0006P). Verify that the report processed successfully on the UBE server.

5. Stop JD Edwards EnterpriseOne on the first node using the Cluster Administration tools.

6. To stop cluster services on the first node, right-click the node name and select Cluster Service. All groups will failover to the second node.

7. Verify that all resources are online on the second node and repeat these steps.

See Also

Managing Server Jobs

Setting Advanced Options for JD Edwards EnterpriseOne Resources

This task explains how to set up advanced options for JD Edwards EnterpriseOne on a Windows NT cluster in a two-server configuration.

1. From the Cluster Administration main menu, open the group that contains the resource that you want to modify.

2. Select a resource, and then select Properties from the File menu.

3. Select the Advanced tab, and select one of these options:

   • Do Not Restart

   • Restart

   If you want to disable failover, select Do Not Restart.

4. Review the values on the form.

   For more information about these values, see the appropriate Microsoft clustering documentation.

Setting Failover and Failback Parameters

This task explains how to set up fail parameters for JD Edwards EnterpriseOne on a Windows NT cluster in a two-server configuration.

1. From the Cluster Administrator main menu, select the appropriate group, then select Properties from the File menu.

2. Select the Failover tab, and review these fields:

   • Threshold: Determines the number of failovers attempted by MSCS.

   • Period: Determines the period of time during which MSCS attempts failovers.

3. Select the Failback tab and review these options:

   • Prevent Failback

   • Allow Failback

     The setting for this option can be immediate or during a set period of time.

   For more information about these parameters, see the appropriate Microsoft clustering documentation.

Troubleshooting a Windows Cluster

If you encounter problems with the Windows cluster, review these topics for possible solutions.

Changing an IP Address

If you move the cluster equipment to another area, you may have to change the IP address for cluster nodes and any virtual machines connected to them. To perform this task, complete these steps:

1. Remove all defined resources and groups.

2. Uninstall the DBMS cluster software.

3. Uninstalling MSCS.

4. Change the physical IP address in the nodes.

5. Reinstall MSCS using the new IP address for the virtual machine.

6. Reinstall SQL Server Cluster Manager and Oracle Failsafe.

Reinstalling MSCS

If you already installed a version of Microsoft Cluster software, before you reinstall, you must uninstall the software using Add/Remove programs.