![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.Note that if you change the value of this parameter, you may also need to change the value of the MAXPOOLSIZE parameter, which is specified in the $SWDIR/etc/staffcfg (UNIX) or SWDIR\etc\staffcfg (Windows) file. This depends on whether or not your TIBCO iProcess Objects Server has CR 14735 implemented. If your TIBCO iProcess Objects Server contains CR 14735, you do not need to set MAXPOOLSIZE. If it does not contain CR 14735, you must set MAXPOOLSIZE according to the information below.To ensure that you do not run out of database connections, you must make sure that the value of the MAXPOOLSIZE parameter in the staffcfg file is set to the proper value. Running out of database connections can result in the TIBCO iProcess Objects Server failing with an ER_SYSTEM error. The value to set MAXPOOLSIZE depends on the number of threads being used. Therefore, to determine its value, you must use the value of the NumThreads configuration parameter. Use the following formula to determine the value to set the MAXPOOLSIZE parameter:
• NumCPUs is the number of processors on the system.
• DFLTMAXTHREADS is the default value, 5.SWDIR\bin\swentobjsv -v
•
# of CPU's : Number_of_CPU# of Threads: Number_of_Threads
Be aware that if you are running multiple TIBCO iProcess Objects Servers on the same machine, and they are different versions that allow a different upper range for NumThreads, TIBCO iProcess Objects Server Configuration Utility will allow you to set the upper limit up to 32,767. Ensure that you specify only the number of threads allowed for the version of server you are configuring.The number of SAL sessions to pool in the general user pool. (Anonymous users use their own pool (see Anonymous parameters on Anonymous Parameters).)where process_msg is the name of the function where the timeout occurred, and user is the name of the user that timed out trying to get a SAL session.Lower Bound: 0
Upper Bound: 7
Default: 2
On UNIX systems, this configuration parameter is not automatically written to your TIBCO iProcess Objects Server configuration file (swentobjsv.cfg) when you upgrade from an earlier TIBCO iProcess Objects Server. (It can be found in the “sample” configuration file (sample.cfg) that is written to your system when you upgrade.) To make use of this parameter, you must manually add it to your configuration file.
• Set the NumFiles configuration parameter to the desired maximum number of files to open. If present, the TIBCO iProcess Objects Server will use this value to set the maximum number of open files. If NumFiles is NOT specified, the TIBCO iProcess Objects Server will use the TCPMaxClients parameter as described below to determine the maximum number of open files. (Note - By default, the NumFiles parameter is NOT specified.)
• Allow the TIBCO iProcess Objects Server to calculate the maximum number of open files using the value in the TCPMaxClients configuration parameter (see TCPMaxClients). The calculation shown below is used:The TIBCO iProcess Objects Server will automatically use the formula shown above to set the maximum number of files if the NumFiles parameter is not specified.(12 * Number of users) + 100
− Run the command ulimit -n unlimited to set the file limit to the operating system design limits; this command will only be successful if TIBCO iProcess Engine is started as the root user or if the system limits allow this.Lower Bound: 148
Upper Bound: System limit
Default: There is no default. If this parameter is not specified, the TCPMaxClients parameter is used to calculate the number of files.
The StackSize parameter is not included in the configuration file ($SWDIR/seo/data/swentobjsv.cfg) by default. If you want to set the stack size to a value different from the default, you must manually add this parameter to the configuration file.If you experience this type of error, increasing the thread stack size may resolve the problem. The default stack size is 2MB per thread. To increase this value, you must manually add the StackSize parameter to your configuration file. Note that increasing the stack size will increase the overall memory size of TIBCO iProcess Objects Server.Lower Bound: 100 (Although the lower bound of 100K is enforced, this parameter should probably not be set to a value lower than the default.)Upper Bound: Limited by system thread stack size limits
Default: 2MB (AIX, HP-UX, Linux, and Solaris)
Note: Empty information is returned for both TIBCO iProcess Objects and the TIBCO iProcess Server Objects client. The functions that are used to return values for each client are as follows:
The CacheProcEAISep parameter is not included in the swentobjsv.cfg configuration file by default when you install or upgrade TIBCO iProcess Objects Server. To cache the EAI step definition, you must manually add this parameter to the configuration file.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |