`
`Exhibit
`
`2005
`
`Exhibit
`
`2005
`
`
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporalion. All rights reserved
`
`WOSA Backgrounder: Delivering Enterprise Services to the
`Windows-based Desktop
`
`Created: July 1993
`
`Abstract
`
`In-today's enterprise computing environment it's vital to provide users with seamless access to a
`wide range of services across multiple platforms. WOSA does this by providing developers with the
`interface necessary to build Microsoft® WindowsTM-based applications that integrate these services.
`
`Overview
`
`Ever since the first personal computer was connected to a mainframe, information systems (IS)
`managers have been integrating information from a variety of sources. Today, this isn't just an
`option, it's a necessity. To stay competitive, organizations must provide their PC users with easy
`access to the full range of resources in their enterprise computing environments. As information
`services have become more specialized, however, the process of integrating these resources has
`become more complicated.
`
`WOSA makes it easier to integrate enterprise computing services
`
`Windows™ Open Services Architecture (WOSA) provides a single, open-ended interface to
`enterprise computing environments, hiding the programming complexities from users and
`application developers. Microsoft® Windows-based desktop applications that take advantage of the
`WOSA interface enable users to enjoy seamless access to available information without having to
`know anything about the type of network in use, the types of computers in the enterprise, or the
`types of back-end services available. As computing environments and information resources
`change, business applications built using WOSA will still work. In other words, WOSA not only
`enables Windows-based applications to connect seamlessly to a/l the resources users need, but it
`also protects a corporation's technology investments.
`
`WOSA consists of three categories of services, including common application services,
`communication services, and vertical market services. WOSA common application services include
`components which allow Windows-based applications to seamlessly connect with different
`vendor-implementations of information services; WOSA communication services provide
`applications standard access to network communications; and WOSA vertical market services
`enable Windows-based applications to access specialized services found in specific vertical
`markets.
`
`Common application services
`
`II Open Database Connectivity (ODBC) allows seamless access across heterogeneous database
`systems from within Windows-based applications.
`
`II Messaging Application Program Interface (MAPI) allows mail-enabled Windows-based
`applications to communicate and interoperate with multiple mail services.
`
`III Windows Telephony allows desktop applications to access corporate telephone networks no
`
`Backorounders and White Papers
`
`Paoe 1
`
`Microsoft Develooment Librarv
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Wmdows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All rights reserved.
`
`matter the type of telephone network or the type of PC-telephone connection.
`
`III
`
`License Service Application Program Interface (LSARI) makes it easier for corporations to
`implement centralized software license management.
`
`Communication services
`
`II Windows SNA Application Program Interface standardizes a corporation's method for host
`connectivity by providing open access to IBM® SNA API categories .
`
`.. - Windows Sockets allows Windows-based applications to access network services across
`multiple transport protocols such as TCP/IP, IPXlSPX and AppleTalk®.
`
`l1li Microsoft RPC is a remote procedure call facility that is compatible with the Open Software
`Foundation's DCE RPC, making it easier to build distributed client-server applications across
`heterogeneous networks.
`
`Vertical market services
`
`.. WOSA Extensions for Financial Services provide Windows-based applications with a standard
`interface to services common in the banking industry.
`
`l1li WOSA Extensions for Real-Time Market Data allow Windows-based applications to receive live
`market data from many different sources.
`
`These nine WOSA components make Windows an open platform which truly integrates the
`important computing resources that are integral parts of the enterprise environment.
`
`A common interface brings consistency and stability
`
`The Windows operating system presents users with a consistent application interface. Once users
`learn how to use one application, they can quickly learn others. Similarly, WOSA presents
`programmers of distributed applications with a consistent interface for communicating with back-end
`services such as database managers and messaging systems. Instead of learning a different set of
`application programming interfaces (APls) for every vendor's implementation of a service,
`programmers building applications with WOSA only need to learn a single set of APls for all
`implementations of a particular service. Furthermore, when an existing service is modified or
`replaced, the front-end application is unaffected if the new back-end service communicates using
`the WOSA interface.
`
`WOSA also provides tremendous benefits for corporate developers by making it possible to
`integrate custom business applications with packaged software. IS managers can select
`Windows-based application software according to the task at hand,. and not be limited to choosing
`applications solely because they happen to work with products that are already in use. WOSA is
`supported by the Microsoft Windows family of operating systems, including Windows, Windows for
`Workgroups, and Windows NPM.
`
`WOSA and Information at Your Fingertips
`
`Microsoft's vision of computing encompasses the entire enterprise. The long-range goal is to make
`the PC the best way to get information. We call this vision Information at Your Fingertips. By making
`the PC the center of information access for the corporation, individuals and organizations are
`
`Backarounders and White Papers
`
`Pace 2
`
`Microsoft Development Librarv
`
`

`

`WOSA Backgrounder: Delivering Enterprise Services to the Wmdows-based Deskrop
`(c) 1992. 1993 Microsoft Corporation. All rights reserved.
`
`empowered as information becomes increasingly easy to find and use.
`
`The Windows operating system and WOSA are critical components of this vision. Windows provides
`a proven graphical user interface that makes users more productive. And WOSA provides a
`standard and reliable way to integrate the wide variety of enterprise services today's users need .
`
`.6Jlplicaticn 1
`
`Database 1
`
`Database 2
`
`AllX:'r natillE' 1: Diif(>ren t applica tioos for ea ch da~aba se
`
`ftpplicatien
`
`Database 1
`
`Database :2
`
`AllPrnative 2~ Unique data base aooess: call' fer l'ach ddtabdsl'
`
`Alternative application deSigns for accessing multiple databases. Adding support for
`multiple databases traditionally has meant either that users must learn additional
`applications or that developers must invest additional time, effort, and money to modify
`applications.
`
`Managing Heterogeneous Computing Environments
`
`In the absence of a consistent way to connect front-end applications to various back-end services,
`developers are forced to incorporate support for vendor-specific APls into their applications. This
`means that in order to support multiple services they have either had to build new applications or
`modify existing ones to accommodate multiple sets of APls.
`
`Typically, users must learn a new application for each information source. As more information
`sources are added, users are required to deal with the system's underlying complexity. This results
`in an appreciable loss of productivity.
`
`For example, consider an executive information system (EIS) that was designed to support a single
`Oracle' database on a VAX: minicomputer by making direct calls to the Oracle database engine.
`Now suppose that the developer needs to provide the EIS with access to information stored on a
`SQl Server database running on a PC system. The EIS developer is faced with two equally
`
`Backgrounders and White Papers
`
`Page 3
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: DelIVering Enterpnse Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. Ali rights reserved.
`
`unsatisfactory alternatives:
`
`III Create a new application to access the SQL Server database. This solution requires users to
`work with a different application for each database, and also requires significant programming
`effort.
`
`III Modify the existing application to provide access to the SQL Server database in addition to the
`Oracle database. This solution spares users from having to learn a second application, but still
`incurs significant programming costs.
`
`'w'indowsAAs
`
`'w'indOf/s
`Sl'r.vice-pTOJide T
`InleT facl's
`
`WOSA architecture. Windows APls provide the link for Windows-based applications.
`Windows service-provider interfaces provide the link for service providers. Together they
`enable Windows-based applications to access a wide range of services across multiple
`environments.
`
`The WOSA Solution
`
`WOSA provides a single system-level interface for connecting front-end applications with back-end
`services. WOSA accomplishes this by providing a common set of APls to all applications. The
`WOSA interfaces are tightly integrated with the operating system, not the individual applications.
`The WOSA APls thus serve as an abstraction layer to computing resources, eliminating the need to
`incorporate any vendor-dependent source code in front-end applications.
`
`WOSA is extensible both in the types of service it can provide (Le. database, mail, licensing, etc.),
`and in the number of implementations of any given service it can support (i.e. for mail services,
`PROFS®, Microsoft Mail, Novell® MHS, etc.). New services and service implementations can be
`added as needed. Applications written to the WOSA set of APls not only have access to service
`implementations and computing environments available today, but also to future service
`implementations and computing environments.
`
`In order to provide transparent access for applications, each implementation of a particular service
`Simply needs to support the functions defined by its service-provider interface (SPI). This not only
`gives applications seamless access to multiple service implementations, but it also gives service
`software seamless access to any WOSA-enabled client application.
`
`Backgrounders and White Papers
`
`Page 4
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder. Delivering Enterprise Services to the Windows-based Desktop
`(c) 1992, 1993 MIcrosoft Corporation. All rights reserved.
`
`The WOSA Architecture
`
`WOSA uses Windows dynamic link libraries (DLLs) which allow software components to be linked at
`run time. In this way, applications are able to connect to services dynamically. An application needs
`to know only the definition of the interface, not its implementation.
`
`Building Open Solutions
`
`Microsoft is committed to providing an open platform that delivers all the benefits of open systems.
`The specifications for all WOSA components have been developed through an open process in
`which independent software vendors and industry groups work together to create the best possible
`design. WOSA incorporates eXisting standards whenever available, and through the open process
`new groups have been formed to define standards where they are needed.
`
`As an open architecture WOSA's benefits can be measured across two dimensions: choice and risk.
`In deploying enterprise systems, WOSA enables IS departments and users freedom of choice in
`terms of vendors, applications, operating environments, and hardware platforms supported.
`Between the thousands of applications available on the Windows platfonrn today and the
`interoperability provided by WOSA, IS managers and users truly have the benefit of choice. IS
`managers can use this choice to tailor systems solutions to effectively meet the needs of individual
`users.
`
`WOSA also dramatically reduces risk in several ways. As corporations move to the client-server
`model of computing, WOSA allows an organization to build the most useful and productive business
`applications on the PC platform, while utilizing existing information resources. A corporation can
`thus leverage existing systems in a way that would not be possible without the interoperability that
`WOSA provides. Risk is also reduced through WOSA-derived scalability and portability. As an
`organization's data resource needs grow, services can be re-implemented on more powerful
`platfonrns without requiring changes to business applications. Similarly, different implementations of
`an existing service can be transparently ~ubstituted should the need arise.
`
`The benefits of WOSA
`
`WOSA provides Windows users with seamless connections to diverse enterprise computing
`environments. In doing so, WOSA also provides the following specific open system benefits:
`
`.. Easy upgrade paths.
`
`.. Protection of software investment.
`
`.. More cost-effective software solutions.
`
`.. Flexible integration of multiple-vendor components.
`
`.. Short development cycle for solutions.
`
`.. Extensibility to include future services and implementations.
`
`Backgrounders and White Papers
`
`Page 5
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Wmdows-based Desktop
`(c) 1992. 1993 Microsoft Corporation. All rights reserved.
`
`.~D
`
`v\rlndows-based
`application
`
`VSAM
`In production
`
`DB2
`Planned for
`future release
`
`SQL Server
`Planned for
`future release
`
`Current and planned implementations. WOSA provides the flexibility for Windows-based
`applications to move from the current production system to a new system with different
`back-end services.
`
`Easy upgrade paths.
`
`Because WOSA enables a single application to work with multiple back-end services, IS managers
`can upgrade or change those services without effecting either their users or their applications.
`
`Protection of software investment.
`
`WOSA protects an organization's software investment by enabling existing applications written to
`the WOSA interface to access, without modification, new service implementations on a variety of
`platforms. Users can thus work with new information resources without having to learn how to use
`new applications.
`.'
`
`More cost-effective software solutions .. '
`
`As WOSA-based applications become more readily available, IS managers will be able to use
`off-the-shelf products to create integrated software solutions that are at least as powerful as far more
`expensive custom alternatives. This modular approach makes it easy to tailor software solutions to
`specific business needs. With WOSA, IS managers can focus on making the enterprise more
`effective, and not be sidetracked by frustrating compatibility issues.
`
`Flexible integration of multiple-vendor components.
`
`WOSA's flexible, open architecture supports multi-vendor environments and, in any given
`environment, multiple implementations of a single type of service. As a result, WOSA makes it easy
`to switch from one implementation to another. This ability is important for organizations whose
`long-range plans may require different products than they use today, and it is critical for companies
`that are unsure of their long-term requirements.
`
`Backgrounders and White Papers
`
`Page 6
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Wmdows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All nghts reserved.
`
`VVindows-based
`applications
`
`Windows
`
`VVindows
`Service-provider
`inter1aces
`
`PROFS
`
`AII-in-one
`
`Oracle
`
`Service
`providers
`
`SQL Server
`
`WOSA Dll implementation. WOSA's Dll implementation makes it easy to add support for
`new service providers without having to make changes to the Windows-based applications.
`Since linking is done at run time, services can be added as needed.
`
`Short development cycles for solutions.
`
`WOSA relieves corporate developers fro.m the burden of managing access to back-end services. By
`providing access to various implementations of back-end services in the system software, WOSA
`eliminates the need for application developers to reinvent solutions for each new service
`implementation. Developers can provide access to new implementations simply by plugging existing
`components together without additional programming effort.
`
`Extensibility to include future services and implementations.
`
`WOSA is designed to be extensible, meaning that new types of services can be added to the
`architecture as needed. WOSA's DLL-based implementation enables new APls to be added without
`disrupting existing ones. Without modification, applications can take advantage of new service
`implementations, and can be extended to access entirely new services as desired.
`
`Other Open Systems
`
`While the term "open system" is used frequently, the benefits and promises of many open system
`efforts have failed to materialize. It is, however, important to understand how some other open
`system solutions compare or interoperate with WOSA.
`
`Backgrounders and White Papers
`
`Page 7
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder. Delivenng Enterprise Services to the Windows-based Desktop
`(c) 1992. 1993 Microsoft CorporatJOn. All rights reserved.
`
`Distributed systems
`
`The Open Systems Foundation's Distributed Computing Environment (DCE) is a source-code
`product that, when implemented by a computer manufacturer on a particular operating system,
`provides a standardized set of distributed services across systems. In addition, DCE defines
`wire-level protocols that describe the interaction of the various DCE components. Its remote
`procedure call (RPC) mechanism is the communication basis for all the other services. WOSA
`complements DCE because Microsoft has written it's own smaller, faster implementation of RPC
`that is compatible with the DCE RPC. This allows developers and customers using Microsoft
`Wi!1dows to build distributed applications that interoperate with many other operating systems in a
`heterogeneous, networked environment. Over time, Microsoft's RPC will gain more interoperability
`features including DCE-style security and naming services.
`
`Single service standards
`
`The purpose of single service APls, such as Vendor-Independent Messaging (VIM), is to provide a
`single-service environment on multiple hardware and operating system platforms. Single service
`APls may solve some specific problems for cross-platform development efforts, but they do not
`provide an integrated, consistent approach to connect with all types of services. WOSA, however,
`provides this Single, integrated approach that truly addresses the needs of users, application
`developers and service providers.
`
`Universal clients
`
`Many operating systems claim to be "universal clients" in the sense that they require service
`implementations to conform to service protocols. They do not, like WOSA, support a variety of
`service implementations under a consistent programming interface. Some vendors define secondary
`interfaces such as gateways as a way of supporting WOSA-style connectivity. These
`implementations incur more overhead. and are at the mercy of various middleware vendors for
`continued support and compatibility. In contrast. the WOSA APls constitute direct. core interfaces to
`services used by the operating system.
`.'
`
`WOSA: The Right StrategiC Platform
`
`Standardizing applications on the Windows operating system in general and WOSA in particular is a
`safe and strategiC decision for IS managers, system integrators, corporate developers. independent
`software vendors (ISVs). and providers of back-end computing services. WOSA enables all these
`groups to work together to build highly functional. cost-effective software solutions to business
`problems.
`
`WOSA and IS managers
`
`IS managers must provide computing services to a variety of users whose information needs are
`often quite diverse. In the absence of a truly flexible platform. IS managers must often decide
`whether to build custom solutions for each type of user or to sacrifice individual needs by adopting a
`Single common solution. WOSA eliminates the need to make such compromises. Users can work
`with the applications that best meet their needs, and IS managers can feel confident that the chosen
`applications will work together seamlessly.
`
`Backarounders and White Papers
`
`PaoE>B
`
`Microsoft Develooment Librarv
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All rights reserved.
`
`WOSA and systems integrators
`
`WOSA eliminates the obstacles that are often associated with integrating custom software packages
`into a heterogeneous environment. WOSA's flexibility enables systems integrators to combine
`custom front-end applications with commercially available software packages and back-end services.
`
`WOSA and independent software vendors
`
`Independent software vendors gain the same benefits from WOSA as do corporate developers. In
`addition, ISVs can use WOSA as a way to market a single implementation of their application to
`multiple service providers. Likewise, WOSA enables back-end service providers to market a single
`product that is immediately compatible with many existing front-end applications. With WOSA, the
`ISV's market opportunities are expanded to include customers who use any product that supports
`the WOSA interface. Because it is easy to build service-provider interface libraries for new service
`providers, the ISV's horizons are not limited by issues of interoperability.
`
`Database Server
`
`DEC VAA
`
`ASMOO
`
`File Server
`
`Windows-based Workstation
`
`WOSA integrates information resources. Windows Open Services Architecture enables
`seamless access to multiple computing platforms and information resources. WOSA
`represents a Significant step towards the vision of Information at Your Fingertips.
`
`Conclusion
`
`The primary goal of the Windows Open Services Architecture is to make it simple for customers to
`integrate personal computers with a wide variety of back-end services. The primary benefit of
`WOSA is that it enables customers, systems integrators, software developers, and vendors to focus
`on building solutions rather than overcoming incompatibilities between various products.
`
`Backgrounders and White Papers
`
`Page 9
`
`Microsoft Development Librarv
`
`

`

`WOSA Backgrounder: Delivenng Enterpnse Services to the Wmdows-based Desktop
`(c) 1992, 1993 Microsoft Corporation All rights reserved.
`
`The WOSA effort requires a strong commitment and a significant technology investment from
`Microsoft, as well as the support of major industry players. WOSA components are designed
`through an open process that incorporates input and feeaback from many independent industry
`vendors. The commitment to the WOSA philosophy is demonstrated by Microsoft's work with the
`SQl Access Group for ODBC, the Open Software Foundation, and various coalitions of software
`vendors and solution providers. This commitment will continue to be developed through Microsoft's
`Open Process.
`
`Today, WOSA is supported in the Microsoft Windows family of operating systems, including
`Windows, Windows for Workgroups and the powerful Windows NT. With strong and growing
`inaustry support from both service providers and application developers, WOSA makes Windows
`the strategic choice for any corporation facing the challenge of integrating their information
`resources. Such integration is central to realizing the important vision of Information At Your
`Fingertips.
`
`For more information
`
`More information on WOSA is available by calling Microsoft Developer Services Team toll-free at
`(800) 227-4679. If you require TDDrrT (text telephone) for the hearing impaired, call (206)
`635-4948. In Canada, call (800) 563-9048. Outside the 50 United States and Canada, contact your
`local Microsoft subsidiary. You can also contact Microsoft by fax at (206) 936-7329. Specify
`Developer Services Team, RWF on your cover sheet.
`
`The Microsoft Developer Network
`
`The Microsoft Developer Network is an annual membership program created to support all
`developers who write software for the Microsoft Windows family of operating systems or who use
`Microsoft products for development. Members receive technical and resource information on a
`regular basis through three channels: the Microsoft Developer Network CD, the Microsoft Developer
`Network News and the MSDNLlB Forum on CompuServe®. For more information call (800)
`759-5474, seven days a week, 24 hours ,a day.
`
`Open Database Connectivity
`
`Information has become a key asset to corporate competitiveness. To stay competitive, corporations
`need access to accurate and timely information. Companies are striving to achieve a higher level of
`accuracy and effectiveness in areas such as pricing, quality control, market analysis, capacity
`planning, inventory management, customer service, and billing. At the same time users need
`graphical user interfaces, leading edge analytical tools, and better ways of accessing and viewing
`information-all without having to know the structure or language of the underlying DBMS and
`network hardware.
`
`For historical, strategic and technological reasons, corporations typically have applications and
`database systems residing on diverse platforms. To support these systems and also meet growing
`business and user demands, a corporation's database strategy must be:
`
`.. Open. Corporations tend to develop long-term relationships with their database vendors, but do
`not want to be tied to proprietary systems.
`
`.. Scalable. As system throughput, database size, or number of users increases, the company
`needs a smooth upgrade path.
`
`Backgrounders and White Papers
`
`Page 10
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: Delivering Enterprise Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All rights reserved.
`
`In addition, the database strategy should include:
`
`II Support for legacy systems. Solutions must support ;:l plan for co-existence with existing
`systems and/or a plan that provides a migration path as systems evolve.
`
`II Provisions for security and manageability. The system components and data must be
`manageable and secure.
`
`Open Database Connectivity (OOSC ) allows an organization to implement database solutions that
`meet all of these key criteria. OOSC is Microsoft's strategic interface for accessing data in a
`heterogeneous environment of relational and non-relational database management systems. OOSC
`eases the burden of data access by creating a single vendor-neutral, open, and powerful interface to
`database systems. OOSC is vendor neutral-allowing access to databases from multiple vendors.
`OOSC is open-it is based upon work in progress on the Call Level Interface specification by the
`SQL Access Group, and was designed through an open process incorporating feedback from
`numerous software vendors and corporations. oose is powerful-it supports a vast array of SQL
`(Structured Query Language) features, including outer joins, scalar functions, stored procedure calls,
`and facilitates accessing enterprise data in a heterogeneous environment. OOSC is a significant
`step towards interoperable applications.
`
`oose eases the client-server application development burden
`
`OOSC alleviates the need for developers to learn multiple programming interfaces by providing a
`universal data access interface. It allows an organization to develop applications that integrate
`legacy data, are scalable, and that can support disparate databases across the company with a
`single programming interface. A Single client application can use OOSC to work transparently with
`many different database systems. For example, a company may develop a single quality control
`application which is used by multiple divisions and subsidiaries, even though each division and
`subsidiary may use a different database product.
`
`Windows-based
`app'irion
`
`OOSC API
`Windows
`
`SQL-Server
`
`Oracle
`
`Backgrounders and White Papers
`
`Page 11
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All rights reserved.
`
`oose architecture. Oose allows a single client application to seamlessly access data from
`many different database platforms. As a corporation's data resource needs change, new
`database service implementations can be added or substituted without disrupting client
`applications written to the oose specification.
`
`ODBC enjoys tremendous industry acceptance, with many endorsements from within the database
`vendor community, as well as from many application vendors and corporate developers. ODBC
`drivers have been completed for over 20 different database server products. In addition, ODBC
`connectivity is already available in many popular front-end applications and development tools such
`as_Microsoft VisualBasic™, PowersoftTM PowerBuilder™, and KnowledgeWare® ObjectView. And
`the list of products using ODBC is continually growing. ODBC truly demonstrates how Windows
`Open Services Architecture is making access to critical enterprise resources easier to implement
`and easier to use.
`
`Messaging Application Program Interface
`
`An organization's success is tightly bound to the ability of its employees and workgroups to establish
`and maintain effective communication. Without this ability, even simple projects quickly become
`unwieldy and uncoordinated, negatively impacting the quality of the delivered product. Today,
`electronic-mail has become an important part of the communication infrastructure within many
`corporations. Sut many companies have found that the introduction of electronic mail alone has not
`solved their communication and productivity problems. This is largely due to the complexity of most
`electronic mail applications, and their inability to truly integrate information for enterprise-wide
`workgroup applications.
`
`Ideally, the computer networks that have already permeated the corporate world should serve .as
`highly efficient communication backbones for organizations. To provide this functionality, the
`messaging system must be:
`
`• Flexible and open. To truly facilitate communication, the system must connect to multiple
`applications across multiple hardware platforms and support existing standards.
`
`• Easy to implement and use. The messaging system must not only provide seamless
`communication capabilities to users, but it also must provide easy access to communication
`capabilities for workgroup applications.
`
`The Messaging Application Program Interface (MAPI) meets these key criteria and delivers on the
`promise of more effective enterprise-wide communications. MAPI consists of a standard set of APls
`that provide complete system-independence for applications, enabling them to access rich
`messaging capabilities. MAPI is flexible and open - MAP I-enabled applications are not tied to a
`specific vendor's electronic mail system, and MAPI supports existing standards such as the X.400
`API Association's Common Messaging Calls (CMC). MAPI is easy to implement and use - using
`MAPI, Windows-based applications can now provide users with straightforward access to workgroup
`and enterprise-wide communications.
`
`How MAP I Works
`
`MAPI provides a layer of functionality between the applications and the underlying messaging
`systems. This allows each to be developed independently of the other, making it easy to write
`powerful messaging-enabled applications that will work across multiple systems. On a
`Windows-based desktop, the user simply selects the desired drivers from the control panel as easily
`as if installing different printers.
`
`Backgrounders and White Papers
`
`Page 12
`
`Microsoft Development Library
`
`

`

`WOSA Backgrounder: Delivering Enterpnse Services to the Windows-based Desktop
`(c) 1992, 1993 Microsoft Corporation. All rights reserved.
`
`MAPI thus frees organizations to choose messaging systems and applications according to what
`best meets the organization's needs, rather than choosing from the few that happen to be
`compatible. As drivers become available, a single application can work with multiple messaging
`systems such as Microsoft MAIL, Novell® MHS, and IBM PROFS. Once a driver is installed, the
`user is never