13.6.3. Configure the ISAPI Redirector to Send Client Requests to the JBoss Enterprise Application Platform
This task configures a group of JBoss Enterprise Application Platform 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 13.6.4, “Configure ISAPI to Balance Client Requests Across Multiple JBoss Enterprise Application Platform Servers”.
- You need full administrator access to the IIS server
Procedure 13.13. Task
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.
isapi_redirect.propertiesfile.Create a new file called
C:\connectors\isapi_redirect.properties. Copy the following contents into the file. Substitute the value
JBOSS_NATIVE_HOMEwith the actual location where you installed the JBoss Native components when you performed the task Section 13.6.2, “Configure Microsoft IIS to Use the ISAPI Redirector”.
# Configuration file for the ISAPI Redirector # Extension uri definition extension_uri=JBOSS_NATIVE_HOME/sbin/isapi_redirect.dll # Full path to the log file for the ISAPI Redirector log_file=c:\connectors\isapi_redirect.log # Log level (debug, info, warn, error or trace) # Use debug only testing phase, for production switch to info log_level=debug # Full path to the workers.properties file worker_file=c:\connectors\workers.properties # Full path to the uriworkermap.properties file worker_mount_file=c:\connectors\uriworkermap.properties #Full path to the rewrite.properties file rewrite_rule_file=c:\connectors\rewrite.propertiesIf you do not want to use a
rewrite.propertiesfile, comment out the last line by placing a
#character at the beginning of the line. See Step 5 for more information.
uriworkermap.propertiesfile 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
# images and css files for path /status are provided by worker01 /status=worker01 /images/*=worker01 /css/*=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 /web-console/*=worker02;use_server_errors=400 /web-console/css/*=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 /app-01|/*=worker01 # Requests to /app-02 or /app-02/something will be routed to worker02 /app-02|/*=worker02
workers.propertiesfile contains mapping definitions between worker labels and server instances. The following example file shows the syntax of the file. Place this file into the
# 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 Enterprise Application Platform server definition, port 8009 is standard port for AJP in EAP worker.worker01.host=127.0.0.1 worker.worker01.port=8009 worker.worker01.type=ajp13 # Second JBoss Enterprise Application Platform server definition worker.worker02.host= 127.0.0.100 worker.worker02.port=8009 worker.worker02.type=ajp13
rewrite.propertiesfile 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
#Simple example # Images are accessible under abc path /app-01/abc/=/app-01/images/
Restart the IIS server.Follow the appropriate procedure for restarting your IIS server, depending on its version.
C:\> net stop iisadmin /Y C:\> net start w3svc
C:\> net stop was /Y C:\> net start w3svc
The IIS server is configured to send client requests to the specific JBoss Enterprise Application Platform servers you have configured, on an application-specific basis.