Autodesk 15606-011408-9330 User Guide - Page 73

When installed, the MapAgent reads the MapServer_IP value from the registry and gets all the MapGuide Server IPs that can handle requests. The ISAPI and NSAPI MapAgents keep track of the number of requests each Autodesk MapGuide Server is currently handling. The CGI MapAgent cannot keep track of the number of requests each Autodesk MapGuide Server is handling. When a new request comes in, the ISAPI and NSAPI MapAgents assigns the new request to the Autodesk MapGuide Server that is currently handling the fewest requests. 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. For more information, see "Understanding Multiple Simultaneous Server Requests" on page 56. You may also want to consider purchasing a third-party load-balancing solution such as Microsoft Windows NT Load Balancing Service (WLBS), the F5 Networks 3DNS Controller, or the RADWARE 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 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 Data Type Text PortsInternetAvailable REG_SZ Y UseInternetPorts REG_SZ Y Ports REG_MULTI 6600-6610 Setting Up Your Servers | 73