With the handler control record, you can influence the behavior of the handler execution. Since handler processes are triggered on a frequent basis, and each process is relatively time-consuming, it is important that you set the right value in this handler control record to optimize the system performance.
1. Start transaction merep_pd.
2. Choose the Runtime Component tab page.
3. Choose Display <-> Change.
4. Under Handler, select Enabled.
To prevent clients from synchronizing you can deselect Enabled. When the handler is disabled, all incoming messages from the client have the I-waiting status. After enabling the handler again, messages with status I-waiting will be processed when one of the following occurs:
? The merep_retry_BP job runs (either scheduled or started manually).
? The administrator triggers the handler manually for all mobile IDs using transaction merep_mon.
5. Set Log Level to 2.
6. Set Max.Number Handlers to 5.
7. Deselect Loopback.
8. Deselect Batch user may differ from logon user.
When you schedule a handler background job, you must set this indicator. If the indicator is not set, the handler prevents the background job from being executed.
The scheduled handler job selects the data packages of the relevant user on the mobile device or in the back end, but edits them with the user name that the job scheduled with transaction SE36. The authorization checks also refer to the batch user.
9. Choose Save.