Export (0) Print
Expand All

Internet presence scenario: Determine governance

Office 2007

Updated: December 18, 2008

Applies To: Office SharePoint Server 2007

Updated: 2008-12-18

Important Important:

This article is one of a series of articles that describes an end-to-end scenario that outlines how to plan, design, build, and maintain an enterprise's Internet presence Web site based on Microsoft Office SharePoint Server 2007.

Governance is the set of policies, roles, responsibilities, and processes that are established and recorded in an enterprise to guide, direct, and control how the organization uses technologies to accomplish business goals. Effective governance anticipates the needs and goals of both the organization's IT teams and its business divisions.

The governing group

Representatives from the Infrastructure team and the Solutions team form a governing group to determine the guidelines for managing and maintaining the Internet presence site and its supporting Web server farms. The governing body is chaired and sponsored by the senior manager ultimately responsible for the success of the Internet presence site. Other participants in the governing body include:

  • Program managers from the Infrastructure team and from the Solutions team.

  • The IT service manager

  • The IT service administrator responsible for the site

  • The tester

  • The content manager

The governing body initially meets weekly. The goal is to produce a document that specifies the responsibilities of both teams in their partnership to host and maintain the Internet presence site of the enterprise. After the initial service agreements and responsibilities are negotiated and documented, the governing group will meet less frequently to monitor the success of the current implementation and to continuously improve the governing process and the underlying services.

Infrastructure team responsibilities

The Infrastructure team will manage the authoring, production, and failover environments. The governance agreements differ for each environment. Each governance agreement is associated with a particular cost level. Service levels covered by governance agreements include the following:

  • Frequency of changes to content deployment

  • Recovery time and recovery point objectives

    • In the production farm, no data should be lost. Recovery should occur within 3 hours.

    • In the authoring farm, at most fifteen minutes of data can be lost. Recovery should be within 5 hours.

  • Backup schedules that support recovery points

    • In the authoring farm, differentials are ongoing. A full backup, including the search database, will be run between 02:30 and 05:00 daily.

    • The production farm’s content database will be backed up Thursday nights before content deployment is run. On Saturdays after content deployment, a full backup will include the search database.

    • The failover farm will be backed up manually before and after patching.

  • Availability and disaster recovery objectives, including failover timing and disaster recovery response agreements

  • Standard maintenance windows in which availability is not guaranteed

    • Authoring farm, daily between 23:00 and 05:00 daily.

    • Production farm, Saturday 12:00 to Sunday 12:00.

    • Failover farm, Monday 12:00 to Tuesday 12:00.

Solution team responsibilities

The Solutions team agrees to comply with the following requirements:

  • Certain file types, such as .exe, will not be uploaded to any site.

  • All authors and designers will take required Microsoft Office SharePoint Server 2007 training.

  • All sites will use a two-tiered Recycle Bin to minimize support calls for file recovery.

  • Solution packages submitted for deployment will be accompanied by installation instructions that detail how to install and uninstall the package.

  • Customizations are accompanied by test documents and results.

  • Solution packages that upgrade a previously deployed customization are accompanied by documentation that describes the changes, considerations in upgrading the customizations, and rollback instructions.

  • Solution packages are submitted with a completed checklist that testifies to the use of coding and testing best practices in developing the custom site elements.

  • Solution packages can write data only to content databases — they do not write to the file system.

Resources

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable books for Office SharePoint Server 2007.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft