Exchange Adapter Server

Top  Previous  Next

What is the Exchange Adapter Server?

The Exchange Adapter Server provides Email, Contacts, Tasks* and Calendar support for Exchange ActiveSync (EAS) devices.  It does this by transforming Domino data  to present it to EAS clients devices as Exchange ActiveSync data and vice versa and thereby allowing it to work with the EAS client's native Email, Contacts and Calendar applications.  Supported EAS clients include Apple iPhone/iPod, Palm Pre/Pixi, various Android devices (including both native and "RoadSync" EAS implementations), Nokia Symbian Series 60 3rd and 5th edition devices with Nokia's 'Mail for Exchange'.


* Currently, no EAS enabled Tasks application is available for the iPhone.


By default, the Exchange Adapter Server is set not to run and so, if you want to support EAS clients, you need to configure and enable it.


       Configuring the Exchange Adapter Server

1.Expand the Configuration node in the navigation tree and select Servers and Groups.  The action pane will display the configured servers.
2.Right mouse click the server and select Properties from the pop-up menu.
3.Select the Exchange Adapter Server tab.  It will highlight the currently active template, by default (Default Exchange Adapter Settings).  We recommend that you do not change this.  Click the Configuration Wizard button - the one with the magic wand icon.
4.On the Welcome screen, if you are supporting Exchange ActiveSync (EAS) clients e.g. iPhone, Palm Pre, Android make sure that the box Run the Exchange Adapter Service is checked and then click the Next button.  If you are not supporting EAS clients, leave the box unchecked and skip the remaining steps on this page.
5.On the Exchange Adapter General Settings page, you can configure the TCP address and port that the Exchange Adapter server listens on for EAS devices.  This is normally configured as * (all addresses) and port 615.  Do not change this from the default value unless there are port conflicts.  This port will normally be used only for internal (e.g. in-house wireless LAN) connections.  External (e.g. cellular) connections will normally connect via an mSuite Proxy or the CommonTime Switching Center (CSC).
6.Now select the certificate that will be used for the SSL encryption. The default is mSuite CA, this is the self signed certificate created by the mSuite installer.   This is OK if you are using the CSC - however, if you are using your own mSuite Proxy, you will need to use your own certificate.  This certificate will be installed on and served up by the Exchange Adapter but the certificate must relate to the machine where the mSuite Proxy is installed because that is the machine that devices actually connect to (devices are not aware that their connections are forwarded to the Exchange Adapter server).

Note: The characteristics of the certificate are described here.  To change to another certificate, that certificate must be installed on the machine running the Exchange Adapter and appear in the list of available certificates.  If this is not the case, use the Add certificate button to include your certificate and then select it from the list.

7.If you are using your own Proxy (DMZ or Local) then you can configure the system to only allow secure (SSL) connections from EAS devices by unchecking the box marked Allow non-secure connections.
If you are using the CommonTime Switching Center (CSC), the Allow non-secure connections box must be checked even if the devices are using SSL.
8.(New in version 5.14) On the Exchange Adapter Device Settings screen, uncheck the box(es) for any device type(s) that will not be allowed to replicate.
9.Click Next to continue then click Finish to complete the wizard.
10.Restart the Exchange Adapter Server to implement the configuration changes.
11.Unless you are using the CommonTime Switching Center (CSC), you must now configure an Enterprise or Local proxy see: Proxy Installation. The Exchange Adapter will take its proxy configuration from the CMS configuration - using the same IP and Port as the CMS to communicate to the Local or Enterprise proxy.



 Palm Pre SSL Certificates

SSL certificates can be a source of problems with the Palm Pre.

The certificate used by the server must have a trusted root on the device - this means that if you are using a self signed certificate, you must get the root onto the device by some means.
Public SSL certificates issued by organizations like Verisign, Thawte etc. should work OK.
The EAS server must be a hostname that is in the DNS.  From version 1.1 of WebOS, IP address is also supported as an alternative to hostname.
The SSL certificate must be issued for the host or IP being used - the device will check that the certificate matches the name or IP address.
SSL is optional, use http://myserver.mydomain.myext when configuring the device for non-SSL or https://myserver.mydomain.myext for SSL


For more information see: or contact Palm support.

Page url: