Phase I Server Core Requirements

If any application that ships with the BDG implements a given logo feature, the middle column of the table is marked Yes. In many cases where the implementation of the feature is described in this guide, a hyperlink to the relevant topic is provided.

Requirement	Met (Yes/No)	Description
Win32®	Yes. See About Win32 Logo Compliance.	All major client/server program files (DLLs and EXEs) must be 32-bit.
Single Sign-On	Yes. See About Unified Logon.	Unified logon is one of the most important attributes of a Windows NT/BackOffice network; it enables the server application to take advantage of Windows NT security. Additionally, customers need not log on separately to each server application.
Runs as a Windows 2000 Server service or COM+ application	No	Application supports a multi-threaded operating environment in a preemptive multi-tasking environment.
Publish Perfmon counters	No	Publish metrics which identify throughput, resource use, and response time.
Publish events to event log	No	Publish application-specific, diagnostic events related to the five (5) most common environment conditions. Future work item for Fitch & Mather.

Running as a Service

Because the CML application (the BDG's first scenario) is a distributed, three-tier application, it is difficult for all its parts to tightly fit the Windows NT service model. Still, the CML can probably be counted as running as a service because it exhibits an important attribute of a Windows NT service: it runs in the context of IIS, which itself is a Windows NT service. When the first request arrives for a CML page, IIS starts the CML application.

However, the following factors could be used to argue that the CML does not run as a Windows NT service:

Part of the CML application's logic (the UserInfo component) runs on the client. The parts that run on the Web server respond only when a client makes requests.
The CML's COM components are instantiated not through IIS but through MTS, which is an out-of-process local server.
You cannot directly control the CML through the Service Control Manager of Windows NT Server.
If the CML application is not running and a request is made for one of its pages, it should be able to start itself. This is a problem if IIS is not already running because a request for a CML page does not automatically start IIS.