Configuring additional websites with IIS redirector for JBoss Application Server

After you have set up Internet Information Services (IIS) redirector to work with JBoss AS, you can configure IIS to redirect JSP and Java Servlet requests for more than one website.

This may be required if, for example, you want to run a test and a production deployment of NexJ CRM simultaneously. You might configure https://server1.yourcompany.local:8443/nexj/Contact.htma and http://server1.yourcompany.local:8543/nexj/Contact.htma.

Ensure that there are multiple redirectors configured on the application server. This means that you have an additional directory similar to mod_jk, for example, mod_jk_node2.

If you require Secure Socket Layer (SSL) authentication for the additional website, ensure that the SSL certificate for IIS has been installed and that the website has been bound to an HTTPS port. For more information, see Configuring IIS to use SSL.

You can configure the redirector by using the Internet Information Services (IIS) Manager, by running Appcmd.exe commands in a command-line window, or by editing configuration files directly.

Refer to your Microsoft IIS documentation for more information.

To set up the IIS redirector for an additional website using the Internet Information Services (IIS) Manager:

  1. In the Microsoft Management Console (MMC), navigate to Server Manager > Roles > Web Server (IIS) > Internet Information Services (IIS) Manager. In the Internet Information Services (IIS) Manager panel, navigate to the additional website. For example, select Test.
  2. Double-click ISAPI Filters.
    1. Delete the ISAPI filter with a filter name of jakarta or any filters that point to the isapi_redirect-1.2.40.dll file that resides in the mod_jk directory.
    2. Add a new ISAPI filter, setting the Filter name to jakarta and the Executable to point to the additional isapi_redirect-1.2.40.dll file, for example the one that resides in the mod_jk_node2 directory.
  3. Right-click the name of your website and select Add Virtual Directory.
    Add a new virtual directory, setting the Alias to jakarta and the Physical Path to the mod_jk_node2 directory.
  4. Select the virtual directory named "jakarta" and double-click Handler Mappings.
    1. Delete the ISAPI-dll handler mapping.
    2. Add a new module mapping with a different meaningful name, for example ISAPI-dll_node2.
      Set the Request Path to *.dll, the Module to IsapiModule, and the Executable (optional) to the fully qualified path to the additional isapi_redirect-1.2.40.dll file, for example, the one in the mod_jk_node2 directory.
    3. In the Edit Module Mapping dialog, click Request Restrictions. In the Mapping tab, select the Invoke handler only if request is mapped to request restriction and set its value to File. In the Access tab, set the access to Execute.
    4. Click OK twice to save all changes.
    5. If the Edit Module Mapping confirmation dialog appears, click Yes.
    6. In the Handler Mappings panel, right-click ISAPI-dll_node2 and select Edit Feature Permissions. Ensure that the Execute permission is selected.
  5. Select the name of your machine and double-click ISAPI and CGI Restrictions.
    Create a new restriction, if it doesn't already exist, setting the Description to jakarta and the ISAPI and CGI path to the fully qualified path to the additional isapi_redirect-1.2.40.dll file, for example, the one in the mod_jk_node2 directory. Enable the Allow extension path to execute option.
  6. Select your website and double-click HTTP Response Headers. Remove any ASP.NET headers which were automatically created by IIS.
  7. If you require Secure Socket Layer (SSL) authentication for the website, select your website and double-click SSL Settings. Enable the Require SSL option.
  8. Restart the website for the changes to take effect.
Microsoft IIS can now be used to redirect requests to multiple websites.