Show TOC

 Implementing the Exchange TransportLocate this document in the navigation structure

Purpose

Implementing the Groupware Transport for Microsoft Exchange connectivity.

Process

Based on Multiple Domain Considerations you can choose to Install your IIS (MSX-A components) in a separate box, in the Portal server or in the Exchange server. 

Note
Note  Use IIS Version 5.0 or above.

Configure the J2EE engine with the appropriate proxy settings for accessing your IIS.

Note

Consider the following for CDO 1.21 installations:

  • If you are installing IIS on the Exchange server ensure that CDO1.21 is also installed with Exchange server.
  • If you are not installing IIS on the Exchange server, install Microsoft Outlook with CDO 1.21 on the IIS server.
  • Never install Outlook with CDO on the Exchange server. It overwrites the registry entry at HKEY_CLASSES_ROOT\CLSID\{3FA7DEB3-6438-101B-ACC1-00AA00423326}\InprocServer32. This might affect the OWA functionality of Exchange Server.

If you are using CDO installed with Outlook, Outlook should be the default e-mail client. You can check whether Outlook is the default e-mail client by checking the following registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail.

If you are using CDO installed with Outlook 2000, Outlook should be configured to access corporate/Workgroup. To check this, start Outlook 2000 and choose Tools  →   Options. On the Mail Services tab, choose Reconfigure Mail Support and follow the instructions that appear.

To enable SSO using Kerberos authentication, the SSO2KerbMap ISAPI module must be installed and configured. For more information, see SAP note 735639 and 922040.