Autodesk 15606-011408-9320 - MAP R6.3 CPU MODEL-UPG 4/5 MIN 2 CPUS INITL, Руководство пользователя

Страница: 52 / 190

52
|
Chapter 3 Designing Your System
advantage of multiple servers. If your server receives numerous client
requests for Autodesk MapGuide, you will end up with many separate
instances of the CGI agent communicating with Autodesk MapGuide
Server. This can adversely affect your performance.
ISAPI The ISAPI (Internet Server Application Programming Interface)
agent is an alternative to CGI. It is an API that extends the capabilities of
Microsoft Internet Information Server. (If your web server is Netscape, use
CGI or NSAPI instead.) The ISAPI agent is in the form of a DLL (Dynamic
Link Library). The ISAPI DLL resides on the computer, so it is faster than
the CGI agent. It is also fairly easy to install. However, you can install the
ISAPI agent only on a Microsoft Internet Information Server.
NSAPI The NSAPI (Netscape Server API) agent is similar to the ISAPI agent
except that it works on the Netscape Enterprise Server. Like ISAPI, it is
faster than CGI, making it better for your server’s performance.
Using a Remote MapAgent
The Autodesk MapGuide MapAgent uses RPCs (remote procedure calls) to
forward client requests for map data to Autodesk MapGuide Server. Because
RPC calls can be made across a network, the MapAgent does not need to
reside on the same computer as Autodesk MapGuide Server. This is useful for
enhancing security, because it allows you to publish maps from your public
server while keeping your data, Autodesk MapGuide Server, and the commu-
nication between them secure on your private internal LAN.
For example, you could have your web server, MapAgent, HTML files, and
supporting files for the HTML files (such as bitmaps that appear in the web
page, not within the map) all on a public server outside of the firewall or
other Internet security mechanism you are using. Inside the firewall, you
would have Autodesk MapGuide Server and your resources (databases, SDFs,
and raster images that appear within the map). With this setup, not only is
all of your data behind the firewall, but all communication between
Autodesk MapGuide Server and your data takes place behind the firewall.
This approach allows the whole world to use your maps, but it minimizes the
possibility of hackers accessing your data files or taking advantage of the
communication between Autodesk MapGuide Server and your databases.
The only hole in the firewall is between the MapAgent and Autodesk
MapGuide Server, and the data passed between them is only useful for
display in Autodesk MapGuide Viewer. For more information, see “Data File
Placement” on page 57.