– Fresh install of WindowsServer 2003 R2 (includes SP2)
– Running IIS v6, DNS, ActiveDirecory and Tomcat services.


A) Add the ISAPI redirector to Tomcat.

1. Go to and download isapi_redirect-1.2.26.dll to any suitable temporary folder.

2. Browse to Your_Path_to_Tomcat\bin\ and create a folder ISAPI. In my test environment it is C:\xampp.151\tomcat\bin\ISAPI.

3. Rename recently downloaded isapi_redirect-1.2.26.dll to C:\xampp.151\tomcat\bin\ISAPI\isapi_redirect.dll

B) Back up and modify two Tomcat properties files.

1. Go to Your_Path_to_Tomcat\conf\ and back up the and files.

2. Create the file. In my test environment, it looks like this:


# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
workers.java_home=C:\Program Files\Java\jdk1.5.0_11\

# You should configure your environment slash... ps=\ on NT and / on UNIX
# and maybe something different elsewhere.

# The workers that your plugins should create and work with

#------ DEFAULT ajp13 WORKER DEFINITION ------------------------------
# Defining a worker named ajp13 and of type ajp13
# Note that the name and the type do not have to match.
2.c Create file. In my test environment it's 
contents is as follows:


C) Create and adjust some registry keys and string values required by isapi_redirect.dll.

In my test environment they are as follows:

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation]

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi 

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi 

D) Make IIS v6 modifications.

1. Start IISManager (click Start > Run… > inetmgr).

2. Under Web Sites, right-click on the Default Website.

3. Select New > Virtual Directory and click Next.

4. Specify jakarta for the Alias and click Next.

5. Browse to Your_Path_to_Tomcat\bin\ISAPI\ and click Next.

6. Select Read and Execute (such as for ISAPI applications or CGI) and click Next to
complete the wizard.

7. Under Web Sites, right-click on the Default Website and go to Properties.

8. Click the ISAPI Filters tab.

9. Click Add and specify jakarta for Filter Name and Your_Path_to_Tomcat\bin\ISAPI\isapi_redirect.dll for Executable.

10. Under Web Sites, right-click on Web Services Extensions.

11. Select Add a new Web service extension

12. Specify Tomcat for Extension name and Your_Path_to_Tomcat\bin\ISAPI\isapi_redirect.dll for Required files.

13. Check Set extension status to Allowed.

These modifications are continued in Part F below.

E) Install eGuide and resolve it’s incompatibilities with JDK 1.5.0_XX

1. Install eGuide as usual to Your_Path_to_Tomcat\webapps\ folder
In my test environment it is C:\xampp.151\tomcat\webapps\

2. Go to and download to any suitable temporary folder. Now
extract its contents to the same temporary folder.

3. Browse to \xalan-j_2_5_1\bin and copy the following three files to Your_Path_to_Tomcat\webapps\eGuide\WEB-INF\lib:


In my test environment it is C:\xampp.151\tomcat\webapps\eGuide\WEB-INF\lib

4. Browse to Your_Path_to_Tomcat\webapps\eGuide\ and copy the index.html file to C:\Inetpub\wwwroot\ folder which is default Home Directory for IIS6.

F) IIS v6 Modifications (continued)

1. Under Web Sites, right click on the Default Website.

2. Select New > Virtual Directory and click Next.

3. Specify eGuide for Alias and click Next.

4. Browse to Your_Path_to_Tomcat\webapps\eGuide\ and click Next.

5. Select Read and click Next to complete the wizard. The eGuide virtual directory is necessary for IIS6 to serve static components of eGuide, such as .GIF images and so on.

6. Under Web Sites, right-click on the Default Website and go to Properties.

7. Click the Documents tab.

8. Click Add and specify index.html as the default content page. Use the Move Up button to make it “upper”.


1. Restart both Tomcat and IIS v6.

2. Open up your favorite browser and type in http://localhost/jsp-examples/

Note: The last “/” is important to get the best results. If you type “http://localhost/jsp-examples” without the last “/” you will get a “Page
not found” error. If something goes wrong here, recheck your registry values and and files.

3. Type in http://localhost/servlets-examples/ and verify your results.

4. Type in http://localhost and you should see the eGuide Setup page.

eGuide Setup to access MAD

You will be prompted for some eGuide configuration parameters. If you really want to access MAD via eGuide, you should specify the parameters here, very carefully. Obviously, you can’t use some of the advanced features like RBS with MAD.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

By: 9159506
Apr 1, 2008
8:23 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow