Use the web services gateway to map an existing service - either an inbound or an outbound service - to a new web service that appears to be provided by the gateway. The gateway service acts as a proxy: your gateway service users need not know whether the underlying service is being provided internally or externally.
For a high-level task view of how you configure the web services gateway as part of an overall bus-enabled web services configuration, see Enabling web services through the service integration bus.
You configure each gateway service for a specific gateway instance, so you must create a gateway instance before you can configure any gateway services for it.
Decide which method to use to configure these resources. You can create a new gateway service by using the administrative console as described in this task, or by using the createWSGWGatewayService command.
The following figure shows how a gateway service looks, to client requestor applications, as if it is an inbound service. However, a gateway service is also mapped to a service destination on which a target service, either an internal service or an externally-provided web service, is available. A client request is received by an endpoint listener, then passed through an inbound port to the gateway service; the target service is either an internal service available directly at the destination or an external service available at the destination through one or more outbound ports; you can also apply JAX-RPC handlers and WS-Security bindings at the ports.
A gateway service is the web interface for an underlying service (the target service). The gateway service is made available at a different location to the target service, so you can replace or relocate the target service without changing the details for the associated gateway service. You can also have more than one target service (that is, more than one implementation of the same logical service) for each gateway service. For more information, see Target services and gateway services.
The target service can be either an externally-provided web service, or a service that is available internally to your organization, and it can be located at a destination that is on a different bus to the gateway service. If the target service is an internal service, the new gateway service is always created based upon the template WSDL for the service and the bus destination at which it is available. If it is an externally-provided web service, the new gateway service is usually created based upon the externally-published WSDL for the service, and at a new bus destination. However if the target is an externally-provided web service that is already available at a bus destination (for example because it has previously been configured as an outbound service) then you should provide the destination details as part of the new gateway service creation process. Otherwise the same external web service is made available at two different destinations.
When you create a new gateway service, you configure a single target service as a new web service that seems to be provided by the gateway. After you create your new gateway service, you can add more target services (that is, more implementations of the same logical service) by modifying the existing gateway service configuration.
To create a new gateway service by using the administrative console, complete the following steps. For more information about the new gateway service properties, see Gateway services settings.