IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Converting a WebSphere Enterprise Service Bus service transactional behavior manually

Configure the Transactional Mode property and the Coordinated Transaction property in IBM® Integration Bus to define the equivalent transactional behavior of a mediation module.

In IBM Integration Bus, the following properties control the transactional behavior of an integration service or application:
  • The transactional mode property, that you set on nodes.
  • The message flow Coordinated Transaction property, that you set at deployment time for a message flow.
In WebSphere® Enterprise Service Bus, Quality of Service (QoS) qualifiers and the Invocation Style are the properties that control the propagation of transactions in a mediation module.

In IBM Integration Bus, you set the message flow transactional behavior at deployment time for each implementation of a mediation flow component. In WebSphere Enterprise Service Bus, you set the mediation module transactional behavior during development.

By default, IBM Integration Bus and WebSphere Enterprise Service Bus behavior is to manage message flow transactions by using a one-phase commit, that is, manage transactions locally:
  • In IBM Integration Bus, you enable the Coordinated Transaction property.
  • In WebSphere Enterprise Service Bus, you set the Transaction qualifier to Local.

Configure the following resources and associated properties to define the equivalent transactional behavior that is configured in a WebSphere Enterprise Service Bus mediation module:

  1. Configure individual nodes in a message flow to set the required level of participation of each node in a transaction. For each node, configure the property Transaction Mode to determine how a node participates in a message flow transaction. You set this property on Input nodes, Output nodes, Request nodes, Reply nodes, Compute nodes, and Database nodes. You can set this property to one of the following values:
    • Yes to indicate that the node is part of a message flow transaction.
    • No to indicate that the node is not part of a message flow transaction.
    • Automatic to indicate that all subsequent nodes in the message flow assume the transactional characteristics of this node.
    For more information, see Configuring transactionality for message flows.
    Note: To choose the value of the Transaction Mode property for WebSphere Enterprise Service Bus primitives, you must consider the type of primitive:
    • For primitives that do not call external web services, check the value that is set for the Transaction qualifier of the primitive. This value determines the transaction behavior of the primitive in a mediation flow component.
    • For Callout primitives and for Service Invoke primitives, you must consider the value that is set in WebSphere Enterprise Service Bus for the Transaction qualifier of the primitive. You must also consider the value of the Join Transaction qualifier or the Suspend Transaction qualifier:
      • If the Transaction qualifier is set to Global and a client calls a service synchronously, the value that is set for the Join Transaction qualifier on the interface determines how the service joins the client propagated transaction.
      • If the Transaction qualifier is set to Global and a service makes a synchronous invocation of a target service, the value that is set for the Suspend Transaction qualifier determines whether the client propagates the transaction to the target component or not.
  2. Configure the overall message flow transactional behavior. Set the message flow Coordinated Transaction property. For more information, see Configuring global coordination of transactions (two-phase commit).
    • In IBM Integration Bus, you set the property Coordinated Transaction.
    • In WebSphere Enterprise Service Bus, you set the Transaction qualifier.

bm33068_.htm | Last updated Friday, 21 July 2017