Using 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 you to make the most commonly-required types of update in a consistent manner, where modifying the underlying objects directly would be error-prone.
The wsadmin scripting client is run from
Qshell. For more information, see the topic "Configure Qshell to
run WebSphere Application Server scripts".
These commands are only valid when used with WebSphere Application Server Version 6 and later application servers. Do not use them with earlier versions.
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 actually 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 you 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:
wsadmin> $AdminTask help SIBWebServices
wsadmin> $AdminTask help command_name
You can use administrative commands to complete any of the following tasks.: