The Politics of Costs
| Understanding and Deploying LDAP Directory Services > 24. Case Study: A Large University > Directory Drivers |
Directory DriversBig State University had for many years been providing centralized email and directory services to the campus via the Big State mainframe computing system. The mainframe was a proprietary system, increasingly expensive to maintain, and it did not play well with the Internet. The primary driver behind Big State's directory deployment was the desire to replace the mainframe directory and email services. This meant deploying an online campus phone book, along with the more challenging task of deploying directory-based email software to provide campuswide service to the bigstate.edu domain. We discuss the needs of these applications in more detail in the following sections. A secondary driver behind the deployment was the future need to deploy many campus-wide directory-enabled applications. The directory could serve as a central authentication and access control database that could be shared across these applications, as well as a repository of organizational and other directory information. Most of these applications could be used by university employees and students, but some could be used by prospective students, alumni, and other non-university users.
|
Index terms contained in this sectionapplicationsdeploying Big State University case study Big State University case study deploying directory-enabled applications replacing mainframe email and directory services case studies Big State University deploying directory-enabled applications replacing mainframe email and directory services directories case studies Big State University 2nd 3rd |
| 2002, O'Reilly & Associates, Inc. |
EAN: 2147483647
Pages: 245