Clearing all scheduled tasks 

Use administrative commands to clear the scheduler of all tasks.


Before you begin


Only perform this procedure if you need to recreate all scheduler tasks. If you see an exception relating to LTPA tokens in the system log before each task runs, then you should perform this procedure to clear the scheduled tasks. This might be required, for example, after a new LTPA token is imported into IBM Connections or imported from a server in another cell as the result of enabling single sign-on, when reverting the databases from a production environment to a staging environment, or after generating new LTPA keys due to a corporate security policy or LTPA timeout.


About this task


Do not run the command documented here unless the clusters hosting the applications and the applications themselves are running. The administrative command used in this procedure interacts with the scheduler MBeans for each application to enumerate the scheduled tasks, and clear the tasks. The WAS scheduler is not application-aware, so as long as the clusters hosting an application are running, the scheduler will attempt to run the scheduled tasks for that application, even if the application itself is stopped. Each attempt to run a scheduled task for a stopped application results in an error message to the log.

If you disable or stop an application, be sure to also cancel any scheduled tasks associated with it.


Procedure

  1. Start the wsadmin client by completing the following steps:

    1. From the dmgr host, go to...:

        app_server_root>\profiles\<dm_profile_root>\bin

        where <app_server_root> is the WAS installation directory and <dm_profile_root> is the dmgr profile directory, typically dmgr01. For example, on Windows:

        C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

        Attention: You must run the following command to start the wsadmin client from this specific directory because the Jython files for the product are stored here. If you try to start the client from a different directory, then the execfile() command that you subsequently call to initialize the administration environment for an IBM Connections component does not work correctly.

    2. Enter the following command to start the wsadmin client:

      • AIX or Linux:

          ./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>

      • Microsoft Windows:

          wsadmin -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>

        where:

        • <admin_user_id> is the user name of a person in the Administrator role on the IBM WAS.

        • <admin_password> is the password of the WAS administrator.

        • <SOAP_CONNECTOR_ADDRESS Port> is the SOAP port for the WAS. The default value of the SOAP port is 8879. If you are using the default port value, you do not need to specify this parameter. If you are not using the default and you do not know the port number, you can look up its value in the WAS Integrated Solution Console. To look up the SOAP port number, perform the following steps:

          1. Open the WAS Integrated Solution Console for the deployment manager, and then select System Administration -> dmgr.

          2. In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number.

        For example:

        • AIX or Linux:

            ./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879

        • Microsoft Windows:

            wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879

  2. Use the wsadmin client to access the IBM Connections configuration files.

    1. Enter the following command to access the IBM Connections configuration file: execfile("connectionsConfig.py")

        If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.

  3. Make sure that all clusters and applications are started and that no scheduled tasks are currently running by retrieving a list of tasks. Use the following command:

      Scheduler.listAllTasks()

      From the returned list, determine what to do next using these guidelines:

      Wsadmin client message

        Recommended action

      Status = running

        Wait until the task is completed.

      Skipping <app_name> application

        This means that the cluster hosting the application is not started. Restart the cluster.

      Here is a sample of the type of response you may receive when listing scheduled tasks:

      wsadmin>Scheduler.listAllTasks()
      Task Name | Status | Next Fire Time | Interval Communities tasks LifecycleRetryQueuedEvents SCHEDULED Mon Feb 07 09:01:00 EST 2011 0 1 0-23/3 ? * * EventLogCleanup SCHEDULED Mon Feb 07 09:30:00 EST 2011 0 30 0-23/3 ? * * Activities tasks TrashAutoPurgeJob SCHEDULED Sun Feb 13 02:00:00 EST 2011 0 0 2 ? * SUN ActivityAutoCompleteJob SCHEDULED Sat Feb 12 23:00:00 EST 2011 0 0 23 ? * SAT DatabaseRuntimeStats SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 * * * ? 30MinStats SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0/30 * * * ? DailyStats SCHEDULED Mon Feb 07 11:00:00 EST 2011 0 0 11 * * ? Forums tasks TrashAutoPurgeJob SCHEDULED Sun Feb 13 02:00:00 EST 2011 0 0 2 ? * SUN Profiles tasks Profiles Worker Process SCHEDULED Mon Feb 07 08:36:46 EST 2011 20seconds Files tasks SearchClearDeletionHistory SCHEDULED Mon Feb 07 16:00:00 EST 2011 0 0 0,8,16 * * ? MetricsDailyCollection SCHEDULED Tue Feb 08 00:00:00 EST 2011 0 0 0 * * ? TagUpdateFrequency SCHEDULED Mon Feb 07 10:00:00 EST 2011 0 0 0-22/2 * * ? DirectoryGroupSynch SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 * * * ? FileActuallyDelete SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 0-23/3 * * ?|0 30 1-23/3 * * ? Wikis tasks SearchClearDeletionHistory SCHEDULED Mon Feb 07 16:00:00 EST 2011 0 0 0,8,16 * * ? MetricsDailyCollection SCHEDULED Tue Feb 08 00:00:00 EST 2011 0 0 0 * * ? TagUpdateFrequency SCHEDULED Mon Feb 07 10:00:00 EST 2011 0 0 0-22/2 * * ? DirectoryGroupSynch SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 * * * ? FileActuallyDelete SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 0-23/3 * * ?|0 30 1-23/3 * * ? News tasks NewsDataCleanup SCHEDULED Mon Feb 07 23:00:00 EST 2011 0 0 23 ? * * NewsCheckUpdatedPersons SCHEDULED Mon Feb 07 08:50:00 EST 2011 0 50 * * * ? EmailDigestDelivery SCHEDULED Mon Feb 07 09:00:00 EST 2011 0 0 * ? * * MetricsCollector SCHEDULED Tue Feb 08 02:00:00 EST 2011 0 0 2 ? * * PersonSpreadTranche SCHEDULED Tue Mar 01 22:00:00 EST 2011 0 0 22 1 * ? Search tasks 20min-file-retrieval-task SCHEDULED Mon Feb 07 08:41:00 EST 2011 0 1/20 0,2-23 * * ? 15min-search-indexing-task SCHEDULED Mon Feb 07 08:46:00 EST 2011 0 1/15 0,2-23 * * ? nightly-optimize-task SCHEDULED Tue Feb 08 01:30:00 EST 2011 0 30 1 * * ? nightly-sand-task SCHEDULED Tue Feb 08 01:00:00 EST 2011 0 0 1 * * ? wsadmin>

  4. After performing any suggested actions, run the following command to clear the scheduled tasks:

      Scheduler.clearAllTasks()

  5. Restart the cluster servers to force the scheduled tasks to be recreated.

    1. From the WAS admin console, expand Servers, click Server Types, and then click WebSphere application servers.

    2. Select the check box for one server per cluster, and then click Restart.


Parent topic

Scheduling tasks


April 28, 2011 10:54:49 AM by Klaus Bild  
   

 

Apr 28, 2011 10:54:49 AM Klaus Bild   1

});