Starting a scheduled task immediately

You can start a scheduled task at any time by running a script.

About this task

To start a scheduled task immediately, run the executeSchedulerTaskImmediate.jacl script by entering one or other of the following commands, depending on whether WSRR is deployed in a cluster configuration, or a stand-alone or federated node configuration. Run the commands from the <WAS_INSTALL_ROOT>\WSRR\admin\scripts_cell directory. You must enter a command all on one line.

Procedure

In a cluster configuration:

<WAS_INSTALL_ROOT>\bin\wsadmin -f executeSchedulerTaskImmediate.jacl
-cluster <CLUSTERNAME> -taskname <TASKNAME>

In a stand-alone or federated node configuration:
```
<WAS_INSTALL_ROOT>\bin\wsadmin -f executeSchedulerTaskImmediate.jacl
-cell <CELLNAME> -node <NODENAME> -server <SERVERNAME> -taskname <TASKNAME>
```
<TASKNAME> must be a valid task name that is configured in a valid scheduler properties file; it corresponds to the name attribute of the <scheduler-task> element in the scheduler configuration XML file.

Results

You are returned to the command prompt when the specified task has completed, or after a default wait time of 10 minutes, whichever occurs first. You can change the wait time by supplying an optional -wait parameter, followed by the wait time in seconds. If the task has completed, the following message is displayed:

ServiceRegistryRepository#executeSchedulerTaskImmediate task_name task completed.

If the task has not completed, the following message is displayed:

Task will continue to run on server, check server log files for more information.

To see the progress of the task, examine the SystemOut.log file on the WebSphere® Application Server. This file is located in your WebSphere Application Server profile logs directory; for example, C:\IBM\WebSphere\AppServer\profiles\default\logs\server1\SystemOut.log. The entries in the log are similar to the following:

[09/12/09 10:12:39:684 GMT] 00000029 scheduler I GSR5174I: Task: Promotion with task id: 52 started.
                  .
                  .
                  .
[09/12/09 10:12:40:043 GMT] 00000029 scheduler I GSR5175I: Task: Promotion with task id: 52 complete.

Note: If the task is a long running task, you might have to increase the wsadmin client SOAP time out value, to prevent the client timing out before the service discovery task completes. See Java™ Management Extensions connector properties in the WebSphere Application Server Information Center for details.

Example

c:\WebSphere\AppServer\bin\wsadmin -f executeSchedulerTaskImmediate.jacl
-cluster cluster1 -taskname Promotion