Copyright © Cloud Software Group, Inc. All rights reserved.

Overview

The TIBCO iProcess Objects Director is a standalone program that maintains a list of TIBCO iProcess Objects Servers that are configured in a node cluster. When a client needs access to a TIBCO iProcess Objects Server, it first establishes a connection to TIBCO iProcess Objects Director. The TIBCO iProcess Objects Director then decides, based on a “pick method,” which TIBCO iProcess Objects Server the client should connect to.

The list of known TIBCO iProcess Objects Servers is updated dynamically as TIBCO iProcess Objects Server instances are started and stopped. The TIBCO iProcess Objects Director maintains this list by checking the process_config table of iProcess Engine to which it is associated.

For efficiency reasons, after having TIBCO iProcess Objects Director choose a TIBCO iProcess Objects Server for you, you should login directly to that same TIBCO iProcess Objects Server for all subsequent logins. This is because a SAL session is started for a user the first time they login; subsequent logins can use that same SAL session, resulting in a much more efficient and faster login.

The TIBCO iProcess Objects Director can be installed on any machine in a node cluster, independent of TIBCO iProcess Objects Server and client installations. However, you must be using a TIBCO iProcess Engine to use TIBCO iProcess Objects Director. You must also be using a TIBCO iProcess Objects Server that includes CR 10676, and either TIBCO iProcess Objects or TIBCO iProcess Server Objects that includes CR 16970.

Multiple Instances of the 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 the 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 will cause 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 a 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 the TIBCO iProcess Objects Director.

Starting and Stopping the TIBCO iProcess Objects Director

Starting and stopping TIBCO iProcess Objects Director is handled by the Process Manager. Once installed on a node, the TIBCO iProcess Objects Director process will be listed in the process configuration table with the process name DIRECTOR. The DIRECTOR process can be started and stopped with all the other SPS processes by using the following commands:

SWDIR\bin\swstart

SWDIR\bin\swstop

Or, you can start or stop individual TIBCO iProcess Objects Director instances using the following commands:

SWDIR\util\swsvrmgr START MachineID DIRECTOR ProcessInst

SWDIR\util\swsvrmgr SHUTDOWN MachineID DIRECTOR ProcessInst

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

TIBCO iProcess Objects Director Version

You can determine the version of TIBCO iProcess Objects Director by executing the following from the command line:

•	SWDIR\bin\spodirector -v (Windows) or $SWDIR/bin/spodirector -v (UNIX)

•	what $SWDIR/bin/spodirector (UNIX only)

TIBCO iProcess Objects Server TCP Port Configuration

All TIBCO iProcess Objects Servers that want to make use of TIBCO iProcess Objects Director must be configured to use static TCP ports. This allows TIBCO iProcess Objects Director to be configured with those port numbers so it knows the TCP port number to use when establishing a connection between a client and a TIBCO iProcess Objects Server. For information about configuring TCP ports on TIBCO iProcess Objects Servers, see TIBCO iProcess Objects Server Administrator’s Guide.

The TIBCO iProcess Objects Director determines which TCP port to use by using the BASE_TCP_SERVICE_NAME process attribute (see BASE_TCP_SERVICE_NAME) and the server’s instance number.

The TIBCO iProcess Objects Director assumes the first instance of each TIBCO iProcess Objects Server will use the TCP port established by BASE_TCP_SERVICE_NAME (which defaults to 28021), the second instance uses the base port plus 1, the third instance uses the base port plus 2, and so forth.

For example, if BASE_TCP_SERVICE_NAME = “DEFAULT” (port 28021) and there are five TIBCO iProcess Objects Server instances on two nodes (two on Node 1 and three on Node 2), the five instances of TIBCO iProcess Objects Server must be configured with the following TCP ports:

Node	Server Instance	TCP Port
1	1	28021
1	2	28022
2	1	28021
2	2	28022
2	3	28023

Copyright © Cloud Software Group, Inc. All rights reserved.