Message Sets: Importing from SCA Export or SCA Import: generated objects

A number of objects are generated when you import from an SCA export or SCA import.

  • An Integration Bus SCA definition file. The file extension is .insca for an import component, or .outsca for an export component. The .insca or .outsca files are stored in an Integration Bus SCA Definitions folder under the message set project. If multiple SCA Import/Exports are imported into a message set, each has its own .insca or .outsca file.
    You can drag the Integration Bus SCA Definition onto the Message Flow Editor to create a skeleton flow.
    • Dragging and dropping a .insca object onto the Message Flow editor creates a pair of SCAInput and SCAReply nodes if the Integration Bus SCA definition interface contains one or more request-response operations. Otherwise, only the SCAInput node is created.
    • Dragging and dropping a .outsca object onto the Message Flow editor creates either a SCARequest node, or a pair of SCAAsyncRequest and SCAAsyncResponse nodes.
  • Corresponding message definitions (.mxsd) files are created from the XSD types that are used by the messages specified in the WSDL interface in the SCA Import or Export. The message definitions are stored in their respective target namespaces.
  • If the SCA Import or SCA Export being imported uses a web services Binding type, the deployable WSDL is imported into the message set.
  • If the SCA Import or SCA Export being imported uses an MQ Binding type, a deployable WSDL is not imported into the message set.
  • A log is created for the import in the log folder under the message set project.