BMC Remedy Action Request System 7.1.00: Configuring

List queue
Scalability
The list queue handles AR System operations that might require significant time,
block access to the database, or both. Examples of these operations include
ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics.
One or more threads can serve the list queue if a list queue is configured. To
configure a list queue, see “Defining queues and configuring threads” on page 131.
Private queues
Administrators can also create private queues for specific users who need
dedicated access. For example, you might create a private queue for a user who is
performing critical operations that you do not want blocked by other users. Private
queues guarantee a certain bandwidth dedicated to clients using these queues.
Private queues support all operations except restructuring operations.
Restructuring operations are supported only by the administration queue (see
“Administration queue” on page 25). To configure a private queue, see “Defining
queues and configuring threads” on page 131.
Each private queue can be supported by one or more threads. To connect a user to
a private queue, see “Configuring clients for AR System servers” on page 170.
Threads
The term thread is short for “thread of execution.” Threads allow the server to
process concurrent client requests. Each thread within the multithreaded server
can carry out a client request before returning to the queue to process the next one.
Start only as many threads as your database and system resources can reasonably
support. The total number of threads cannot exceed the number of database
connections that are available to the AR System server.
All threads within a process share network and system resources; therefore,
consider carefully the available resources of your network when establishing the
minimum and maximum thread settings for your server queues.
There are three types of AR System threads:
Dispatcher
Worker
Thread manager
The following sections describe the different types of threads.
Dispatcher thread
The dispatcher thread routes requests to the appropriate queues. This thread
receives connection requests from clients. The dispatcher thread then places the
requests into the appropriate queue where each request can be handled by one of
multiple worker threads.
Every call that the dispatcher thread receives is assigned an RPC ID that can be
used to identify the call from the time the call is placed into a queue until a
response is sent to the client.
Chapter 1 BMC Remedy Action Request System 7.1.00 architecture 27