Platform SDK: Exchange Server |
You can add services to Microsoft Exchange Server systems by extending the Microsoft Exchange Server Administrator program or by developing a separate server application.
The Administrator program is used to perform operations such as creating mailboxes, managing basic Microsoft Exchange Server components, and managing directory objects. You can extend the Administrator program by adding custom property pages and adding application-specific extension data.
Server applications for Microsoft Exchange Server interact with user services such as the information store and the directory. Server application components can reside on a server running Microsoft Exchange Server, or on any computer running Windows NT Server, even if that system is not running Microsoft Exchange Server.
Microsoft Exchange Server runs as a mail server on the Windows NT Server operating system, which allows it to take advantage of the platform's reliability, scalability, and multitasking capabilities. For example, Windows NT Server multitasking allows Microsoft Exchange Server to simultaneously update directory information, transfer information to a client, and route information to other servers and foreign systems.
The following figure shows how clients such as the directory and the information store access Microsoft Exchange Server services with complete independence from the underlying network. All communication between clients and services in the Microsoft Exchange Server environment is handled through remote procedure call (RPC) messages that can travel over almost any type of network, including Novell NetWare, Microsoft networks, and TCP/IP.
Client access of services running on Microsoft Exchange Server
Because services running on Microsoft Exchange Server support standard interfaces such as MAPI, clients can access them the same way they access other MAPI service providers. This simplifies Microsoft Exchange Server client application development. Programmers use APIs that they may have already used to access other MAPI services. Using these open interfaces, developers can build applications that include electronic mail, group scheduling, forms routing, bulletin boards, and workflow automation. Microsoft Exchange Server also allows existing MAPI-compliant applications from third-party vendors to interact with services running on Microsoft Exchange Server.