WAS v8.5 > Develop applications > Develop SCA composites > Develop SCA applications
Develop asynchronous SCA services and clients
We can create applications that use Service Component Architecture (SCA) OASIS specifications to asynchronously run request-response services.
New feature:
SCA OASIS specifications support the asynchronous running of request-response services. This enables a client thread to continue doing other work while the service runs. We can use SCA OASIS annotations and APIs in Java interfaces to enable asynchronization in services.
To learn about asynchronous invocations of SCA services, see the SCA OASIS Java Common Annotations and APIs specification. For a list of common annotations in SCA OASIS specifications, see http://docs.oasis-open.org/opencsa/sca-j/javadoc/index.html. An SCA client and an SCA service have independent capabilities for asynchronous invocation which can be intermixed. This means that a client can synchronously run an asynchronous service or asynchronously run a synchronous service.
Typically, a client asynchronously runs an asynchronous service.
When developing an asynchronous service and client, consider the following:
- Use the SCA OASIS annotation @AsyncInvocation in the Java service interface to enable asynchronization.
- Use the SCA OASIS annotation @AsyncFault in the Java service interface for exception errors.
- In the composite definition, use the implementation.java type for the SCA component.
- Asynchronous interfaces are supported by binding.sca only.
Topics in the procedure cover developing SCA services and clients that run asynchronously.
Deploy the SCA composites in a business-level application.
For SCA OASIS applications, an sca-contribution.xml file is required for deployable composites in the META-INF/ directory, and not in a subdirectory.
Subtopics
- Develop asynchronous SCA services
We can create services that use SCA OASIS specifications to asynchronously run request-response services. - Develop asynchronous SCA clients
We can create clients that use SCA OASIS specifications to run asynchronously. - Develop asynchronous SCA services
We can create services that use Service Component Architecture (SCA) OASIS specifications to asynchronously run request-response services. - Develop asynchronous SCA clients
We can create clients that use Service Component Architecture (SCA) OASIS specifications to run asynchronously.
Related concepts:
Unsupported SCA specification sections
Related
Configure the SCA default binding
Create SCA business-level applications
Reference:
API documentation