Exchange Web Services Managed API Evaluation Criteria
This topic provides information about using the Microsoft Exchange Web Services (EWS) Managed API 1.1 to develop messaging and calendaring applications. The EWS Managed API provides an intuitive managed interface for clients to access Exchange mailboxes by using Exchange Web Services.
EWS messages are sent by means of HTTP and HTTPS and might be blocked by Internet firewalls. The EWS Managed API must be used with applications that work with the Microsoft .NET Framework.
| Criteria | Description |
|---|---|
|
Application Domain |
The EWS Managed API is used in applications that use messaging to send and process e-mail messages and calendar, task, and contact information, and allow programmatic access to mailbox and public folders. |
|
Major Objects |
The EWS Managed API provides proxy objects that provide access to Exchange mailboxes, user settings, and some Active Directory information. |
|
Data Access Model |
The EWS Managed API provides information in a hierarchical set of objects. |
|
Threading Models |
Application threading depends entirely on the client, and does not affect the EWS Managed API. Exchange Web Services uses HTTP or HTTPS, so no connection state information is retained between transactions. |
|
Application Architectures |
Exchange Web Services places no restrictions on the client application architecture. |
|
Remote Usage |
The EWS Managed API is ideal for remotely accessing Exchange. Because Exchange Web Services communicates by using HTTP and HTTPS, corporate firewalls and routers often do not require special configuration. |
|
Transactions |
The EWS Managed API does not support transactions. |
|
Management Capabilities |
The EWS Managed API does not directly provide management capabilities. Exchange Web Services calls that are created by the EWS Managed API generate Windows event log entries. Performance counters are available to measure the performance of Exchange Web Services. |
|
Availability |
The EWS Managed API is available as a download. |
| Criteria | Description |
|---|---|
|
Languages and Tools |
The EWS Managed API is based on the .NET Framework. Any .NET language can be used to develop against the EWS Managed API. |
|
Managed Implementation |
The EWS Managed API is a managed API. |
|
Scriptable |
The EWS Managed API can be used in scripts. |
|
Test/Debug Tools |
Microsoft Visual Studio can be used to debug EWS Managed API applications. The EWS Managed API also contains a tracing feature that captures the SOAP XML messages that are sent and received. |
|
Expert Availability |
It should not be difficult to find developers who have created EWS Managed API–based client applications. |
|
Available Information |
Information about the EWS Managed API is available in the SDK, forums, and blogs. For information specific to the EWS Managed API, see the Exchange Web Services Managed API 1.0 SDK or the Exchange Server 2010 Web Services SDK, developer forums, or the Exchange Server Developer Center. |
|
Developer/Deployment Licensing |
Refer to your Exchange Server and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your EWS Managed API applications are developed and deployed. |
| Criteria | Description |
|---|---|
|
Design-Time Permissions |
No special developer permissions are required for using the EWS Managed API with a computer running Exchange Server. The Exchange server must be configured to allow Web service access, and the developer must have permissions to access the data that the application will use. |
|
Setup Permissions |
Because applications that use the EWS Managed API run on either the client or middle tier, typically no special permissions are needed for setup. If the Setup program makes changes in the Exchange store, the user who is running Setup must have the necessary permissions to make those changes. |
|
Run-time Permissions |
To use an EWS Managed API client application, the client must use a valid domain account to access the computer on which the Client Access server role is installed. |
|
Built-in Security Features |
The EWS Managed API can use NTLM, Kerberos, or Basic authentication. It is recommended that XML requests and responses be sent by means of SSL. |
|
Security Monitoring Features |
Client Access servers use the Microsoft Internet Information Services (IIS) security monitoring features. |
| Criteria | Description |
|---|---|
|
Server Platform Requirements |
The EWS Managed API can be used by Exchange servers that have Exchange Web Services enabled. Exchange Web Services was introduced in Microsoft Exchange Server 2007. Different Exchange server versions support different capabilities; the EWS Managed API can connect to an use functionality in Exchange Server 2007 SP1 and later, and Exchange Server 2010 and later. |
|
Client Platform Requirements |
The EWS Managed API client applications require the .NET Framework 3.5 or later versions. |
|
Deployment Methods |
The EWS Managed API client applications are deployed based on their client architecture and technology. |
|
Deployment Notes |
None. |
