You can set the Web services gateway to act purely as a proxy for your service, then use JAX-RPC handler lists to set the endpoints for incoming request messages for the service.
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 service integration technologies.
You configure each proxy service for a specific gateway instance, so you must create the gateway instance before you can configure any proxy services for it.
You can create a new proxy service through the administrative console as described in this task, or you can create a new proxy service through the command line.
When you create a new proxy service configuration, the gateway takes no action with regard to that service other than to invoke it. When you configure a proxy service, you also configure a JAX-RPC handler list that uses the javax.xml.rpc.service.endpoint.address to set the target endpoint for the service. You then attach the handler list to the inbound port for the proxy service.
A proxy service configuration has no actual target services and therefore no WSDL that the gateway can use to configure the service invocation. A generic proxy WSDL file is used to configure the basic parameters for the invocation call (for example which binding to use), but you can override the default by supplying your own equivalent generic proxy WSDL file. If the JAX-RPC handler list is not deployed, then the gateway attempts to send all requests to the fake Web address specified in the <soap:target address> tag in the proxy WSDL file.
For more detailed information, see JAX-RPC handlers and proxy operation.
To create a new proxy service configuration through the administrative console, complete the following steps:
http://host_name:port_number/wsgwsoaphttp1/soaphttpengine/your_bus/ProxyService/ProxyServiceInboundPortthen requesting clients indicate that they are sending a one-way request by using the following URL:
http://host_name:port_number/wsgwsoaphttp1/soaphttpengine/your_bus/ProxyService/ProxyServiceInboundPort?operationMode=oneway
jms:/queue?destination=jndi_queue&connectionFactory=jndi_factory&targetService=your_bus/ProxyService/ProxyServiceInboundPortthen requesting clients indicate that they are sending a one-way request by using the following URL:
jms:/queue?destination=jndi_queue&connectionFactory=jndi_factory&targetService=your_bus/ProxyService/ProxyServiceInboundPort&operationMode=oneway