You can run many
tcsadmin commands against a single tc
Runtime instance or a group of tc Runtime instances. The following
guidelines describe the behavior of commands if you run then against a
group and a failure occurs:
Group application deployment and configuration commands, such as
sequentially and synchronously. For example, if you use
tcsadmin to deploy a Web application to a group, the
script deploys the application to one of the tc Runtime instances in
the group, waits for the deployment to succeed or fail, then deploys
the application to another tc Runtime instance in the group, and so on
until the script has attempted to deploy the application to all
members of the group. You cannot specify the order of execution for
the tc Runtime instances in a group.
If the script encounters a failure when deploying to one tc Runtime instance in the group, it reports the failure but then continues to deploy the application to any remaining tc Runtime instances in the group.
Group control commands, such as
start, also happen
sequentially and synchronously, and you cannot specify the order in
which the tc Runtime instances in the group start, stop, and restart.
However, if the script encounters a failure when starting, stopping,
and restarting a tc Runtime instance, the script stops all execution
and does not continue to execute the command
against any remaining tc Runtime instances. Server control actions
that have already executed are not rolled
For example, assume a tc Runtime group includes five tc Runtime
instances that are all currently stopped and you execute the
start command against the group. Assume that two tc
Runtime instances started successfully, but then the third encountered
a problem and returned a failure. The script stops all execution. At
that point, the first two tc Runtime instances are still started, and
the remaining three are still stopped.