Autodesk 15606-011408-9330 User Guide - Page 48

Planning Your Directory Structure, Directory Structure Guidelines

Page 48 highlights

Planning Your Directory Structure The first step in designing your system is planning the structure of the files and directories you will have on your server. For example, will you have all of your files under one main directory, or will you split them into project directories? Will you have all of your data in one directory, to be used by all projects, or will you have a separate data directory for each project? Part of planning your directory structure comes from your own understanding of how many projects and how much data you have, and a major consideration is setting up the structure so that your files are secure. Note This chapter assumes you are familiar with Windows NT®, Windows® 2000, and Web server administration. If you are not, look up "Windows NT," "Windows 2000," and "Web servers" in the Autodesk MapGuide Help index. Directory Structure Guidelines You will need to create a directory structure for any of the file types you use with Autodesk MapGuide. In some cases you will also have to create virtual directories that map to physical directories. Your main security strategy is to keep your data repositories hidden from the Internet. You do this by placing spatial and attribute data away from the physical directories that are exposed to your server's HTTP processing. Virtual directories provide a mapping between the Web server directory structure and the physical directory structure in your file system. For example, when you install Autodesk MapGuide Server, it creates the virtual directory /MapGuide6/Sample_World/ on your local host, which maps to the physical installation directory c:\Program Files\AutodeskMapGuideServer6 \Projects\Sample_World\web The following illustration shows the physical installation directory: Sample project with recommended directory structure 48 | 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

48
|
Chapter 3
Designing Your System
Planning Your Directory Structure
The first step in designing your system is planning the structure of the files
and directories you will have on your server. For example, will you have all
of your files under one main directory, or will you split them into project
directories? Will you have all of your data in one directory, to be used by all
projects, or will you have a separate data directory for each project? Part of
planning your directory structure comes from your own understanding of
how many projects and how much data you have, and a major consideration
is setting up the structure so that your files are secure.
Note
This chapter assumes you are familiar with Windows NT
®
,
Windows
®
2000,
and Web server administration. If you are not, look up
Windows NT,
Windows 2000,
and
Web servers
in the Autodesk MapGuide Help index.
Directory Structure Guidelines
You will need to create a directory structure for any of the file types you use
with Autodesk MapGuide. In some cases you will also have to create virtual
directories that map to physical directories. Your main security strategy is to
keep your data repositories hidden from the Internet. You do this by placing
spatial and attribute data away from the physical directories that are exposed
to your server
s HTTP processing.
Virtual directories provide a mapping between the Web server directory
structure and the physical directory structure in your file system. For
example, when you install Autodesk MapGuide Server, it creates the virtual
directory
/MapGuide6/Sample_World/
on your local host, which maps to the
physical installation directory
c:\Program Files\AutodeskMapGuideServer6
\Projects\Sample_World\web
The following illustration shows the physical installation directory:
Sample project with
recommended directory
structure