Autodesk 15606-011408-9008 User Guide - Page 49

Group files into projects with project directories, Place files under a virtual directory

Page 49 highlights

This setup is designed for maximum portability and security as well as ease of maintenance. By setting up your projects in this way, you can easily move an entire project from one computer to another, as all of the necessary data is under the project directory. You can also add additional directories and subdirectories, as needed. As shown in the illustration on page 48, when you map a virtual directory to ..\Projects\Sample_World\web, your data directories (..\Database, ..\Raster, and ..\SDF) are not exposed to the Internet. Clients can only access the folders and files within the folder to which the virtual directory is mapped. Using virtual directories enables you to keep the same URL, even if you change file paths on your system. If you change file paths, just update the virtual directory mapping. Virtual directories also enable you to grant Execute permission to directories you create. Use the following guidelines for setting up your directory structure. Group files into projects with project directories After you group files into projects with project directories, map virtual directories to the ..\\web directory. For example, if you create two project folders on the file system of your Autodesk MapGuide Server, ..\Projects\project1 and ..\Projects\project2, map virtual directories to ..\Projects\project1\web and ..\Projects\project2\web but do not put your data in directories below ..\web. Place files under a virtual directory Unlike raw data, you must place all HTML-related files, including MWFs, under a virtual directory so they are directly accessible to the Internet. For example: ..\Projects\project1\web\map1.html (www..com/project1/map1.html) ..\Projects\project2\web\map2.html (www..com/project2/map2.html) Place files in directories that have Execute permission You need to place your report files and server-side scripts in directories that have Web server Execute permission. If you are running Microsoft Internet Information Server (IIS), and you want to assign Execute permissions to a directory, you must create a virtual directory that maps to it, regardless of whether that directory is under the Web root or not. Planning Your Directory Structure | 49

  • 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

Planning Your Directory Structure
|
49
This setup is designed for maximum portability and security as well as ease
of maintenance. By setting up your projects in this way, you can easily move
an entire project from one computer to another, as all of the necessary data
is under the project directory. You can also add additional directories and
subdirectories, as needed.
As shown in the illustration on page 48, when you map a virtual directory to
..\
Projects\Sample_World\web
, your data directories (..\
Database
, ..\
Raster
,
and
..\SDF
) are not exposed to the Internet. Clients can only access the
folders and files within the folder to which the virtual directory is mapped.
Using virtual directories enables you to keep the same URL, even if you
change file paths on your system. If you change file paths, just update the
virtual directory mapping. Virtual directories also enable you to grant
Execute permission to directories you create.
Use the following guidelines for setting up your directory structure.
Group files into projects with project directories
After you group files into projects with project directories, map virtual direc-
tories to the
..\<project name>\web
directory. For example, if you create two
project folders on the file system of your Autodesk MapGuide Server,
..\Projects\project1
and
..\Projects\project2,
map virtual directories to
..\Projects\project1\web
and
..\Projects\project2\web
but do not put your data
in directories below
..\web
.
Place files under a virtual directory
Unlike raw data, you must place all HTML-related files, including MWFs,
under a virtual directory so they are directly accessible to the Internet. For
example:
..\Projects\project1\web\map1.html
(www.<your domain>.com/project1/map1.html)
..\Projects\project2\web\map2.html
(www.<your domain>.com/project2/map2.html)
Place files in directories that have Execute permission
You need to place your report files and server-side scripts in directories that
have Web server Execute permission. If you are running Microsoft Internet
Information Server (IIS), and you want to assign Execute permissions to a
directory, you must create a virtual directory that maps to it, regardless of
whether that directory is under the Web root or not.