Show TOC

Procedure documentationMonitoring Event-Controlled Processing Locate this document in the navigation structure


Proper functioning of the Event Handler and the Task Manager are prerequisites for problem-free and dependable message transmission and transaction processing of the SOAP runtime.

Both the Task Watcher and the Event Handler work in the background and are started from AUTOABAP. AUTOABAP is a background process that is automatically started up every 5 minutes.


The user can avail of appropriate Authorizations.


Task Watcher

The Task Watcher process supports dependable transaction processing.

Call transaction TWADMIN in order to check how the Task Watcher is running. The system issues an appropriate message (TW is active) in the Monitor Status area.

If the status TW is not active appears and this does not change in the next few minutes, it is likely that the service destination (refer to Creating a Service Destination) is not configured correctly. Check this using the report SRT_ADMIN_CHECK. The function of the Task Watcher depends on the existence and correct functioning of the service destination in client 000.

Choose the Start Watcher pushbutton if the Task Watcher does not run. Choose the Refresh pushbutton to display the status change. If you cannot get the Task Watcher to run, you will find more information in the section Troubleshooting in the Web Service Runtime..

  • Open Active Tasks Tab

    List of all LUWs (refer to Database LUW) that are registered in the transaction handler of the SOAP runtime. The open active tasks are queried by the Task Watcher in order to determine whether the LUW is still active. You can set the frequency for this query in the field Period in Seconds. During the query, the system checks the existence of a database lock. In addition to the database changes made within it, a database LUW also consists of database locks. The database system uses locks to ensure that two or more users cannot change the same data simultaneously, since this could lead to inconsistent data being written to the database. The lifespan of database locks is limited to the lifespan of a database LUW.

    If the values in the Task ID column are identical, the displayed objects belong to the same LUW.

    In the T column, you can have the following values:


    Active task: waiting for COMMIT or ROLLBACK, and - in the case of an unintentional ROLLBACKS - waiting for a callback in th background.


    Waiting for COMMIT or ROLLBACK


    CALLBACK is currently being executed If this status does not change, then this is an error (for example, a syntax error in a program). Select the corresponding row and choose Set Status (below right) to start the process again.

    • Open Inactive Tasks Tab

      List of all LUWs that were terminated by a ROLLBACK WORK or canceled during the execution of an LUW due to a short dump or server shutdown. A callback is executed by the Task Handler for those tasks contained in the list.

    Event Handler

    Proper functioning of the event handler is a prerequisite for dependable messaging.

    The WS-RM Event Handler is started by the AUTOABAP process. This process produces child processes when a WSRM event is performed. The standard value is 3. The number of these processes can be configured using the RSEHCONFIG report. In the Maximum Allowed Processes field, enter a 0 and choose F8 to stop the Event Handler - for example, for troubleshooting. Restart the Event Handler when troubleshooting is finished. For more information, refer to the section Troubleshooting in the Web Service Runtime.