To run the command, use the AdminTask object of the wsadmin scripting client.
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 adds the configuration for an OutboundPort to an OutboundService.
If an OutboundPort for the OutboundService by the given name already exists, or the name of the port does not correspond to a port in the service element of the service provider WSDL (as defined on the OutboundService) the command fails.
The command creates the port destination. If a destination with the specified or default name 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, then the command fails.
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. In addition, if the proxy server requires authentication, then the user ID and password can be set as parameters on the command.
If this is the first port for the OutboundService, then it is set as the default, and the service destination default routing is set to point to the port destination.
set outPort [$AdminTask addSIBWSOutboundPort $outService {-name "MyServiceSoap" -node "MyNode" -server "server1"}]