Autodesk 15606-011408-9330 User Guide - Page 54

Architecture and Performance, Which Ma nt to Install

Page 54 highlights

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 architectures 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 communicating 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

54
|
Chapter 3
Designing Your System
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.