1 / 28

What You Need to Know About Exchange Web Services

Required Slide. SESSION CODE: UNC310. What You Need to Know About Exchange Web Services. Jason Henderson Principal Program Manager Microsoft Corporation. Agenda. Exchange 2010 Online Platform Capabilities Migrating from legacy APIs Exchange 2010 Exchange Web Services Capabilities

sadah
Télécharger la présentation

What You Need to Know About Exchange Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Required Slide SESSION CODE: UNC310 What You Need to Know AboutExchange Web Services Jason Henderson Principal Program Manager Microsoft Corporation

  2. Agenda • Exchange 2010 Online Platform Capabilities • Migrating from legacy APIs • Exchange 2010 Exchange Web Services Capabilities • How to use Exchange 2010 Web Services • Key Take-Aways • It is easy to build rich applications using Exchange Web Services • Exchange Web Services works seamlessly across on-premises and hosted Exchange

  3. Exchange as a Platform

  4. Exchange Web Services APIs The Exchange 2010 Platform • API for interacting with Mailbox Content • Email, Calendaring, Tasks, Contacts • Mailbox Autodiscovery • Authentication and Login • Delegation and Impersonation • Change Notifications • User and Application Settings Configuration Content, Management, Control • PowerShell APIs • API for Exchange Management • Mailbox creation • Server Configuration • Resource Management • Transport APIs • API for controlling the flow of content • Access to message properties and content in transport • Transport Rules

  5. Exchange Server 2010 API Changes API Deprecation Roadmap Exchange Server 2007 Exchange Server 2010 Client Client CDO 1.2.1 CDO 1.2.1 Exchange MAPI Client EWSManaged API PowerShell Outlook Object Model NET.Mail Exchange MAPI Client Outlook MAPI System.NET.Mail OutlookMAPI OutlookObject Model PowerShell Client Access Server Transport Server Client Access Server Transport Server MAPI Exchange Web Services Agents Transport APIs Exchange Web Services Agents Transport APIs Mailbox Server Mailbox Server MAPI WebDav Non-Exchange API Roadmap ExOLE DB CDOEx (3.0) Store Events Deemphasized Virus Scan API VSS Virus Scan API VSS Deprecated

  6. Exchange Web Services

  7. Exchange Web Services Rich Experience • Enables full client functionality • Application logic consistent with Outlook Easy to Use • .NET-based EWS Managed API 1.0 • Full Visual Studio support Online-Ready • Single API for Server and Online • The power of Web Services and .NET NEW For more information:http://msdn.microsoft.com/Exchange

  8. Rich

  9. EWS 2010 Application Functionality • Calendar • Create/Modify/Retrieve Appointments • Retrieve Availability Information • Suggest Best Appointment Time • Time Zone Service • Retrieve Available Rooms • E-mail • Send/Retrieve/Forward/Reply Mail • Retrieve MIME Content • Search/Delete/Move/Copy Mail • Folder Move/Copy/Create/Permissions • Setting Auto-Response Message • Tasks • Create/Delete/Update Tasks • Search for Tasks • Contacts • Create/Update/Delete Contacts • Set picture • Set all properties like e-mail addresses, phone numbers, location • Create Contact Groups

  10. ApplicationsUsingEWS • Service Applications • Like: • Synchronization • Project Server 2010 • CRM Contact Synchronization • Notifications • Auto-Scheduler Applications • Room Availability • Client Applications • Like: • Email Clients • Outlook • Entourage • Apple Mail.app • Free/Busy, VoiceMail, Contacts • Microsoft Office Communicator • Portal Applications • Like: • Web Parts • Shared Calendar Views • 5 Most Recent E-mails • PIM Systems • Course Management

  11. EWS SP1 Functionality Enhancements Exposing the full power of Exchange through the APIs NEW Exchange Web Services Managed API 1.1 Exchange 2010 Exchange Web Services API • Delegate management • Folder permissions • Public folders • Post items • Id conversion • Exchange 2010 SP1 • Exchange 2010 • Create, retrieve and modify Inbox Rules • Programmatic access to Archive Mailbox • Conversations Actions • Firewall traversing Notifications • Improved Administration features • Improved Mixed Version support • Throttling Protection Support • Control Application access to EWS • Client Certificate Authentication support Exchange 2007 SP1 • Full Private Distribution List support • User Configuration Objects • Folder Associated Items • Message tracking • Unified Messaging • SOAP AutoDiscover • Enhanced Time Zone support • Room resource Availability information • Indexed Search • Dumpster Access • MailTips information • Exchange 2007 • Full access to items, folders and attachments: • Create • Get • Update • Delete • Availability • Out of Office settings • Notifications • Synchronization • Name Resolution • Distribution Lists Expansion • Search

  12. Easy

  13. Easy: EWS Managed API Simplifies Coding Coding in the various EWS APIs paradigms available GetFolderType request = new GetFolderType(); request.FolderShape = new FolderResponseShapeType(); request.FolderShape.BaseShape = DefaultShapeNamesType.AllProperties; DistinguishedFolderIdTypeinboxId = new DistinguishedFolderIdType(); inboxId.Id = DistinguishedFolderIdNameType.inbox; request.FolderIds = new BaseFolderIdType[] { inboxId }; GetFolderResponseType response = serviceBinding.GetFolder(request); FolderInfoResponseMessageTyperesponseMessage = response.ResponseMessages.Items[0] as FolderInfoResponseMessageType; if (responseMessage.ResponseClass == ResponseClassType.Success) { FolderType inbox = responseMessage.Folders[0] as FolderType; } <soap:Envelope> <soap:Body> <m:GetFolder> <m:FolderShape> <t:BaseShape>AllProperties</t:BaseShape> </m:FolderShape> <m:FolderIds> <t:DistinguishedFolderIdId="inbox" /> </m:FolderIds> </m:GetFolder> </soap:Body> </soap:Envelope> <s:Envelope> <s:Body> <m:GetFolderResponse> <m:ResponseMessages> <m:GetFolderResponseMessage ResponseClass="Success"> <m:ResponseCode>NoError</m:ResponseCode> <m:Folders> <t:Folder> <t:FolderIdId="..." ChangeKey="..." /> <t:FolderClass>IPF.Note</t:FolderClass> <t:DisplayName>Inbox</t:DisplayName> ... </t:Folder> </m:Folders> </m:GetFolderResponseMessage> </m:ResponseMessages> </m:GetFolderResponse> </s:Body> </s:Envelope> Folder inbox = Folder.Bind(service, WellKnownFolderName.Inbox); Increased Productivity • “After working with Exchange for about 10 years  I can say that this is by far the most intuitive and easy to use API ever and developers who never worked with Exchange before have little trouble using it. “ • – Fortune 500 Financial Services Company Developer Raw XML Auto-generated proxies EWSManaged API • Cross-platform • No client-side logic • Manual plumbing • Multiple platforms • Class-based access • No client-side logic • Windows only (.NET 3.5) • Fully Object Oriented • Smart client-side logic

  14. Using AutoDiscoverSending a Meeting RequestCreating a FolderRetrieving and Creating Inbox RulesUsing Streaming Notifications DEMO

  15. Exchange 2010 SP1Mailbox Server Client Application Exchange 2010 SP1 Web Services Streaming Notifications OpenStreamingConnection Request Notification Subscription Subscription Request Event Data Subscription Response Exchange 2010 SP1Client Access Server

  16. Online Ready

  17. Moving Exchange into the Cloud Roadmap for Exchange Cloud Development • Traditional Development • Exchange on Premise • Applications on Premise • Hybrid S+S Software • Exchange in the cloud (Exchange Online) • Applications on Premise • Pure Cloud Development • Exchange in the Cloud (Exchange Online) • Applications in the Cloud (Azure)

  18. Application Impersonation Enable middle-tier application to access user data without username/passwords Create model for “Impersonating” a user that is secure and easy Exchange 2010Mailbox Server Client Application Server AppServer granted the ApplicationImpersonation role to John’s department AppServer verifies John’s identity Request for calendar data made “as” John AppServer$\ NetworkService Impersonating “John” “John” authenticates with http:/appserver John Exchange 2010Client Access Server

  19. Moving from on-premises to Exchange Online • Plan for throttling and minimize your load on Exchange • Think through cloud deployment and application provisioning • Determine the authentication model that works best • End User Credentials • Application Impersonation for service account access

  20. Review You have learned… • Exchange 2010 Online Platform Capabilities • Exchange Web Services • Remote PowerShell • Transport Rules • Exchange 2010 Exchange Web Services Capabilities • How to use Exchange 2010 Web Services • Using AutoDiscover • Creating a meeting request • Creating a folder • Creating and retrieving rules • Using Streaming Notifications

  21. Additional Resources • Learn about Exchange Online • http://microsoft.com/online • Learn more about Exchange Web Services • MSDN • http://msdn.microsoft.com/en-us/library/bb204119(EXCHG.80).aspx • Download the Exchange Web Services Managed API 1.0 • “Inside Microsoft Exchange 2007 Web Services” – Available from MS Press • Hands On Lab • http://blogs.msdn.com/exchangedev/

  22. Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Related Content • Breakout Sessions • UNC 207: Building Communications Enabled Business Processes with Microsoft Communications Server “14” • UNCS 322: The New Microsoft Communicator “14” SDK: Integrating, Extending and Adding Contextual Data to the New Communicator Experience • UNC 401: Advanced SIP-Based Solutions Built on the Microsoft Unified Communications Managed API 3.0 and Microsoft Communications Server “14”

  23. Unified Communications Track Call to Action! Learn More! • View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online • Visit microsoft.com/communicationsserver for more Communications Server “14” product information • Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter • Check out Microsoft TechNet resources for Communications Server and Exchange Server • Visit additional Exchange 2010 IT Professional-focused content • Partner LinkorCustomer Link (Name: ExProPword: EHLO!world) Try It Out! • Exchange 2010 SP1 Beta downloadis now available from the download center!

  24. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

  25. Required Slide Complete an evaluation on CommNet and enter to win!

  26. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

  27. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

  28. Required Slide

More Related