Filters (Magic xpa 3.x)

« Go Back


Created ByKnowledge Migration User
Approval Process StatusPublished

Filters (Magic xpa 3.x)

Server-side – Filters Setting


You can use the Filters setting to specify how threads are allocated for different types of requests, such as HTTP requests, SOAP requests, COM requests, and requests without a filter.

Filters allow for a better Service Level Agreement, by ensuring that requests of one type do not exhaust the capacity of the broker and server(s) to serve requests of other types.

Example: The example below shows you how an enterprise server with a license of 20 threads can be designated to service different types of requests:

HTTP_endusers:40% | SOAP_primary:10% | SOAP_secondary:5% | RemoteCalls:10% | COM:0%

  • HTTP_endusers – 8 threads (40% of 20 threads)

  • SOAP_primary – 2 threads (10% of 20 threads)

  • SOAP_secondary – 1 thread (5% of 20 threads)

  • RemoteCalls – 2 threads (10% of 20 threads)

  • COM – 1 thread (0% of 20 threads) – The minimum number of calculated threads is 1.

  • Requests without filter – 6 threads (remaining 30% of 20 threads)

Note: If the accumulated percentage is greater than 100%, the last filter entry that exceeds the accumulated percentage of 100% will be adjusted to be equal to 100% and all subsequent filters will be discarded.


When setting the keyword in the Magic.ini file, the value is sent from the server to the broker, and supersedes the default setting of the broker (for the specific server).

Client-side – Filter Setting


To instruct the broker to serve requests from the current requester under a specific Filter, set in the relevant Mgreq.ini file (usually in same folder as the requester): Filter=name, for example: Filter = HTTP_endusers.


Similarly, to instruct the broker to serve the Remote Calls from a Magic xpa engine under a specific Filter, set in the Service Properties: Filter=name, for example: Filter= RemoteCalls.