Configuring the Microsoft Windows Cluster

Status

If you are...

This task is...

Installing a new iProcess Engine Version 11.9.0

Required if you use a Windows Cluster

Upgrading from an iProcess Engine Version 11.0 or later

Required if you use a Windows Cluster

Database

Oracle, SQL Server

Description

If you are installing the iProcess Engine into a Microsoft Windows Cluster, you must perform some additional tasks to enable the iProcess Engine to operate in the Microsoft Windows Cluster environment.

Procedure

Perform the following steps:

1. Add the SWDIR environment variable. This is required for IPAC on all the nodes in the Windows Cluster.
2. To configure secondary nodes:

  1. Add "Staffware Users", "Staffware Administrators" groups with iProcess users (for example, TIBCO\iPEUser) from Computer Management --> Local Users and Groups --> Groups.

  2. Open Services. Right-click iProcess<node name>AdminConsole service -> properties -> Log On -> This Account and login again by entering the password.

  3. Export "TIBCO iProcess" registries from iPE installed machine and Import entry to each node in windows cluster.
3. Copy NobleNet Portmapper to C:\Program Files (x86).
4. Run swadm to move the iProcess engine from Cluster Name to Role Name. swadm MOVE_SERVER <Logical Machine ID> <Role Name>. See Open the Control Panel window, and select Administrative Tools > Failover Cluster Manager. for <Role Name>.
5. Configure Service Startup on every node:

 

NobleNet Portmapper

Automatic

 

iProcess<nodeName>ProcessSentinels

Manual

 

iProcess<nodeName>AdminConsole

Manual
6. If you did not check the Auto Start Processes On Service Startup check box when you ran the installer (see Configuration), set the iProcess Engine PM_AUTO_BOOT process attribute value to 1 (so that iProcess Engine processes automatically start after the Process Sentinels have started).
7. Open the Control Panel window, and select Administrative Tools > Failover Cluster Manager.
a. Install a new Role for the iProcess Engine Process Sentinels service. This role must have the following properties:
 

Property

Description
 

Role name

Any suitable descriptive name you choose.
 

IP Address

Assign a static IP address to this role that will be used by all client programs to connect.
 

Resources

Add both the entries given :

  • iProcess Sentinels Service

  • iProcess Admin Console Service.
 

Service name

Add both the entries given :

iProcessnodeNameProcessSentinels (add following dependency to this)

— Cluster Disk (where iProcess Engine is installed)

iProcessnodeNameAdminConsole (add following dependency to this)

— Cluster Disk (where iProcess Engine is installed)

where, nodeName is the node name of this iProcess Engine.

Note: There must be no spaces anywhere in the name or at the end of the string.

 

Registry Replication > Root Registry Key

Add both of the following entries:

• RegistryLocation\TIBCO iProcess\TIBCO iProcess Engine\Nodes\nodeName
• RegistryLocation\TIBCO iProcess\TIBCO iProcess Objects Server\Nodes\nodeName

where:

RegistryLocation is SOFTWARE.

nodeName is the node name of this iProcess Engine.
8. If you are using EMS, you must now:

  1. install the same EMS Version on each secondary machine in the cluster. See TIBCO Enterprise Message Service Installation for more information about how to install EMS.

  2. configure EMS to work as part of the cluster. For more information about how to do this, see EMS documentation.

Warning 

If you are upgrading your version of TIBCO EMS, you must follow the instructions in How Do I Upgrade TIBCO EMS. Failure to do so will result in the loss of work queue data.

9. If you are using Hawk, you must now:

  1. install the same Hawk Version on each secondary machine in the cluster. You can find the Hawk Version distribution set and documentation in the SWDIR\hawk folder. See TIBCO Hawk Installation and Configuration for more information about how to install Hawk.

  2. configure Hawk to work as part of the cluster. For more information about how to do this, see Hawk documentation.

10. If your Microsoft Windows Cluster is not running software to ensure that services, components, and shared DLLs are replicated between machines, and therefore identical between the machines in the cluster, run the following command on each secondary machine in the cluster:

 

  SWDIR\mscluster\mscluster

This command creates the following shared resources and services that are required by iProcess Engine:

— iProcess nodeName Process Sentinels service
— iProcess nodeName Admin Console service
— NobleNet Portmapper for TCP service
— iProcess Events64 COM+ application
— iProcess COM+ Bridge COM+ application

where nodeName is the node name of this iProcess Engine.

It also replicates the port numbers used by the iProcess Engine watcher and worker process sentinels in the %systemroot%\system32\drivers\etc\services file.

See Also

See Microsoft documentation for more information about the Cluster Administrator tool.