If --wait-for-cc 0, the command fails when Command Central is not online.

Both {--wait | -w} and {--wait-for-cc | -t} options use the value of the CC_WAIT environment variable. Use {--wait-for-cc | -t} in conjunction with {--wait | -w} if you specify a value for {--wait-for-cc | -t} higher than 120 seconds. In this case, specify a value for {--wait | -w} higher than the value of {--wait-for-cc | -t}.

When you monitor a long-running job, you can use the {--wait-for-cc | -t} and {--sync-job | -j} options to continue monitoring the job even after Command Central is restarted. See the example in sync-job.

This option is most helpful with commands that trigger long-running jobs, for example the apply composite templates command. However, you can use the option with any command. In the following example, the command attempts to retrieve the list of products installed in the local installation and if Command Central does not respond, the command checks the status of Command Central and waits for Command Central to be online for 60 seconds:

You can also set waitForCC as a parameter of the cc tasks included in an Ant script that executes CLI commands. See Parameters to Use with the cc Task.

To wait for 60 seconds for Command Central to come online: