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


Configuring the SCAInput node

When you add a SCAInput node to a message flow, configure it to process messages that are read from files.

Before you begin

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

About this task

You can put an instance of the SCAInput node into a message flow in either of the following ways:
  • Drag an IBM Integration Bus SCA definition with an extension of .insca from a message set onto the message flow editor canvas. If the .insca file contains only one-way operations, dragging a .insca file onto the canvas creates a SCAInput node. Otherwise, a pair of SCAInput and SCAReply nodes is created. If you use this method, many of the values for the properties of the node or nodes are supplied by the IBM Integration Bus SCA definition.
  • Drag an instance of the node from the node palette onto the canvas. You then configure the node by dragging an IBM Integration Bus SCA definition with an extension of .insca onto the node.

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.

To configure the node, complete the following steps.

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 IBM Integration Bus SCA definition and Message routing properties.
  3. In IBM Integration Bus SCA definition, specify the name of the IBM Integration Bus SCA definition that contains configuration properties for the SCAInput node. If you 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. Optional: In Message routing, specify whether to allow message propagation to dynamic terminals for the operations that are defined in the SCA message or to the common Out terminal. By default, each operation is routed to its own terminal. You can select:
    • Route each operation to its own terminal. The default. One terminal is generated on the node for each operation defined in the interface of the IBM Integration Bus SCA definition and messages are propagated to the appropriate terminal.
    • Route to a common out terminal. One Out terminal is generated on the node. All messages are propagated to this terminal. If you select this option, the Propagate only SOAP body (owned by XMLNSC domain) check box is disabled and you cannot select it.

    If you specify the IBM Integration Bus SCA definition property by typing a file name, or by selecting an IBM Integration Bus SCA definition by using the Browse facility, on an SCAInput node that already has dynamic terminals configured on it, the existing dynamic terminals are replaced. If you specify a file name that is not valid, previously existing dynamic terminals are removed and no terminals are added.

    If you drag an IBM Integration Bus SCA definition onto an SCAInput node that already has dynamic terminals configured on it, a dialog box is displayed allowing you to confirm whether you want to override the existing dynamic terminals with dynamic terminals that might be generated from the IBM Integration Bus SCA definition. If you choose to override existing dynamic terminals, any existing connections that are configured for these terminals are also deleted. You can specify that this dialog box is not displayed again.

    If you drag an IBM Integration Bus SCA definition onto an SCAInput node that already has an Out terminal, no dynamic terminals that are generated from the IBM Integration Bus SCA definition are added and the node continues to operate with its Out terminal.

  5. 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. 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:
    • Web Service. Requests from WebSphere Process Server are sent as SOAP messages over the HTTP transport. See the WSDL properties table in Terminals and properties for SCAInput for details of binding properties that are either supplied by the IBM Integration Bus SCA definition, or that you must set.
    • MQ. Requests from WebSphere Process Server arrive as WebSphere MQ messages. See the MQ properties table and the Transactionality table in Terminals and properties for details of binding properties that are either supplied by the IBM Integration Bus SCA definition, or that you must set.

      If an MQ binding is specified, 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.

  6. Optional: On the Input Message Parsing tab, change the default domain. The properties are set automatically when the WSDL file is configured:
    • If the Binding type is Web Services, the Message domain is always SOAP.
    • If the Binding type is MQ, the Message domain defaults to XMLNSC if the data bindings for all operations are using XML. Otherwise, the default domain is BLOB. You can change the domain to MRM, XMLNSC, XMLNS, MIME, JSON, DFDL, or BLOB.
  7. On the Parser Options sub tab, set the properties that are associated with the parser.
    • Parse timing by default is 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.
  8. On the Validation tab, provide validation details that are 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.
  9. On the Instances tab, 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.
  10. On the Retry tab, define how retry processing is carried out when a failure gets rolled back to the input node.
    • The Retry mechanism defines the format of the mechanism, and its type is Enumerate. Set the property to either Failure or Short and long retry.
    • The Retry threshold property defines the number of retries to correct the failure, and its type is Integer.
    • The Short retry interval property defines the time that the client waits in seconds before attempting to correct the failure, and its type is Integer.
    • The Long retry interval property defines the time that the client waits in seconds before attempting to correct the failure, and its type is Integer.

ac68511_.htm | Last updated 2015-03-27 19:26:05