Internet presence scenario: Plan solution management
Updated: December 18, 2008
Applies To: Office SharePoint Server 2007
Topic Last Modified: 2008-12-10
|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.|
Beginning of scenario
The solution architect, solution developer, and content manager plan how the solution will be managed. Solution management includes the following:
Identifying elements of the solution to manage
Identifying the environments: the server farms that the Infrastructure team needs to develop, author, and publish the solution.
The processes that the Solutions team will need to build the solution and propagate the solution from one server farm to another.
The planning team first determines the types of solution elements that Web authors, site designers, and developers will create.
Authored site elements include the following:
The planning team determines the environments that they need to manage the various elements and processes in the solution.
Next, the Solutions team determines the set of processes for propagating content and solutions through the various environments.
Content authoring and approval will take place in the authoring farm. This is the primary purpose of that farm. To help assure that all content has been reviewed and approved before it is published, authored content will have major/minor versioning enabled, check-ins and check-outs will be required, and the default Approval workflow will be required to approve content.
Completed and approved site artifacts —master pages, layout pages, style sheets, and other design elements — must be propagated to the other farms on which the site will be made available.
Publishing a Web site based on Office SharePoint Server 2007 uses the content deployment feature, which copies a source site collection to a destination site collection. For each Web page that is deployed, all items in the content database that the page depends on — such as images, style sheets, or layout pages — are also deployed. Content deployment can either be run automatically, based on a schedule, or it can be run manually.
The planning team decides on a two-tier content deployment method for publishing content:
Coded site elements, such as a custom data connection, custom Web part, and custom navigation control, will be developed in the development environment. Developers will create and test custom site elements on workstations hosting Microsoft Visual Studio 2005. The development team will use Visual Studio 2005 Team System as a source control and configuration management system.
Using the integration farm, developers and testers will test the coded elements in the context of sample site content. Testers will also use this farm to verify that all site elements work together as expected.
Tested coded site elements that are completed and tested in the integration environment will be deployed to each front end server on every Office SharePoint Server farm on which they will be used. To do this, a software configuration management administrator will package the customizations as one or more SharePoint solution packages. These solution packages will then be installed on all front end servers in:
The following graphic illustrates the solution management architecture designed by the solution architect, solution developer, and content manager:
Developers check in and out of Visual Studio 2005 Team System.
Developers deploy completed site elements for debugging and testing with data.
Designers create master pages, layout pages, and cascading style sheets for the Internet site. Files are managed by using document management and workflow.
Designers deploy layouts and sample content to supply data for testing.
Developers bundle site elements as solution packages and deploy them to the authoring, production, and failover farms.
Administrators deploy the site to a staging site collection for quality control.
Approved content is deployed to publishing site and failover site collection.
The planning team investigates how to migrate the initial content from the current Web site solution to the site. The team considers using the SharePoint content migration APIs to build a custom tool. Consulting the Migration and Upgrade Resource Center for SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkID=104403), the team learns about a product that is certified by Microsoft and that migrates content and metadata to Office SharePoint Server 2007. The team decides to use this product rather than its internal resources to develop a custom solution for migrating content.
The team plans to migrate its current content after the initial site has been developed and copied to the integration farm. The team will use the certified product to configure content migration to the integration farm, to test and verify it there. After verifying the implementation in the integration farm, the team will run content migration in the authoring farm to import all the content from their current solution.
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.