Idle Event Handler: Overview

Running a significant number of LID-based programs concurrently might cause the Lawson Security Server to stop running. A large number (1200 to 1500) of concurrent LID users would have to be using the system in order for this situation to occur. Therefore, the majority of Lawson customers will not see this problem and will not need to take the corrective action described here.

To address this problem, Lawson has developed two methods for handling security server events: a Dedicated Event Handler and an Idle Event Handler.

The dedicated handler checks for events from all processes. By default, only this handler is configured so events from all processes are constantly monitored.

The idle event handler is used for events that need attention only initially and are checked less frequently.

If you decide to configure the idle event handler, some processes will be checked by the idle event handler and others--those most likely to need constant attention--will be handled by the dedicated handler. When you configure the event handler, you do not specify which processes should be handled by it. This logic has been built into the handler.