Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# The iProcess Engine and Hardware Clustering

To cater for the loss of a physical server, the iProcess Engine can be deployed with a hardware cluster. The following section describes:

| • | Deploying the iProcess Engine in a hardware cluster for UNIX

| • | Deploying the iProcess Engine in a hardware cluster for Windows

## Deploying the iProcess Engine in a Hardware Cluster for UNIX

There are two methods of deploying a hardware cluster, active-active and cold standby. The iProcess Engine is not supported in an active-active hardware cluster. However, it is supported in a cold standby hardware cluster. An example of a cold standby hardware cluster is shown :

Each server is built in exactly the same way. Servers A and B are up and running and server C is a cold standby. If server A or B fails, server C is started and takes the place of the failed server.

To deploy the iProcess Engine in a cold standby hardware cluster:

| • | An iProcess Engine should be installed on each server in the cluster.

| • | If Server A or B fails, start the cold standby server and use SWDIR\swadm move_server to move the iProcess Engine processes from the failed server to the cold standby server. See "Administering Servers" in the TIBCO iProcess Engine Administrator’s Guide for more information about the SWDIR\swadm move_server command.

Note: This can be done automatically by writing a script that uses the SWDIR\swadm move_server command.

## Deploying the iProcess Engine in a Hardware Cluster for Windows

The iProcess Engine can be used with Microsoft Server Clustering when deployed in a Windows environment. Microsoft defines a cluster as "a group of independent computers that work together collectively to provide a common set of services". When combining an iProcess node cluster with a Microsoft Server Cluster, each iProcess Engine node is contained within its own virtual server. Each virtual server is run on its own physical server. The iProcess Engine is installed on a shared disk that is accessible to all servers in the cluster. It is configured to work within the virtual server at installation by specifying a Cluster Network Name. If a physical server fails, the Microsoft Server Cluster automatically relocates the virtual server onto a secondary physical server and restarts the iProcess Engine.

To install the iProcess Engine in a Microsoft Windows Cluster, see the TIBCO iProcess Engine (Oracle) for Windows Installation or the TIBCO iProcess Engine (SQL) for Windows Installation guide, depending on the version of the database you are using.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.