Using IBM Integration Bus SCA definitions to configure message flows
Use IBM® Integration Bus SCA definitions to create and configure SCA nodes in a message flow.
- Binding type and interface information which is present in SCA import or SCA export components
- WSDL that defines the interface
- XSD files that describe the message format
The IBM Integration Bus SCA definition files appear in a folder, named Integration Bus SCA Definitions, in the message set project.
A .insca file contains an SCA Import component, and is used to configure SCAInput and SCAReply nodes.
A .outsca file contains an SCA Export component, and is used to configure SCAAsyncRequest, SCAAsyncResponse, and SCARequest nodes.
To create and configure SCA nodes, drag IBM Integration Bus SCA definitions, which are generated from SCA import or export files, into the message flow editor. This action automatically creates the appropriate nodes, and completes many of the configurable properties of the nodes. The nodes cannot be used if there is no IBM Integration Bus SCA definition with which to configure the nodes.
For Web Services binding, the data defines the service and the port name for the service within the WSDL that is invoked. It also defines an SCA endpoint address, extracted from the WSDL.
For MQ binding, the data defines the WebSphere® MQ connection properties, the message binding format, the replyTo destination, and transaction and security information. 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. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.