Salesforce

Magic Request Broker Behavior (Magic xpa 2.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Magic Request Broker Behavior (Magic xpa 2.x)

The Magic Request Broker (MRB) manages the request queue, which is based on priorities from 0 to 9, where 0 is the lowest priority. Each item in the queue contains the following information:

  • Request ID

  • Priority

  • Execution status

  • Application name

  • Original request packet

  • Error codes

The MRB manages a list of associated Runtime engines containing the following information for each Runtime engine:

  • Address

  • Status

  • Current application

  • Available applications

Automatic Reload

The Magic Request Broker automatically reloads when an abnormal termination occurs. The Magic Request Broker reloads through an administrative process that monitors the Magic Request Broker.

Automatic Termination of the Enterprise Server

If the Magic Request Broker terminates and restarts, normally or abnormally, the enterprise server connected to the broker session will terminate after 60 seconds or less. This applies only to an enterprise server running in the background mode.

Load Balancing Algorithm

The Magic Request Broker load balancing mechanism ensures that requests are directed to the engines based on a calculation of the best performance (the lower values of the average request time divided by the engines' priority) and the least number of active contexts.

To control the engines' priority, refer to the Load Balancing Priority environment keyword of the engine.

Related Topics

Reference
Attachment 
Attachment