Configuration Parameters
The TIBCO iProcess® Objects Server is configured using configuration parameters. The operating system you are using will determine how you modify the parameters:
The TIBCO iProcess® Objects Server stores all configuration parameters in the Windows Registry in the following key:
\HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO iProcess\TIBCO iProcess Objects Server\Nodes
Each TIBCO iProcess® Objects Server keeps its configuration under a key with the same name as the node name of the server. Note that it is highly recommended that you use the configuration utility to modify parameters rather than editing the registry directly.
If any configuration parameters are missing when the TIBCO iProcess® Objects Server is started, they will be automatically created with default values. The TIBCO iProcess® Objects Server will not start if any configuration parameters have invalid values.
ConfigKey=Values
where:
ConfigKey is the name of the configuration parameter.
Value is the value of the parameter.
Lines beginning with a # are ignored and can be used for comments or for temporary changes. Blank lines are ignored and can be used to improve the readability of the file.
If any configuration parameters are missing when the TIBCO iProcess® Objects Server is started, they will be automatically created with default values. If any of the configuration parameters contain invalid values, the TIBCO iProcess® Objects Server will not start.
To make changes to the configuration file, you must first stop the UNIX TIBCO iProcess® Objects Server, make your changes, then restart the server.
iProcess Objects Server Configuration File When Upgrading
[UNIX only] If you are upgrading TIBCO iProcess Objects Server from an earlier version on a UNIX system, the installation program will not overwrite your server configuration file, $SWDIR/seo/data/swentobjsv.cfg, if it exists. (Since this is an upgrade, the only reason the configuration file wouldn’t already exist is if it has been manually moved/deleted). The installation program won’t overwrite your existing configuration file because you may have customized it for your particular needs.
| • | If the swentobjsv.cfg file does not exist, the installation program will install both an swentobjsv.cfg file and a sample.cfg file in the $SWDIR/seo/data directory. These files will be exactly the same. |
| • | If the swentobjsv.cfg file does exist, the installation program will install only a sample.cfg file in the $SWDIR/seo/data directory. |
In both cases above, the newly installed configuration file (swentobjsv.cfg and/or sample.cfg) is the configuration file for the version of the server to which you are upgrading. It may contain new configuration parameters or other changes. Note, however, that all configuration parameters in the new configuration file(s) are commented out — if used as is, iProcess Objects Server will use the default values for all parameters.
If the new configuration file contains new/modified information, you can copy that information and paste it into your configuration file. (You can use the diff program (diff swentobjsv.cfg sample.cfg) to determine what is different between your configuration file and the new configuration file.)
Whether or not you make any modifications, the $SWDIR/seo/data directory must contain a swentobjsv.cfg file, which will be used to configure iProcess Objects Server when it is started.
Also, if any of the configuration parameters contain invalid values, iProcess Objects Server will not start. Note that since iProcess Objects Server log file is not opened until after the configuration file is read, if there is an error in the configuration file, it is not written to the log file. Instead, it is written to the $SWDIR/logs/seo_error file (this file is created when iProcess Objects Server starts, so the presence of the file does not mean there were errors).