Alphabetical List of Process Attributes

Defines whether or not to log the case data changes in the audit trail when these changes are made by iProcess Insight, iProcess Workspace (Browser), or the setCaseData TIBCO iProcess Server Objects interface, rather than by normal step processing.

Controls whether the Open Work Item and Keep Work Item audit trail entries are enabled.

Defines the number of days to delay the auto-purge operation.

Defines the destination queue to which work items are redirected when the owner of the work items has been deleted.

Defines the redirect location of work items for a currently deleted user.

Defines the limit of actions per workflow transaction.

Enables you to define the refresh period for updating the cached list of cases currently on the system.

Defines whether or not iProcess checks if any outstanding delayed-release EAI steps have been successfully withdrawn before committing the purge transaction.

Defines the number of loops to process before the background process checks for sw_error.log files, which are located in the SWDIR\logs directory and available disk space.

Defines the number of case numbers to be cached.

Defines whether or not the list of available procedures in the TIBCO iProcess Workspace’s Case Start dialog is automatically refreshed.

Defines the size of the shared memory segment (in Kb) that should be allocated for shared memory debug logs.

Defines the number of messages that are cached by the DBQD process when it requests a block of messages from a database message queue.

Defines the number of concurrent threads that the DBQD process uses to process RPC requests for messages from its cache from BG or WISMBD processes.

Defines the default major version number that TIBCO iProcess Modeler will use when a new procedure is saved.

Defines the default minor version number that TIBCO iProcess Modeler will use when a new procedure is saved.

Defines the character set to be used for output encoding.

Defines whether case counts are displayed for procedures in the Live (Dead) Cases column of the Case Administrator dialog box, when a user starts iProcess Administrator from iProcess Workspace (Windows).

Defines whether or not a new user name is validated as an O/S user account when you add an iProcess user from the User Manager tool of TIBCO iProcess Administrator.

Defines whether or not the Possible iProcess User List button is displayed in the User Manager tool of TIBCO iProcess Administrator.

Defines the times during the day when the Deadline Manager checks the iProcess database for expired deadlines.

Defines the EAI server plug-ins that need to use the Microsoft Distributed Transaction Coordinator (MSDTC).

Defines a time threshold (in milliseconds) for the duration of processing an EAI step.

Defines how long the Mbox Daemons will remain idle when all Mbox queues in the Mbox set are empty.

Defines the number of seconds to increment the EMPTYMBOXSLEEP value by when a BG or WISMBD process requests a message from an empty Mbox.

Defines the maximum value (in seconds) that EMPTYMBOXSLEEP can be set to.

Defines whether or not background case prediction is enabled on the node.

Enables the JMX server that is loaded into RPC_TCP_LI to allow the existing clients to connect to the iProcess Engine.

Defines whether the audit_date timestamp, which is written in the audit_trail table, records when the user operates a specified instruction or when the BG processes a specified instruction.

Defines the maximum number of procedure definitions that can be cached in memory by the BG, WIS and SPO processes.

Defines a priority value for case deadlines that override all other priorities set for case deadlines.

Defines whether the WIS session, which is used to retrieve work items, should be freed up in the WIS memory or not after the lock, keep, forward, release, undo, or unlock operation.

Defines the character set to be used for output encoding for messages published to the IAPJMS process from the BG or WIS process.

Defines the port number that is used for message communications between the BG process and the IAPJMS library.

Defines whether or not the BG process is enabled to publish audit activities to the IAPJMS process.

Defines whether or not failed message transactions should be rolled back.

Defines whether or not the JMS topic name is static or dynamically configured at run-time.

Defines whether message delivery is synchronous or asynchronous.

Defines how long the IAPJMS process should wait before it times out if there is a network error.

Defines the topic name for the JMS destination if activity monitoring is enabled.

Defines whether users may keep or release work items even if pack data has changed.

Defines how many times a failed message in a message queue is retried before being moved to the exception queue.

Defines the delay (in seconds) between each retry attempt for a failed message in a message queue, before the message is moved to the exception queue.

Defines the JVM attributes that should be specified for the Java Virtual Machine when it is started.

Defines the default location where passwords should be validated when a user attempts to log in to this iProcess Engine node.

Defines whether or not to insert a Transaction Control step automatically as the first step of all main cases.

Defines the time limit in seconds before the Deadline Manager will re-post unprocessed deadline messages.

Defines the maximum number of times to loop during the prediction process.

Determines the maximum number of nested sub-procedures supported by the server.

Defines a time threshold (in milliseconds) for the duration of dequeuing a message from an Mbox set.

Defines the unique identifier of the Mbox set to be used by a BG process when dequeuing messages received from a WISMBD process.

Defines the unique identifier of the Mbox set to be used by a BGPREDICT process when posting case changes messages to a BG process.

Defines the unique identifier of the Mbox set to be used by a WISMBD process when dequeuing messages received from a BG process.

Defines the unique identifier of the Mbox set to be used by a process when writing to a BG process.

Defines the unique identifier of the Mbox set to be used by a BGPREDICT process when posting case changes messages to a BG process.

Defines the unique identifier of the Mbox set (as defined in the mbox_set table) to be used by the BG process when writing to a WISMBD process.

Defines whether or not to migrate only live cases from previous versions to a new version when deploying from TIBCO Business Studio to TIBCO iProcess Engine.

Defines the amount of disk space (in Kilobytes) required for the background process to run.

Defines who has permission to unlock the work items.

Defines whether or not case data normalization is enabled.

Defines where iProcess Engine should obtain the list of users when it populates the Possible iProcess User List in the User Manager tool of TIBCO iProcess Administrator.

Defines whether or not the Process Sentinels automatically start the server processes after the Process Sentinels have started.

Defines whether or not, in TIBCO iProcess Modeler, a user has to enter a comment whenever they save a procedure.

Defines whether or not, in TIBCO iProcess Modeler, a procedure’s version number will be incremented whenever it is saved.

Defines the maximum number of instances of a procedure version.

Defines whether or not, if a process fails, the Process Sentinels automatically write to disk the contents of that process’ debug shared memory segment.

Defines whether or not a server process will automatically restart after a failure.

Defines the maximum number of times the Process Sentinels will attempt to restart a failed process.

Defines time (in seconds) during which Process Sentinels suspends or restarts a failed process.

Defines the amount of time the Process Sentinels will remain idle for.

Defines in which way you want to publish system events.

Defines the number of REQ IDs to be cached.

Determines how many of the latest versions of the procedure definition to cache when the iProcess Objects Server process restarts or quick starts.

Defines the number of items that must exist in a work queue for it to be cached when the WIS process restarts or quick starts.

Determines whether to enable the retry function that retrieves work items from the staffo database table for the configured Oracle RAC.

Defines whether or not iProcess Workspace (Windows) can access iProcess Engine.

Allows the batching of RPC calls to reduce the overhead in processing RPC calls individually.

Defines the maximum number of threads that the WIS and WQS processes can use to process RPC requests from client applications.

Defines the timeout period (in seconds) that an RPC request waits for a response from the iProcess Engine process.

Defines the port number that is used for message communications between the “worker” process (Process Sentinel) and the processes that audit system events if you want to publish system events using TIBCO Hawk Agent.

Defines the JMS topic name for the JMS destination that is used to publish system events, if publishing system events is enabled.

Defines the UNIX shared memory key that is allocated (using the ftok system call) when the WQS process is started.

Defines whether or not to contain the audit trail message (with message ID 34), which writes the information about procedure migration, in the published Monitor Event Detail message.

Determines how many of the latest versions of the procedure definition to cache when the iProcess Objects Server process starts normally.

Defines the maximum amount of time (in milliseconds) that an iProcess Objects Server process should take to acquire for a mutual exclusion lock (mutex) before processing a message if multiple SSO clients use the same user name to log in to TIBCO iProcess Engine. If the time for acquiring a user’s mutex is over the time specified by the SPO_USERMUTEX_WAITTIME attribute, the duration will be recorded and later reported in the sw_warn log.

Defines whether or not to insert a Transaction Control step automatically as the first step of all sub-cases.

Defines the directory where the IAPJMS process will look for the Java libraries that it needs.

Defines whether you want to audit system events after installing or upgrading to TIBCO iProcess Engine 11.9.0.

Defines the time zone that this node will operate in.

Sets a limit on the number of unprocessed deadline messages that are posted by the Deadline Manager.

Defines the ways to purge vast quantities of cases in the Oracle AQs.

Defines whether to set the priority for the case deadlines by using the value of the SW_CP_VALUE field if the value of the FORCE_DEADLINE_PRIORITY attribute is set to the default value, 0.

Defines the number of Wait IDs to be cached.

Defines the maximum size (in bytes) of the sw_warn and sw_error log files before the files stop logging error messages.

Defines the notice period (in seconds) that iProcess Engine processes are given before a resynchronization takes place.

Defines the interval (in seconds) at which iProcess Engine checks to see if its timestamps are in step with Windows system time.

Defines the interval (in seconds) at which iProcess Engine checks to see if its timestamps are in step with Windows system time.

Defines the size (in threads) of the pool of threads that is used to perform caching of work queues.

Defines the number of items that must exist in a work queue for it to be cached when the WIS process starts normally.

Defines the maximum amount of time (in seconds) that an RPC processing thread in the WIS process waits for a work queue to be cached.

Defines the number of work items that the CDQP update thread will update in a single operation when updating CDQP field values for a WIS process’ queues.

Defines the number of times the WIS process attempts to retrieve the unfound work items from the staffo database table because a delay occurred between two Oracle RAC instances.

Note: This attribute is only used on configured Oracle RAC.

Defines the count boundary at which a work queue will be split into multiple blocks of work for filtering purposes, based on the number of work items in the queue

Defines the number of threads in the queue filtering thread pool, used to process additional blocks of filtering work

Defines the interval (in seconds) after which an index on a queue will be refreshed by a WIS process.

Defines the number of locks in the internal lock pool used by the WIS process

Defines the number of new item requests to be batched together.

Defines whether or not a change in the lock status of a work item is counted as a change to the work item.

Defines the timeout period (in seconds) after which a WIS process will automatically shut down, starting from the time at which it was last accessed (by a TIBCO iProcess Workspace, SAL application or TIBCO iProcess Objects Server).

Defines the timeout period (in seconds) after which a WIS process will automatically shut down, starting from the time at which iProcess Engine was shut down.

Defines the time (in minutes) after which the cached work queue that waits to be handled by the WIS process is cleared from the cache, starting from the time at which the client who last accessed this work queue logs off.

Defines the maximum amount of time (in seconds) that the queue update thread in the WIS process performs updates before going back to idle state.

Defines how often the queue update thread in the WIS process wakes up and updates the queues handled by the WIS process.

Allows the use of priority escalation in the WIS process to be disabled.

Defines the port number that is used for work queue delta messages between the WIS process and the IAPJMS process.

Defines the default topic name for the JMS destination used by the WIS process for work queue delta publication.

Allows the gathering of RPC call stats within the WQS process to be configurable.

Defines the maximum number of slots available in the SWRPCMTS multi-threaded RPC server shared library for threads to perform queue searching.

Defines how often (in seconds) the contents of the WQS/WIS shared memory are written to the wqs_index table in the database.

Defines the number of WIS processes that should be dedicated to handling user queues and group queues respectively.