Multiple Instances of TIBCO iProcess Objects Director

Multiple instances of TIBCO iProcess Objects Director can be run in a node cluster. You may want to run multiple instances of TIBCO iProcess Objects Director on a single machine, each using a different pick method. Or, you may want to run multiple instances on multiple machines for redundancy purposes. Each instance of the Director runs independently from other instances.

Theoretically, you can run up to 99 instances of the Director (the same as for TIBCO iProcess Objects Server), although in reality, it does not seem reasonable nor practical to run that many instances.

Adding and Deleting Instances of TIBCO iProcess Objects Director

When TIBCO iProcess Objects Director is initially installed on a machine, it becomes instance 1 by default. A new installation of a TIBCO iProcess Objects Director on a machine causes an entry to be automatically added to the process_config table, as follows:

 

Machine ID	Process Name	Process Instance
1	DIRECTOR	1

Once the initial installation is completed, additional instances of TIBCO iProcess Objects Director can be added to or deleted from the process_config table using the following swadm commands:

SWDIR\util\swadm add_process MachineID DIRECTOR Y
SWDIR\util\swadm delete_process MachineID DIRECTOR ProcessInst

For example, after adding a second instance to machine 1, the process_config table appears as follows:

 

Machine ID	Process Name	Process Instance
1	DIRECTOR	1
1	DIRECTOR	2

For information about using the swadm utility, see TIBCO iProcess Engine Administrator’s Guide.

Process attributes are used to configure TIBCO iProcess Objects Director. Each of the process attributes can be configured differently for each instance of TIBCO iProcess Objects Director when you are running multiple instances of the Director. For instance, each instance might use a different “pick method” to choose a TIBCO iProcess Objects Server. For information about these process attributes, see Configuring TIBCO iProcess Objects Director.