IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning
Tuning the REST interface for federated BPM resources
The federated REST API can become a bottleneck if your federation domains contain more than two systems and you have many clients that interact concurrently with the federated BPM REST API. A common cause of this problem is that the thread pool does not have enough threads to handle the service requests from the clients.
The internal thread pool used by the Federated BPM REST API has a maximum of 200 threads. To increase the number of threads in the thread pool, create a custom work manager, and then assign it to the federated BPM REST API.
Procedure
- Start the administrative console.
- Select Resources > Asynchronous beans > Work managers.
- Select the scope that matches the scope of the REST services gateway, then click New.
- Specify values for the following properties for the custom work manager.
For all other properties, accept the default values or customize the values as needed.
- Name
- Specify the name by which the work manager is known for administrative purposes.
- JNDI name
- Enter wm/BpmFederatedRestWorkManager as the JNDI name.
- Description
- Specify a description of the work manager for administrative purposes.
- Work request queue size
- The work request queue is a buffer that holds submitted units of work until a thread is available for them to run. Calculate the value using the following formula:
(minimum_number_of_threads + maximum_number_of_threads) / 2.- Work request queue full action
- Specifies the action taken by the work manager when the thread pool is exhausted. Select BLOCK from the list.
- Maximum number of threads
- The maximum number of threads to be created in the thread pool.
- Growable
- Select the Growable check box. This property enables the maximum number of threads to be exceeded temporarily. These additional threads are discarded when the work on the thread completes.
- Click OK, then Save.