Learn about SCA composites (deprecated)

Find links to Service Component Architecture (SCA) resources for learning, including conceptual overviews, tutorials, and samples.

Deprecated feature: 8.5.5.19 or later

The Service Component Architecture (SCA) programming model and samples are deprecated, and will be removed in a future release. You cannot deploy new SCA business-level applications.

Update your applications to use different programming models. The programming models that you use vary depending on how you previously incorporated SCA in your application.

If you used SCA for binding, consolidate the ways in which your application is exposed to a few standards, such as Java API for RESTful Web Services (JAX-RS) or Java Message Service (JMS). For example, use JAX-RS for application bindings. To minimize the duplication of binding level implementation, structure your application to use shared code.

If you want to continue to use SCA as part of your long-term strategy, consider hosting your applications on IBM Business Process Manager.

How do I?...

Develop SCA composites

Select the implementation type for an SCA composite (Updated for Version 8.5)

Develop SCA services from existing WSDL files

Develop SCA services with existing Java code

Develop SCA service clients

Develop asynchronous SCA OASIS services and clients (New in Version 8.5)

Specify bindings for SCA components

SCA default binding
Web service binding (Version 8.5 adds OASIS support)
EJB binding in SCA OSOA applications
EJB binding in SCA OASIS applications (New in Version 8.5)
JMS binding (Version 8.5 adds OASIS support)
Atom binding
HTTP binding

Create wire format handlers (Version 8.5 adds OASIS support)

Wire OSOA and OASIS components together to enable SCA applications to interoperate (New in Version 8.5)

Use existing Java EE modules and components as SCA implementations

Use OSGi applications as SCA component implementations

Use Spring 2.5.5 containers in SCA applications

Configure work managers for SCA applications:

Configure work managers for one-way operations (Version 8.5 adds OASIS support)
Configure the default SCA work manager for the SCA layer

Use SDO 2.1.1 in SCA applications (Version 8.5 adds OASIS support)

Deploy SCA composites in business-level applications

Create SCA business-level applications using the administrative console

Create SCA business-level applications using wsadmin scripts

Administer deployed SCA composites

Update deployment settings for SCA composites

Start business-level applications

Stop business-level applications

Update SCA composite artifacts

View composite definitions

View SCA domain information

View JMS bindings on references and services of SCA composites

Export WSDL and XSD documents

Delete business-level applications

Update business-level applications

Configure security for SCA applications

Authorize access to resources:

Use SCA authorization and security identity policies (Version 8.5 adds OASIS support)
Use the SCA RequestContext.getSecuritySubject() API

Secure policy sets in web service bindings:

Configure a web service binding for SCA transport layer authentication (Version 8.5 adds OASIS support)
Configure a web service binding to use SSL (Version 8.5 adds OASIS support)
Configure a web service binding for LTPA authentication
Map abstract intents and manage policy sets (Version 8.5 adds OASIS support)

Conceptual overviews

SCA overview (Version 8.5 adds OASIS support)

SCA components

SCA composites

SCA application package deployment

Security configurations for SCA applications (Version 8.5 adds OASIS support)

SCA transaction intents

Samples

The product offers sample files that support SCA specifications. You can use these sample SCA files in business-level applications. The sample files are downloadable. SCA services are packaged in Java™ archive (JAR) files that you import as assets to the product repository and then add as composition units to business-level applications. Samples include detailed deployment instructions in a readme.html file.