Making an externally-hosted web service available internally
Create an outbound service. An outbound service provides access, through one or more outbound ports, to a web service that is hosted externally. An outbound service can be used by any of your internal systems that can access the service integration bus on which it is hosted. To make an externally-hosted service available through a bus, you first associate it with a service destination, then you configure one or more port destinations (one for each type of binding, for example SOAP over HTTP or SOAP over JMS) through which service requests and responses are passed to the external service. You get the port definitions from the WSDL, but you can choose which ones you want to create.
Before you begin
This topic assumes that you have created and installed a Service Data Objects (SDO) repository (used for storing and serving WSDL definitions) on every server that is to play a service integration bus web services role.
To create an outbound service, you must know the location of the externally-published WSDL file that describes the service. This WSDL file is either available at a web address or through a UDDI registry.
If the WSDL file for your outbound service is stored in a UDDI registry, you associate the outbound service with a UDDI reference to the registry. You select the UDDI reference from a drop-down list, so you must configure the UDDI reference before you configure a new outbound service that uses it.
About this task
In the following figure, each message is passed from the outbound service to the target service through an outbound port. A separate outbound port is created for each available binding. JAX-RPC handlers and WS-Security settings can be applied at the ports.
Requests and responses to an outbound service are sent across any transport binding (for example SOAP over HTTP, SOAP over JMS, EJB binding) that is available to both the target service and the service integration bus. Each available binding type is represented by an outbound port configured at a port destination. For more information, see Outbound ports and port destinations.
- You can associate JAX-RPC handler lists with ports, so that the handlers can monitor activity at the port, and take appropriate action depending upon the sender and content of each message that passes through the port.
- You can set the level of security to be applied to messages (the WS-Security binding). The security level can be set independently for request and response messages.
Procedure
Results
What to do next
Because the service is hosted externally, you might also need to enable proxy server authentication for each port to get permission to access the Internet.
If you want to secure your new outbound service, or apply any JAX-RPC handler lists to the ports, or enable proxy server authentication for any of the ports, use the administrative console to modify your outbound service configuration.