Importing SCA Modules to Create Composite Service Definitions

Websphere Business Services Fabric v7.0
Contact us...

Importing SCA Modules to Create Composite Service Definitions

A composite service is a service whose implementation calls other services.

A composite service in Composition Studio refers to a System Component Architecture (SCA) module. A composite service may be as simple as an SCA module that implements and exposes a web service or it may include complex Business Process Execution Language (BPEL) programs and have bindings to other services exposed by other modules.

When you import a composite service, the metadata captured tells you about the following items:

1. Services exposed by an SCA module
2. Services consumed by the SCA module
3. Dynamic Assembly decisions performed by the composite service

When you import a composite service, endpoints are created for export bindings that have a binding type of SCA or Web Service Bindings set to use the SOAP/HTTP protocol.

When you edit your selected context specification, the results will modify any open simulations that are currently pointing to the current Dynamic Assembly Component. You must ensure that you do not change the dimensions. It is also desirable that you update your simulation when you update your context specification.

It is necessary to create composite service definitions to feed the dynamic assembler information about the interfaces, modules, and dynamic assembly components that will be deployed. This is done by importing SCA modules that exist in the workspace into Composition Studio.

1. In the the Business Application Explorer, right-click Loans Origination App Project and select New\Composite Service ()
2. Select the SCA Project to be imported (i.e LoanOrigination) and click Finish ().  The following are created:
1. The import operation creates a Composite Service object that will show up in the Business Application explorer (). 
2. It will also create Service Interface definitions for interfaces used by the module. 
3. Endpoints are created for SOAP/HTTP or SCA Exports in the modules. Even though multiple modules may use a given service interface, the system does not create duplicates. Instead, it provides warning messages like the following ()
3. Once a composite service is created, changes in the original SCA module can be performed by carrying out the import again. It is important to import a module again if there are changes to its imports, exports or DA Components.
4. For each of the remaining modules listed below, carry out the same import steps 1 to 2 above ()
   

   Project	Name Space	SCA Project (module)	Description
   Loans Origination App Project	Loan Origination (Technical)	LoanOrigination	Module contains BPEL that captures the main process flow modeled in Business Space. Has several DA (Dynamic Assembler) Components, with one for each business service used in the flow.
   Loans Origination App Project	Loan Origination (Technical)	CheckCredit	Uses another dynamic assembler to select among three backend credit services.
   Loans Origination App Project	Loan Origination (Technical)	ReviewCollateral	Provides implementation of pass-through and human collateral review process variations.
   Loans Origination App Project	Loan Origination (Technical)	FinalReview	Provides implementations for automated and human underwriting.
   Loans Origination App Project	Loan Origination (Technical)	NotifyCustomer	Provides implementations for automated and human implementations.

Related links

1. Modeling, developing, assembling, deploying and managing an application
2. Working with the Fabric templates in Business Space
3. Business Space Information Center