Before you start: You must
have created a message set that contains message definitions. The
wizard gives an error if the set of message definitions is empty.
To generate a Broker SCA definition:
- Switch to the Integration Development perspective.
- In the Application
Development view, right-click the folder
that contains the message set file from which you want to generate
a Broker SCA definition, and select . This action starts the Generate Broker SCA Definition wizard.
- Step through the wizard providing the details as required. Some of the panels and options are subject to settings that
you make within the wizard and might not always be shown. Also, some
fields in the wizard might be grayed out. This happens when a field
has a mandatory setting, or when the field is not used because of
settings that have already been made in other fields.
By
default, the wizard creates the Broker SCA definition in the message
set project.
On completion of the Generate
Broker SCA Definition wizard, you have generated either
a .insca or a .outsca Broker
SCA definition that is stored in the SCA category under the message
set project.
A .insca Broker SCA definition
is a compressed file that contains an SCA import and all the XSDs
and WSDLs that are referenced directly or indirectly by the SCA import
and a .outsca Broker SCA definition is a compressed
file that contains an SCA export and all the XSDs and WSDLs that are
referenced directly or indirectly by the SCA export.
Specifically,
the Broker SCA definition contains:
- A WSDL interface that contains one or more operations.
- XSDs that correspond to the messages that are used in the operations
defined in the interface.
- If you have selected a Web services binding, the WSDL contains
service and binding information that defines the endpoint.
- If you have not selected a Web services binding, the SCA Import
or Export must contain binding information for another binding that
is supported by IBM Integration Bus.
Last updated Friday, 21 July 2017