[AIX Solaris HP-UX Linux Windows][z/OS]

Developing asynchronous SCA services and clients

You can create applications that use Service Component Architecture (SCA) OASIS specifications to asynchronously run request-response services.

Before you begin

[AIX Solaris HP-UX Linux Windows][z/OS] New feature 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. You can use SCA OASIS annotations and APIs in Java interfaces to enable asynchronization in services.newfeat

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.

About this task

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:

Topics in the procedure cover developing SCA services and clients that run asynchronously.

Procedure

  1. Develop an asynchronous SCA service.
  2. Develop an asynchronous SCA client.

What to do next

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.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=tsca_oasis_asynch
File name: tsca_oasis_asynch.html