Configuring the SCAAsyncRequest node (deprecated)

se the SCAAsyncRequest node with the SCAAsyncResponse node to construct a pair of message flows that invoke a WebSphere® Process Server service 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 SCAAsyncRequest node.

There are two methods of putting an instance of the SCAAsyncRequest 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 a node onto the canvas
If you have dragged an instance of the node from the palette onto the canvas, use one of the following methods to start to configure it:
  • Drag an Integration Bus SCA definition with an extension of .outsca onto the node.
  • Type the file name in the SCA file name option in the Properties view of the node.
  • Browse to the file (SCA file name option in the Properties view of the node.)
Dragging a .outsca file onto the canvas
  • If the .outsca file contains a WSDL that has only a single, one-way operation defined, a SCARequest node is created.
  • If the .outsca file contains a WSDL that only has request-response operations, you first select the operation, and say whether you want the outbound request to be sent synchronously or asynchronously. For a synchronous request, a SCARequest node is created and configured. For an asynchronous request, a pair of SCAAsyncRequest and SCAAsyncResponse nodes are created and configured.
  • If the .outsca file contains a WSDL that has a mixture of one-way and request-response operations defined, and you select a one-way operation, a SCARequest node is created.

About this task

The values for many of the node properties are provided in 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.
    1. Unique identifier. You must specify the unique string that is common to your pair of SCAAsyncRequest and SCAAsyncResponse nodes. This property is mandatory.
    2. In IBM Integration Bus SCA definition, specify the name of the IBM Integration Bus SCA definition that contains configuration properties for the SCAAsyncRequest 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.
      • Type a file name that is relative to the message set project in which the IBM Integration Bus SCA definition exists.
      • 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, 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 (deprecated).
      • Drag an IBM Integration Bus SCA definition from a message set onto the node.
  3. On the Binding tab, specify properties that relate to the WebSphere Process Server binding. Some of the properties on this tab are derived from the IBM Integration Bus SCA definition.
  4. Optional: If required, change your binding type.
    The value of the Binding type property is derived from the binding information in the IBM Integration Bus SCA definition. It is read-only. Possible values are:
    • WebService. Requests from WebSphere Process Server are sent as SOAP messages over the HTTP transport. See the WSDL properties table in SCAAsyncRequest node Terminals and properties for details of binding properties that are either supplied by the IBM Integration Bus SCA definition, or that you need to set.
    • MQ. Requests from WebSphere Process Server arrive as IBM MQ messages. See the MQ properties table and the Transactionality table in SCAAsyncRequest node Terminals and properties, for details of binding properties that are either supplied by the IBM Integration Bus SCA definition, or that you need to set. For more information about using IBM MQ with IBM Integration Bus, see Installing IBM MQ.

What to do next

For information on configuring the SCAAsyncRequest node to use SSL, see Setting up a public key infrastructure and review the information that relates to the SOAPAsyncRequest node.