Application Domain
Application Domain
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. This topic provides information about how the different technologies compare with regard to Application Domain.
| Technology | What types of applications is this technology used for? |
|---|---|
| Active Directory Services Interfaces (ADSI) | When you are using ADSI to access the Active Directory® directory service, you can use many different application types. Active Directory stores information about resources and resource users in one or more organizations. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | CDOSYS is used in applications that create and send messages by using the SMTP and NNTP protocols, and that create Active Server Pages (ASP) applications that have messaging capabilities. CDOSYS also includes transport event sinks, which are described separately. |
| CDOSYS SMTP/NNTP Event Sinks | The event sink features of CDOSYS are typically used in applications that append disclaimers or other notices to e-mail sent through your server, archive messages, detect and discard unsolicited bulk mailings, detect and discard inappropriate newsgroup postings, check inbound messages for viruses, forward and filter messages automatically, and so on. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | CDOEX is used in applications that use messaging to send and process e-mail, calendar, and contact information, as well as allow programmatic access to mailbox and public folders. Note that CDOEX can only be run from a computer on which Microsoft® Exchange is installed. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | CDOEXM is used in administrative applications and scripts to control, examine, and diagnose Exchange servers and stores. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | CDOWF is used within workflow processing systems, enabling them to define and control workflow processes, and to respond to workflow events that are part of those processes. |
| Exchange OLE DB Provider (ExOLEDB) | Applications that use ExOLEDB typically access information from the Exchange store by using SQL queries. ExOLEDB can be used to retrieve and manipulate all types of data in the Exchange store that the user has permission to access. ExOLEDB also provides full-text search capability over items in the Exchange store. |
| Exchange Store Event Sinks | Exchange store events are used to respond to occurrences within the Exchange store. These typically include timers, notifications, automatic categorization, workflow applications, item validation, and Exchange store maintenance. |
| Exchange Web Forms | Applications that use Exchange Web forms typically leverage the authenticated remote-access capabilities of Outlook Web Access to display information about items in the Exchange store in a manner that is not already available. Custom forms stored in Exchange can mix-and-match functionality from the Exchange Web Forms renderer and Active Server Pages with HTML. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | Applications can use WebDAV to access folders, items, and item properties in the Exchange store. WebDAV is an extension to HTTP/1.1, and so can more easily be used across firewalls. Because WebDAV is a standard protocol, more choices are available for the client platform and client programming language. |
| WebDAV Notifications | WebDAV notifications are typically used in remote client applications that already use WebDAV to communicate with the Exchange server. Typical applications include Web-based messaging clients and collaboration applications that are using Exchange public folders. |
| Incremental Change Synchronization (ICS) | Applications that use ICS typically synchronize changes between Exchange an non-Exchange information stores. ICS can also be used for one-way and two-way synchronization between Exchange stores. |
| Lightweight Directory Access Protocol (LDAP) | Applications that use LDAP typically retrieve or manage user- and computer-resource information stored in a directory service such as Active Directory. Because Exchange uses Active Directory to store user and configuration information, LDAP is used to communicate with the directory in applications that manage users and server configuration. |
| Messaging Application Programming Interface (MAPI) | Client applications that use MAPI access user mailbox and public folder information stored in Exchange, and user directory information stored in Active Directory. Client applications that use MAPI are typically e-mail clients and applications that require complex e-mail processing. |
| Outlook Object Model (OOM) | Applications that use the OOM typically perform user-specific message handling, mailbox cleanup, and so on. In environments where Outlook is consistently available, small custom applications are sometimes created that use OOM for making changes in the user's mailbox or public folders without using more complex development technologies. OOM is sometimes used for message processing in an ad-hoc workflow process, especially where access to the Exchange server is not permitted. |
| Outlook Web Access | Modifications to Outlook Web Access are typically minor stylistic or graphical modifications to the display theme. Major modifications to Outlook Web Access are not recommended or supported. Some customers reverse-engineer the URLs that Outlook Web Access uses to display mailbox and public folder information, such as Inbox data, Calendar, and Contacts. They then use those URLs inside other Web-based applications, consoles, or portals. This use of Outlook Web Access is also not recommended. |
| Exchange Rules | Exchange rules are typically used to specify user-defined actions that are to be performed on messages that arrive in folders of the user's mailbox. In addition, it is possible to use a set of predefined rules on public folders. |
| SMTP Event Sinks | Typical applications that use SMTP events include virus scanners, mailing list services, message routing services, queuing applications, local delivery mail storage, and protocol command extensions. |
| Windows Management Instrumentation (WMI) providers for Exchange | WMI applications that use the Exchange providers are intended for system monitoring and management consoles, administrative migration, analysis, and maintenance scripts. |
| Exchange Backup and Restore API | Applications use this API to back up and restore Exchange storage groups and databases. |
| Exchange writer for the Windows Volume Shadow Copy Service | Applications use VSS to back up and restore Microsoft Exchange Server 2003 storage groups. |
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: June 2006
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.