Implementing the Solution

By mapping each goal to a specific requirement and solution, you create an easy to follow architecture for your portal. Each requirement is implemented by one of more features and you can create an installation and configuration checklist that maps directly to your requirements.

This section walks though the SharePoint implementation for each requirement and solution outlined in Table 22.2.

Publishing allowed only to staging server

You will configure the ability to deploy content across multiple servers, from one site collection to another so that staged content is modified on the internal server and published content is modified only via the content deployment process.

You must first define the content deployment path and then configure a job to deploy content for the content path. The content deployment path defines the relationship between the two site collections for deployment. Jobs determine the specific content to be deployed from the source to the target and the schedule upon which the deployment occurs.

Creating content deployment path

Paths and jobs are created from the SharePoint 3.0 Central Administration site.

1.	From Central Administration, navigate to the Operations page.
2.	In the Content Deployment section, click Content deployment paths and jobs.
3.	On the Manage Content Deployment Paths and Jobs page, click New Path.
4.	In the Name and Description section, enter Internet publishing in the name field and a “Content path for publishing content to the Internet server” in the description field for the new path.
5.	In the Source Web Application and Site Collection section, select the SharePoint-80 Web application and root site collection which contains the content you want to deploy.
6.	Enter the URL to the External Central Administration server in the Destination Central Administration Web Application field.
7.	Select the Connect by using a different account radio button and the Use Integrated Windows Authentication radio button in the Authentication Information section.
8.	Enter the username and password of an account that has access to the destination central administration server in the required fields and click Connect.
9.	Upon successful connection, enter the SharePoint-80 Web application and root site collection where you want to deploy the content, as shown in Figure 22.2. Figure 22.2. Entering the destination site collection for your content deployment [View full size image]
10.	Leave the Deploy user names box unchecked so that user names associated with the content will not be visible on the destination site collection.
11.	Select None in the Security Information section so that no security information associated with content is deployed with the content.
12.	Click OK.

Creating a content deployment job

To create a content deployment job using the new path, follow these steps:

1.	From Central Administration, navigate to the Operations page.
2.	In the Content Deployment section, click Content deployment paths and jobs.
3.	On the Manage Content Deployment Paths and Jobs page, click New Job.
4.	In the Name field, enter Internet publishing for the content deployment job.
5.	In the Path section, choose the Internet Publishing content deployment path on the Select a content deployment path menu.
6.	In the Scope section, select Entire site collection so that the job includes all sites in the site collection in the deployment.
7.	Select the Run this job on the following schedule check box and specify a schedule to replicate content every 12 hours.
8.	In the Deployment Options section, select Deploy all content, including content that has been deployed before because the volume of content is low.
9.	Select the Send e-mail when the content deployment job succeeds check box in the Notification section.
10.	Select the Send e-mail if the content deployment job fails check box.
11.	Enter an e-mail address for the Web manager’s alias in the Type email addresses field.
12.	Click OK.

Enabling anonymous access

You will enable anonymous access on the Internet-facing server only. Because security information is not preserved in your content deployment job, the permissions that are configured on your internal server are not applied to the external server. There are two places that anonymous access must be enabled—in central administration and in the site.

Enable anonymous access using central administration

To configure anonymous access for the Internet-facing server, follow these steps:

1.	From the Internet server desktop click Start Programs Administrative Tools SharePoint 3.0 Central Administration.
2.	In Central Administration click the Application Management tab.
3.	Under Application Security click Authentication providers.
4.	Click the default zone for the SharePoint-80 Web application.
5.	From the Edit Authentication page, as shown in Figure 22.3, check the Enable anonymous access box and then click Save. Figure 22.3. Edit Authentication page [View full size image]

Enabling anonymous access in the site

After anonymous access has been enabled in central administration, it needs to also be enabled on the site collection. To do that for the Internet-facing root site collection, follow these steps:

1.	From the home page of the MOSS 2007 site, click Site Actions Site Settings Modify All Site Settings.
2.	Under Users and Permissions click Advanced permissions.
3.	Click Settings Anonymous Access and you will see the page in Figure 22.4. Figure 22.4. Change Anonymous Access Settings [View full size image]
4.	Select Entire Web site so that anonymous users can view all pages in your Web site and view all lists and items that inherit permissions from the Web site.

Creating a professional Internet presence

You have provisioned a site collection using the Publishing Portal template in the Publishing template tab. This site has a clean, centered look and feel, as shown in Figure 22.5. However, you should modify this look and feel with your company logo and help link in the footer.

Customizing the master page with a company logo

Before modifying the master page to include the logo, you must upload your corporate logo to the Site Collection Images library. To do this, follow these steps:

1.	From the home page of the site, click Site Actions and choose View all Site Content.
2.	Click Site Collection Images.
3.	Click Upload on the top navigation bar.
4.	Enter or browse to your company logo file and click OK.
5.	Click Check In to complete the upload.

After uploading the image, proceed with modifying the master page to incorporate the logo. To do this, follow these steps:

1.	From the home page of the site, click Site Actions.
2.	Choose Modify all Site Settings in the Site Settings menu.
3.	In the Galleries section, select Master pages and page layouts.
4.	Left-click the BlueBand.master file and select Edit in Microsoft Office SharePoint Designer.
5.	Click Yes in the dialog box asking you if want to check the file out and the security warning dialog box.
6.	Switch to Design view. Click the triangle logo in top left corner of the master page and press Delete on your keyboard to remove the default image.
7.	In the top menu, choose Picture from the Insert menu.
8.	Select From File.
9.	Browse to or enter the path to the company logo graphic in the Site Collection Images library and click Insert.
10.	Click OK in the Accessibility Properties dialog box.
11.	From the File menu in SharePoint Designer, click Save.
12.	Click Yes in the Site Definition Page Warning dialog box.
13.	Right-click BlueBand.master in the Folder List task pane and choose Check In.
14.	In the Check In dialog box, select Publish a major version.
15.	Click OK.
16.	When prompted, approve the new master page.

Add a global footer to your site

You can add a global footer to the site pages so that users have a link to provide feedback and ask for help. To do this, follow these steps:

1.	From the home page of the site, click Site Actions.
2.	Choose Modify all Site Settings in the Site Settings menu.
3.	In the Galleries section, select Master pages and page layouts.
4.	Left-click the BlueBand.master file and choose Edit in Microsoft Office SharePoint Designer.
5.	Click Yes in the dialog asking you if want to check the file out and the security warning dialog box.
6.	Switch to Code view and select <table.master> in the menu above the code window, as shown in Figure 22.6. Figure 22.6. Finding the active table so that the link can be inserted below it [View full size image]
7.	Scroll to the bottom of the highlighted code and place your cursor at the end of the last highlighted </table> HTML tag.
8.	Press Enter and add the following code, replacing “address” with an e-mail. <table class="ms-globallinks" style="width: 100%" cellspacing="0" cellpadding="3"> <tr> <td><a href="mailto:address">Submit Feedback</a></td> </tr> </table>
9.	From the File menu in SharePoint Designer, click Save.
10.	Right-click BlueBand.master in the Folder List pane and choose Check In.
11.	In the Check In dialog box, select Publish a major version.
12.	Click OK.
13.	When prompted, approve the new master page.
14.	Refresh the home page in your browser and review the changes, as shown in Figure 22.7. Figure 22.7. Reviewing the design changes [View full size image]

Creating global navigation

To create the global navigation, first build out your site structure and modify the navigation to suit your purposes. Then you can use the global navigation controls to configure and order your navigation.

Building the site structure

You will create the following site structure:

• Product Information: A subsite that provides product information and resources for company products.

• Press Releases: The press release page provides summary information for all current press release articles.

• Support Articles: A subsite for publishing support articles.

• About Us: This page provides high-level information about the company.

To build out this structure, follow these steps:

1.	From the Site Actions menu on the Internet portal home page, choose Create Site.
2.	Enter the site title and URL and then click Create.
3.	From the Site Actions menu on the Internet portal home page, choose Create Page.
4.	Enter Press Releases for the title, and select the (Welcome Page) Blank Web Part Page layout.
5.	Click Create.
6.	Repeat steps 1 to 2 to create the Support Articles site.
7.	Repeat steps 3 to 5 to create the About Us page.

After you have created your sites and pages, you must publish the pages so that they are visible to your users. To do this, follow these steps:

1.	From the Site Actions menu on the Internet portal home page, choose View All Site Content.
2.	Select the Pages library.
3.	Left-click the Press Releases page and choose Check In.
4.	Select the option to publish a major version, as shown in Figure 22.8. Click OK. Figure 22.8. Check in new pages [View full size image]
5.	Cancel the new workflow.
6.	Navigate to the Pages library.
7.	Left-click the Press Releases page and click Approve/reject.
8.	Select “Approved. This item will become visible to all users.” and click OK. Confirm OK when prompted that this will cancel the workflow.

Modifying the global navigation

Your site structure now supports your goals, but you should reorder the global navigation. To do this, follow these steps:

1.	Click the Site Actions menu on the Internet portal home page.
2.	Choose Modify Navigation from the Site Settings menu.
3.	Select Press Releases and click Move Up twice so it is in the second position, as shown in Figure 22.9. Figure 22.9. Modifying the global navigation order [View full size image]
4.	Select Search and click Move Down twice so it is in the last position.
5.	Click OK.

Creating a press release publishing process

The press release publishing process will be governed by using a site content type and a page layout so that public relations staff can easily create a new press release, even if they do not do it frequently. To create the press release process, complete the following high-level steps:

1.	Create a site column for product versions.
2.	Create a Press Release content type.
3.	Create a Press Release page layout.
4.	Associate the Page Layout with a site.
5.	Enable page scheduling.
6.	Create a new Press Release page.

Creating a site column for press releases

You need a new site column to support the press releases so that the content type can specify a product name. To create this site column, follow these steps:

1.	Click Site Actions on your portal home page.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	In the Galleries section, click Site columns.
4.	Click Create.
5.	Enter these values: Column name: Product Version The type of information in this column is: Choice Put the site column into: Existing Group: Custom Columns Require that this column contains information: No Type each choice on a separate line.
6.	Click OK.

Creating a Press Release custom content type

Once the site column has been created, you can create the content type for a press release using that site column. Follow these steps to create a content type:

1.	Select Site Actions from the top right corner on the portal home page.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Select Site content type in the Galleries section.
4.	Click Create from the Site Content Type Gallery toolbar.
5.	Name the new content type Press Release.
6.	Select Publishing Content Types in the Select parent content type from drop-down menu of the Parent Content Type section.
7.	Select Page from the Parent Content Type drop-down menu of the Parent Content Type field.
8.	Select the New Group radio button and enter Press Release as a name for the new group. Now add columns to the new content type from the Site Columns gallery.
9.	Click Add from existing site columns from the bottom of the Columns section.
10.	Add Article Date, Byline, Page Content, and Product Version from the Available columns list, as shown in Figure 22.10. Click OK when warned that the Page Content control must be updated by using a Web browser. Figure 22.10. Selecting the site columns for the Press Release content type [View full size image]
11.	Select No from the Update List and Site Content Types section and click OK.

Creating page layouts in SharePoint Designer

To create the page layout template that will be used to author new press releases, follow these steps:

1.	Open your portal site in Office SharePoint Designer.
2.	Choose SharePoint Content from the New option in the File menu.
3.	Choose SharePoint Publishing from the list.
4.	Choose Press Release from the Content Type Group and Content Type Name drop-down menus.
5.	Enter a URL and Title for the new page layout.
6.	Click OK.
7.	In the Toolbox pane in the top right, expand the SharePoint Controls node.
8.	Expand the Content Fields node.
9.	Drag the Article Date, Byline, Product Version, and the Page Content fields into the PlaceHolderMain content placeholder.
10.	Save and check in the new page layout.

Associating page layouts with libraries

Now that you have a page layout, associate the page layout with the pages library by following these steps:

1.	Click Site Actions in the top right corner of the portal home page.
2.	Choose Modify all Site Settings from the Site Settings menu.
3.	Select Page layouts and site templates from the Look and Feel category.
4.	Select “Pages in this site can use only the following layouts” and add the Press Release and (Welcome Page) Blank Web Part Page page layouts.
5.	Click OK.

Enabling page scheduling

Page scheduling allows you to set the start date and end date for each press release. To enable page scheduling, follow these steps:

1.	On the portal home page, choose View All Site Content from Site Actions menu.
2.	Select the Pages library.
3.	From the Settings menu on the top navigation bar, choose Document Library Settings.
4.	Select Versioning settings and enable content approval; verify as well that both major and draft versions are allowed. These settings must be activated in order to enable item scheduling.
5.	Click OK.
6.	Select Manage item scheduling.
7.	Select Enable scheduling of items in this list.
8.	Click OK.

You are now able to schedule the publication of pages in this document library. To do this, follow these steps:

1.	On the site that stores your page library, click View All Site Content from the Quick Launch navigation.
2.	Select the Pages library.
3.	On the item for which you want to edit the scheduling, select Edit Properties.
4.	Enter the scheduling start date (or choose “immediately”) and the scheduling end date.
5.	Click OK.

Creating pages

Now that you have created a new page layout using a custom content type, create a new press release ready for use on the site by following these steps:

1.	On the site on which you want to publish your new page, select Create New Page from the Site Actions menu.
2.	Enter today’s date as the Title of the new page. The URL field autopopulates with the title; change the URL if necessary.
3.	Select the Press Release page layout you created from the Page Layout list.
4.	Click Create.
5.	Fill out the content fields and click Publish.

Using the Content Query Web Part

Use the Content Query Web Part to display the titles and descriptions of your technical articles, grouped by Product Version on the Support Articles site home page. To do this, follow these steps:

1.	Navigate to the press release page.
2.	Choose Edit Page from the Site Actions menu.
3.	Click Add a Web Part in the left column.
4.	Select Content Query Web Part and click Add.
5.	Select Modify Shared Web Part from the edit menu of the Content Query Web Part.
6.	Expand the Query section and select Press Release as the content type.
7.	In the Additional Filters section, configure to show items when Scheduling End Date is less than or equal to [Today].
8.	Expand the Appearance section and enter Press Releases in the Title field.
9.	Click OK.

Configuring press release archive

Use the Records Repository feature to store press releases in our archive. To enable this functionality, complete these high-level steps:

1.	Provision a Records Repository site.
2.	Create a Records Repository storage document library.
3.	Define the routing behavior.
4.	Configure the connection settings for the records repository.

Provisioning a Records Repository site

The records repository site is the site that will contain the archived content. To create your records repository site, follow these steps:

1.	Go to your intranet site collection home page and choose Create Site from the Site Actions menu.
2.	Use these settings for the New SharePoint Site page: Title: Records Vault Description: Location for press release storage URL name: http://intranet/records Template: Enterprise tab Records Center
3.	Click Create. The Operation in Progress screen appears.

Create the records storage location document libraries

Now implement a file plan for press releases, as shown in Table 22.3.

Table 22.3. Press Release File Plan

Item	Value
Records	Press Release
Description	Press Releases that were published to the Internet
Media	Internet
Record Category	Publicity
Retention	3 years
Disposition	None
Contact	admin

Your first task is to create the document library:

1.	From the Site Actions menu in our records repository site, choose Create.
2.	Under the Libraries heading, select Document Library.
3.	On the New Document Library page, enter Press Release Archive for Name and click Create, accepting the defaults for the rest of the fields.
4.	Click Press Release Archive under the Documents heading in the left navigation bar.
5.	Click Settings and select Create Column on the menu bar.
6.	On the Create Column page enter these values: Column Name: Filing Date Type: Date and Time Require that this column contains information: Yes
7.	Click OK.
8.	Click Settings and select Document Library Settings.
9.	Under the Permissions and Management section, click Information management policy settings.
10.	On the Information Management Policy Settings page, choose the option for Define a policy and click OK.
11.	On the Edit Policy: Document page use the following values: Administrative Description: Press releases will be stored for 3 years after their filing date. Policy Statement: Press releases will be stored for 3 years after their filing date. Check Enable Expiration. Under The retention period is, click A time period based on the item’s properties. Select Filing Date + 3 years. Select Perform this action and Delete from the pulldown. Click OK.
12.	The policy for this document library has now been configured.
13.	Return to the Records Vault home page by clicking Records Vault in the breadcrumb at the top of the page.

Define the Records Routing Behavior for the Record Type

By setting the records routing, you define how documents are mapped to the appropriate document libraries. To define records routing for your press releases, follow these steps:

1.	Select Configure Record Routing from the Links section on the page.
2.	In the Record Routing page, click New.
3.	On the New Item page, enter the information for the Press Release record routing: Title: Press Releases Description: Public Relations press releases Location: Press Release Archive Aliases: PR
4.	Click OK.

Configure the connection to Records Center settings

Now provide the URL to the Records Center site on the Central Administration site, allowing both the UI and object model to use the Send To function when a press release should be retained as a Record.

1.	Open SharePoint Central Administration and click the Application Management tab.
2.	Under the External Service Connections section, click Records center.
3.	Set the values as shown in Figure 22.11: Choose Connect to a Records Center. URL: http://intranet/records/_vti_bin/officialfile.asmx Display name: Records Vault Figure 22.11. Configure Connection to Records Center Page [View full size image]
4.	Click OK.
5.	Your SharePoint applications are now able to send files to the Records Center.

Configuring bug tracking indicators

Product bugs are stored in an Issue Tracking list on the intranet. The product tracking list has been customized with the following columns:

• Product Version: Choice of product to which the bug applies.

• Product Build: Build number (if applicable).

• Product Feature (to be consistent with the rest of the exercise): Choice of feature to which the bug applies.

• Bug Type: Choice of setup, typical usage, documentation, or update.

The executives and product managers want to see the status of active bugs. To achieve this objective, we are going to create KPIs by product version, product feature, and bug type for the Executive Dashboard.

To satisfy this requirement, you have four high-level steps:

1.	Create the views for the bug tracking list.
2.	Create product version KPIs.
3.	Create product feature KPIs.
4.	Create bug type KPIs.

Creating the sales views to support KPIs

You need to create views of the bug list to support the KPIs that you want to configure:

• All Open Bugs with High Priority

• Active bugs for each product

• Active bugs for each feature

• Active bugs for each bug type

To create the high-priority view, follow these steps:

1.	From the View menu in the upper right corner of the bug tracking list, choose Create View.
2.	Select Standard View.
3.	Enter High-Priority Active Bugs as the view name.
4.	Scroll to the Filter section and select Show items only when the following is true. Select Issue Status is equal to Active, And radio button, and Priority is equal to (1) High, as shown in Figure 22.12. Figure 22.12. Setting the filter criteria for your High-priority Active Bugs view [View full size image]
5.	Click OK.

To create the view for each product view, follow these steps:

1.	From the View menu in the upper right corner of the list, choose Create View.
2.	Select Active Issues in the Starting from an existing view section.
3.	Enter Active ProductA Bugs as the view name.
4.	Scroll down to the Filter section and select “And” between the existing filter and the new one and set the new filter to be Product Version equals ProductA.
5.	Click OK.
6.	Repeat steps 1 to 5 for any other product versions that you want to include as KPIs.

To create the view for each feature, follow these steps:

1.	From the View menu in the upper right corner of the list, choose Create View.
2.	Select Active Issues in the Starting from an existing view section.
3.	Enter Active Feature1 Bugs as the view name.
4.	Scroll down to the Filter section and select “And” between the existing filter and the new one and set the new filter to be Product Feature equals Feature1.
5.	Click OK.
6.	Repeat steps 1 to 5 for any other product features that you want to include as KPIs.

To create the view for each bug type, follow these steps:

1.	From the View menu in the upper right corner of the list, choose Create View.
2.	Select Active Issues in the Starting from an existing view section.
3.	Enter Active Setup Bugs as the view name.
4.	Scroll down to the Filter section and select “And” between the existing filter and the new one and set the new filter to be Bug Type equals setup.
5.	Click OK.
6.	Repeat steps 1 to 5 for any other bug types that you want to include as KPIs.

Creating bug KPIs

Now add a KPI for each view that you created in the previous section.

1.	Navigate to the Management site on the intranet.
2.	Select View All Site Content in the left navigation.
3.	Select Create in the top navigation bar.
4.	Select KPI List from the Custom Lists section.
5.	Enter the name of the KPI list as Bug Status Indicators and click Create.
6.	Select Indicator using data in SharePoint list from the New menu.
7.	Enter High-Priority Bugs in the Name field.
8.	Enter the location of the bug tracking list and select the High-Priority Active Bugs view in the SharePoint List and View section, as shown in Figure 22.13. Figure 22.13. Entering the list and view for a KPI [View full size image]
9.	Select Number of list items in the view.
10.	Select that lower values is better and enter the goal (green) and warning (yellow) values for the organization. We used 0 for the green value and 1 for the yellow value.
11.	Enter the link to the bug tracking list in the Details Link section for drilling down on the indicator.
12.	Click OK.

Now add KPIs for your product views by following these steps:

1.	Choose Indicator using data in SharePoint list from the New menu.
2.	Enter Product A Bugs in the Name field.
3.	Enter the location of the bug tracking list and select the Active ProductA Bugs view in the SharePoint List and View section.
4.	Select “Percentage of the list items in the view where” and due date is less than [Today], as shown in Figure 22.14. Figure 22.14. Calculating percentage past-due bugs [View full size image]
5.	Change the better values to be lower and enter the goal (green) and warning (yellow) values for the organization. We used 5 (5%) for the green value and 30 (30%) for the yellow value.
6.	Enter the link to the bug tracking list in the Details Link section for drilling down on the indicator.
7.	Select OK.
8.	Repeat steps 1 to 7 for the product feature and bug type views/indicators.

Adding the KPI Web Part to the Management home page

To highlight the importance of the KPI list items, add them to the home page of the management site so that executives can easily see them every time they visit the site. To do this, follow these steps:

1.	Navigate to the home page of the Management collaboration site.
2.	From the Site Actions menu, choose Edit Page.
3.	Select Add a Web Part in the left zone.
4.	Select Key Performance Indicators from the Dashboard section.
5.	Click Add.
6.	From the Edit menu of the Key Performance Indicators Web Part, select Modify Shared Web Part.
7.	Browse or enter the path to the Bug Status Indicators in the Indicator List field.
8.	Select Traffic Lights in the Change Icon field.
9.	Click OK.
10.	Click Exit Edit Mode.
11.	Confirm that the KPI list has been added to the page.

Configuring the technical article workflow process

The technical article workflow process requires that you create a content type for the technical article and associate a workflow with the content type. After you have done that, you create a page layout for your technical article and associate that with the support subsite you created.

Create a site content type for the technical article

To support the technical article publishing process, you will create a content type that will contain the site columns for the technical article fields. To create this content type, follow these steps:

1.	Choose Site Actions on the Internet portal home page.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Under Galleries, click Site content types.
4.	Click Create.
5.	Enter these values: Name: Technical Article Parent Content Type: News type (in the custom content type group) Put this site content type into: Click New group: and enter Technical Article for the new group name
6.	Click OK.
7.	At the bottom of the Site Content Type: Technical Article page, click Add from existing site columns to add the Product Version column that you created for your press release process.
8.	From the Select columns from: pulldown, pick Custom Columns.
9.	Click the Add button to add the Product Version column, and your screen should look like Figure 22.15. Figure 22.15. Adding Site columns [View full size image]
10.	Click OK.

Adding workflow to your Technical Article content type

To add a workflow to your technical article, follow these steps

1.	Begin at the Internet portal home page and click Site Actions Site Settings Modify All Site Settings.
2.	Under Galleries click Site content types.
3.	Filter the Show Group: box by Technical Article.
4.	Click Technical Article.
5.	Click Workflow settings.
6.	Click Add a workflow.
7.	Enter Article Approval as the unique name for the workflow.
8.	Check the Start this workflow when a new item is created box. Your screen should be similar to Figure 22.16. Click Next. Figure 22.16. Adding a workflow page [View full size image]
9.	On the Customize Workflow page place the cursor next to the Approvers button, enter the technical editor as an approver, and click the Check names button to confirm the name is correct.
10.	Add a message to include with the request “Please approve this article.”
11.	Check the Post-completion Workflow Activity box to update the approval status.
12.	Click OK.

Creating page layouts in SharePoint Designer

Now create the page layout template that will be used to author technical articles by following these steps:

1.	Open your portal site in Office SharePoint Designer.
2.	Choose SharePoint Content from the New option in the File menu.
3.	Select SharePoint Publishing from the SharePoint Content list.
4.	Select Technical Article from the Content Type Group and Content Type Name drop-down menus.
5.	Enter a URL and Title for the new page layout as shown in Figure 22.17. Figure 22.17. Creating a new page layout for the technical article [View full size image]
6.	Click OK.
7.	In the Toolbox pane in the top right, expand the SharePoint Controls category node.
8.	Expand the Pages Fields node.
9.	Drag the Title and Contact Name from the Page Content fields and the Product Version field from the Content fields section into the PlaceholderMain (Custom) content placeholder.
10.	Save, check in, and approve the new page layout.

Associating page layouts with libraries

Now that you have a page layout, associate the page layout with the technical article subsite by following these steps:

1.	Click Site Actions in the top right corner of the Support Articles home page.
2.	Choose Modify all Site Settings from the Site Settings menu.
3.	Select Page layouts and site templates from the Look and Feel category.
4.	Select “Pages in this site can use only the following layouts” and add the Technical article page layout, as shown in Figure 22.18. Figure 22.18. Adding the Technical Article page layout [View full size image]
5.	Click OK.

Using the Content Query Web Part

Use the Content Query Web Part to display the titles and descriptions of your technical articles, grouped by Product Version on the Support Articles site home page. To do this, follow these steps:

1.	Navigate to the home page of the Support Articles site.
2.	Choose Edit Page from the Site Actions menu.
3.	Click Add a Web Part in the left column.
4.	Select Content Query Web Part and click Add.
5.	Select Modify Shared Web Part from the Edit menu of the Content Query Web Part.
6.	Expand the Query section and select Technical Article as the content type, as shown in Figure 22.19. Figure 22.19. Configuring the Content Query Web Part
7.	Scroll to the Additional Filters section and select Product Version is equal to ProductA, as shown in Figure 22.20. Figure 22.20. Applying additional filters to the Content Query Web Part
8.	Expand the Appearance section and enter Product A Articles in the Title field.
9.	Click OK.
10.	Repeat steps 3 to 10 to put a Content Query Web Part for Product B in the right-hand column.
11.	Click Submit for Approval to publish and approve page. See Figure 22.21 Figure 22.21. Reviewing the Content Query Web Part results [View full size image]
12.	Add an article and view the page to see published article appear in the Content Query Web Part.

Configuring site variations

You are going to use site variations to publish the Internet content for your company to Latin. You must complete two high-level steps to configure site variations.

1.	Define Variations parameters.
2.	Configure Variation Labels to determine the locale and create the site variation hierarchy.

Configuring variation support

To configure site variations, follow these steps:

1.	From the top-level site the Internet portal site collection, click Site Actions in the top right corner.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Under the Site Collection Administration category, select Variations.
4.	In the Variation Home section, enter the / as the location for the target variations to indicate that the root site will be used.
5.	In the Automatic Creation section choose Automatically create site and page variations to automatically create a copy of all variations.
6.	In the Recreate Deleted Target Page section, select Recreate a new target page when the source page is republished so that a new target page is created when the source page is republished.
7.	Click the Send e-mail notification to owners when a new site or page is created or a page is updated by the variation system check box. This sends e-mail notification that a new subsite or page of a target site is created, or when a target page is updated with revisions from the source variation by the site owner.
8.	In the Resources section, select Reference existing resources to use existing resources.
9.	Click OK.

Configure site variation labels

To configure site variation labels, follow these steps:

1.	From the home page of the Internet portal, click Site Actions in the top right corner.
2.	Select Modify All Site Settings from the Site Settings menu.
3.	On the Site Settings page, under the Site Collection Administration section, select Variation labels.
4.	On the Variation Labels page, click New Label.
5.	From the Label and Description section, type a descriptive name in the Label Name field as shown in Figure 22.22. The name you enter will become the URL string. Figure 22.22. Configuring variation labels [View full size image]
6.	Choose a user-friendly name in the Display Name field. These are typically localized versions of a label. The display name will appear in the Site Management Tool hierarchy.
7.	Select the locale for the variation and enter it in the Locale field. This denotes formatting for elements such as date, time, and currency.
8.	In the Hierarchy Creation section, select Publishing Sites and All Pages. This creates a hierarchy of publishing sites and all pages.
9.	Click OK.
10.	Click Create Hierarchies to create the site variation. A link now appears in the Global Navigation bar for the source site defining the different language variations available for users requiring native language support.

Enabling auditing

Enable the auditing settings for the Internet site so that Web managers can view the activity for the site and make appropriate decisions for future growth and usage.

To configure audit settings

The audit settings tell SharePoint which events you want to track. To configure audit settings, follow these steps:

1.	Click the Site Actions menu in the top right corner of the Internet Portal home page.
2.	Choose Modify All Site Settings from the Site Settings menu on the site you want to configure.
3.	In the Site Collection Administration section, click the Site collection audit settings link.
4.	On the Configure Audit Settings page, in the Documents and Items section, select the events you want to audit: Opening or downloading documents, viewing items in lists, or viewing item properties Editing items Checking out or checking in items Moving or copying items to another location in the site Deleting or restoring items
5.	In the Lists, Libraries, and Sites section, select the events you want to audit: Editing content types and columns Searching site content Editing users and permissions
6.	Click OK.