Special Interest Groups

In addition to the Core Baseline Requirements (the requirements of Phase I, Phase II, or Phase III), your application must comply with two or more of the following application- and technology-specific requirements. It is recommended that applications follow the Systems Management Server guidelines and at least one other.

Requirement Met (Yes/No) Description
SNA Server    
Support for SNA gateway No Client application must use WOSA APIs or use FMI, or SNA Server client APIs, or SNA Server compatibility APIs for IBM PC Support or Client Access/400.
SQL Server    
Database access using ODBC, OLE DB, and/or ADO Yes. See Accessing the Database from ASP Pages. Application supports accessing database tables, views, and other database objects using ODBC, OLE DB, and/or ADO.
Store data in SQL Server tables Yes. See SQL Server and the CML and Database Design. Application-specific data, such as code tables, are stored in SQL Server tables.
Application administration tools function as a snap-in to the Enterprise Manager No Application administration tools will support a central administration strategy by extending the Enterprise Manager MMC.
Exchange Server    
A Messaging client application must use MAPI for send and post functionality No Client handles messaging functions by MAPI for sending and posting.
Upgrade Messaging client application from MAPI to CDO Yes. See Using CDO in the CML/LitCrit Application. Application uses Collaboration Data Objects (CDO) to provide messaging and collaboration functionality, including discussion, calendaring, mailbox access, and SMTP support.
Systems Management Server    
Must be installable using Systems Management Server No Application includes PDF and MIF files and supports unattended install and uninstall.
Internet Information Server    
Use Active Server Pages with COM components Yes. See Active Server Pages in the CML and COM Components and Objects. Application uses component object model to encapsulate business logic; any language can be used that supports COM.
Scripts to call server-side components and generate client HTML Yes. See Active Server Pages in the CML and COM Components and Objects. Scripts are used to call server-side components and generate HTML for the user interface.
Use session "keep alive" No Application uses a session keep alive timer to periodically send packets.
Extend IIS MMC if the application requires an administration user interface No Application administration tools will support a central administration strategy by extending the IIS MMC.
Application uses IIS for HTTP communication. Yes. See IIS Brings the CML to the Web. Applications that require HTTP must work with IIS.
Small Business Server    
Server applications that use CALs cannot exceed the number of SBS CALs No SBS includes 25 user licenses; SBS applications should follow the same rule.
Integration with SBS Console as required to simplify application administration No Support a central administration strategy by using a single console.
Integration with SBS setup No Client-side code must use the SBS Setup Computer wizard.
Terminal Server Edition    
Support for thin clients No Applications must install and function properly in Terminal Server mode.
Application Development Tools    
Build BackOffice applications No Must be able to create a client or server application that meets the appropriate BackOffice logo requirements.
COM+ Component Services    
Use COM+ services No Components must be built and deployed as COM+ applications.
Asynchronous Message Queuing    
Use Asynchonous Message Queuing in one of two scenarios No An application must use either MSMQ or COM+ queued components where asynchronous communication between components is provided.
Enterprise Edition Features    
Support for Very Large Memory (VLM) Not tested in this environment. Application can operate on a server with over 2 GB of RAM.
Support for Symmetrical Multiprocessors (SMPs) Not tested in this environment. Application processing leverages four or more processors in a server.
Support for Microsoft Cluster Server No Applications must integrate with the clustering wizard so that multiple instances of an application are running.
Office 2000 Client Compatibility    
Compliance with "Designed for" Windows logo guidelines for Windows 2000 and Windows 98 applications No All file system-based applications must successfully meet the requirements for the Designed for Windows logo program.
User interface (UI) design No Stand-alone client applications should meet standard Office 2000 toolbar styles, main menu bar entries and accelerator keys, dropdown menus and accelerator keys, basic dialog boxes, and help topics.
Extensibility No Stand-alone client applications should use COM add-ins to establish automation calls or links between client application, Office 2000, and Microsoft BackOffice or Windows application service (Internet Information Server or Microsoft Transaction Server).
Data access connectivity No Stand-alone client applications should include data access connectivity with a Microsoft BackOffice or Windows NTS application service — using ODBC, OLE DB, DCOM, or MAPI — and include Office 2000 component in the final application workflow.
Office 2000 Application Services   Must fulfill one or more
Document creation or form tracking integration in application workflow No Stand-alone client applications should support at least one Office 2000 document type or form tracking function in application workflow with BackOffice or Windows NTS application service.
Data analysis and reporting components in application workflow No Stand-alone client applications should support at least one Office 2000 data analysis or reporting function generated using BackOffice or Windows NTS application data.
Calendaring, contact, and journaling integration in application workflow No Stand-alone client applications should support at least one Microsoft Outlook 2000 calendaring, contact, or journaling function in application workflow with BackOffice or Windows NTS application service.
Project scheduling integration in application workflow No Stand-alone client applications should support using Microsoft Project editor user interface, task scheduling engine, database schema along with BackOffice connectivity.