Enterprise Software

How to integrate Share Point Portal Services and Content Management Server 2002

SPPS and CMS can be powerful tools for allowing users to collaborate. The problem comes when you want the programs to collaborate with each other. That's where the Content Integration Pack comes in. Here's how to get ready to use it.


Microsoft Share Point Portal Services (SPPS) 2001 and Content Management Server (CMS) 2002 provide similar services for different sets of users. By design, SPPS provides intranet services to your internal users while CMS provides content management functions that make it easier to provide content to users outside the organization. Out of the box, SPPS and CMS do not directly make use of features from one another. With the release of CMS 2001/SPPS 2001, Microsoft made available the Content Integration Pack (CIP) that allows direct integration. This article focuses on version CIP2 supporting CMS 2002/SPPS 2001, which is also available for download.

Why use it?
SPPS can be used to maintain documents similar to the method used by other document management systems. Versioning and access control are included as features. The CMS product—when separate from SPPS—would need to be heavily extended in order to support some of these features. Changes made to the SPPS-enabled documents would not necessarily be translated to a CMS-enabled Web site, a feature that is enabled using CIP2. Second, the powerful search functionality of SPPS can be made available to CMS, and CMS workflow can be integrated into SPPS.

My configuration
For this article, I will be deploying CMS 2002, SPPS 2001, and CIP2 on a Windows 2000 SP3 server. All services will reside on the same server for this demonstration.

Requirements
The system software requirements for CIP2 are:
  • Windows 2000 SP2 Server (a version supporting Windows Server 2003 should be available soon)
  • Content Management Server 2002
  • Share Point Portal Services 2001
  • SQL Server 2000 Standard or Enterprise with SP2
  • Internet Information Services 5

Hardware requirements are:
  • An 800-MHz or faster processor
  • A minimum of 512 MB RAM
  • An NTFS-formatted drive with 1 GB of hard disk space plus 50 MB for the cache folder

The process
The process for installing CIP2 begins with the installation of Windows 2000 Server and Service Pack 2. During this installation, make sure to install Internet Information Services (IIS) 5.

SQL Server 2000
SQL Server 2000 is a required component for CMS and, therefore, for CIP2. To install SQL Server 2000 (Standard or Enterprise are supported), insert the SQL Server 2000 CD into the server. This will autostart the SQL Server installer. If you have autorun disabled, you can start the installation by executing the autorun.exe program from the root of the CD. From the main Installer menu, choose SQL Server 2000 Components.

The next screen of the installer asks you to select the component you would like to install—the database server or the analysis services. For this demonstration, only the database server is needed. Choose the Install Database Server option to continue.

The database server installation begins on the Computer Name screen, which asks whether you want to install SQL on the local machine or on a remote machine. For this example, I will install it on the local machine named CMSSPS.

The Installation Selection screen then appears. Since this is a new SQL Server, indicate this by selecting Create A New Instance and clicking Next.

The next few screens simply ask for your name, company name, product key, and agreement to the license agreement. Once you have these screens filled out, you'll see the Installation Definition screen. Here, the installer asks what you want to install. Your choices include Client Tools, Server And Client Tools, or Connectivity Only. For this example, I will install the server plus the client tools.

SQL Server 2000 supports multiple instances on a single server. The next screen, the Instance Name screen, asks if you would like to rename this instance or if you would like to use the default name. For this article, we'll just use the Default name.

The Setup Type screen then appears. In a typical installation, you would probably install SQL Server onto its own drive and keep it separate from the operating system by selecting Custom and filling out the appropriate fields. Since this is being installed in my lab and I don't have a second drive in this machine, I will install SQL Server to the OS drive and perform a Typical installation.

The Services Account screen appears next. For additional security, you can choose to run each SQL service under a special account. While I recommend this in production environments, in a lab—or "proof of concept" project—this is not necessary. I will run SQL under the Administrator's credentials.

You'll then see the Authentication Mode screen. SQL Server supports two authentication modes—Windows Authentication and Mixed Mode. Windows Authentication makes SQL Server use the NT user database while Mixed Mode supports both NT authentication and SQL Server authentication. For security, I recommend Windows authentication and will use it for this demonstration.

After this, the Licensing screen asks for your licensing type—per seat or per processor. After this selection is made, SQL Server 2000 installation begins. When this is done, download and install the latest SQL Server Service Pack. As of this writing, that is SP3a.

SQL Server Service Pack 3a
If you are running on a production system, do not follow the instructions in this section before consulting the Service Pack 3a installation guide. Depending on the services supported by your installation, there are very different steps that must be followed. If you have simply followed along on a new server for this article, these steps will work for you.
  • Download Service Pack 3a from Microsoft
  • Extract the contents of the Service Pack by executing the downloaded file
  • Browse to c:\sql2ksp3\x86\setup
  • Execute setupsql.exe.

The Service Pack Setup program resembles SQL Server's Setup program. After some screens introducing the Service Pack and the associated license agreement, you are asked which instance you would like to update on the Instance Name screen. In this example, I installed only the default instance; therefore, it is in the only one available to update.

Next, you'll see the Connect To Server screen. Here, you need to choose the authentication mode that will be used to apply Service Pack 3a. Since I have only Windows authentication support, that is the selection I will choose.

Before the update is installed, you are warned if the SA password is blank. Since this was a new installation, my password is blank and I will provide one. You should never run a SQL Server—especially one connected to the Internet—without an SA password.

The second-to-last step of the update is to choose whether or not to install certain security enhancements. I will choose to update SQL Server to SP3a.

Finally, you are asked if you would like to automatically send information to Microsoft in the event of a fatal server crash. After this step, the Service Pack will begin installation. When you are done, you need to restart the server.

Content Management Server 2002
Now it's time to tackle CMS 2002, which has some software prerequisites that should be met before installation of the product begins. CMS's software prerequisites include:
  • Internet Explorer 6—IE6 can be downloaded from Microsoft. A reboot is required after installation.
  • .NET Framework—The appropriate .NET Framework can be found on the CMS 2002 CD in the \support\dotnet folder. Execute the 'dotnetfx.exe' program to install this prerequisite. No reboot is required after this installation is complete.
  • .NET Framework SP2—The appropriate .NET Framework can be found on the CMS 2002 CD in the \support\dotnet folder. Execute the 'dotnetfxsp2.exe' program to install this prerequisite. A reboot is required after this installation.
  • Internet Explorer WebControls—From the root of the CMS 2002 CD, open up the WebControls folder and execute iewebcontrols.msi.

The next step is to create the database that will be used by CMS. Start the SQL Server manager from Start | Programs | Microsoft SQL Server | Enterprise Manager. Expand the Databases tab under the server you are working on. Right-click the Databases option and choose New Database from the shortcut menu. I will name my sample database cmssps as shown in Figure A below.

Figure A
Create a new database for CMS


Since I am going to use the Administrator account for both CMS services (CMS system account and initial administrator), there is no further configuration. You will need to grant appropriate permissions to the newly created database if you decide to use a different account for the CMS system account (which you should in a production environment).

CMS 2002 uses two Web sites under IIS 5. The first one is for the actual site itself, while the second one is used for the CMS Server Configuration Application (SCA). For this example, I will use the IIS default site for the CMS site and will create a new site for SCA.

Choose Start | Programs | Administrative Tools | Internet Services Manager. Right-click the name of your server and choose New | Web Site from the shortcut menu. This will start the Web Site Creation Wizard. The first step of the wizard asks for a site name. For this example, I will name my site 'sca'.

The next step of the wizard, the IP Address And Port Settings screen, asks for addressing and port information. I will let this site run on all unassigned IP addresses and it will use port 2000.

The next screen, Web Site Home Directory, asks for the path to the files that will be used for this site. I will install the files into c:\inetpub\scaroot. You should also deselect Allow Anonymous Access To This Web Site on this screen.

The final screen asks for the permissions associated with the SCA site. I will simply accept the default permissions of Read and Run scripts. Click Next and Finish to complete the process.

Product installation
With the prerequisites installed, the database created, and a site ready for the SCA, you can install CMS 2002. To start the installation, execute Setup.exe from the root of the CMS 2002 CD. Choose Install Components from the main menu and Install MCMS components from the next menu. In Figure B below, you can see that I have mostly chosen a default installation, except to include the Site Manager component.

Figure B
CMS 2002 component selection


The next screen requests your user information and product key while the following screen asks for cache size determination. I will use the default size of 2048 MB located in C:\Program Files\Microsoft Content Management Server\server\. The next screen asks whether you would like to launch the database configuration application after installation is complete. I have accepted the default, which will start this wizard. After this step, files are copied to the server based on the selections that you have made.

After installation completes, the Database Configuration Application begins. The first step asks you under which compatibility mode you would like to run. Your choices are ASP.NET mode only or Mixed Mode, which includes ASP.NET and ASP. I will choose Mixed Mode for this example as shown in Figure C.

Figure C
CMS compatibility mode selection


The next screen asks you to choose a site which will host CMS content. I will choose the Default Web Site for this purpose. Likewise, you need to choose a site which will host the SCA. I will choose the SCA site created earlier for this purpose.

The next screen asks you to provide the username and password for the user credentials that CMS will use. I will use the local Administrator account for this purpose.

Next, you are asked to select the database that will be used for this site. Earlier, I created a database called cmssps, which is the one that I will use here. The next few screens are simply informational. Choose Next on these screens to move through the installation. During this process, you will also need to provide credentials for the CMS Initial Administrator user. For this, I will again user the local Administrator account.

To complete the installation of CMS 2002, I will install the sample site that comes with the installation. To do this, you need to rerun the Setup.exe from the root of the CMS CD and select Install Components from the main menu and Install Sample Site from the next menu. After this process has completed, browsing to http://192.168.1.102/WoodgroveNet/ will result in content from the sample site being displayed. Of course, you should make sure that the IP address that you use actually matches the server you are working on if you are following along at work. This completes the installation of CMS 2002.

Share Point Portal Services 2001
Share Point Portal Services is the third major component that needs to be installed before installing the Content Integration Pack. For this example, I downloaded the Share Point evaluation from Microsoft's Web site.

Before starting the installation for SPPS, you need to disable automatic proxy detection on your server. You can do this from Start | Settings | Control Panel | Internet Options | Connections | LAN Settings and deselecting both options under Automatic configuration.

The installation
To begin the installation, either insert the SPPS 2001 CD into the server's CD-ROM drive or run the Launch.exe program from the root of the CD or the location to which you extracted the downloaded SPPS evaluation.

On the main menu, select Server Installation. The first screen of substance in the installation warns you that the search services previously installed on this system will be upgraded during the installation of SPPS 2001. The next screen asks for you to accept the license agreement. After doing so, you are asked where you would like to install SPPS 2001. I will use the default of C:\Program Files\SharePoint Portal Server for the programs and C:\Program Files\SharePoint Portal Server\data for data files.

The next screen asks you to provide a user whose credentials will be used to crawl the content of the site. I will use the local Administrator user for this demonstration. You also need to specify a valid e-mail address for external site administrators.

After these selections are made, SPPS 2001 files are copied to the server. After this step is complete, the New Workspace Wizard starts. You need to create at least one SPPS workspace before continuing. For this example, I will create a workspace named TechRepublic with a description of TechRepublic Sample Workspace as shown in Figure D.

Figure D
Create a workspace


The next screen asks for workspace contact information. Enter your name and e-mail address on this screen. On the next screen, you are provided with a summary showing your selections. Click Finish to create the workspace.

Client configuration
If you are running Office XP, you do not need to do anything on the client side for the workspace to function properly. The required components are installed with Office XP and the 2003 beta. If you are running an older version of Office, you will need to install client connectivity. I will not go over this step here.

SPPS Service Pack
As of this writing, SPPS SP2A is the latest Service Pack available for SPPS. It can be downloaded from Microsoft. SP1 or greater is required for CIP2. For my installation, I will use SP1 since SP2 cannot install on the trial version of SPPS. A reboot is required after the installation of the Service Pack.

Content Integration Pack 2
With SQL, CMS, and SPPS installed, it's time to integrate CMS and SPPS so that they can take advantage of each other's features. For this step, I have downloaded CIP2 and extracted the bundle into C:\CIP.

From the location to which you have installed CIP, execute Setup.exe. If you have CMS and SPPS installed on the same server as I do in this example, you will need to run the installer twice. The first time will be to configure CIP for CMS, while the second will install the necessary SPPS integration components.

On the first screen, select Install Content Management Server Pack and click Continue. The first two screens of the installer provide product and licensing information. Click Next on these screens to continue. The first screen of substance asks for the location to which you want to install the product. The default is C:\Program Files\ContentIntegrationPack\, which is what I will use for this example as shown in Figure E.

Figure E
Determine where you want to install the CMS portion of CIP2


After making this selection, CIP2 components for CMS will be installed. After the files are copied, the installer requests that you provide the login credentials that you used for CMS as shown in Figure F.

Figure F
Provide credentials for CMS


The next step is to re-run the CIP2 installer. This time, choose Install SharePoint Portal Server Pack as the selection and click Continue. If you have not installed at least SP1 for SPPS, you will not be able to continue.

During the installation, you will be required to provide certain information about your installation. Specifically, you will be asked to provide the name of the CMS server, the user name and password for a user with read rights to SPPS, and the name of the database to which you would like to write integration pack files. See Figure G for more details.

Figure G
Provide details for the final step of this installation.


Getting things together
SPSS and CMS can be powerful tools for allowing users to collaborate with each other. The problem comes when you want the programs to collaborate with each other. That's where the Content Integration Pack comes in.

Editor's Picks

Free Newsletters, In your Inbox