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

User Parameters

This dialog is from the Windows TIBCO iProcess Objects Server Configuration Utility. The configuration param7eter 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.

CheckOSUser

Flag indicating if all new TIBCO users must exist as O/S users.

This parameter is applicable only if TIBCO iProcess Engine does not require a password. This is specified in the $SWDIR/etc/staffpms (UNIX) or SWDIR\etc\staffpms (Windows) file (for information about configuring TIBCO iProcess Engine to check for passwords, see TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide ).

TIBCO iProcess Engine contains a DISABLE_USER_CHECK process attribute that is checked before the CheckOSUser parameter is checked. If the DISABLE_USER_CHECK attribute is set to 1, the new user does not have to be an existing O/S user, regardless of how the CheckOSUser parameter was set.

Values: 0 (No) or 1 (Yes)
Default: 0 (No)

SEOPasswordRequired

Flag indicating whether user passwords will be checked by TIBCO iProcess Objects Server.

This parameter is applicable only if TIBCO iProcess Engine requires a password. This is specified in the $SWDIR/etc/staffpms (UNIX) or SWDIR\etc\staffpms (Windows) file (for information about configuring TIBCO iProcess Engine to check for passwords, see TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide ).

If TIBCO iProcess Engine is set to not require passwords, this parameter is forced to 0 (No) regardless of the setting in this configuration file.

Values: 0 (No) or 1 (Yes)
Default: 1 (Yes)

AuditUserAdmin

Flag specifying if user administrative changes should be written to the audit log. Audit messages are written to the $SWDIR/logs/swentobjuaXX_timestamp.log (UNIX) or SWDIR\logs\SWEntObjUaXX_timestamp.log (Windows) file (for information about the audit log, see TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide ).

Note that the audit log file is never rolled over by TIBCO iProcess Objects Server; it is the responsibility of administrator at your site to back up and remove this file.

Values: 0 (No) or 1 (Yes)
Default: 1 (Yes)

MultipleLogins

Flag specifying whether or not to allow simultaneous connections to the TIBCO iProcess Objects Server from the same user name.

If you are using a web-based client (for example, TIBCO iProcess Workspace (Browser)), this flag must be set to 1 (enable multiple logins). Disabling multiple logins only makes sense in thick-client applications.

 

Values: 0 (No) or 1 (Yes)
Default: 1 (Yes)

ImplicitMoveSysInfo

This configuration parameter allows you to control when the MOVESYSINFO function is performed.

If this parameter is set to 1 (the check box in the Windows TIBCO iProcess Objects Server Configuration Utility is checked), the TIBCO iProcess Objects Server will implicitly call MOVESYSINFO whenever an administrative function is performed, i.e., any function that affects a user, group, role, attribute, or queue supervisor definition. Note that this can tie up the background and WIS/WQS processes for long periods of time if there are lots of users. This is the default.

If this parameter is set to 0, the TIBCO iProcess Objects Server will not call the MOVESYSINFO function whenever an administrative function is performed. This allows the client application to use the MoveSysInfo method to explicitly call the MOVESYSINFO function. This allows the client application to control when the MOVESYSINFO function will occur. For information about the MoveSysInfo method, see TIBCO iProcess Objects or TIBCO iProcess Server Objects on-line help.

Values: 0 (No) or 1 (Yes)
Default: 1 (Yes)

DBConnectionAccess

This configuration parameter allows you to control user access to the database configuration information. This parameter can be set to the following states:

•	Disabled - This is the default setting. The database configuration information is not accessible by any user.

•	Enabled - no access restriction - The database configuration information is accessible by all users.

•	Enabled - must be an administrator - The database configuration information is accessible only by system administrators (users whose MENUNAME attribute is ADMIN).

Values: 0 (Disabled), 1 (Enabled for all users), or 2 (Enabled only for system administrators)
Default: 0 (Disabled)

IAPConfigAccess

This configuration parameter allows you to control user access to TIBCO iProcess Engine’s activity publication configuration. This parameter can be set to the following states:

•	Disabled - This is the default setting. The activity publication configuration is not accessible by any user.

•	Enabled - no access restriction - The activity publication configuration is accessible by all users.

•	Enabled - must be an administrator - The activity publication configuration is accessible only by system administrators (users whose MENUNAME attribute is ADMIN).

Values: 0 (Disabled), 1 (Enabled for all users), or 2 (Enabled only for system administrators)
Default: 0 (Disabled)

 

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