During application assembly or deployment, a reference (a service dependency) is typically resolved to an actual deployed SCA service.
Use this option when the target service is another SCA service that is in the same domain as the client component, or rather, the component with the reference.
When you have configured the SCA default binding for your SCA service, the @target attribute is typically used to resolve an SCA client reference to the SCA component service. You can also use the @target attribute to resolve an SCA reference when using the SCA non-default bindings. Using this mechanism, the client does not need to know the endpoint of a service that is calculated during run time in order to resolve to it. Whereas a binding-specific endpoint can contain server-specific information such as an Hypertext Transfer Protocol (HTTP) port for a Web service binding, the @target attribute does not require an update when the client-service pair is deployed to a new server with different ports. You can also redeploy a target service within the domain from a single server to a cluster without requiring a change to the reference-side composite definition. If you use this approach, remember that you must use bindings of the same type, meaning that the reference must share a common binding with the service it is targeting.
You must resolve an SCA reference using a binding-specific endpoint if you invoke non-SCA services over non-default bindings or if you have compatible SCA services that are hosted in another domain.
In general, obtain the binding-specific endpoint from the service provider.
If your target service is another SCA service, see the documentation for configuring the particular SCA binding to learn more about which binding-specific endpoint is used for a given service deployment over a particular binding.
You have identified your SCA client's reference to a target service that it will consume.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |