Process configuration defines the behavior of a process at runtime. You can specify, or edit, the modifiers, mode, and activation type for a process. You can also define process properties and process variables, add or remove services and references, and configure the process dependencies. Open a process in
TIBCO Business Studio™ for BusinessWorks™ if it is not already open and go to the
Properties view. Configure the properties for a process by selecting the appropriate tab in the
Properties view.
General
Property Name
|
Description
|
Package
|
Displays the name of the package containing the process. This field is not editable. To rename the package name, select the bulb icon on the right side. It open a
Rename Package dialog box. Change the package name using the
Rename Package dialog box.
|
Name
|
Name of the process. This field is not editable. To rename the process name, select the bulb icon on the right side. It open a
Rename Process dialog box. Change the process name using the
Rename Process dialog box.
|
Description
Property Name
|
Description
|
Description
|
Description of the process.
|
Advanced
Property Name
|
Description
|
Target Namespace
|
Target namespace for the process.
You can specify a different target namespace.
|
Modifiers
|
Modifiers define the visibility of the process outside its package:
- Public: can be invoked by processes that are defined either inside or outside the package.
- Private: can be invoked only by processes that are part of the same package.
|
Mode
|
Mode defines whether the process depends on the engine to maintain its state:
- Stateful: Stateful processes maintain the state across multiple operations. They are better suited when you need the server to maintain the state across operations. For processes that involve related message exchanges between the same or different consumers, conversations can be used to maintain state across operations.
- Stateless: Stateless processes do not maintain state. They are better suited when you need to process higher loads of requests as each operation is executed independently. They do not require correlation or conversations between multiple operations in a process , thus allowing the server to process each operation without maintaining any state information. The client can choose to maintain the state information, if needed.
|
Activation
|
Activation mode for a process defines the way in which processes are activated at runtime.
- Multiple AppNodes: At runtime, the application is distributed and activated on all the AppNodes in the AppSpace. In the event of a failure on one of the AppNodes, the application continues to run with fewer AppNodes.
- Single AppNode: At runtime, the application is activated on only one AppNode in the AppSpace. In the event of a failure, another AppNode will be activated and any check pointed data can be recovered.
Note: This feature requires the engine persistence mode to be set to group and the database and group provider to be configured. See Configuring Database for the Engine and Configuring Group Provider for the Engine for details.
|
Activity Error Variable
|
By default, this check box is selected for migrated processes. During migration, activity error variables are created for activities in the process that contain error transitions. Additional activity error variables are also created for activities with fault types, and or, if new activities with fault types are added to the process.
If you are configuring a process created in ActiveMatrix BusinessWorks 6.x, and you select this check box, activity error variables are created for activities in the process that have fault types. If new activities with fault types are added to process, additional activity error variables are created.
Clear the check box removes activity error variables created for activities with fault types. Global error variables and activity error variables for activities with error transitions are not affected.
|
Namespace Registry
|
Namespaces and prefixes can be configured at the Process level. Click the Configure namespace registry link field from the Advance tab of the Process configuration to view, add, change or delete prefixes for namespaces used in the input bindings of the activities in the process definition. Process namespace registry applies to the current process.
Namespaces and prefixes can also be configured at the Module level. To add a new prefix for a namespace or to change the current namespaces and prefix configurations, from the Module Descriptors > Overview getting started area, click the Configure namespace registry link. Module namespace registry applies to all the processes in the module.
If you have defined both, Process level and Module level configurations for a namespace, the Process level registry takes precedence over the Module namespace registry.
When namespace registry is applied, prefixes in the activity input bindings are updated using the prefixes defined in the namespace registry where the namespaces are referred to.
A list of namespaces and their prefixes is automatically populated when an input or output binding is created or modified. This list is populated at the Process level or at the Module level, depending on the preference set at Windows > Preferences> BusinessWorks > Namespace Registry.
|
Process Properties
Add or delete process properties variables in the following format:
Property Name
|
Description
|
Property Name
|
Provide a property name.
|
Data Type
|
Supported Data Types are:
- Boolean
- DateTime
- Integer
- Long
- PassWord
- String
- Data Format
- FTP Resource
- HTTP Client
- HTTP Connector
- Identity Provider Resource
- JDBC Connection
- JMS Connection
- JavaGlobalInstanceResource
- KeyStoreprovider Resource
- LDAP Authentication
- Notify Configuration
- Proxy Configuration
- Rendezvous Transport
- SMTP Resource
- SSL Client
- Subject Provider Resource
- TCP Resource
- ThreadPool Resource
Data types may vary depending on the additional plug ins installed.
|
Default Value
|
Provide the Default value based on a data type.
|
Process Variables
Process variables are used to store temporary data that are used by the process to store values other than simple output from an activity. Simple type or Complex Type variables can be created.
Services
Use the
Services tab to create additional services.
References
Use the
References tab to create additional references that are consumed by the process.
Dependencies
The
Dependency tab can be used for troubleshooting any unresolved element-namespace issues in your process. This tab provides a view of what WSDL & XSD namespaces are currently being imported, and it also provides a way to add a new namespace import that will resolve a specific Element. If you choose the Element, the appropriate namespace import is then added to make sure that the element resolves.
Copyright © Cloud Software Group, Inc. All rights reserved.