You can configure JRun to work with Internet Information Server 4.0, 5.0, on Windows NT, 2000, and XP systems.
This section describes the following:
For more information about advanced web server connection techniques, see JRun Administrator's Guide.
Before configuring IIS, use the following procedure to ensure that the IIS Admin Service startup type is set to automatic or manual, and not disabled:
The Services control panel appears.
The Properties window appears.
Use the following procedure for connecting JRun to an IIS web server.
For details, see "Running the Web Server Configuration tool".
The IIS website specifies the location of the filter or application mappings.
Note: All means install the filter and application mappings at the global level so that they apply to all websites that currently exist. For more information, see .
ISAPI filter JRun installs an ISAPI filter module, which IIS invokes to handle events during HTTP request processing.
Application mappings An application mapping connects a filename extension with the application that processes the file. For example, if you select .jsp, when the web server receives a request for a .jsp file, it uses the mapping to the JRun web server connector to process the page. By selecting application mappings, you turn off the ISAPI filter and gain the use of IIS security in JSP pages.
You cannot delete a mapping if it is the only one specified. You must have at least one mapping specified in the list box.
Note: In Web Server Properties, if you selected a website, the filter or application mappings are applied at the website level. If you selected All, the filter or application mappings are applied at the global level.
JRun connects to the web server.
Note: This step assumes that IIS is listening for connections on the default port 80. If not, use http://web-server-hostname:webserver-port-number.
The default page for the web server to which you connected appears, showing that you successfully configured the connection between JRun and your external web server.
Note: JRun creates an IIS virtual directory, called JRunScripts, for each website that you configure. If you install IIS at the global level, the Web Server Configuration tool creates a JRunScripts directory for each existing website. If you configure a website after you installed JRun, you must run the Web Server Configuration tool again to create a JRunScripts directory for the new website.
You can remove the web server configuration in one of two ways:
Select the IIS web server configuration, and click Remove.
java -jar jrun_root\lib\wsconfig.jar -ws iis -site sitename -r
ISAPI filters can respond to events when IIS receives an HTTP request. If you select Use ISAPI Filter while running the Web Server Configuration tool, JRun installs a DLL that is added to the other ISAPI filters in the web server memory. The location of the jrun.dll file is in a subdirectory under jrun_root\lib\wsconfig.
The instructions in this section are optional. The default configuration of JRun does not require you to make any changes to the JRun ISAPI filter. However, if you install other ISAPI filters, you might have to make changes.
When several ISAPI filters register for the same event (or notification), IIS calls them sequentially. Filters with a higher priority are run before filters with a lower priority. The priority levels High, Medium, and Low are read-only properties that you cannot change using the Internet Services Manager or other metabase editor. The JRun priority level is High.
While you cannot change a filter's priority level, you can determine which filter responds to an event first if it shares the same priority level as another filter. Use the following procedure to change the JRun ISAPI filter's priority.
The Microsoft Management Console (MMC) appears and opens the iis.msc Snap-In.
The Internet Services Manager appears.
The Properties window appears.
If you installed a global filter, right-click the system name and select Properties or click the system name to expand the list of websites.
Your changes are applied.