Note: From Version 7.5 onwards, WebSphere Process Server has been renamed IBM Business Process Manager Advanced. Information in this
topic that refers to IBM Business Process Manager Advanced Version
7.5 is also applicable to WebSphere Process Server Version
7.0. Similarly, from Version 7.5 onwards, WebSphere Integration Developer has been renamed IBM Integration Designer. Information in this topic that
refers to IBM Integration Designer Version 7.5 is
also applicable to WebSphere Integration Developer Version
7.
SCA is a specification that describes a model for building applications
and systems using a service-oriented architecture (SOA).
IBM Integration Bus provides built-in message
flow nodes that allow interoperability with WebSphere Process Server. These nodes support inbound
and outbound scenarios with WebSphere Process Server.
In an inbound scenario, a service component in WebSphere Process Server can send a request to IBM Integration Bus. In an outbound scenario,
a message flow in IBM Integration Bus can
send a synchronous or asynchronous request to WebSphere Process Server.
The nodes are configured by a Broker SCA definition. You can create
a Broker SCA definition in two ways:
- From an SCA import or SCA export component that is defined in IBM Integration Designer Version 7.5 or WebSphere Integration Developer Version 7 and imported into IBM Integration Bus.
- From an IBM Integration Bus message set.
The SCA nodes cannot be used without a Broker SCA definition
to configure them.
If you want to call services available on
IBM Integration Bus, you must either:
- Import an SCA import component from WebSphere Integration Developer and create a message flow that
uses an SCAInput node,
or
- Generate an inbound Broker SCA definition and export the .insca file
to WebSphere Integration Developer
If you want to call a service in
WebSphere Process Server,
you must either:
- Import an SCA export component from WebSphere Integration Developer and configure a message flow
using the Broker SCA definition that is created, or
- Generate an outbound Broker SCA definition and export the .outsca file
to WebSphere Integration Developer
When designing message flows with SCA, you must select a suitable
transport (also called a
binding). The SCA nodes support
these transports:
Important: The SCA nodes do not support the SCA binding
in WebSphere Integration Developer, which is used only for
SCA invocations between modules running within WebSphere Process Server.
The following topics describe how to work with SCA:
Last updated Friday, 21 July 2017