Autodesk 15606-011408-9320 - MAPGUIDE R6.3 CPU MODEL-UPG 4/5 MIN 2 CPUS INITL User Manual page 69

If you are using the ISAPI or NSAPI version of the MapAgent, the requests are
distributed to the servers in a rotating manner. If you are using the CGI
version of the MapAgent, it has no persistent memory between requests, so
it distributes the requests randomly among the servers.
You may also want to consider purchasing a third-party load-balancing
solution such as Microsoft Windows NT Load Balancing Service (WLBS), F5
Networks' 3DNS® Controller, or RADWARE's Web Server Director™ (WSD)
products.
Firewalls
When you use a remote MapAgent, you need to configure your firewall to
permit DCOM penetration from the outside to the inside. First, you must
limit the DCOM port range on the Autodesk MapGuide Server computer. By
default, a DCOM server uses port 135 for handshaking and uses any port in
the range of 1,024 through 65,535 to service the DCOM call. To limit the
range of DCOM, you must again use REGEDT32.EXE.
Add the following three values to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet (the Internet
key does not exist by default, so you might need to create it):
Autodesk MapGuide Server RPC Values
Value Name
PortsInternetAvailable
UseInternetPorts
Ports
The value in "Ports" specifies the range of ports on the server that are valid
for use by RPC. (The value "6600-6610" is simply an example.) You can
specify multiple ranges for availability by entering each range on a separate
line. You will need to restart Windows for the changes to take effect.
Now that you have specified which ports are available for use by RPC (port
135 and the ports you specified in the "Ports" value), you must configure
your firewall to allow the MapAgent computer to establish a connection with
the Autodesk MapGuide Server computer on these ports.
Data Type Text
REG_SZ Y
REG_SZ Y
REG_MULTI 6600-6610
Setting Up Your Server
|
69