Multi-Broker Environments (Magic xpa 3.x)
Using multiple brokers allows you to have separated environments, such as one environment (broker + enterprise servers) for development and another environment for deployment.
|
Note:
|
It is relatively easy to misuse multi-broker environments by using several brokers for several applications, for administration purposes. In such cases the broker turns out to be a pipe, losing its ability to perform load balancing. For administration issues, it is better to use services in the Monitor application, since the broker refers only to the application pointed out by the service. For example, the function activation <RQLOAD (‘Default Service’,)> will return statistics only regarding the application pointed out by the service ‘Default Service’ in the services table.
|
Another possibility is to use the command line requester: mgrqcmdl –que=load –app=app1
Another advantage of multi-broker environments is using brokers as agents to start enterprise servers on other machines. Other brokers can be used to start enterprise servers on their own machines, using the [REMOTE_APPLICATIONS_LIST] section in the mgrb.ini file of the main broker.
|
Note:
|
Developers may want to access several brokers on the same machine from different requesters activated by a Web server. This can only be achieved if the Web server reads the mgreq.ini file from a different directory for each requester; for example, from the directory assigned to a different alias. Such ability can be used to set different MessagingServer entries in the different mgreq.ini files and thus enable the access of different brokers. If the Web server uses the same directory for all of its aliases, then only one broker can be accessed.
The registry key HKEY_LOCAL_MACHINE/SOFTWARE/MAGIC/MGREQ must not be used in order to enable the scenario described above.
|
