This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Quality of service qualifier reference

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Qualifiers are specifications that define a set of communication characteristics required by an application for transmission priority, level of route reliability, transaction management, and security level. You can specify quality of service qualifiers in the assembly editor. These qualifiers define how much management must be provided for a component at run time.
Usually, you should think about quality of service qualifiers when you are designing your error handling strategy. You can set qualifiers on
  • Interfaces
  • References
  • Implementations

The system generates qualifiers that promote the propagation of transactions and reliable asynchronous message delivery where possible. You can change these preset qualifiers in the assembly editor. In some cases, the implementation requires that some qualifiers are set a certain way. In such cases, the system either blocks you from making the change or generates an error message.

Some implementations determine how qualifiers must be set. In these situations, the system generates the qualifiers for you. If you change the values of those generated qualifiers, you risk creating validation errors. If you are working with Java™ components, you need to set the qualifiers yourself.

Here are the qualifiers that you can set in IBM® Integration Designer. Click the qualifier name to see details.

Table 1. Qualifiers used in the assembly editor
Qualifier Set on ... Description
Activity session qualifier Implementation Determines if the component's processing will be run under an activity session, an alternative unit-of-work scope to a transaction.
Asynchronous invocation qualifier Reference Determines if asynchronous invocations should occur as part of a client transaction.
Asynchronous reliability qualifiers Reference Three qualifiers (reliability, request expiration, and response expiration) that you can use to determine the reliability of asynchronous message delivery.
Qualifier: Business object (BO) instance data validation Interface Confirms that the data passed in to an operation (usually a business object instance) matches the XSD types of the operation's inputs.
Event sequencing qualifier Interface Places a control on the order in which the runtime environment processes events.
Join activity session qualifier Interface Specifies if the target service is capable of joining a client propagated activity session.
Join transaction qualifier Interface Specifies if the target service is capable of joining a client propagated transaction.
Reliability Reference See "asynchronous reliability"
Security identity qualifier Implementation Provides a logical name for the identity under which the implementation runs at run time.
Security permission qualifier Interface Allows access only to users who have been granted a particular security role.
Store and forward qualifier   Allows you to store asynchronous messages when exceptions occur at run time.
Suspend activity session qualifier Reference Determines whether the client will propagate the activity session to the referenced component.
Suspend transaction qualifier Reference When the invocation is synchronous, the qualifier determines whether the client will propagate the transaction to the referenced component.
Transaction qualifier Implementation Determines the logical unit of work that the component's processing runs.