createSIBWSOutboundService command
Use the createSIBWSOutboundService command to create a new service integration bus-enabled web services outbound service configuration.
We can create a new outbound service configuration by as described in this topic, or using the administrative console as described in Making an externally-hosted web service available internally.
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 Configure Qshell to run WebSphere scripts .
Command-line help is provided for service integration bus commands:
- For a list of the available bus-enabled web services
commands, plus a brief description of each command, enter the following command at the wsadmin prompt:
print AdminTask.help('SIBWebServices')
- For overview help on a given command, enter the following command at the wsadmin prompt:
print AdminTask.help('command_name')
After using the command, save the changes to the master configuration using the following command:
AdminConfig.save()
Purpose
This command creates a new OutboundService object, that represents a protocol attachment to a service provider. When you run this command you must identify a single service element within a WSDL document.
Target object
ObjectName of the messaging bus within which the service is created.
If the WSDL is to be retrieved through a proxy, the server on which the command is running must have the system properties that identify the proxy server set correctly. If the proxy requires authentication, then the user ID and password can be set as parameters on the command.
After we have run this command, you use other commands to further configure the service. For example, to add an outbound port.
Required parameters
- -name
- The outbound service name.
- -wsdlLocation
- The location of the service provider WSDL file.
This is either a web address or the service-specific part of a UDDI service key. If we specify a UDDI reference, the WSDL location is assumed to be a UDDI service key.
Here is an example of a full UDDI service key:
- uddi:blade108node01cell:blade108node01:server1:default:6e3d106e-5394-44e3-be17-aca728ac1791
The service-specific part of this key is the final part:
- 6e3d106e-5394-44e3-be17-aca728ac1791
Conditional parameters
- -wsdlServiceName
- The name of the service within the WSDL. Only required if the service provider WSDL contains more than one service, or the WSDL is located through a UDDI registry.
- -wsdlServiceNamespace
- The namespace of the service within the WSDL. Only required if the service provider WSDL contains more than one service, or the WSDL is located through a UDDI registry, or the service is not in the default namespace for the WSDL document.
Optional parameters
- -uddiReference
- If we specified a UDDI service key as the WSDL location, supply the UDDI reference for the target UDDI registry.
- -destination
- The name of the service destination.
The command creates the service destination. If a destination with the specified or default name already exists, the command fails.
- -userId
- The user ID that you use to retrieve the WSDL.
- -password
- The password that you use to retrieve the WSDL.
Example
- Jython:
- outService = AdminTask.createSIBWSOutboundService(bus, ["-name", "MyService", "-wsdlLocation", "http://myserver.com/MyService.wsdl"])
- Jacl:
set outService [$AdminTask createSIBWSOutboundService $bus {-name "MyService" -wsdlLocation "http://myserver.com/MyService.wsdl"}]
Related information:
Reference topic