Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# TCP Parameters

Note | This dialog box is from the Windows TIBCO iProcess® Objects Server Configuration Utility. The configuration parameter names shown in the callouts are from the UNIX TIBCO iProcess® Objects Server configuration file. This illustration provides a cross-reference to determine which fields to change when using the configuration utility.

# TCPServiceName

This identifies the port number on which the TIBCO iProcess® Objects Server will listen for client connections. This can be specified in the following ways:

| • | Specify a value of “DEFAULT”. This means use a dynamic port, which causes the operating system to assign the port number when the TIBCO iProcess® Objects Server starts. This designation is used if you are issuing a UDP broadcast to determine the available TIBCO iProcess® Objects Servers, or you are sending a directed UDP message to a specific TIBCO iProcess® Objects Server.

See TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide for information about issuing UDP broadcasts or sending directed UDP messages.

| • | Specify a value other than “DEFAULT”. This means use a static port, which causes the TCP port number to be fixed for the TIBCO iProcess® Objects Server you are configuring. This is used if you are manually creating the node object that represents the TIBCO iProcess® Objects Server, which requires that you know the TCP port the TIBCO iProcess® Objects Server is using. You must also configure the TIBCO iProcess® Objects Server to use a static TCP port if you are using TIBCO iProcess Objects Director to choose a TIBCO iProcess® Objects Server for you. (For information about manually creating a node object that represents the desired TIBCO iProcess® Objects Server, see TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide. For information about using TIBCO iProcess Objects Director, see TIBCO iProcess Director Administrator’s Guide.)

To configure the TIBCO iProcess® Objects Server to use a static TCP port, either specify the desired TCP port number in the `TCPServiceName` parameter, or specify a “service name” that will map to the TCP port number. If using a service name, you must add the service name to the `%SystemRoot%\System32\Drivers\Etc\Services` file (Windows) or `/etc/services` file (UNIX) that maps the service name to the TCP port on which you want the TIBCO iProcess® Objects Server to listen for client connections. (If you specify a service name in this parameter, and that service name does not exist in the `services` file, the TIBCO iProcess® Objects Server will not start.)

## Multiple Instances of the TIBCO iProcess® Objects Server (on UNIX Systems)

The following is the process a UNIX TIBCO iProcess® Objects Server goes through to establish a TCP port when it starts up when you are running multiple instances of the TIBCO iProcess® Objects Server:

| 1. | The TIBCO iProcess® Objects Server looks to see if an instance-specific TCPServiceName parameter is defined for the instance of the TIBCO iProcess® Objects Server that is starting. For example, if instance 2 of the TIBCO iProcess® Objects Server is starting, it looks for TCPServiceName02 (the instance number appended to the parameter name is always two digits and zero padded). If the instance-specific parameter exists, it uses the TCP port specified.

| 2. | If an instance-specific TCPServiceName parameter has not been defined, the TIBCO iProcess® Objects Server will look to see if the “generic” TCPServiceName parameter (without the instance number appended to the TCPServiceName parameter) has been defined. If it has been defined, it determines the TCP port number assigned to that parameter. It then considers that the “base” TCP port number. Using the base TCP port number, it adds the TIBCO iProcess® Objects Server’s instance number (minus 1; because the base number is used by instance 1) to the base TCP port number to determine the TCP port for that instance of the TIBCO iProcess® Objects Server (e.g., if the base TCP port number is 10000, instance 3 of the TIBCO iProcess® Objects Server will use TCP port 10002).

| 3. | If neither the instance-specific nor the “generic” TCPServiceName parameter has been defined, it defaults to dynamic, causing the operating system to assign the port number when the TIBCO iProcess® Objects Server is started.

## Multiple Instances of the TIBCO iProcess® Objects Server (on Windows Systems)

The following is the process a Windows TIBCO iProcess® Objects Server goes through to establish a TCP port when it starts up when you are running multiple instances of the TIBCO iProcess® Objects Server:

1. The TIBCO iProcess® Objects Server looks to see if you’ve assigned a TCP port to the specific instance of the TIBCO iProcess® Objects Server that is starting (i.e., you’ve selected the specific instance in the TIBCO iProcess® Objects Server Configuration Utility and specified a TCP port different than that specified for “<ServerName>(default)” in the utility). If an instance-specific assignment exists, it uses the TCP port specified.

2. If an instance-specific assignment does not exist (i.e., the TCP port assignment for the specific instance of the TIBCO iProcess® Objects Server is the same as “<ServerName>(default)” in the TIBCO iProcess® Objects Server Configuration Utility). This causes the TCP port assignment for “<ServerName>(default)” to become the “base” TCP port. Using the base TCP port number, it adds the TIBCO iProcess® Objects Server’s instance number (minus 1; because the base number is used by instance 1) to the base TCP port number to determine the TCP port for that instance of the TIBCO iProcess® Objects Server (e.g., if the base TCP port number is 10000, instance 3 of the TIBCO iProcess® Objects Server will use TCP port 10002).

Length: 40 characters maximum

Default: DEFAULT

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.