Understanding and Deploying LDAP Directory Services > 26. Case Study: An Enterprise with an Extranet > Maintenance |
MaintenanceIn this section we describe the various procedures used to maintain HugeCo's extranet directory. Data Backup and Disaster RecoveryBackups of the extranet directory servers are handled in the same manner as backup of the other directory servers. A 4mm DAT drive is attached to the master extranet directory server, and backups are performed nightly. The backups are transferred off-site as part of the twice-weekly schedule described in Chapter 25. Disaster recovery services for extranet applications were added to the contract that HugeCo maintains with a disaster recovery vendor. Maintaining DataMaintenance of extranet directory data involves two data sources ”the Oracle database that tracks information about the authorized HugeCo retailers, and the managers at the individual retailers. Each of these data sources is considered authoritative for certain directory information. The Oracle database is considered the authoritative source for information about the individual retail outlets. The retailer name , telephone and fax numbers , mailing address, retailer number, and list of authorized products are all synchronized from the Oracle database into the directory on a regular basis using a set of Perl scripts developed by HugeCo's IS staff. An established procedure is used to add or remove retailers from the Oracle database, and these changes propagate to the directory via the synchronization scripts. The entries corresponding to individual employees at the retailers, on the other hand, are owned by the manager at each particular retailer. When a new employee is to be granted access to the extranet applications, the manager uses a special Web-based application to create a new entry in the directory; this creates the directory entry for the employee and sets an initial password. Similarly, when an employee leaves a retailer, access must be revoked . The manager can accomplish this by using the same Web-based application.
MonitoringMonitoring of the extranet application and directory servers is handled by the existing monitoring system described in Chapter 25. TroubleshootingProcedures were added to the existing HugeCo directory escalation process to accommodate the Web and directory servers that support the new extranet applications.
|
Index terms contained in this sectionbackupsHugeCo case study case studies HugeCo maintenance 2nd 3rd 4th 5th 6th 7th 8th data maintenance HugeCo case study 2nd 3rd 4th 5th directories case studies HugeCo 2nd 3rd 4th 5th 6th 7th 8th disaster recovery HugeCo case study extranets HugeCo case study maintenance 2nd 3rd 4th 5th 6th 7th 8th HugeCo case study maintenance backups and disaster recovery data 2nd 3rd 4th 5th monitoring troubleshooting maintenance HugeCo case study backups and disaster recovery data 2nd 3rd 4th 5th monitoring troubleshooting monitoring HugeCo case study performance monitoring HugeCo case study troubleshooting HugeCo case study |
2002, O'Reilly & Associates, Inc. |