Publishing Multiple Pages

Manifold IMS can publish multiple pages at once. There are two main ways to publish multiple pages:

 

§      Publish several different pages using several different .map files.

§      Publish several different pages using several different components within the same .map file.

 

Multiple Pages using Multiple .map Files

 

To publish multiple map files, create a separate directory for each web page to be created. Place the config.txt, default.asp and default.css files created for that page by File - Export - Web Page into the directory along with an image subdirectory containing the standard toolbar button images.

 

For example, if we published a map of Mexico we might place that in C:\Inetpub\wwwroot\mexico\ and if we also published a world map we might place that in C:\Inetpub\wwwroot\world\.

 

Create a separate IIS application for each directory containing the files for that page.

 

images\sc_multiple_applications.gif

 

For example, in the screenshot above we see an Internet Services Manager of a web site with several IIS applications. Three of them (manifold, mexico and texas) are Manifold IMS applications created using three different .map files. Each of the directories contains the config.txt, default.asp and default.css files created for that web page by the File - Export - Web Page dialog. Each of the application directories also contains a directory called images with the standard image files for toolbar buttons and controls that is also created by the Export Web Page dialog.

 

It may seem wasteful to duplicate the images directory for every application, but the images used are of negligible size. Duplicating the images directory for each page served by the map server simplifies the default.asp code and also allows easy customization of the appearance of toolbar buttons for each page if so desired.

 

Multiple Pages using the Same .map File

 

Different components from the same .map file can be used with different map server pages. However, all map server pages must be part of the same IIS application. To do this, create one directory with several subdirectories for each page. Create the IIS application on the parent directory.

 

Suppose, for example, we have created a usa.map file containing several drawings showing different data sets for the United States. One web page will show a map that contains several layers of interest to education. Another will show a map containing income layers and a third will show population layers.

 

We might create directories as follows:

 

C:\InetPub\wwwroot\usa with subdirectories

 

C:\InetPub\wwwroot\usa\education

 

C:\InetPub\wwwroot\usa\income and

 

C:\InetPub\wwwroot\usa\population

 

The education directory would contain the config.txt, default.asp and default.css files for the education map. The income directory would contain the config.txt, default.asp and default.css files for the income map, and the population directory would contain the files for the population map. The config.txt files for all three pages would use usa.map as the originating map file; however, the component used would be different.

 

We would create the IIS application on C:\InetPub\wwwroot\usa. All processes launched, including those for the default.asp files in education, income and population would thus be part of the same application and could use the same .map file.

 

images\sc_multiple_applications2.gif

 

The illustration above shows the application and directory structure within Internet Service Manager.

 

Troubleshooting

 

See the troubleshooting topic Problems with the Internet Map Server for detailed checklists of what might be wrong.

 

The number one problem with IMS reported to tech support is that users neglect to add the IUSR_ account the IUSR_ account (or, the NETWORK SERVICE account or ASPNET account if applicable) with access permissions to the .map file in use. Using Windows Explorer (do not just depend on the IIS management console or other server management console), right click on the .map file, choose Properties and verify in the Security that the IUSR_ account for the system has necessary read and execute permissions.

 

Take time to think through all permissions issues. The Internet access account must have permissions to get to all the data that is used in the web site. For example, suppose our IMS project uses a linked image. Because linked images use data from the Data Cache folder (the

default), we must also be sure to give the IUSR_ account (or, the NETWORK SERVICE account or ASPNET account if applicable) read permissions to access all files in that folder.

 

Note

 

You must be running Manifold System Professional Edition or greater to have the capabilities discussed in this topic. All Manifold editions except Personal Edition include the map server. If you are running Manifold System Personal Edition you will not have the capabilities discussed in this topic.

 

See Also

 

Map Server Overview

Creating a Web Site

IMS Queries

Optimizing Performance