Architecture And Performance; Which Mapagent To Install - Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 User Manual

Map authors can also control whether developers have access to the
tracking ID using the getTrackingID() and setTrackingID() methods. You
control the security of this data from the Map Window Properties dialog box
in Autodesk MapGuide Author.

Architecture and Performance

This section discusses the different server agents and distributed architec-
tures that you can implement for Autodesk MapGuide Server and how they
affect performance. On installation, Autodesk MapGuide Server selects a
MapAgent based on the Web server it detects. You can, however, go back to
the installation program and install a different MapAgent at any time.

Which MapAgent to Install

There are three types of Autodesk MapGuide Server agents (MapAgents) that
you can install:
CGI—This MapAgent works on any type of Web server and is easy to


install. Therefore, if you are building a Web server for the first time, and
you are not distributing or mirroring your map data across multiple
servers, you might want to install the CGI MapAgent instead of the ISAPI
or NSAPI MapAgents to avoid complications. Note that the CGI
MapAgent is slower than the ISAPI and NSAPI MapAgents because it does
not run as part of the Web server.
ISAPI—The ISAPI (Internet Server Application Programming Interface)


MapAgent is an ISAPI server extension that can be loaded by Microsoft
Internet Information Server (IIS). Because it runs as part of the Web server
process, it improves performance by eliminating the overhead of commu-
nicating between the Web server and a separate CGI executable. The ISAPI
MapAgent resides on the user's 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 IIS.
NSAPI—The NSAPI (Netscape Server API) MapAgent is similar to the ISAPI


MapAgent, except it works on the Netscape Enterprise Server. Like ISAPI,
it is faster than a CGI MapAgent, and thus optimizes your server's
performance.
For more information, see "Understanding Multiple Simultaneous Server
Requests" on page 56.
|
54 Chapter 3 Designing Your System