After you develop a Service Component Architecture (SCA)
component, you can use bindings to specify how SCA services and references
enable the component to communicate with other components and applications.
Services and references enable a component to communicate with
other components and applications. By design, however, SCA services
and references say nothing about how this communication occurs. Bindings
are used to determine how a component communicates. 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 that is used to call a service. Depending on what the SCA
component is communicating with, a component might or might not have
explicitly specified bindings.
All binding types contain a set of configurable attributes that
you can define to provide the runtime environment with additional
information regarding component communication. For example, the following
optionally defined name and identity attributes are common to all
binding types:
- Name
- Allows distinction between multiple binding elements on a single
service or reference.
- Uri
- Defines for a binding of a reference the target URI of the reference
(either the component or service for a wire to an endpoint within
the SCA domain or the accessible address of some endpoint outside
the SCA domain). For a binding of a service the URI attribute defines
the URI relative to the component that contributes the service to
the SCA domain. For details regarding specific URI formats, see CICS processing of services. CICS does not support
the Uri attribute for intra-composite binding. Use
instead the promote and target attributes
of the service or reference.
Note: Intents and policy sets are not supported in CICS.