Setting up the IIS redirector for JBoss AS

Configure the Internet Information Services (IIS) to redirect JSP and Java Servlet requests to JBoss Application Server (JBoss AS).
Before carrying out these steps, install Microsoft IIS and the following additional components.
  • ISAPI Filters
  • ISAPI Extensions
  • IIS: ASP.NET
  • IIS: .NET Extensibility

If you require Secure Socket Layer (SSL) authentication for the website that represents NexJ CRM, 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 may need to use a proxy server in order to integrate a NexJ solution into your network architecture. The ISAPI filter checks and redirects requests made to the IIS web server to JBoss Application Server.

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.

The following instruction apply to a new deployment of IIS. If you already have other websites deployed using IIS, some of the components may exist with appropriate settings and do not need to be created or modified.

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

  1. To open IIS Manager, click the Start button, type inetmgr in the Search box, and click Enter.
  2. In the Connections panel, expand the navigation until you find your web site. Select the web site.
    For example, find and select Default Web Site.
  3. Double-click ISAPI Filters.
    Add a new ISAPI filter, setting the Filter name to jakarta and the Executable to point to the isapi_redirect-1.2.40.dll file.
  4. 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 directory.
  5. Select the virtual directory named "jakarta" and double-click Authentication. Ensure that only Anonymous Authentication is enabled.
  6. Select the virtual directory named "jakarta" and double-click Handler Mappings.
    1. Double-click the ISAPI-dll handler mapping.
      Set the Request path to *.dll and the Executable (optional) to the fully qualified path to the isapi_redirect-1.2.40.dll file.
    2. Click Request Restrictions. In the Access tab, set the access to Execute.
    3. Click OK twice to save all changes.
    4. If a confirmation dialog appears, click Yes.
    5. In the Handler Mappings panel, right-click ISAPI-dll. Select Edit Feature Permissions. Ensure that the Execute permission is selected.
  7. 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 isapi_redirect-1.2.40.dll file. Enable the Allow extension path to execute option.
  8. Select your website and double-click HTTP Response Headers. Remove any ASP.NET headers which were automatically created by IIS.
  9. If you require Secure Socket Layer (SSL) authentication for the website, select your website and double-click SSL Settings. Enable the Require SSL option.
  10. Restart the website for the changes to take effect.
Microsoft IIS can now be used to redirect requests to the website.