Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Connecting to a TIBCO iProcess Objects Server via a Director

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

## TIBCO iProcess Objects

The key of the SWNodeInfo object (available in the Key property) obtained through one of the methods described in the previous subsection identifies whether the object represents a TIBCO iProcess Objects Server or Director, as follows:

    SWNodeInfo.Key = ComputerName|NodeName|IsDirector|InstanceNumber

If IsDirector = Y, it represents a Director; if IsDirector = N, it represents a Server.

Once the client has an SWNodeInfo object that represents a TIBCO iProcess Objects Director, the key from that object can be passed in the NodeKeys parameter of the `Login` method:

    Login (NodeKeys, Password, [UserName])

If the `NodeKey` represents a Director (IsDirector = Y), the Director uses the “pick method” specified when the Director was configured to determine which TIBCO iProcess Objects Server the client should connect to. Internally, a TCP connection is established between the client and the TIBCO iProcess Objects Server that the Director selected. From the user’s standpoint, the selection and connection to the TIBCO iProcess Objects Server is transparent. All future transmissions, while that user is logged in, are made directly to the TIBCO iProcess Objects Server instance.

Note that if the client fails to connect to the TIBCO iProcess Objects Server (for example, an invalid user name or password is passed), it will NOT be logged in the TIBCO iProcess Objects Director’s log. Once TIBCO iProcess Objects Director gives the client a TIBCO iProcess Objects Server to log in to, communication with TIBCO iProcess Objects Director is complete. You must use the TIBCO iProcess Objects Server’s log to troubleshoot this type of problem.

Note | For efficiency reasons, after having TIBCO iProcess Objects Director choose a TIBCO iProcess Objects Server for you, you should log in 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 log in; subsequent logins can use that same SAL session, resulting in a much more efficient and faster login.

## TIBCO iProcess Server Objects

To connect to a TIBCO iProcess Objects Server via a TIBCO iProcess Objects Director, you must have a vNodeId object that represents the Director (the vNode object returned by getNodes or verifyNode can be cast to a vNodeId object).

Pass the vNodeId object that represents TIBCO iProcess Objects Director in the constructor for the desired Server Object. For example:

    sUser(vNodeId aNodeId,
          String aUserName,
          String aPassword)

If the vNodeId object represents TIBCO iProcess Objects Director, the Director use the “pick method” specified when the Director was configured to determine which TIBCO iProcess Objects Server the Server Object should connect to. Internally, a TCP connection is established between the Server Object and the TIBCO iProcess Objects Server that the Director selected. From the user’s standpoint, the selection and connection to the TIBCO iProcess Objects Server is transparent. All future transmissions, while that user is logged in, are made directly to the Server instance.

Note that if the client fails to connect to the TIBCO iProcess Objects Server (for example, an invalid user name or password is passed), it will NOT be logged in the TIBCO iProcess Objects Director’s log. Once the TIBCO iProcess Objects Director gives the Server Object a TIBCO iProcess Objects Server to log in to, communication with TIBCO iProcess Objects Director is complete. You must use the TIBCO iProcess Objects Server log to troubleshoot this type of problem.

Note | For efficiency reasons, after having the TIBCO iProcess Objects Director choose a TIBCO iProcess Objects Server for you, you should log in 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 log in; subsequent logins can use that same SAL session, resulting in a much more efficient and faster login. (Use the `getNodeId` method to get the vNodeId object for the particular instance of the TIBCO iProcess Objects Server to which you are connected so you can connect to that same instance at a later time.)

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.