This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Interoperability between SCA modules and Open SCA services

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The IBM® WebSphere® Application Server V7.0 Feature Pack for Service Component Architecture (SCA) provides a simple, yet powerful programming model for constructing applications based on the Open SCA specifications. The SCA modules of IBM Integration Designer use import and export bindings to interoperate with Open SCA services developed in a Rational® Application Developer environment and hosted by the WebSphere Application Server Feature Pack for Service Component Architecture.

An SCA application invokes an Open SCA application by way of an import binding. An SCA application receives a call from an Open SCA application by way of an export binding. A list of supported bindings is shown in Invoking services over interoperable bindings.

Invoking Open SCA services from SCA modules

SCA applications developed with IBM Integration Designer can invoke Open SCA applications developed in a Rational Application Developer environment. This section provides an example of invoking an Open SCA service from an SCA module using an SCA import binding.
Figure 1. Component in SCA module invoking Open SCA service
Illustration of a component in an SCA module invoking an Open SCA service. The call is made by way of an import in the SCA module, which connects to the service.

No special configuration is required to invoke an Open SCA service.

To connect to an Open SCA service by way of an SCA import binding, you provide the component name and service name of the Open SCA service in the import binding.
  1. To obtain the name of the target component and service from the Open SCA composite, perform the following steps:
    1. Ensure that the Properties tab is open by clicking Window > Show View > Properties.
    2. Open the composite editor by double-clicking the composite diagram that contains the component and service. For example, for a component named customer, the composite diagram is customer.composite_diagram.
    3. Click the target component.
    4. In the Name field of the Properties tab, note the name of the target component.
    5. Click the service icon associated with the component.
    6. In the Name field of the Properties tab, note the name of the service.
  2. To configure the IBM Integration Designer import to connect it to the Open SCA service, perform the following steps:
    1. In IBM Integration Designer, navigate to the Properties tab of the SCA import that you want to connect to the Open SCA service.
    2. In the Module name field, enter the component name from step 1.d.
    3. In the Export name field, enter the service name from step 1.f.
    4. Save your work by pressing Ctrl+S.

Invoking SCA modules from Open SCA services

Open SCA applications developed in a Rational Application Developer environment can invoke SCA applications developed with IBM Integration Designer. This section provides an example of invoking an SCA module (by way of an SCA export binding) from an Open SCA service.
Figure 2. Open SCA service invoking component in SCA module
Illustration of a service component in Open SCA invoking a component in an SCA module. The call is made by way of a reference, which connects to an export in the SCA module.

To connect to an SCA component by way of an Open SCA reference binding, you provide the module name and export name.

  1. To obtain the name of the target module and export, perform the following steps:
    1. In IBM Integration Designer, open the module in the assembly editor by double-clicking the module.
    2. Click the export.
    3. In the Name field of the Properties tab, note the name of the export.
  2. Configure the Open SCA reference that you want to connect to the IBM Integration Designer module and export:
    1. In Rational Application Developer, open the composite editor by double-clicking the composite diagram that contains the component and service.
    2. Click the reference icon of the component reference to display the reference properties in the Properties tab.
    3. Click the Binding tab on the left side of the page.
    4. Click Bindings and then click Add.
    5. Select the SCA binding.
    6. In the Uri field, enter the IBM Integration Designer module name, followed by a slash (/), followed by the export name (which you determined in step 1.c).
    7. Click OK.
    8. Save your work by pressing Ctrl+S.

Invoking services over interoperable bindings

The following bindings are supported for interoperability with an Open SCA service.
  • SCA binding
    In IBM Integration Designer, when an SCA module invokes an Open SCA service by way of an SCA import binding, the following invocation styles are supported:
    • Asynchronous (one-way)
    • Synchronous (request/response)

    The SCA import interface and the Open SCA service interface must use a web services interoperability (WS-I) compliant WSDL interface.

    Note that the SCA binding supports transaction and security context propagation.

  • Web service (JAX-WS) binding with either the SOAP1.1/HTTP or SOAP1.2/HTTP protocol

    The SCA import interface and the Open SCA service interface must use a web services interoperability (WS-I) compliant WSDL interface.

    In addition, the following qualities of service are supported:

    • Web Services Atomic Transaction
    • Web Services Security
  • EJB binding

    A Java™ interface is used to define the interaction between an SCA module and an Open SCA service when the EJB binding is used.

    Note that the EJB binding supports transaction and security context propagation.

  • JMS bindings

    The SCA import interface and the Open SCA service interface must use a web services interoperability (WS-I) compliant WSDL interface.

    The following JMS providers are supported:
    • WebSphere Platform Messaging (JMS Binding)
    • WebSphere MQ (MQ JMS Binding)
Note: Business Graphs are not interoperable across any SCA bindings and, therefore, are not supported in interfaces used to interoperate with the WebSphere Application Server Feature Pack for Service Component Architecture.