Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# 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.

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.

TIBCO iProcess Objects Director assumes the first instance of each TIBCO iProcess Objects Server uses 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 five TIBCO iProcess Objects Server instances exist 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

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