Copyright © Cloud Software Group, Inc. All rights reserved.
Copyright © Cloud Software Group, Inc. All rights reserved.


Chapter 2 Configuring the TIBCO iProcess Objects Server : TCP Parameters

TCP 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.
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:
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.
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.
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.
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.
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
TCPResolveName
This flag specifies if the server should employ TCP name resolution (DNS, host file, YP, etc.). Setting this value to 1 causes the TIBCO iProcess Objects Server to do name resolution of all client connection requests. If set to 0, the TIBCO iProcess Objects Server uses the client IP address and TCP connection port to identify clients.
This parameter is used for debugging purposes. When set to 1, the machine name of the client appears in the log file, instead of the client’s IP address.
Setting this parameter to 1 may have a negative impact on performance. It is recommended that you normally leave this parameter set to 0 unless debugging.
Values: 0 (no) or 1 (yes)
Default: 0
BindToPrimaryIPAddr (Windows Only)
Specifies whether or not the TIBCO iProcess Objects Server should bind the TCP and UDP ports to the primary IP address of the machine. Checking this box (value of 1) causes the ports to be bound ONLY to the primary IP address of the machine (this is the behavior of previous releases of the TIBCO iProcess Objects Server). Not checking this box (value of 0) causes the TCP and UDP ports to be bound to ADDR_ANY. This allows TCP (client) connections to the TIBCO iProcess Objects Server over any of the network interfaces on the machine, rather than just the primary interface.
If this parameter is set to 1, the SWClientInfo.Name property returns the following information:
<Client IP Address>:<TCP Port #>
For example: 10.12.84.135:9288
If this parameter is set to 0 (the default), the SWClientInfo.Name property returns the following information:
<Client IP Address>:<TCP Port #> - <Server IP Address>:<TCP Port #>
For example: 10.12.84.135:9288 - 10.12.84.36:1520
Values: 0 or 1
Default: 0
TCPMaxClients
The maximum number of concurrent client connections.
Windows Systems
A value of 0 means no imposed maximum (still bound by the license, however).
Lower Bound: 0
Upper Bound: none
Default: 0
UNIX Systems
Increasing this value will require that the system supports an increased number of open files as well as raising the amount of memory that will be used (approx. 16K of additional memory will be used for each 1,000 that this parameter is increased). Under normal circumstances, this value should be set to slightly above either your licensed number of users or the maximum number of clients that you expect to connect to the TIBCO iProcess Objects Server.
If a client connects to the TIBCO iProcess Objects Server and that connection causes the total number of connections in the TIBCO iProcess Objects Server to exceed TCPMaxClients, the connection will be aborted and the client will get a “TIBCO iProcess Objects Server disconnected” error on the login. (The TIBCO iProcess Objects Server error log will be written to if this occurs.)
This parameter may also be used by TIBCO iProcess Engine startup script to determine the maximum number of open files — see the NumFiles parameter on NumFiles (UNIX Only) for more information.
Lower Bound: 64
Upper Bound: 32,767
Default: 1,024
TCPQLength
Number of TCP connection requests to allow the TCP kernel to queue up. A value of 0 means the maximum allowed by the kernel. Under normal operating conditions, it is recommended that you do not change the value of this parameter.
Lower Bound: 0
Upper Bound: none
Default: 0
TCPRequestPages
Number of pages for request buffers. Each page is 2,048 bytes. It is not normally necessary to change the value of this parameter from its default value.
Values: 1 to 8
Default: 1 (2,048 bytes)
TCPResponsePages
Windows Systems
Number of pages for response buffers. Each page is 2,048 bytes. It is not normally necessary to change the value of this parameter from its default value. The value of this parameter would only need to be increased in an installation where the TIBCO iProcess Objects Server responses to a client request are very large.
Values: 1 to 8
Default: 2 (4096 bytes)
UNIX Systems
The size of the response buffer defined in number of pages, where each page is 2,048 bytes.
This value defines the maximum amount of data that the server will send to the client in one transmission; the server then waits for the client to acknowledge receipt of that transmission before sending the next buffer.
Depending on your network configuration, it may be beneficial to set this value to any number up to the maximum (8 pages, which is 16,384 bytes), particularly if large amounts of data are being sent back to the client.
Under normal circumstances, the buffer size should be set to your network buffer limit or the TIBCO iProcess Objects Server limit (16,384 bytes), whichever is lower.
The maximum network buffer size can be displayed with the ndd command, as follows:
/usr/sbin/ndd /dev/tcp tcp_max_buf
The default size for this is 1,048,576 bytes, which allows the configuration parameter to be set to the maximum 8 pages.
Values: 1 to 8
Default: 2 (4096 bytes)

Copyright © Cloud Software Group, Inc. All rights reserved.
Copyright © Cloud Software Group, Inc. All rights reserved.