Please find the following MSDN article, which describes, the list of programming technologies, that can be helpful to apply in Exchange Collaborative applications.
Some of the of technologies available: ADO, ADSI, CDO, EXOLEDB, LDAP, MAPI, Schema, Search, Store Events, WebDAV, Webforms, WMI Providers.
ActiveX Data Objects (ADO) are used to navigate through Web Storage System. ADO allows the developer to access all Microsoft Database APIs, as well as search for and bind objects. ADO contains built-in objects that the developer can use to add features to the application. This permits developers to add dynamic objects to a static Web page.
ADSI is a standard Windows-based interface for meta-directory applications. A meta-directory is a high-level network directory service designed to unite account and resource information from multiple network operating environments. The goal of ADSI is to synchronize this information across differing directories. Meta-directories extract security and account data from each directory, and then manage this information as part of an external database.
ADSI is comprised of a series of client-side DLLs that provide a common set of directory management functions. You can access these functions from almost any environment. As a result, you can add or remove user accounts, configure shared resources, and browse the directory tree all from a single, integrated console. Exchange 2000 uses ADSI to integrate application services with Active Directory's security and account functions. You can also access ADSI using Microsoft Visual Basic, Scripting Edition (VBScript) and Microsoft Windows Script Host to perform directory maintenance tasks.
Collaboration Data Objects (CDO) was originally called "OLE Messaging" and later "Active Messaging". CDO is a COM wrapper of the MAPI library and can be called from any development language that supports automation. For example, Simple MAPI, CDO is primarily designed for client activities. CDO implements most but not all MAPI functionality, although far more than Simple MAPI.
Some activities that can be accomplished using CDO:
• Log onto the messaging system with specific profiles or with anonymous authentication.
• Compose messages, address and resolve recipients, send, receive, and read messages, add attachments, automate replies.
• Manage calendars; create meetings and appointments.
• Manage folders and messages within the information store.
• Manage Addresses, especially within the Personal Address Book (PAB).
This is a high performance OLE DB driver. The ExOLEDB provider is a server-side component, and is therefore used only to access public stores and mailbox stores that reside on the same server. You can, however, access data on the server remotely by wrapping functionality into Component Object Model (COM) components, which can be utilized by ASP and other Web applications. The ExOLEDB provider is also ideal for use in COM+ components and Exchange store event and workflow sinks that run on the server. To access remote public stores and mailbox stores, use the WebDAV protocol, MAPI, or CDO 1.2.1.
The Lightweight Directory Access Protocol (LDAP) protocol is a distributed, hierarchical directory service protocol that you use to gain access to repositories of users and other network objects. Because LDAP is not typically tightly integrated with the host operating system, information can be kept in both LDAP and in a name service such as Network Information Service. When you use LDAP to gain access to the groups, you reduce redundancy and maximize LDAP's scalability.
LDAP gives you the option of using paged or non-paged results when performing a search. With non-paged results, the maximum number of objects returned is limited by the MaxPageSize constraint on the domain server. With paged results, there is no maximum. You can return all the results. You set the LDAP client page size in the Search Options dialog box. This value cannot exceed the MaxPageSize constraint imposed by the domain server.
MAPI will generally mean MAPI32.dll, or the APIs contained. It's an API, implemented largely in MAPI32.dll (Messaging Application Programming Interface, 32 bit build). By using this, developers implement a series of Providers. Providers come in three major types, Transport Providers, Message Store Providers, and Address Book Providers. Providers are DLLs that implement a specific pseudo COM API, such as IMessageStore, and the underlying required interfaces, such as IMAPIProp.
The Exchange store provides a means to define schema information for items. By using the schema capabilities of the Exchange store, you can make schema information about your application discoverable to schema-aware applications such as the Exchange store Structured Query Language (SQL) query processor.
You can search for items in the Exchange store using a familiar Structured Query Language (SQL) syntax, which is based on the syntax defined by the Microsoft Indexing Service Query Processor.
You can respond to events that occur in the Exchange store programmatically. With events, you can write your own custom logic that executes on the server in response to changes in the data in the Exchange store. Exchange store events occur:
- When Exchange store items are saved, deleted, moved, copied, or modified.
- When a store is started or shut down.
- When a specific time interval has elapsed.
- You can write event sinks that can receive notification of these events.
The World Wide Web Distributed Authoring and Versioning (WebDAV) protocol provides access to an extensible set of associated properties. WebDAV also defines protocol commands used to search, move, copy, delete, lock and unlock resources, and make new collections of resources (folders).
Exchange Web forms is a Web-based forms technology that is built on Internet standards. An Exchange Web form is a Web page that is registered in the form registry of the Exchange store.
Microsoft Windows Management Instrumentation (WMI) supports custom Exchange management and monitoring applications through a set of WMI providers.