Autodesk 15606-011408-9320 User Guide - Page 51

Accessing Data from the Autodesk MapGuide Viewer API, Architecture and Performance

Get Autodesk 15606-011408-9320 - MAPGUIDE R6.3 CPU MODEL-UPG 4/5 MIN 2 CPUS INITL PDF manuals and user guides
UPC - 606121429586
View all Autodesk 15606-011408-9320 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

Accessing Data from the Autodesk MapGuide Viewer API Map authors can control whether developers can access coordinate values and map layer setup data using the API getVertices() and getLayerSetup() methods. You control the security of this data from the Map Layer Properties dialog box in Autodesk MapGuide Author. If you allow API access, you can also specify that the application must send a specific passkey first, which the application developer passes in with the unLock method. The developer can then use the getVertices() and getLayerSetup() methods to access the coordinate values and layer setup data. For more information, refer to the Autodesk MapGuide Viewer API Help. We do not recommend hard coding the passkey in your HTML application script because users can always view the source code of an HTML page. One option is to prompt users for their user IDs and passwords when they attempt to view secured data and then authenticate the user ID and password against a database on your server. 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 your Autodesk MapGuide Server and how they affect performance. On installation, Autodesk MapGuide Server selects a map agent based on the web server it detects. You can, however, go back to the installation program and install a different map agent at any time. Which MapAgent to Install There are three types of Autodesk MapGuide Server agents (MapAgents) that you can install:  CGI This agent works on any type of web server and is easy to install. Therefore, if this is your first time building a web server, you might want to install the CGI agent instead of the ISAPI or NSAPI agents to avoid complications. However, you should note that CGI applications do not scale well on Windows NT/2000, meaning that they will not be able to take Architecture and Performance | 51

  • 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
Architecture and Performance
|
51
Accessing Data from the Autodesk MapGuide Viewer API
Map authors can control whether developers can access coordinate values
and map layer setup data using the API
getVertices()
and
getLayerSetup()
methods. You control the security of this data from the Map Layer Properties
dialog box in Autodesk MapGuide Author. If you allow API access, you can
also specify that the application must send a specific passkey first, which the
application developer passes in with the
unLock
method. The developer can
then use the
getVertices()
and
getLayerSetup()
methods to access the coordi-
nate values and layer setup data. For more information, refer to the
Autodesk
MapGuide Viewer API Help
.
We do not recommend hard coding the passkey in your HTML application
script because users can always view the source code of an HTML page. One
option is to prompt users for their user IDs and passwords when they attempt
to view secured data and then authenticate the user ID and password against
a database on your server.
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 your Autodesk MapGuide Server and how
they affect performance. On installation, Autodesk MapGuide Server selects
a map agent based on the web server it detects. You can, however, go back to
the installation program and install a different map agent at any time.
Which MapAgent to Install
There are three types of Autodesk MapGuide Server agents (MapAgents) that
you can install:
CGI
This agent works on any type of web server and is easy to install.
Therefore, if this is your first time building a web server, you might want
to install the CGI agent instead of the ISAPI or NSAPI agents to avoid com-
plications. However, you should note that CGI applications do not scale
well on Windows NT/2000, meaning that they will not be able to take