Specify how queue managers handle queued requests
You can control how queue managers handle queued requests by
modifying the properties of queue managers. You set properties for
all queue managers, not for specific servers.
You can modify the following transaction properties for queue
managers:
Requests security
This property controls which users and groups can submit queued
requests to provisioning engines and the type of procedures that
they can execute. Options for executing procedures include the
following:
- Execute procedures
A user with Execute Procedures permissions can run only MPF
procedures that do not change the XML of a procedure. These
procedures must be part of a namespace that is registered in the
configuration database.
- Execute with caller's credentials
A user with Execute with Caller's Credentials permission can
pass a security context in the request. Setting the Execute Trusted
Procedures permission to Allow automatically sets the
Execute with Caller's Credentials permission to Allow.
- Execute trusted procedures
A users with Execute Trusted Procedures permissions can run MPF
procedures that change the XML of a procedure. These procedures can
be executed without being previously registered in the
configuration database. The default users and groups with execution
permissions for executing trusted procedures include:
Administrator, MPFAdmins, and MPFTrustedUsers.
For more information on related security topics, see Managing security.
Max
queue size
This property controls the maximum number of requests the queue
manager can store in the queue. The default max queue size is
10,000 requests.
Action request threads
Each thread is responsible for taking a request from the queue
and sending it to provisioning engines. The greater the number of
threads, the greater the number of requests that MPF can process
simultaneously. A greater number of threads will consume more
hardware resources. You can use this option to tune the performance
for request processing. The default number of action request
threads is two threads.
Stability thread wait time
This property controls the interval between scans of the
transaction log database. During these scans, MPF searches for
queue actions for which dependencies have been satisfied and are
now ready to run, or have previously failed and are now ready to be
retried.
Transaction log pool size
This property specifies the maximum number of connections that
can be established to one transaction log database. The default
setting is 100 simultaneous connections.
Change the status of individual queue managers
You can activate, deactivate, start, or stop a queue manager on
a server. When you deactivate a queue manager, MPF signals the
client to stop sending requests to that queue manager. When you
stop a queue manager, the client continues to send requests to the
stopped queue manager. However, the queue manager blocks all
requests until you start the queue manager again.
For more information, see To
activate, deactivate, start, or stop the Provisioning Queue Manager
service on a server.