Magic Request Broker (MRB) (Magic xpa 3.x)
Magic xpa provides a middleware agent known as the Magic Request Broker. The Magic Request Broker, also referred to as the broker, maintains the pool of available Magic xpa Runtime engines.
|
Note:
|
In addition to the Magic Request Broker, Magic xpa supports an In-Memory Data Grid (IMDG) as its underlying messaging layer.
|
When a Runtime engine loads, it registers itself with the broker. Each subsequent engine also registers itself with that broker.
When the broker loads it starts listening on its defined port. The broker handles a list of all the available Magic xpa Runtime engines and directs each request from the Magic xpa Internet requester to the available Runtime engine for execution.
Each Runtime engine can handle more than one request simultaneously, each in its own thread.
The request broker provides load balancing and recovery capabilities to handle any fail over.
The main functions of the Magic Request Broker are:
-
Queuing client requests
-
Allocating available runtime engines for requests
-
Logging all operations
-
Maintaining and distributing the status of all submitted requests
-
Activating programs in asynchronous (No Wait) mode
Distributed Application Architecture Using the Broker Middleware
Prerequisites
Magic Request Broker Files
Mgrb.ini
Magic Request Broker Behavior
Filters
Multi-Broker Environments
Port Usage
Resolving Host Names
Log Files and Unknown Errors
Partitioning Error Messages
Monitoring the Broker
Broker chapter in the Mastering Magic xpa guide
