Integration with IIS

Answer:
If you have the flexibility to install XC Connect on another computer that is not running IIS this will save you a certain amount of headaches with IIS.

The hardware requirements for the XCN Server are *very* minimal - i.e. you do not need a high-powered machine to run XC Connect and/or XC Vault.

Also, please note that if you perform these integration steps on an existing Microsoft Exchange Server running IIS 6, Outlook Web Access will no longer be available upon enabling IIS 5.0 Isolation Mode.  This is a limitation of the IIS->Tomcat connector and is not something we can control.

As an alternative to integrating with IIS you can access Xchange Network's instance of Tomcat directly by appending :8080 to any URLs.  For example, the Administration page would be http://[server]:8080/xcnetwork/admin/.  This will allow you to use all existing MIcrosoft Exchange functionality (OWA included) and you do not have to perform the integration steps below.  Please note that this will require opening up port 8080 in your server's firewall if needed.

Integration Steps:

1. Download iis_integration.zip from here and save it to a temporary location.

2.  If you have already installed our software with IIS running continue to Step 3. Other install our software with IIS running.  It will detect that IIS is running, and try to handle it by installing to only listen on port 8080. When the window pops open to tell you this, click "OK" and continue. The installation is complete when the "Getting Started" page pops open in your browser. At this point you can close your browser and continue to step 3.

Note: If you click the "Getting Started" link which attempts to start the Server Setup Wizard, you will get a new browser window with an error message or a blank screen. Ignore this, close the browser and continue to step 3.

3.  Once the installation is complete, unzip the IIS integration files supplied to you by Support to the c:\xcnetwork\ directory (all paths in the zip are relative to the c:\xcnetwork directory).  Say 'Yes' to any overwrite messages.

4.  In the c:\xcnetwork\common\ directory, there should be a file called iis_redirect.reg.  Double-click on this file to insert the contents into the registry, and accept the changes.

5.  Open up the IIS Configuration Manager (Start -> Settings -> Control Panel -> Administrative Tools -> Internet Services).

6.  Right-click on 'Default Web Site' and select New -> Virtual Directory.  Hit 'Next' and then for the alias enter 'jakarta' and click on 'Next'.  For 'Directory', browse to c:\xcnetwork\tomcat\bin and click on 'Next'.  On this page, check the 'Execute (such as ISAPI applications or CGI)' box and click on 'Next'.  Finally, click on 'Finish' to complete the virtual directory creation.

7. Right-click on 'Default Web Site' again and select 'Properties'.  Select the 'ISAPI Filters' tab and click on 'Add'.  For the 'Filter Name' enter 'jakarta' and for the 'Executable' browse to :\xcnetwork\tomcat\bin\isapi_redirector.dll.  Click on 'Ok' and then click on 'Ok' again to close the properties dialog.

8.  Lastly, right-click on 'Default Web Site' and select 'Stop'.  Then, right-click again on 'Default Web Site' and select 'Start'.

9.  At this point, IIS is fully configured and now Tomcat needs to be restarted.  To do this, go to Services (Start -> Settings -> Control Panel -> Administrative Tools -> Services) and find the XCNetworkApp service.  Right-click on this service and select 'Properties' and make sure the
'Startup type' drop-down says 'Automatic'.  Next, click on 'Stop' to stop the service and then click on 'Start' to start the service again.  Finaly, click 'Ok' to close the dialog.

10.  For IIS 6 (Windows Server 2003):  Two extra steps are necessary.  If you have an earlier version of IIS, skip these steps.

a.  Open up the IIS Configuration Manager (Start -> Settings -> Control Panel -> Administrative Tools -> Internet Services) if it is not already open.  Right-click on 'Web Sites', choose 'Properties', and go to the 'Service' tab.  Check the 'Run WWW service in IIS 5.0 isolation mode' box.  When you hit 'Apply' or 'OK' you will be informed you need to restart IIS and whether you wish to now. This restart is required and will bring your website down for about 5 seconds.

b.  In the IIS Configuration Manager, right-click on 'Web Service Extensions' and choose 'Add a new web service extension...'.  For the 'Extension name' enter 'Tomcat'.  Then, click 'Add...' and browse to c:\xcnetwork\tomcat\bin\ and choose isapi_redirector.dll.  Finally, check the 'Set extension status to Allowed' and click 'Ok'.

11.  Now, Tomcat and IIS should be working together, so you should be able to access the Xchange Network Server's admin page via the URL: http://localhost/xcnetwork/admin/.

Troubleshooting:

If when you select the link above you get a 404 or 'Page cannot be found error', please ensure that you created the virtual directory 'jakarta'. Also, make sure that you have executed the registry change detailed in step 3.

If when you click on the link above you get a 500 error, or 'Page cannot be displayed', make sure that you have executed the registry change from step 3.  At this point you should also make sure that the filter has been loaded properly by IIS.  To do that, go to the IIS admin console and right-click on 'Default Web Site' and select 'Properties'.  Choose the ISAPI Filters tab and make sure that the 'jakarta' filter is present, and that there is a green up arrow next to it on the left.  If this is not the case, please try removing and adding the filter again, and then restarting the IIS Admin Services service and stopping and starting the 'Default Web Site'.

If you are still having problems accessing the admin page through IIS, please contact support@xcnetwork.com so that we can further diagnose your problem.

Please rate this article (1 being worst, 5 being best):
1 2 3 4 5

Click here to send specific feedback about this article.

home products buy now try now xc bridge partners support contact about us knowledge base site map privacy