> Installation and Upgrade Guide > Configuring and Verifying IIS

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Configuring and Verifying IIS

This appendix describes how to configure and verify IIS to support the Exchange Remote API. For details on installing the Remote Exchange API, see Installing the Exchange Remote API to Enable Groupware Integration,.

This chapter discusses:

Configuring IIS is the first procedure that you must perform when preparing the system before running the Exchange Remote API installer. For details on all of the procedures required to prepare the system, see Preparing the System for Microsoft Exchange Integration (Windows Only).

After running the Exchange Remote API installer, you must verify proper configuration of IIS.

 

Configuring and Verifying IIS 6.0 on Windows 2003

This section describes pre- and post-installation steps to verify that IIS is configured to support the portal. It includes the following topics:

Configuring IIS

Perform this procedure before installing the Exchange Remote API. Configure IIS on the machine on which you are planning to install the Exchange Remote API.

To configure IIS:

  1. Ensure that you have installed the latest hotfixes for IIS and .NET.

    2. If IIS is not installed on your host computer, use the Manage Your Server utility to add Application Server as a role. This process installs and configures IIS, as well as enables ASP .NET.

  2. Ensure the WWW Service is configured to start automatically. To configure Services:
    1. Click Start | Administrative Tools | Services.
    2. Right-click World Wide Web Publishing Service and then click Properties.
    3. Configure the service to start automatically.
  3. To ensure that .NET is registered in IIS, verify that the .asmx, .aspx, and .asax application extensions have been configured for IIS Web sites, To verify registered application extensions:
    1. In IIS Manager, right-click the Web Sites folder and then click Properties.
    2. Click the Home Directory tab.
    3. Click the Configuration button.
    4. Click the Mappings tab.
    5. In the application extensions box, verify that the .asmx, .aspx, and .asax extensions have been installed and reference the .NET 1.1 aspnet_isapi.dll library.

      6. If .NET has not been registered to IIS, register it with the ASP .NET registration utility., which is located in the .NET Framework installation. For example: 

      C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiiis.exe -i
  4. On Windows 2003, portal components run in IIS 5.0 Isolation Mode. To configure IIS 6.0 for IIS 5.0 Isolation Mode:
    1. In IIS Manager, expand the local computer, right-click Web Sites and then click Properties.
    2. Click the Service tab, select the Run WWW service in IIS 5.0 isolation mode check box, and then click OK.
  5. Configure request handling for Web extensions used by Collaboration. To configure permissions for Web extensions:
    1. In IIS Manager, expand the local computer and click Web Service Extensions.
    2. Use the controls to set ASP .NET to enable request handling.
  6. Verify that IIS Directory Security is configured with a user name - password pair to enable anonymous access:
    1. In IIS Manager, expand the local computer, right-click Web Sites, and select Properties.
    2. Click the Directory Security tab.
    3. Ensure that Enable Anonymous Access is selected and that the user name - password pair is valid.
Note: After installation, you may change security settings according to your security plan. For information on security in the portal, see the Deployment Guide for BEA AquaLogic User Interaction G6 and the Administrator Guide for BEA AquaLogic Interaction Collaboration.

Verifying IIS Configuration

Perform this procedure after installing the Exchange Remote API. Verify IIS configuration on the machine on which you installed the Exchange Remote API.

To verify IIS configuration:

  1. Verify that the portal gateway filter (also known as the Plumtree Gateway filter) has been installed. To display the ISAPI filter stack:
    1. In IIS Manager, expand the local computer, right-click Web Sites and then click Properties.
    2. Click the ISAPI Filters tab and make sure that the Plumtree Gateway filter is installed and ordered above the ASP.NET filter in the stack. If necessary, re-order the stack.
    3. Restart IIS.
  2. Verify that the .pt extension mapping has been added to the portal Web site and is properly configured. To display extension mappings:
    1. In IIS Manager, expand the Web Sites folders to display the portal virtual directory; right-click the portal virtual directory and then click Properties.
    2. Click the Home Directory tab.
    3. Click the Configuration button.
    4. Click the Mappings tab.
    5. In the application extensions box, verify that the .pt extension has been installed; click Edit and verify that the .pt extension references the .NET 1.1 aspnet_isapi.dll and that the Verb list includes GET, HEAD, POST, OPTIONS, PROPFIND, PROPPATCH, MKCOL, LOCK, UNLOCK, PUT, DELETE, COPY, and MOVE.

 

Configuring and Verifying IIS 5.0 on Windows 2000

This section describes pre- and post-installation steps to verify that IIS is configured to support the portal. It includes the following topics:

Configuring IIS

Perform this procedure before installing the Exchange Remote API. Configure IIS on the machine on which you plan to install the Exchange Remote API.

To configure IIS:

  1. Ensure that you have installed the latest hotfixes for IIS and .NET.
  2. To ensure that .NET is registered in IIS, check that the .asmx, .aspx, and .asax application extensions have been configured for IIS Web sites, To check registered application extensions:
    1. In IIS Manager, right-click the Web Sites folder and then click Properties.
    2. Click the Home Directory tab.
    3. Click the Configuration button.
    4. Click the Mappings tab.
    5. In the application extensions box, verify that the .asmx, .aspx, and .asax extensions have been installed and reference the .NET 1.1 library.

      6. If .NET has not been registered to IIS, register it with the ASP .NET registration utility, which is located in the .NET Framework installation. For example: 

      C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiiis.exe -i

Verifying IIS Configuration

Perform this procedure after installing the Exchange Remote API. Verify IIS configuration on the machine on which you installed the Exchange Remote API.

To verify IIS configuration:

  1. Verify that the portal gateway filter (also known as the Plumtree Gateway filter) has been installed. To display the ISAPI filter stack:
    1. In IIS Manager, expand the local computer, right-click Web Sites and then click Properties.
    2. Click the ISAPI Filters tab and make sure that the Plumtree Gateway filter is installed and ordered above the ASP.NET filter in the stack. If necessary, re-order the stack.
    3. Restart IIS.
  2. Verify that the .pt extension mapping has been configured for the portal virtual directory. To display extension mappings:
    1. In IIS Manager, expand the Web Sites folders to display the portal virtual directory; right-click the portal virtual directory and then click Properties.
    2. Click the Home Directory tab.
    3. Click the Configuration button.
    4. Click the Mappings tab.
    5. In the application extensions box, verify that the .pt extension has been installed; click Edit and verify that the .pt extension references the .NET 1.1 aspnet_isapi.dll library and that the Verb list includes GET, HEAD, POST, OPTIONS, PROPFIND, PROPPATCH, MKCOL, LOCK, UNLOCK, PUT, DELETE, COPY, and MOVE.

  Back to Top       Previous  Next