Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.


Chapter 2 Configuring the TIBCO iProcess Objects Server : UDP Parameters

UDP Parameters
This dialog 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.
SWEOServiceDesc
String used to describe the TIBCO iProcess Objects Server to clients. The client has access to this value in the SWNodeInfo.SWEOSrvDesc property (TIBCO iProcess Objects), vNode.getSEOSrvDesc method (TIBCO iProcess Server Objects (Java)), or vNode.SEOSrvDesc property (TIBCO iProcess Server Objects (.NET)). The value of this parameter can be any string that is useful to the client for identifying the server.
Length: 64 chars max
Default: TIBCO iProcess Objects Server
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 “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.)
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)
The following is the process a UNIX 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.
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.
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.
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

Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.