Managing requestor pooling for a mobile app

Pega Platform provides a Service Package specifically for offline data synchronization. The Service Package contains settings that define the requestor pool. The requestor pool is a set of requestors reserved for use by the services in the Service Package. Requestor pooling often improves the performance of a service. Requestor pooling enables requestor reuse, shares allocated resources, and eliminates server wait time for requestor creation.

Requestors associated with a pool belong in one of two categories:

• Idle requestors are currently in the pool, waiting for a service request.
• Active requestors are currently out of the pool, managing service requests.

The Service Package contains pooling settings that let you adjust the maximum number of idle requestors, the maximum number of active requestors, and the maximum time the system waits for an idle requestor.

Use the Settings tab of the Offline Configuration landing page in Dev Studio to quickly edit the pooling settings. Updating the settings updates the values on the Pooling tab of the Service Package.

Alternatively, you can directly edit the service package record and connection settings in the Service Package. On the Settings tab of the Offline Configuration landing page, click the OfflineServicePackage link to open the Service Package record.

Before you update the settings, determine the number of offline users you expect to be using your mobile app. In a small organization, the number can be relatively small. However, if the app is widely distributed among many thousands of users, you will likely need to increase the requestor numbers accordingly.

The Maximum idle requestors setting defines the size of the pool. To allow an unlimited number of idle requestors by keeping them until they time out, set Maximum idle requestors to -1.

The Maximum active requestors setting defines the maximum number of concurrent requestors to allocate to the service. To allow an unlimited number of active requestors, and eliminate wait time, set Maximum active requestors value to -1. If requestor pooling is disabled, set Maximum active requestors to 1.

The Maximum wait (in seconds) specifies how long the system waits for a requestor to return to the pool when a service request arrives and the number of active requestors has reached the Maximum active requestors value. If the time interval passes before any requestor returns to the pool, the request fails. The system sends a failure message to the external client system.