Advanced Process Properties

Properties Page

Property

Description

Error

Error Handler Task

The task step that the Process Engine executes when an error occurs during the execution of a process instance. Also known as a process-wide error step.

If a step with a boundary intermediate error event fails, the transition for that event is taken in response to the failure.

If a step with no boundary intermediate error event fails, the process executes the logic defined in the error handler task.

If a step with no boundary intermediate error event fails and there is no designated error handler task, the process fails.

Cancel

Cancel Handler Task

The task step that the Process Engine executes, along with any downstream transitions, when its status is changed to Cancel by webMethods Monitor or a service invocation. Also known as a process-wide cancel step.

Note:

Designer supports debugging the Cancel Handler Task. When using the Trace view in the Process Debugging perspective, you can manually force the cancellation of a process. See About the Trace View.

Timeout

Timeout Handler Task

The task step that the Process Engine executes when the Maximum Process Execution Time is reached.

Note:

Designer supports debugging the Timeout Handler Task. When using the Trace view in the Process Debugging perspective, you can manually force a process-wide timeout. See About the Trace View.

Maximum Process Execution Time

Defines the maximum length of time a process can execute. The Timeout Handler Task step executes when this setting is reached. If no timeout handler task is defined, the process instance fails. Also known as a process-wide timeout.

The source of this value can be:

A static value that you define.

A value based on a business calendar in My webMethods Server. You can specify the number of days, hours, and minutes.

For more information, see Defining a Process Timeout.

Run Time

Generated Package Name

By default, the name of the generated Integration Server package is set to the name of the project. You can edit the package name. Only ASCII characters are allowed.

Important:

If you change a process-wide property, such as renaming a process or a package, Designer prompts you to regenerate the process.

Quality of Service

This section provides settings that affect process run-time behavior. For complete information about working with these fields, see Setting Quality of Service for a Process.

Optimize Locally: Execute adjacent steps on the same Integration Server without publishing transition documents. Enabled by default.

Express Pipeline: Send a reduced data set between the steps in a process. Enabled by default. Can significantly improve performance with large pipelines (1 MB or more).

Volatile Transition Documents:

Send process transition documents in volatile mode. Enabled by default.

Select Volatile Transition Documentsto specify that Universal Messaging or Broker stores process transition documents and referenced process start documents in the specified message provider RAM.

Clear this check box to specify that Universal Messaging or Broker stores process transition documents and referenced process start documents on the local hard disk drive.

Volatile Tracking: Store process tracking information in memory only. Disabled by default.

Note:

If the Process Engine is running in a clustered environment, volatile tracking cannot be used, and this setting is ignored.

Select Volatile Tracking to specify that the Process Engine stores process status in RAM.

Clear this check box to specify that the Process Engine stores process status in the Process Engine database component.

Minimum Logging Level: Specifies the minimum audit logging threshold that can be set for this process in Monitor (that is, during run time). The default is 5 - Process and all events, activities, and looped activities. Available values are:

1 - None

2 - Errors only

3 - Process only

4 - Process and start events

5 - Process and all events, activities, and looped activities (default)

For more information, see “About Process Model Data Logging” in the PDF publication webMethods Monitor User’s Guide.

Runtime Editable Properties

Note:

All settings in this section can also be modified in Monitor. When you build and upload the process, the settings you define here will replace the existing run-time settings in the Process Audit database.

Synchronize: Click this button to load the settings for the properties in this section from the Process Audit database. For more information, see About Synchronizing Process Runtime Settings with webMethods Monitor .

Emit Process-specific Predefined EDA Events:

Select All/Clear All: Click to select or clear all EDA events.

Select or clear a predefined event type check box to specify whether or not the predefined event is to be emitted for this model. For more information, see Enabling and Disabling Predefined EDA Event Emission for a Process Model.

Steps Enabled for Resubmission

Select or clear a step check box to specify whether or not the step is enabled for resubmission. For more information, see Enabling a Step for Resubmission.

Deprecated properties

Enable deprecated error handling behavior (not recommended): This option is not recommended except in very isolated cases. For more information, see About Step Failure Behavior.

RosettaNet

Synchronous: Select this setting to generate an internal process flag called “synch” with a value of true. The Process Engine then passes this value to the RosettaNet Conversation Manager private data structure used to communicate with RosettaNet. Not selected by default.

Global Process Specification

Use this page to define the inputs and outputs for a callable process. A global process specification, along with a start none event, is used when a callable process is invoked by a call activity step.

The input specification for a callable process determines the data that flows into the start none event in the callable process when it is triggered by a call activity. The output specification for a callable process determines the data that flows out of the callable process and back to the call activity that triggered it. The entire pipeline is automatically sent back to the call activity.

Adding, editing, and removing inputs and outputs for a global process is done the same way as it is for steps. Refer to Create Inputs and Outputs and Remove Inputs and Outputs.

For more information, see Defining a Global Process Specification.

Default Deployment Values

Process will be execution-enabled by default during deployment by Deployer

Select this check box to automatically enable the process for execution when deployed by Deployer.

Process will be analysis-enabled by default during deployment by Deployer

Select this check box to automatically enable the process for tracking and analysis when deployed by Deployer.

Note:

This feature is associated with webMethods Optimize for Process. Analysis-enabled processes can be tracked by Business Activity Monitoring by the Optimize Analytics engine. For more information, refer to webMethods Optimize User’s Guide.