Resolving Host Names (Magic xpa 3.x)
The Magic xpa partitioning architecture lets the different modules (broker, clients, and enterprise servers) reside on different computers. For that purpose, each computer must know the names of the other computers with which it interacts.
For example, let’s say the broker is positioned on one computer, named SRVR_1, and there are two enterprise servers on two different computers, SRVR_2 and SRVR_3. The enterprise servers identify themselves to the brokers using the names SRVR_2 and SRVR_3, and these are the names that the broker passes on to clients when the clients send synchronous requests. Therefore, each client must know how to resolve the names SRVR_1, SRVR_2, and SRVR_3.
The best way to accomplish this is to use DNS (Domain Names Service) or DHCP, a centralized pool of names and their known IP addresses.
|
Note:
|
DHCP should not be mixed with non-DHCP settings. Computers that don’t use DHCP will not know the correct IP address translation, because they use another database (for example, a fixed DNS database).
|
Another way, old-fashioned but simple, is to use a hosts file. The hosts file mechanism requires each computer to have an up-to-date copy of the same hosts file.
|
Note:
|
It is possible to use a specific IP address to access the broker, in mgreq.ini or the servers table of magic.ini, or using the command line requester: mgrqcmdl –host=<ip address> ….
However, using IP addresses to bypass host name resolving (as described above) do not apply for enterprise servers, which are identified by their names, and these names will be used whenever the broker or the requesters need to access them, even if they are in the same computer of the broker. The clients do not make optimization in this area. Each host name is being resolved as is.
|
