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 SIBWebServices
wsadmin> $AdminTask help command_name
For additional details of the command properties, see the related reference topic.
This command creates a new InboundService object that represents a protocol attachment to be used by service requesters. When you run this command you identify a single service element within a template WSDL document, and an existing service destination.
If the WSDL is to be retrieved through a proxy server, the server on which the command is running must have the system properties that identify the proxy server set correctly. If the proxy server requires authentication, then the user ID and password can be set as parameters on the command.
After you have run this command, you can use other commands to further configure the service. For example, you can add an inbound port.
This is either a Web address or the service-specific part of a UDDI service key. If you specify a UDDI reference, the WSDL location is assumed to be a UDDI service key.
uddi:blade108node01cell:blade108node01:server1:default:6e3d106e-5394-44e3-be17-aca728ac1791The service-specific part of this key is the final part: 6e3d106e-5394-44e3-be17-aca728ac1791.
set inService [$AdminTask createSIBWSInboundService $bus {-name "MyService" -destination $destName -wsdlLocation "http://myserver.com/MyService.wsdl"}]