Set the gateway to act purely as a proxy for your service, and use JAX-RPC handlers to set the endpoints for incoming request messages for the service.
To run the command, use the AdminTask object of the wsadmin scripting client.
The wsadmin scripting client is run from Qshell. For more information, see the topic "Configure Qshell to run WebSphere® Application Server scripts".
This command is only valid when used with WebSphere Application Server Version 6 and later application servers. Do not use it with earlier versions.
Command-line help is provided for service integration bus commands:
wsadmin> $AdminTask help WSGateway
wsadmin> $AdminTask help command_name
For additional details of the command properties, see the related reference topic.
This command creates a new ProxyService object with an associated InboundService object, and a TargetService object with an associated OutboundService object.
You then use a service integration technologies command to add any InboundPort objects that are associated with the InboundService object. For more information, see the worked example at the end of this topic.
The command creates the proxy request destination and corresponding reply destination. The proxy request destination is configured to update the reply path to add the proxy reply destination. If a destination with the specified or default names already exists, the command fails.
If a gateway service or proxy service with the same name already exists, the command fails.
If you specify the name of the proxy request destination, the proxy service destination and port destinations are created with names derived from the proxy request destination name. Otherwise, the proxy service destination and port destinations are created with names derived from the proxy service name. The proxy service destination name is created by adding "ProxyService" to the proxy request destination or proxy service name. Each proxy port destination is then named after the proxy service destination, followed by a colon (":"), followed by the port name, followed by "Port". If a destination with any of these names already exists, the command fails.
Either specify the node and server, or specify the cluster. If there is no messaging engine defined for the specified node and server or cluster, the command fails.
The command creates an OutboundService object, with the same name as the proxy service. This new outbound service uses the created destinations, the supplied localization, and either the default proxy WSDL location for the gateway instance or (if specified) the location of the proxy WSDL file. The new outbound service is associated with the ProxyService object.
The proxy WSDL must have only a single service element. If there are multiple ports within the single service element, an outbound port object is created for each one.
The proxy WSDL should never come from UDDI, so only a Web address is supported for the default and overridden proxy WSDL location.
The command uses the proxy destination to create an InboundService object with the same name as the proxy service, and uses the default or specified proxy WSDL location as the template WSDL location.
set proxyService [$AdminTask createWSGWProxyService $wsgw {-name "MyProxyService" -node "MyNode" -server "server1"}]
set proxyService [$AdminTask createWSGWProxyService $wsgw {-name "ProxyService" -node "MyNode" -server "server1"}]
set inServiceName [$AdminConfig showAttribute $proxyService "inboundServiceName"]
set inService [$AdminConfig getid /SIBus:$busName/SIBWSInboundService:$inServiceName/]
set inPort [$AdminTask addSIBWSInboundPort $inPort {-name "SOAPHTTPPort" -endpointListener "soaphttp1" -node "MyNode" -server "server1"}]
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