2 out of 2 rated this helpful - Rate this topic

EWS Managed API evaluation criteria

Exchange

Published: July 16, 2012

Find evaluation criteria information for using the EWS Managed API to develop messaging and calendaring applications.

Applies to:  EWS Managed API | Exchange 2013 | Exchange Online | Exchange Server 2007 | Exchange Server 2007 Service Pack 1 (SP1) | Exchange Server 2010 | Office 365 

In this article
Functional criteria for the EWS Managed API
Development criteria for the EWS Managed API
Security criteria for the EWS Managed API
Deployment criteria for the EWS Managed API
Additional resources

The EWS Managed API provides an intuitive managed interface for clients to access Exchange mailboxes by using Exchange Web Services (EWS). This article provides information that will help you decide whether the EWS Managed API is the right development technology for your application.

Note Note

EWS messages are sent by means of HTTP and HTTPS and might be blocked by Internet firewalls.

The following table lists and describes the functional criteria for the EWS Managed API. For descriptions of the functional criteria, see Functional criteria in the Exchange development technology evaluation criteria descriptions article.

Table 1:  EWS Managed API functional criteria

Criterion

Description

Application function

The EWS Managed API is used to create applications that send and process email messages and calendar, task, and contact information, and allow programmatic access to mailboxes, public folders,  and public folder mailboxes.

Availability

The EWS Managed API is available for download from the Microsoft Download Center. It can be used with Exchange Online as well as Exchange on-premises. You can use the EWS Managed API to access EWS in versions of Exchange starting with Exchange 2007 Service Pack 1 (SP1).

Application architectures

EWS does not restrict the client application architecture.

Remote usage

The EWS Managed API is ideal for accessing Exchange remotely. Because the EWS Managed API uses EWS to communicate by means of HTTP and HTTPS, corporate firewalls and routers often do not require special configuration.

Major objects

The EWS Managed API includes proxy objects that provide access to Exchange mailboxes, user settings, and some Active Directory Domain Services (AD DS) 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. The EWS Managed API uses EWS to communicate by means of HTTP or HTTPS; therefore, connection state information is not retained between transactions.

Transactions

The EWS Managed API does not support transactions.

Management capabilities

The EWS Managed API does not provide management capabilities directly. EWS calls that are created by the EWS Managed API generate Windows event log entries. Performance counters are available to measure the performance of EWS.

The following table lists and describes the development criteria for the EWS Managed API. For descriptions of the development criteria, see Development criteria in the Exchange development technology evaluation criteria descriptions article.

Table 2:  EWS Managed API development criteria

Criterion

Description

Languages and tools

The EWS Managed API is based on the .NET Framework. You can use any .NET Framework language to develop against the EWS Managed API.

Managed implementation

The EWS Managed API can be used with managed code such as C# or other .NET languages.

Scriptable

The EWS Managed API cannot be used in a scripting language and must be used with a compiled code language such as C#.

Test/debug tools

You can use Visual Studio 2010 or a later version 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

Developers who have created EWS Managed API–based client applications are readily available. You can find developer support for the EWS Managed API by visiting the Exchange developer forum.

Available information

Information about the EWS Managed API is available in the MSDN library and in forums and blogs. For information specific to the EWS Managed API, see Explore the EWS Managed API, the Exchange Development forum, and 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.

The following table lists and describes the security criteria for the EWS Managed API. For descriptions of the security criteria, see Security criteria in the Exchange development technology evaluation criteria descriptions article.

Table 3:  EWS Managed API security criteria

Criterion

Description

Design-time permissions

No specific permissions are required in order to use the EWS Managed API to develop against Exchange. The Exchange server must be configured to allow your application to access the web service, and you 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 the middle tier, no specific permissions are required for setup. If the Setup program makes changes in the Exchange store, the user who is running Setup must have the permissions to make those changes.

Run-time permissions

To use an EWS Managed API client application, the client must have a valid domain user 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. We recommend that XML requests and responses are sent by means of SSL to encrypt any sensitive information.

Security monitoring features

Client Access servers use the Internet Information Services (IIS) security monitoring features.

The following table lists and describes the deployment criteria for the EWS Managed API. For descriptions of the deployment criteria, see Deployment criteria in the Exchange development technology evaluation criteria descriptions article.

Table 4:  EWS Managed API deployment criteria

Criterion

Description

Server platform requirements

The EWS Managed API can be used by Exchange servers on which EWS is enabled. The EWS Managed API can use functionality in versions of Exchange starting with Exchange 2007 Service Pack 1 (SP1).

Client platform requirements

EWS Managed API client applications require the .NET Framework 3.5 or a later version.

Deployment methods

EWS Managed API client applications are deployed based on their client architecture and technology.

Deployment notes

None.

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.