| Requirement Server Applications | Justification |
| Run as a Windows NT™ Server service | Allows administrators to have single seat administration of the enterprise. Administrators can remotely start and stop any Windows NT service from any administrative console, without bringing down the server or network. |
| Network independence (support both IPX/SPX and TCP/IP using RPC, OLE, Named Pipes, or WinSock) | Works seamlessly with the most common and efficient network protocols available. Interface to these protocols using common, public interfaces. |
| Support Windows NT unified logon | Enables the server application to take advantage of Windows NT security. Also makes it easy on customers because they do not need to log on to each server application separately. |
| Installable using Systems Management Server (write PDF, support Uninstall and unattended install in setup program, etc.) | Makes the installation process automatic. Makes it easier for customers to keep track of software and monitor licenses. |
| Internet (http) Servers | |
| Support ISAPI as a means of extending WWW functionality | ISAPI is the fastest most scaleable way to add functionality to an Internet (http) Server and there are hundreds of ISAPI compatible extensions already available. Customers have more flexibility in choosing your Internet (http) Server if it supports all these applications. |
| Internet Information Server Extensions | |
| Implemented as ISAPI function, or provide an ISAPI connector to a logo'd server | The release of the Internet Information Server (IIS) made ISAPI is a standard part of Windows NT Server. ISAPI is also much faster and scales much better than CGI. ISAPI extensions can more easily take full advantage of Windows NT Server security and multi-processing capabilities. |
| General Client Requirements | |
| Must meet Client requirements for SNA, Messaging, Systems Management Server, or SQL. | Ensures that specific technical requirements are met, thus enhancing integration between the client and the server application. |
| Installable using Systems Management Server (write PDF, support Uninstall and unattended install in setup program, etc.) | Makes the installation process automatic. Makes it easier for customers to keep track of software and monitor licenses. |
| Must have at least a 16-bit Windows® based client, Win32® client preferred {Note: If have at least Win16 client, will allow logo to be used on other clients (Mac, Unix, OS/2, MS-DOS, etc.) as well} | Ensures that there is a client available for the desktop operating systems most customers have. |
| Use the APIs appropriate to the server application (e.g., ODBC, MAPI) | Ensures seamless integration between the client and the server application. |
| Internet Information Server Client | |
| Support session "keep alives" | Session "keep alives" provide as better user experience by minimizing the time between requests for new pages or new information from the server. With a high latency, slow link, minimizing the response time is necessary. |
| Support NT challenge response | Passing clear text passwords and userids over the network is one of the great security holes in the Internet. NT Challenge Response offers a robust method of only sending encrypted information. |
| SNA Clients | |
| Use WOSA APIs (WinAPPC, WinCPIC, WinRUI, WinSLI) or use FMI | Ensures that the SNA client supports the APIs required to run in a Windows environment |
| Use SNA Server client APIs (support SNA Server user record) | Ensures that the SNA client works with the SNA server. |
| Use SNA Server compatibility APIs for IBM PC Support or Client Access/400 Use SNA Server compatibility APIs for IBM PC Support or Client Access/400 | Ensures that the SNA client will be able to communicate with host machines. |
| Messaging Client | |
| Use MAPI for send and post OR use OLE/Messaging and/or OLE/Scheduling. | Ensures that the messaging client uses the de-facto messaging API for the most common messaging functions, or that the client makes use of OLE to handle basic messaging functions |
| SQL Server Client | |
| Use ODBC and/or DBLib, or Embedded SQL to store data in a SQL Server DB, or to access data stored in a SQL Server DB | Ensures that the SQL client uses the most widely used and supported database APIs to access the SQL database. |
| Systems Management Server Client | |
| Access Systems Management Server Database using SMS APIs or ODBC | Ensures that the Systems Management Server client uses the right APIs to access the Systems Management Server database. |
| Extend data in the database by providing a MIF file | Helps the customer collect data about the desktop, including information about the primary user of the machine and the software which is installed on the machine. |