Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# UDPServiceName

This parameter identifies the port number on which the TIBCO iProcess® Objects Server will listen for UDP messages/broadcasts. This can be specified in one of the following ways:

| • | Specify a value of “DEFAULT” (the default). This causes the TIBCO iProcess® Objects Server to listen for UDP messages or broadcasts on port 55666.

| • | Specify the port number on which you want the TIBCO iProcess® Objects Server to listen for UDP messages/broadcasts.

| • | Specify a “service name” that will map to the UDP port number. This requires that you 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 UDP port on which you want the TIBCO iProcess® Objects Server to listen for UDP messages/broadcasts. (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.)

| • | Specify “None”. This causes the TIBCO iProcess® Objects Server to not open a UDP port, i.e., it will not respond to UDP messages/broadcasts.

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

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

UNIX TIBCO iProcess® Objects Server goes through the following to establish a UDP port multiple instances of the TIBCO iProcess® Objects Server:

| 1. | The TIBCO iProcess® Objects Server checks if an instance-specific UDPServiceName 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 UDPServiceName02 (the instance number appended to the parameter name is always two digits and zero padded). If the instance-specific parameter exists, it uses the UDP port specified (or if “None” is specified, it will not open a UDP port).

| 2. | If an instance-specific UDPServiceName parameter has not been defined, the TIBCO iProcess® Objects Server will look to see if the “generic” UDPServiceName parameter (without the instance number appended to the UDPServiceName parameter) has been defined. If it has been defined, it determines the UDP port number assigned to that parameter. It then considers that the “base” UDP port number. Using the base UDP 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 UDP port number to determine the UDP port for that instance of the TIBCO iProcess® Objects Server (e.g., if the base UDP port number is 55670, instance 3 of the TIBCO iProcess® Objects Server will use UDP port 55672).

| 3. | If neither the instance-specific nor the “generic” UDPServiceName parameter has been defined, the first instance of the TIBCO iProcess® Objects Server is assigned port 55666, instance 2 is assigned 55667, and so on.

## 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 UDP 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 UDP 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 UDP port different than that specified for “<ServerName>(default)” in the utility). If an instance-specific assignment exists, it uses the UDP port specified (or if “None” is specified, it will not open a UDP port).

2. If an instance-specific assignment does not exist (i.e., the UDP 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 UDP port assignment for “<ServerName>(default)” to become the “base” UDP port. Using the base UDP 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 UDP port number to determine the UDP port for that instance of the TIBCO iProcess® Objects Server (e.g., if the base UDP port number is 55670, instance 3 of the TIBCO iProcess® Objects Server will use UDP port 55672).

Length: 40 chars max

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.