IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Advanced development topics > Assuring Quality of Service
Quality of service qualifier reference
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.
Qualifiers used in the assembly editor Qualifier Set on ... Description Activity session 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 Reference Determines if asynchronous invocations should occur as part of a client transaction. Asynchronous reliability Reference Three qualifiers (reliability, request expiration, and response expiration) that you can use to determine the reliability of asynchronous message delivery. Data validation qualifier 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 Interface Places a control on the order in which the runtime environment processes events. Join activity session Interface Specifies if the target service is capable of joining a client propagated activity session. Join transaction Interface Specifies if the target service is capable of joining a client propagated transaction. Reliability Reference See "asynchronous reliability" Security identity Implementation Provides a logical name for the identity under which the implementation runs at run time. Security permission 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 Reference Determines whether the client will propagate the activity session to the referenced component. Suspend transaction Reference When the invocation is synchronous, the qualifier determines whether the client will propagate the transaction to the referenced component. Transaction Implementation Determines the logical unit of work that the component's processing runs.
- Activity session qualifier
The activity session qualifier determines if the component's processing will be run under an activity session, which provides an alternative unit-of-work scope to the one provided by a transaction context.- Asynchronous invocation qualifier
The asynchronous invocation qualifier allows you to specify that an asynchronous invocation.should occur as part of a client transaction. The qualifier determines when the message is sent to the target.- Asynchronous reliability qualifiers
The three asynchronous reliability qualifiers (reliability, request expiration, and response expiration) determine the quality of the delivery of an asynchronous message.- Business object (BO) instance data validation qualifier
A data validation qualifier confirms that the data passed in to an operation matches the XSD types of the operation's inputs. It can be used to validate instance data from a business object.- Event sequencing qualifier
The event sequencing qualifier ensures that events are processed in order and that one event is completely processed before the next one is processed.- Join activity session qualifier
The join activity session qualifier determines whether the target service is capable of joining a client propagated activity session.- Join transaction qualifier
This qualifier determines whether the target service is capable of joining a client-propagated transaction.- Security identity qualifier
The security identity qualifier is a privilege specification that you can use to provide a logical name for the identity under which the implementation runs at run time.- Security permission qualifier
The security permission qualifier specifies a role, which is a semantic grouping of permissions that a given type of users must have to use an operation in an interface.- Store and forward qualifier
The store and forward qualifier can be used to store asynchronous messages when exceptions occur at run time. By default, it is not enabled.- Suspend activity session qualifier
When the invocation is synchronous, the suspend activity session qualifier determines whether the client will propagate the activity session to the referenced component.- Suspend transaction qualifier
When the invocation is synchronous, this qualifier determines whether client will propagate the transaction to the target component.- Transaction qualifier
This qualifier determines the logical unit of work that the component's processing runs. For a logical unit of work, all of the data modifications to resources (not to be confused with changes to the values in a business object) made during a transaction are either committed together as a unit or rolled back as a unit.
Related concepts:
Quality of service: Qualifiers for business services