19.8.4. Configure the ISAPI Redirector to Send Client Requests to JBoss EAP 6


This task configures a group of JBoss EAP 6 servers to accept requests from the ISAPI redirector. It does not include configuration for load-balancing or high-availability failover. If you need these capabilities, refer to Section 19.8.5, “Configure ISAPI to Balance Client Requests Across Multiple JBoss EAP 6 Servers”.

This configuration is done on the IIS server, and assumes that JBoss EAP 6 is already configured as per Section 19.3.6, “Configure JBoss EAP 6 to Accept Requests From External Web Servers”.

Procedure 19.18. Edit Property Files and Setup Redirection

  1. Create a directory to store logs, property files, and lock files.

    The rest of this procedure assumes that you are using the directory C:\connectors\ for this purpose. If you use a different directory, modify the instructions accordingly.
  2. Create the isapi_redirect.properties file.

    Create a new file called C:\connectors\isapi_redirect.properties. Copy the following contents into the file.
    # Configuration file for the ISAPI Redirector
    # Extension uri definition
    # Full path to the log file for the ISAPI Redirector
    # Log level (debug, info, warn, error or trace)
    # Full path to the workers.properties file
    # Full path to the uriworkermap.properties file
    #Full path to the rewrite.properties file 
    If you do not want to use a rewrite.properties file, comment out the last line by placing a # character at the beginning of the line. See Step 5 for more information.
  3. Create the uriworkermap.properties file

    The uriworkermap.properties file contains mappings between deployed application URLs and which worker handles requests to them. The following example file shows the syntax of the file. Place your uriworkermap.properties file into C:\connectors\.
    # images and css files for path /status are provided by worker01
    # Path /web-console is provided by worker02
    # IIS (customized) error page is used for http errors with number greater or equal to 400
    # css files are provided by worker01
    # Example of exclusion from mapping, logo.gif won't be displayed  
    # !/web-console/images/logo.gif=*
    # Requests to /app-01 or /app-01/something will be routed to worker01
    # Requests to /app-02 or /app-02/something will be routed to worker02
  4. Create the workers.properties file.

    The workers.properties file contains mapping definitions between worker labels and server instances. The following example file shows the syntax of the file. Place this file into the C:\connectors\ directory.
    # An entry that lists all the workers defined
    worker.list=worker01, worker02
    # Entries that define the host and port associated with these workers
    # First JBoss EAP 6 server definition, port 8009 is standard port for AJP in EAP 
    # Second JBoss EAP 6 server definition
  5. Create the rewrite.properties file.

    The rewrite.properties file contains simple URL rewriting rules for specific applications. The rewritten path is specified using name-value pairs, as shown in the example below. Place this file into the C:\connectors\ directory.
    #Simple example
    # Images are accessible under abc path
  6. Restart the IIS server.

    Restart your IIS server by using the net stop and net start commands.
    C:\> net stop was /Y
    C:\> net start w3svc

The IIS server is configured to send client requests to the specific JBoss EAP 6 servers you have configured, on an application-specific basis.