+

Search Tips   |   Advanced Search

Specify bindings in an SCA environment

After you develop an Service Component Architecture (SCA) component, we can use bindings to specify how SCA services and references enable the component to communicate with other applications.

Services and references enable a component to communicate with other applications. By design, however, the SCA services and references say nothing about how this communication occurs. Bindings are used to determine how a component communicates with the world outside its domain. SCA services use bindings to describe the access mechanism that clients must use to call the service. SCA references use bindings to describe the access mechanism used to call a service. Depending on what the SCA component is communicating with, a component might or might not have explicitly specified bindings.

The product supports the following binding types:

  1. Select a binding type to use for an SCA component.

    • Use the SCA default binding when to invoke an SCA service from an SCA client.

    • Use the SCA web services binding to specify that an SCA service is made available as a web service or an SCA reference can invoke a web service.

    • Use the SCA EJB binding to integrate SCA with services based on session beans.

    • Use the SCA JMS binding to compose and assemble SCA services from new and existing services.

    • Use the Atom binding to expose collections of data as an Atom feed or to reference existing external Atom feeds.

    • Use the HTTP binding with a wire format of JSON-RPC to expose services to remote web browser clients.

  2. Configure the selected binding and use it in an SCA component or application.


Results

SCA components can use the configured bindings to communicate with other SCA services and references.


What to do next

Deploy the SCA component or application.


Subtopics


Related tasks

  • Configure the SCA default binding
  • Use the SCA default binding to find and locate SCA services
  • Configure the SCA web service binding
  • Configure EJB bindings in SCA applications
  • Use EJB bindings in SCA applications in a cluster environment
  • Configure the SCA JMS binding
  • Use Atom bindings in SCA applications
  • Use HTTP bindings in SCA applications
  • Develop SCA services from existing WSDL files
  • Develop SCA services with existing Java code
  • Develop SCA service clients
  • Deploy and administering business-level applications
  • Manage policy sets using the administrative console

  • Service Component Architecture specifications and APIs