WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer mediations > Configure mediationsConfigure the mediation thread pool
Use this task to configure the mediation thread pool.
The wsadmin tool must be running. For more information, see Start the wsadmin scripting client using wsadmin.sh.
You configure the mediation thread pool to change the number of threads used when running mediations concurrently. Maximum size of the thread pool determines the maximum number of messages that can be mediated concurrently for a messaging engine.
The mediations thread pool, attribute name mediationsThreadPool, is an attribute of the messaging engine. By default, mediationsThreadPool does not exist, and a default thread pool is created and used at run time. In this task, use wsadmin to create a thread pool object, and then modify its properties using JACL, as shown in the examples below:
- Use this example to create a mediationThreadPool object:
AdminConfig.create("ThreadPool" , messagingEngine, [["name" , "stitch.server1-bus2-mediationThreadPool"]] , "mediationThreadPool")In this case, the thread pool name is based on the name of the messaging engine. Although it is not required to do this, it makes it easier to find the thread pool name when using Performance Monitoring Infrastructure (PMI).
- Use this example to modify a mediationThreadPool object:
AdminConfig.modify(AdminConfig.showAttribute(messagingEngine, "mediationThreadPool"), [["maximumSize" , "10"]])maximumSize can contain any of the mediationsThreadPool properties. To add additional parameters, insert [attribute_name attribute_value] within the outer brackets ([]).
There is a space between attribute_name and attribute_value.
Related concepts:
Concurrent mediations
Performance monitoring for mediations
PMI
Reference:
Mediation thread pool properties
Related information:
Mediation thread pool [Settings]