Handler Configuration

Handlers published to the CIC server from Interaction Designer appear in the comprehensive list of available handlers under Handler Names. To move a handler from being available (present) on the server to being activated to run on the server, see the Handlers and Monitor Handlers property pages in the Server Configuration dialog box.

File Name

Handlers published to the default location are stored in Java class files. In general, you should never need to change the handler's Java class file name unless instructed by qualified technical support personnel. Each time a handler is published, Interaction Designer appends a new date code at the end of each handler's Java class file name (for example, DialPlan0_857349795.class). Do not change these names.

Configuring Handlers

It is possible you will never have to change the following default settings for Handlers. If you get any of the messages stated below, we suggest you contact your PureConnect Customer Care representative before changing any of the values.

Maximum Number of Concurrent Handlers

This number determines the maximum number of handlers that can run concurrently. The default, 0, means there is no limit to the number of concurrent Handlers.

If there is a value in this box, and a message appears in the event log stating the Handler has reached its concurrent limit and additional requests to run this handler will be queued up, you can increase the limit. Again, we suggest you contact PureConnect Customer Care before changing this value.

Note: This limit applies only to first-level handler calls. Handlers called from within another handler via the "Subroutine" initiator are not subject to concurrent handler limits. This is a safety mechanism to ensure that ongoing handler operations do not stall when calling a subroutine due to handler concurrency limits.

Maximum Number of Handlers Queued

When the maximum number of concurrent Handlers is reached, this field indicates how many handler requests can be queued until a slot becomes available.

If the Maximum Number of Concurrent Handlers is set to the default, the Maximum Number of Handlers Queued field is gray, and not available. When it is not available, a large allowable maximum value has been pre-set.

This box becomes available when you put a value in the Maximum Number of Concurrent Handlers box. If you get a message in the event log stating the Handler has exceeded its maximum queue limit and request to run this handler will be discarded, you can increase the limit in this box. Type a number in the box. To specify no limit, enter -1 or 0, or click No Limit. Again, contact Customer Support before changing this value.

Handler Priority

You can select Low, Normal, or High. The default setting is Normal.

Step Limit

You might need to increase the step limit if you get a message in the error log stating the Handler has exceeded its step limit. If the Handler should not have exceeded this step limit, there may be an infinite loop in the Handler. The default, 0, has a value of 10,000. If you click No Limit, a -1 appears in the box. Again, we suggest you contact Customer Support before changing this value.