Contents Overview 1 Introduction to Enterprise Development 2 Introduction to the Windows 2000 Platform 11 Tools and Technologies 21 Overview of Lab Solution 30 Lab 1: Reviewing the Lab Solution 35 Best Practices 39 Review 41 Module 1: Developing Enterprise Solutions for Windows 2000 Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  2000 Microsoft Corporation. All rights reserved. Microsoft, BackOffice, MS-DOS, Windows, Windows NT, Active Directory, ActiveX, FrontPage, Intellisense, Jscript, Microsoft SQL Server, PowerPoint, Visual Basic, Visual C++, Visual FoxPro, Visual InterDev, Visual J++, Visual SourceSafe, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Other product and company names mentioned herein may be the trademarks of their respective owners. Module 1: Developing Enterprise Solutions for Windows 2000 iii Instructor Notes This module describes the architecture of an enterprise solution with respect to the Microsoft ® enterprise development strategy and Microsoft Windows ® 2000 Distributed interNet Applications (DNA). It introduces the new features in Windows 2000 and the Microsoft tools and technologies that students can use to develop enterprise solutions. The module also discusses the attributes of the business problem that will be solved in this course and how Microsoft technologies will be used to build the solution. After completing this module, students will be able to: ! Describe the high-level architecture of an enterprise solution that uses Microsoft's enterprise development strategy. ! Explain the terminology and concepts of Windows 2000 DNA. ! Describe some of the key features of the Windows 2000 platform that relate to enterprise development. ! Identify Microsoft tools and technologies used in enterprise development. ! Identify some of the best practices in building distributed, enterprise solutions. ! Describe the high-level design of the Purchase Order application used in the labs for this course. In the lab, students will explore the user interface for the Purchase Order Online application. They will use Microsoft Visual InterDev ® to view the HTML page from which orders will be placed and examine the ASP code used to call the business objects in the lab solution. They will also examine the PurchaseOrderSystem database to become more familiar with the lab application. Materials and Preparation This section provides you with the required materials and preparation tasks that are needed to teach this module. Required Materials To teach this module, you need the following materials: ! Microsoft PowerPoint ® file 1907A_01.ppt ! Module 1: Developing Enterprise Solutions for Windows 2000 ! Lab 1: Reviewing the Lab Solution Preparation Tasks ! Read all of the materials for this module. ! Complete the lab. ! Read the instructor notes and the margin notes for this module. Presentation: 45 Minutes Lab: 30 Minutes iv Module 1: Developing Enterprise Solutions for Windows 2000 Module Strategy Use the following strategy to present this module: ! Introduction to Enterprise Development Describe the three services layers and what happens at each layer. The rest of the topics on various architectures are based on this topic. Describe the application architectures by focusing on where each service resides. Use the diagrams on the slides to explain the architectures. ! Introduction to the Windows 2000 Platform Discuss Windows 2000 in terms of its role as the latest generation of the Windows operating system. It builds on Windows NT technology by adding many features and enhancements. Windows 2000 has enhanced reliability and scalability, and provides ease of use to end users, system administrators, and developers. Introduce some of the key features of the Windows 2000 platform that help developers build enterprise solutions. ! Tools and Technologies Explain that Microsoft tools and technologies are available to build each tier of a distributed application. Briefly describe the enterprise tools available in Microsoft Visual Studio such as Visual Modeler, Visual Studio Analyzer, Visual SourceSafe, and Visual Component Manager. Mention the servers available in Microsoft BackOffice and the COM and XML technologies. All of these technologies will be covered in more detail in later modules. ! Overview of Lab Solution Purchase Order Online is a sample application that is used throughout the labs in this course. It is used to exemplify the concepts covered in the course materials. This sample application is a distributed purchase order application from which users can raise purchase orders for a variety of products. The sample application is based on MS Market, an internal procurement system used within Microsoft. Explain that this lab application was designed as a learning scenario and would require additional design and development to be used in production. ! Best Practices At the end of the module, discuss the best practices for implementing enterprise solutions. Mention that most of these practices are covered in greater detail in various topics throughout the module. Module 1: Developing Enterprise Solutions for Windows 2000 1 # ## # Overview ! Introduction to Enterprise Development ! Introduction to the Windows 2000 Platform ! Tools and Technologies ! Overview of Lab Solution ! Lab 1: Reviewing the Lab Solution ! Best Practices ! Review This module introduces the terms and concepts related to building enterprise solutions based on the Microsoft Windows Distributed interNet Applications (DNA) 2000 platform. You will learn how the Windows 2000 platform provides infrastructure services that can be used by distributed applications for transaction management, asynchronous operations, data management, and security. You will also learn about the Microsoft tools and technologies you can use for enterprise development. Finally, you will be introduced to the lab scenario used to build the labs in this course. Objectives After completing this module, you will be able to: ! Describe the high-level architecture of an enterprise solution that uses Microsoft's enterprise development strategy. ! Explain the terminology and concepts of Windows DNA 2000. ! Describe some key features of the Windows 2000 platform that relate to enterprise development. ! Identify Microsoft tools and technologies used in enterprise development. ! Describe the high-level design of the Purchase Order application used in the labs for this course. Slide Objective To provide an overview of the sections and labs in the module. Lead-in The Windows 2000 platform provides infrastructure services that can be used by distributed applications for transaction management, asynchronous operations, data management, and security. 2 Module 1: Developing Enterprise Solutions for Windows 2000 # ## # Introduction to Enterprise Development ! Application Services ! Application Architectures ! Windows Distributed interNet Applications (DNA) Architecture Windows DNA provides a model for building scalable distributed applications on the Windows platform. It defines the fundamentals of building multitier applications and the Microsoft tools and technologies used to create them. In this section, you will learn about the kinds of services provided by enterprise solutions and how dividing a distributed application into tiers can help make the solution more scalable, robust, and adaptable. This section includes the following topics: ! Application Services ! Application Architectures ! Windows DNA Architecture Module 1: Developing Enterprise Solutions for Windows 2000 3 Application Services ! User Services $ A means of allowing users to interact with the system ! Business Services $ Business logic to retrieve and manipulate data according to specific business rules ! Data Services $ A data store of some type and the logic to manipulate the data Enterprise applications need to be used simultaneously by many users. Although each application may be designed to operate in a specific business environment, distributed applications typically have common design characteristics. The enterprise architecture uses a services model with at least three layers as defined by the Microsoft Solutions Framework (MSF) application model: ! User services A means of allowing users to interact with the system ! Business services Business logic used to retrieve, validate, and manipulate data according to specific business rules ! Data services A data store of some type and the logic to manipulate the data User Services User services are the units of application logic that provide an application with its interface. The user of an application can be a person or another application. Therefore, an application’s interface may be a graphical user interface (GUI) or a programmatic interface. For example, Microsoft Excel has a rich GUI that is implemented by using a workbook/worksheet metaphor. Excel also provides a comprehensive set of programmatic interfaces offering the same features and functionality in the form of Automation. The two types of interfaces are semantically equivalent and are both considered user services. An application’s user services are responsible for managing all aspects of the interaction between the user and the application. To manage this interaction well, you must understand who the users are, the activities that they will need to perform, and the interaction styles that are best suited to the different combinations of user and activity. 4 Module 1: Developing Enterprise Solutions for Windows 2000 Business Services Business services are the units of application logic that control the sequencing and enforcing of business rules and the transactional integrity of the operations that they perform. Business services transform raw data into information for the user through the appropriate application of rules. The goal of a properly designed business service is to isolate business rule enforcement and data transformation logic from their consumers (user and other business services) and from the underlying data services. Isolating the business services logic from the user and data services yields the following advantages: ! Flexibility Allows the developer to choose how and where to deploy the business services: as components on an application server, as stored procedures in a database management system (DBMS), or even on the client. ! Multiple user scenarios Allows the developer to place different types of user interface logic in front of a standard set of business services. For example, a set of business services for performing operations on a customer object is implemented as a single component running on an application server. The services that the component provides could be used in any of the following client scenarios: as macros running inside Microsoft Office, from a custom application developed with Microsoft Visual Basic ® , or from inside HTML pages running inside Microsoft Internet Explorer. ! Ease of maintenance Makes it easier to maintain business rules and logic by isolating changes from the application’s user and data services. ! Replacement of business rules Provides the ability to replace implementations of business services. For example, the set of business rules embodied within a set of business services may vary from country to country; however, the interfaces to those services remain constant. Data Services Data services are the units of application logic that provide the lowest visible level of abstraction used for manipulating data. Data services maintain the availability and integrity of both persistent and nonpersistent data. Data services control and provide access to data in a way that does not require business services to know where the data is located, how the service is implemented, or how it is accessed. While it is possible to identify discrete user and business services (such as services that relate to a customer), services at the data service level are more granular. For example, a system may contain service components for customers, employees, and vendors. At the business service level, each service component would have a unique set of attributes, services, and rules. However, at the data service level, the services represent examples of an entity to the organization. As a result, a data service component named Account Information might be implemented that provides Create, Read, Update, Delete, and Rollback services for customers, employees, and vendors. Module 1: Developing Enterprise Solutions for Windows 2000 5 Application Architectures ! Single-Tier Applications Applications can be implemented as centralized processing systems (often referred to as single-tier solutions), two-tier solutions (client/server), or n-tier systems (three or more tiers). Single-Tier Applications Early systems implemented application services by centralizing all of the processing on a large server and allowing users to access the application through dumb terminals, remote keyboards, and display units with no processing power. The server handled all data storage, business logic, and presentation logic. The above illustration shows how application services are handled in a centralized processing system. These centralized systems provide a number of advantages to the developer. Because all logic is centralized, deploying, maintaining, and upgrading the application is done at the server. No software needs to be installed or maintained at the client computer. However, this design presents some scalability issues. As more users need to access the system, the server needs to cope with a large amount of processing. To a certain extent, adding RAM and improving hardware at the server can alleviate scalability problems, but ultimately this design is not suited to the huge number of users who need to use enterprise systems in today’s organizations. The key to making solutions scalable is to make them distributed. Distributed systems share the processing load between multiple computers. The most basic form of a distributed system is a two-tier application often called a client/server application. 6 Module 1: Developing Enterprise Solutions for Windows 2000 Application Architectures (continued) ! Two-Tier Applications Two-Tier Applications In a two-tier application, the processing is shared between the server and the client computer. The server implements the data services and the client performs the user services logic. The business services can be implemented by the client software (sometimes called the "intelligent client" model) or by the server-based database application (sometimes called the "intelligent server" model), or they can be shared between the client and the server. The above illustration shows how application services are handled in a typical two-tier application. The two-tier design is more scalable than the centralized processing model because much of the load can be taken off the server by the client computers. However, the two-tier model still presents problems in an enterprise environment. Placing the business services on the client makes them difficult to modify and reuse. Each time a business rule changes, a new version of the client software must be written and deployed. Centralizing the business logic on the database server alleviates the problem of updating business rules, but adds more processing load to the server. Additionally, database servers typically use Structured Query Language (SQL) statements in stored procedures to perform business logic. Using stored procedures is not as flexible or efficient as using other languages. Each client computer requires its own database connection, which requires server resources such as RAM, and long-running business processes on the server will tie up these database connections and again lead to scalability problems. [...]... you will focus on designing and developing components for business services by using Visual Basic 6.0 and COM+ services For more information about Windows DNA, go to the Microsoft Windows DNA Web site at msdn.microsoft.com/windowsdna Module 1: Developing Enterprise Solutions for Windows 2000 # Introduction to the Windows 2000 Platform ! Windows 2000 Product Family ! Component Services ! Active Directory... help developers build enterprise solutions This section includes the following topics: ! Windows 2000 Product Family ! Component Services ! Active Directory™ ! ActiveX Data Objects 2.5 ! Web Technologies ! Security 11 12 Module 1: Developing Enterprise Solutions for Windows 2000 Windows 2000 Product Family Product Hardware Support Description Windows 2000 Professional Edition Windows 2000 Server 2 CPUs,... application server Windows 2000 Advanced Server 8 CPUs, 8GB RAM Line of Business / Ecommerce application server Windows 2000 32 CPUs, 64GB RAM Large, mission-critical Datacenter Server OLTP and OLAP database solutions server The Windows 2000 family consists of Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server Each product is optimized for a specific... COM+ component services for building middle-tier business services, and ActiveX Data Objects 2.5 for universal data access Used to manage users in a Windows 2000 Domain environment by using Active Directory services for domain management Supports up to four processors Module 1: Developing Enterprise Solutions for Windows 2000 13 Product Hardware support Description Windows 2000 Advanced Server 8 CPUs... 32-bit applications for the Windows 95, Windows 98, Windows 2000, and Windows NT workstation operating systems The Active Template Library (ATL) is a set of templatebased C++ classes with which you can easily create small, fast COM objects Module 1: Developing Enterprise Solutions for Windows 2000 23 Microsoft Visual InterDev Visual InterDev is a comprehensive development tool for data-driven Web... sources such as the Windows 2000 directory, Microsoft Site Server catalogs, Microsoft Exchange Server mail stores, and (by using the ADO 2.5 Record object) file systems and Web sites For more information about using the ADO Record object, see Module 7: Universal Data Access with ADO 2.5 18 Module 1: Developing Enterprise Solutions for Windows 2000 Web Technologies ! Internet Information Services The... computers For example, you may decide that better performance will be achieved if the data access logic is deployed on the same computer as the business rule logic: ! Physical tier 1: user services ! Physical tier 2: business rules and data access logic ! Physical tier 3: data services Module 1: Developing Enterprise Solutions for Windows 2000 Windows DNA Architecture The Windows DNA platform is based... controls and ActiveX documents 20 Module 1: Developing Enterprise Solutions for Windows 2000 Security ! Authentication $ $ Public Key Certificates $ ! Kerberos version 5 NT LAN Manager (NTLM) Authorization $ Delivery Tip Summarize the Windows 2000 platform and relate the features you’ve discussed to a real-world example Discretionary Access Control List (DACL) Windows 2000 security is easier to use than... object and what operations they can perform on it For example, a file may have an access control list (ACL) stating that users in the Sales group may read the file, while users in the marketing group may change the file For more information about securing COM+ applications, see Module 8: Making Applications Secure Module 1: Developing Enterprise Solutions for Windows 2000 21 # Tools and Technologies !... (ADSI) from Visual Basic to retrieve and update data in the directory For more information about Active Directory, see Module 6: Integrating with Active Directory Module 1: Developing Enterprise Solutions for Windows 2000 17 ActiveX Data Objects 2.5 ! Universal Data Access The ActiveX Data Objects (ADO) 2.5 library is part of the Windows 2000 Server operating system This library of COM objects is built . msdn.microsoft.com/windowsdna. Module 1: Developing Enterprise Solutions for Windows 2000 11 # ## # Introduction to the Windows 2000 Platform ! Windows 2000 Product. the module. Module 1: Developing Enterprise Solutions for Windows 2000 1 # ## # Overview ! Introduction to Enterprise Development ! Introduction to the Windows