You can configure SCA composites that are accessed by Hypertext
Transfer Protocol (HTTP) for custom service endpoints using Web services
bindings.
Before you begin
Before you begin this task, install your Service Component
Architecture (SCA) application.
About this task
When a service is exposed over the SCA Web service binding,
the service endpoint is specific to the server in which the service
is hosted. Clients use this endpoint URI to access the service.
In some cases, you may want clients to indirectly reference the service
by using a proxy server as the service endpoint. For example, a proxy
server is required to implement clustered Web service binding endpoints.
To enable clients to use a proxied endpoints, there are two ways
to do this:
- If your endpoints are specified in the SCA contributions composite
definition or WSDL document location attribute, you must specify the
proxy server endpoint instead of the WebSphere® server specific endpoint.
- If your client resolves the endpoint by using the <reference
target=””> attribute in your client composite definition,
use the administrative console to configure the custom endpoints for
SCA composites that are accessed by the Hypertext Transfer Protocol
(HTTP) protocol. This approach is the most flexible for SCA clients
within the same domain as their service providers. When using <reference
target=””> attribute, SCA references can resolve the service
endpoints without the client specifying endpoints in the composite
definition or WSDL document.
Procedure
- Open the administrative console.
- In the navigation pane, expand .
- Select the HTTP endpoint URL prefix. When entering
custom endpoints you must specify one and only one endpoint URL prefix
each for the HTTP and HTTPS protocols.
Results
You have configured Web services bindings custom endpoints.
What to do next
You can configure the bindings to do transport layer authentication.