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


Configuring the SCAAsyncResponse node

When you add a SCAAsyncResponse node to a message flow, configure it to construct a pair of message flows that start a component asynchronously.

Before you begin

Ensure that the message set contains an IBM® Integration Bus SCA definition with an extension of .outsca with which to configure the node.

About this task

There are two methods of putting an instance of the node into a message flow: You can either drag an instance of the node from the node palette, or drag an IBM Integration Bus SCA definition with an extension of .outsca from a message set, onto the message flow editor canvas. Dragging an IBM Integration Bus SCA definition with an extension of .outsca onto the canvas creates a pair of SCAAsyncRequest and SCAAsyncResponse nodes.

If you have dragged an instance of the node from the palette onto the canvas, you must then start to configure it by dragging an IBM Integration Bus SCA definition with an extension of .outsca onto the node. The values for many of the node properties are provided in the IBM Integration Bus SCA definition. If you have dragged an IBM Integration Bus SCA definition onto the canvas and created a pair of SCAAsyncRequest and SCAAsyncResponse nodes, many of the values for the node properties have already been supplied from the IBM Integration Bus SCA definition.

The properties of the node are displayed in the Properties view. All mandatory properties for which you must enter a value (properties that do not have a default value defined) are marked with an asterisk.

Procedure

  1. Optional: On the Description tab, enter a Short description, a Long description, or both. You can also rename the node on this tab.
  2. On the Basic tab, set the Unique identifier and IBM Integration Bus SCA definition properties.
  3. In IBM Integration Bus SCA definition, specify the name of the IBM Integration Bus SCA definition that contains configuration properties for the node. If you have created the node by dragging an IBM Integration Bus SCA definition from a message set onto the Message flow editor canvas, this property is preset to the name of the IBM Integration Bus SCA definition. If you created the node by selecting it from the palette, you can set this property in one of the following ways:
    • If you have an IBM Integration Bus SCA definition, you can select it from the IBM Integration Bus SCA definitions by clicking Browse.
    • If you have IBM Integration Bus SCA definitions, but no message set, you can create a message set:
      1. Click Browse to open the Integration Bus SCA Definition Selection pane.
      2. Click Import/Create New to open the Import IBM Integration Bus SCA definition wizard.
      3. Enter the message set name and message set project name, then click Next.
      4. Choose the relevant option:
        • If your IBM Integration Bus SCA definition exists in your workspace, click Use resources from the workspace, and select the IBM Integration Bus SCA definition.
        • If your IBM Integration Bus SCA definition is in the file system, click Use external resources, select the IBM Integration Bus SCA definition, then click Next.
      5. Select the IBM Integration Bus SCA definition to import.
      6. Click Finish. A new message set project and message set are created with message definitions. The IBM Integration Bus SCA definition is added to the Integration Bus SCA Definitions folder.
      7. Select the IBM Integration Bus SCA definition from the Integration Bus SCA Definition Selection window, then click OK.
    • If you have a message set but no IBM Integration Bus SCA definition, generate an IBM Integration Bus SCA definition by following the instructions in Message Sets: Generating an IBM Integration Bus SCA definition from a message set.
    • Drag an IBM Integration Bus SCA definition from a message set onto the node.
    • Type a file name that is relative to the message set project in which the IBM Integration Bus SCA definition exists.
  4. On the Binding tab, specify properties that relate to the binding. Some of the properties on this tab are derived from the IBM Integration Bus SCA definition.

    The value of the Binding type property is derived from the binding information in the IBM Integration Bus SCA definition, and is read-only. Possible values are:

    • WebService. Web service responses are sent as SOAP messages over the HTTP transport.
    • MQ. MQ responses arrive as messages.

      If an MQ binding is specified in the SCA definition, WebSphere® MQ is used to process the messages, so you must ensure that WebSphere MQ is installed on the same computer as your integration node. WebSphere MQ is not provided as part of the IBM Integration Bus installation package, but your license for IBM Integration Bus entitles you to install and use WebSphere MQ. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.

      The Propagate only SOAP body (owned by XMLNSC domain) check box is shown only when the Binding type is Web Services. It is not shown when the Binding type is MQ; there are no MQ-specific binding properties.

On the Response Message Parsing tab, the properties are set automatically from the Integration Bus SCA Definition file.

  1. On the Parser Options sub tab, set properties that are associated with the parser.
    • Parse timing is, by default, set to On Demand, which causes parsing of the message to be delayed. For information about how to cause the message to be parsed immediately, see Parsing on demand.
    • XMLNSC Parser Options. Set values for the properties that determine how the XMLNSC parser operates. For more information, see Manipulating messages in the XMLNSC domain.
  2. Use the Validation tab to provide validation based on the message set for predefined messages. For more information about validation, see Validating messages. For information about how to complete this tab, see Validation tab properties.
  3. Use the Instances tab to specify how additional threads are handled for the message flow.
    • The Additional instances pool property specifies whether additional instance threads are allocated from a thread pool for the whole message flow, or from a thread pool for use by that node only. By default, this property is set to Use Pool Associated with Message Flow.
    • The Additional instances property specifies the number of additional threads that the integration node can use to service the message flow and has the default value 0.

ac68541_.htm | Last updated 2015-11-26 23:59:13