Category: IIS Management

Implementing search using indexing services and asp

I wanted to add a search function to the learning modules housed in our learning management system. These modules are of several types, most are HTML/javascript-based modules, but there are also flash, pdf, and MS producer ones as well. Many of them are meant to be viewed while under SCORM control, so it is important that the search feature not interfere with SCORM communication by allowing the user to navigating away from the current module or by removing the surrounding frameset.

When under SCORM control, the script must be able to detect which module is current, and search only within that directory. When not under SCORM control, the user can have the option of searching all content on the server.

It is also important to be able to hold obsolete or private items out of the search.

Continue reading

Make other extensions besides “.shtml” process for Server Side includes

The default extensions which IIS reads for Server Side Includes are .shtm, .shtml and .stm.

Suppose you want server-side includes to be processed in .htm files also? For example you may have file with the .htm extension which has been on the web for some time and has numerous links pointing at it. You could replace it with a file with one of the allowed extensions, and put a redirect in its place, pointing to the new file. Or, if you have access to the IIS server settings, you could add the .htm extension to the list of files processed for SSI.

Click on thumbnail images to see larger version.

  1. Open IIS Manager and right-click the Default Web Site. Select Properties from the popup menu. The Properties dialog appears.

  2. Select the Home Directory Tab and click Configuration under the Application Settings area.

Continue reading

Make a directory on a server part of another server’s domain

Sometimes it is necessary to have files or an application on one IIS web server (Server B) appear as if they were in the same domain as another server (Server A). For example, you may want

http://serverB.com/content

to be accessible via the URL

http://serverA.com/content 

This is useful in cases where you need to avoid cross-doman scripting issues, or simply want to make everything appear to be hosted under one umbrella domain name.

On an IIS server, this can be accomplished by creating a virtual directory on Server A which points to a directory on Server B.

Continue reading