Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# 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:

| • | Windows - In Windows, configuration parameters are modified using TIBCO iProcess® Objects Server Configuration Utility. The configuration utility is available as a Control Panel applet (note that if the server is installed on a 64-bit machine, the utility applet is found under "View x86 Control Panel Icons" on the Control Panel) or by executing SWDIR`\bin\SWEntObjSvCfg.exe`.

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.

| • | UNIX - When using the supported UNIX operating systems (AIX, HP-UX, etc.), the configuration parameters are stored in the text file $SWDIR`/seo/data/swentobjsv.cfg`. The parameters in this file have the format:

    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).

Subtopics

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-2025. Cloud Software Group, Inc. All Rights Reserved.