Installing JRun
Connecting JRun to External Web Servers

Connecting an IIS web server

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:

• "Connecting JRun to IIS"
• "Configuring the JRun ISAPI filter"

For more information about advanced web server connection techniques, see JRun Administrator's Guide.

Connecting JRun to IIS

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:

1. Open the Windows Services utility.
   • (Windows 2000) Select Start�> Programs�> Administrative Tools�> Services.
   • (Windows NT) Select Start�> Settings�> Control Panel�> Administrative Tools�> Services.

     The Services control panel appears.

2. Right-click IIS Admin Service, and select Properties.

   The Properties window appears.

3. Select the General tab.
4. In the Startup type drop-down list box, select automatic or manual.
5. Click OK.

Use the following procedure for connecting JRun to an IIS web server.

To connect JRun and IIS:

1. Run the Web Server Configuration tool and connect to a JRun server.

   For details, see "Running the Web Server Configuration tool".

2. In the Web Server Properties section of the Web Server Configuration tool, select Internet Information Server (IIS), as the following figure shows:

   

3. Select the IIS website that you want to configure.

   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 .

4. To enable the following connector settings, click Advanced:
   • Verbose logging in the connector log
   • The native OS memory allocator, not the web server memory allocator

     

5. In IIS Settings section, specify Use ISAPI filter or Use Application Mappings.

   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.

   • To add an application mapping, enter the file extension in the text box next to the Add button, and click Add.
   • To delete an application mapping, select it in the list box and click Delete.

     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.

6. Click OK.

   JRun connects to the web server.

7. Ensure that your web server is running.
8. To verify the JRun connection to your IIS web server, open a web browser on the IIS web server to the following URL: http://web-server-hostname.

   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.

Removing the JRun connection to IIS

You can remove the web server configuration in one of two ways:

• Using the Web Server Configuration tool:

  

  Select the IIS web server configuration, and click Remove.

• Using the following command:

  java -jar jrun_root\lib\wsconfig.jar -ws iis -site sitename -r
  

Configuring the JRun ISAPI filter

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.

Prioritizing the JRun ISAPI filter

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.

To change the priority of the JRun ISAPI filter:

1. Open the Internet Service Manager:
   • (Windows NT) Select Start�> Programs�> NT 4.0 Option Pack�> Microsoft�Internet�Information�Server�> Internet�Service�Manager.

     The Microsoft Management Console (MMC) appears and opens the iis.msc Snap-In.

   • (Windows 2000) Select Start�> Programs�> Administrative Tools�> Internet�Services�Manager.

     The Internet Services Manager appears.

2. Right-click the website name and select Properties.

   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.

3. Select the ISAPI Filters tab.
4. Select JRun Connector Filter from the list of available ISAPI filters.
5. To move the JRun filter ahead of the other filters in the list, click the up arrow.
6. Click OK.

   Your changes are applied.

7. Restart your web server.

Comments

Add Comment

jrunrandy said on Sep 11, 2003 at 6:33 AM :

Step 8 should probably say something like http://web-server-hostname/index.jsp.

However, since index.jsp is listed in the default web application's welcome-file-list element, the other way it could be rewritten is "To verify the JRun connection to your IIS web server, open a web browser on the IIS web server to the following URL: http://web-server-hostname. If index.jsp displays, the web server connection is configured properly."

tarner said on Jan 14, 2004 at 6:40 AM :

This note should explain how to map the connnector using an IIS (or other) single website to multiple jndi and jrun proxy servers (jrun servers) on a separate jrun app server. Separate context roots. Not helpful. Not clear .

JRun_Spy said on Mar 15, 2004 at 8:11 AM :

how do you get this to work on windows 2003??
i do not see any jrun.dll file in the specified directory.
do you guys ever update this stuff???

No screen name said on Apr 2, 2004 at 5:35 PM :

i'd like to know how to get this to work in windows 2003 as well.

norgus said on Apr 4, 2004 at 7:15 AM :

I really need to get the ISAPI filter working under Windows 2003 Server as well. The option to turn this on is missing completely udner the Advanced button, when adding a Server.

jrunrandy said on Apr 5, 2004 at 9:14 AM :

Go to the Macromedia JRun support center and download the latest Updater. It should have support for Windows 2003.

http://www.macromedia.com/support/jrun/updaters.html

No screen name said on Jun 30, 2004 at 6:56 PM :

The Update3 does not install any of the binaries of the connectors on Windows 2003 Web Edition from my tests on two servers. Is there any body that has gotten it to work?

No screen name said on Nov 10, 2004 at 12:53 PM :

the ISAPI filter under Windows 2003 Server. The option to turn this on is missing completely under the Advanced button, when adding a Server. I've downloaded and installed the latest update. Any suggestions?

Sarge said on Nov 11, 2004 at 5:18 AM :

The JRun connector is not added as an ISAPI filter for IIS 6. The jrun_iis6.dll and jrun_iis6_wildcard.dll are registered as the Macromedia Server Extensions in the IIS 6 Web Service Extensions with an "Allowed" status. The JRun documentation was published before the release of IIS 6, hence it does not provide accurate instructions. You will find information about this in the CFMX 6.1 docs:
see ColdFusion MX 6.1: Manually configuring the web server connector for ColdFusion MX Standalone
http://www.macromedia.com/support/coldfusion/ts/documents/standalone_manual_configure.htm

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/Installing_JRun/servconf5.htm

Add Comment