Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Accessing Multiple Instances of the TIBCO iProcess® Objects Server

The way in which you access multiple instances of the server depends on whether you are using TIBCO iProcess Objects or TIBCO iProcess Server Objects, as described in the following subsections.

## Using TIBCO iProcess Objects

The following are methods you can use to access multiple instances of the TIBCO iProcess® Objects Server using TIBCO iProcess Objects:

| • | UDP Broadcast - Each SWNodeInfo object that is returned from a UDP broadcast contains information about which instance of the TIBCO iProcess® Objects Server the object represents. The SWNodeInfo object key includes the instance number as follows:

       ComputerName|NodeName|IsDirector|InstanceNumber

| • | Directed UDP Message - The AddNodeEx method is used to send a directed UDP message to a specific instance of the TIBCO iProcess® Objects Server. This method contains an InstanceNumber parameter to specify the instance.

| • | Manually Create an SWNodeInfo Object- The MakeNodeInfoEx method is used to create an SWNodeInfo object for a specific instance of the TIBCO iProcess® Objects Server. This method contains an InstanceNumber parameter to specify the instance.

| • | TIBCO iProcess Objects Director - The TIBCO iProcess Objects Director is a standalone program that chooses a TIBCO iProcess® Objects Server for you. The method it uses to choose a server depends on how the TIBCO iProcess Objects Director is configured.

For more information about these methods of accessing multiple instances of the TIBCO iProcess® Objects Server, see TIBCO iProcess Objects Programmer’s Guide.

## Using TIBCO iProcess Server Objects

The following are methods you can use to access multiple instances of the TIBCO iProcess® Objects Server using TIBCO iProcess Server Objects:

| • | UDP Broadcast - Calling the `getNodes` method on sNodeManager causes a UDP broadcast to be issued on the LAN segment. The getNodes method returns an array of vNode objects, one for each TIBCO iProcess® Objects Server that responded to the UDP broadcast. You can then call the `getInstance` method on the vNode object to determine the instance number of that TIBCO iProcess® Objects Server.

| • | Directed UDP Message - Calling the `verifyNode` method on sNodeManager causes a directed UDP message to be sent to a specific instance of the TIBCO iProcess® Objects Server. This method provides an `aInstance` parameter to specify the specific instance of the TIBCO iProcess® Objects Server to receive the UDP message.

| • | Manually Create a vNodeId Object- You can construct a vNodeId object that represents the specific instance of the desired TIBCO iProcess® Objects Server. Note that the constructor for the vNodeId object does not have an `Instance` parameter — you must use the `aTCPPort` parameter to uniquely identify the instance of the TIBCO iProcess® Objects Server the vNodeId object is to represent.

| • | TIBCO iProcess Objects Director - The TIBCO iProcess Objects Director is a standalone program that chooses an TIBCO iProcess® Objects Server for you. The method it uses to choose a server depends on how the TIBCO iProcess Objects Director is configured.

For more information about these methods of accessing multiple instances of the TIBCO iProcess® Objects Server, see TIBCO iProcess Server Objects Programmer’s Guide.

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-2025. Cloud Software Group, Inc. All Rights Reserved.