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

Starting from WebSphere Integration Developer

You can design SOA applications in WebSphere® Integration Developer (IBM® Integration Designer) that need to call services in WebSphere Message Broker, or be called by services in WebSphere Message Broker

Note: From Version 7.5 onwards, WebSphere Integration Developer has been renamed IBM Integration Designer. Information in this topic that refers to WebSphere Integration Developer Version 7 is also applicable to IBM Integration Designer Version 7.5. Similarly, from Version 7.5 onwards, WebSphere Process Server has been renamed IBM Business Process Manager Advanced. Information in this topic that refers to WebSphere Process Server Version 7.0 is also applicable to IBM Business Process Manager Advanced Version 7.5.
  • If you are developing a service on WebSphere Integration Developer and you want WebSphere Message Broker to be able to send requests to it, you create an export component in your WebSphere Integration Developer application.
  • If you want to call a WebSphere Message Broker service from your WebSphere Integration Developer application, you create an import component in your application.
After you have created your WebSphere Integration Developer application, you export a PI file, which you can then import into WebSphere Message Broker.

Use the New Message Definition File wizard or the Start from SCA Import or Export Quick Start wizard to import WebSphere Integration Developer export and import components. See Message Sets: Importing SCA import or SCA export components. Ensure that the import or export components that you import from WebSphere Integration Developer use SOAP 1.1 bindings; a validation error occurs if you attempt to import SCA import components or SCA export components that have been generated with SOAP 1.2 bindings.

Importing the PI file creates the message definition file and the Broker SCA definition files.

If you import a WebSphere Integration Developer import component and create a Broker SCA definition from it, you create a Broker SCA definition with a file extension of .insca. The Broker SCA definition contains:
  • binding information (in a file with an extension of .import)
  • WSDL and XSD files that describe the message format
Broker SCA definitions that are created from imported WebSphere Integration Developer import components provide values for properties on the SCAInput node which can then receive requests from WebSphere Process Server.
If you import a WebSphere Integration Developer export component and create a Broker SCA definition from it, you create a Broker SCA definition with a file extension of .outsca. This file contains:
  • binding information (in a file with an extension of .export)
  • WSDL and XSD files that describe the message format
Broker SCA definitions that are created from imported WebSphere Integration Developer export components provide values for properties on the SCARequest node, or the SCAAsyncRequest and SCARequest nodes, which can then send requests to WebSphere Process Server.
Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:56


Concept topicConcept topic | Version 8.0.0.7 | bc34005_