Understanding MCMS Architecture in Font

Generation PDF 417 in Font Understanding MCMS Architecture

The MCMS architecture is based on the principal of creating web pages dynamically using predefined templates with content placeholders. Interestingly, the manner in which MCMS builds and delivers a web page is similar to the same process in WSS. Therefore, anyone familiar with

WSS architecture will find it easy to grasp the fundamentals of MCMS. Figure 8-1 shows a drawing of the basic MCMS architecture. The biggest difference between the two is that WSS maintains entire pages within its database, while MCMS uses external templates and only stores content in the database.

Just like WSS, MCMS relies on ISAPI filters to intercept HTTP page requests from clients and process them. The filter then examines the intercepted request to see if it corresponds to a page in an MCMS channel, which defines a virtual web site hierarchy controlled by MCMS. If it does, then the request is modified to reference the ASP .NET template that corresponds to the requested page. Because a single MCMS template can be used to render many different pages, the request is also modified to include a reference to the specific page content to render. MCMS then processes the combination of the ASP .NET template and the designated content to produce the requested page. The MCMS database, which contains the page content, consists of several dozen tables and is not intended to be accessed directly. Instead, access to content in the database is always done through the Publishing API (PAPI) and managed by the MCMS server. When pages are created in MCMS, authoring tools are used to write content into the database through PAPI. Content is subsequently read out of the database during the rendering process.

There are obviously many combinations and configurations for both WSS and MCMS. For the purpose of this chapter, I will assume that you have a development environment consisting of a single Windows 2003 server that will host WSS, SPS, and MCMS. The sample data provided

by Microsoft assumes this configuration, and so do the exercises in this chapter. Additionally, I am starting with the assumption that you have already installed or know how to install WSS, SPS, Visual Studio .NET, and Microsoft Office 2003. Before starting the MCMS installation process, you should download service pack 1a for MCMS and CST. Table 8-1 lists the addresses for the required software.

Note If you do not have SPS available, you can still utilize many parts of this chapter. All of the search

http://www.microsoft.com/ downloads/details.aspx FamilyId=62049D3F-24D7-4463A924-550E5DC34095&displaylang=en http://www.microsoft.com/ downloads/details.aspx FamilyId=6E9925C4-91DA-404A86DD-78D51BCF0A51&displaylang=en

The configuration described in this section will install MCMS on the same virtual server as your existing WSS installation; however, you will need to create an additional web site to host the Server Configuration Application (SCA), which can be used to manage MCMS sites. Additionally, you may need to make changes to the Site Application Pool Identity in order to ensure that the MCMS can properly integrate with the SPS search capability. Follow these steps to create a new web site: 1. Log in as an administrator and select Start All Programs Administrative Tools Internet Information Services (IIS) Manager on the Windows 2003 server where MCMS is to be installed. 2. Right-click the Web Sites folder and select New Web Site from the context menu to start the Web Site Creation Wizard. 3. On the Welcome screen, click the Next button. 4. On the Web Site Description screen, name the new web site SCA and click the Next button. 5. On the IP Address and Port Settings screen, set the TCP port to 8080 and click the Next button. 6. On the Web Site Home Directory screen, uncheck the option to allow anonymous access and click the Browse button.