WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Using Broker SCA definitions to configure message flows

Use Broker SCA definitions to create and configure SCA nodes in a message flow.

A Broker SCA definition is a broker artifact that has a .insca or .outsca extension. The artifact contains the following information:
  • 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 Broker SCA definition files appear in a folder, named Broker 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 Broker 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 Broker 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.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:34


Concept topicConcept topic | Version 8.0.0.7 | ac68570_