Autodesk 15606-011408-9008 User Guide - Page 50
Strategically locate Ma nt files, Security
UPC - 606121429517
View all Autodesk 15606-011408-9008 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 50 highlights
For instructions on creating a virtual directory, refer to the documentation that came with your Web server. Strategically locate MapAgent files You can locate your MapAgent files anywhere on the file system where they can be executed by the Web server software. If you are running IIS, we recommend you use the default directory, /MapGuide6/, which the Autodesk MapGuide Server installation creates for your MapAgent files. This way you do not need to create a virtual directory for these files. If you choose to place your MapAgent files elsewhere, you must create a virtual directory that maps to its physical counterpart and assign Execute permissions with your Web server software. Netscape Enterprise Server does not create a default directory. If you use the NSAPI version of the MapAgent, you must enter a pointer in the Netscape configuration file that points to the MapAgent_NSAPI.dll file. Typically, the MapAgent_NSAPI.dll directory is: C:/Program Files/Autodesk/MapGuideServer6/MapAgents If you are going to use the CGI agent, you must create a CGI directory and create a mapping to that directory in the Netscape Administrator. Security Security is an important consideration when setting up any kind of server application. With Autodesk MapGuide, you can implement security for your server computer at a number of different levels. There are three main methods for setting up security: Use the Windows NT or Windows 2000 Administrator tools to set security for files and directories on the server computer. Use your Web server to set security for virtual directories. Plan your direc- tory structure so that files requiring security are not exposed to the Internet, for instance, by physically creating these files hierarchically above their virtual directories. Use Autodesk MapGuide to set up user IDs and passwords, access keys, passkeys to protect resources (such as SDFs and databases), maps, and map layers. 50 | Chapter 3 Designing Your System