SIBWebServices
Use command scripts to configure service integration bus-enabled web services.
To run these commands, use the AdminTask object of the wsadmin scripting client. Each command acts on multiple objects in one operation. The commands are provided to allow us to make the most commonly-required types of update in a consistent manner, where modifying the underlying objects directly would be error-prone.
(iSeries) (iSeries) The wsadmin scripting client is run from Qshell. (iSeries) See Configure Qshell to run WebSphere scripts .
Before and immediately after performing administrative commands that carry out publication to UDDI, save the configuration using either the AdminConfig.save() command or an equivalent command from within the administrative console. This ensures consistency between what is published to UDDI and what is recorded in the service integration bus configuration as having been published to UDDI.
Each command acts on multiple objects in one operation. The commands are provided to allow us to make the most commonly-required types of update in a consistent manner, where modifying the underlying objects directly would be error-prone.
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 at the wsadmin prompt:
- For overview help on a given command, enter at the wsadmin prompt:
print AdminTask.help('command_name')
The following administrative commands are available in this command group.
- createSIBWSOutboundService
- deleteSIBWSOutboundService
- addSIBWSOutboundPort
- removeSIBWSOutboundPort
- setDefaultSIBWSOutboundPort
- createSIBWSInboundService
- deleteSIBWSInboundService
- addSIBWSInboundPort
- removeSIBWSInboundPort
- refreshSIBWSOutboundServiceWSDL
- refreshSIBWSInboundServiceWSDL
- publishSIBWSInboundService
- unpublishSIBWSInboundService
- createSIBWSEndpointListener
- deleteSIBWSEndpointListener
- connectSIBWSEndpointListener
- disconnectSIBWSEndpointListener