Accessing a TIBCO iProcess Objects Director

How you access a TIBCO iProcess Objects Director depends on whether you are using TIBCO iProcess Objects or TIBCO iProcess Server Objects, as follows:

TIBCO iProcess Objects

A TIBCO iProcess Objects client accesses TIBCO iProcess Objects Directors using one of the following methods:

•

Auto-discovery UDP Broadcast  The client can send out a UDP broadcast to auto-discover TIBCO iProcess Objects Directors on the LAN segment. By default, TIBCO iProcess Objects Directors listen for UDP broadcasts on UDP port 28001. You can change this for a TIBCO iProcess Objects Director using the UDP_SERVICE_NAME process attribute (see UDP_SERVICE_NAME). For each TIBCO iProcess Objects Director that responds to the broadcast, an SWNodeInfo object is added to the SWEnterprise.NodeInfos list.

For more information about UDP broadcasts, see TIBCO iProcess Objects Programmer’s Guide.

•

Directed UDP Message  Using the AddNode or AddNodeEx method, the client can direct a UDP message to a TIBCO iProcess Objects Director (AddNodeEx allows you to direct the UDP to a specific instance of the Director). If directed to a TIBCO iProcess Objects Director, the AddNode/AddNodeEx method's IsDirector parameter must be set to True. If TIBCO iProcess Objects Director responds to the UDP message, a SWNodeInfo object representing TIBCO iProcess Objects Director is added to the SWEnterprise. NodeInfos list.

For more information about directed UDP messages, see TIBCO iProcess Objects Programmer’s Guide.

•

Manually Creating an SWNodeInfo Object  Using the MakeNodeInfo, MakeNodeInfoEx, or MakeNodeInfoByTag method, the client can manually add the SWNodeInfo object to the NodeInfos list (MakeNodeInfoEx allows you to add a specific instance of TIBCO iProcess Objects Director). If the SWNodeInfo object is to represent a TIBCO iProcess Objects Director, the MakeNodeInfo/MakeNodeInfoEx method's IsDirector parameter must be set to True when it is called.

For more information about manually creating an SWNodeInfo object, see TIBCO iProcess Objects Programmer’s Guide.

TIBCO iProcess Server Objects

A TIBCO iProcess Server Objects client accesses TIBCO iProcess Objects Directors using one of the following methods:

•

Auto-discovery UDP Broadcast   The client can send out a UDP broadcast to auto-discover TIBCO iProcess Objects Directors on the LAN segment by calling the getNodes method on sNodeManager. This method returns an array of vNode objects, one for each TIBCO iProcess Objects Director that responds to the UDP broadcast. By default, TIBCO iProcess Objects Directors listen for UDP broadcasts on UDP port 28001. You can change this for a TIBCO iProcess Objects Director using the UDP_SERVICE_NAME process attribute (see UDP_SERVICE_NAME).

For more information about UDP broadcasts, see TIBCO iProcess Server Objects Programmer’s Guide.

•

Directed UDP Message  The client can issue a directed UDP message to a TIBCO iProcess Objects Director by calling the verifyNode method on sNodeManager. If TIBCO iProcess Objects Director to which the UDP message was directed responds, the method call returns a vNode object that represents that TIBCO iProcess Objects Director. By default, TIBCO iProcess Objects Directors listen for UDP messages on UDP port 28001. You can change this for a TIBCO iProcess Objects Director using the UDP_SERVICE_NAME process attribute (see UDP_SERVICE_NAME).

For more information about directed UDP messages, see TIBCO iProcess Server Objects Programmer’s Guide.

•

Manually Creating a vNodeId Object  If you have all of the required information (node name, computer name, IP address, and TCP port), you can construct a vNodeId object that represents TIBCO iProcess Objects Director. The aIsDirector parameter in the vNodeId constructor must also be set to True to indicate that the object represents TIBCO iProcess Objects Director.

For more information about manually creating an SWNodeInfo object, see TIBCO iProcess Server Objects Programmer’s Guide.