How to enable SSL on an MCMS 2002 Web site (330815)

SUMMARY

This step-by-step article describes how to create a Microsoft Content Management Server (MCMS) 2002 Web site that has Secure Sockets Layer (SSL) enabled. To do this, you must configure several components.

Note This example uses the WoodGroveNet sample site. Additionally, this example assumes that the SSL certificate has been configured and is issued to https://ServerName.

Configure Site Manager

1. Click Start, point to Programs, and then click Microsoft Content Management Server.
2. Right-click Site Manager, and then click Properties.
3. Change the Target field value. The following is the existing value:

   "C:\Program Files\Microsoft Content Management Server\Client\nrclient.exe" http://localhost:80/NR/System/ClientUI/login.asp

   Change this value to the following value:

   "C:\Program Files\Microsoft Content Management Server\Client\nrclient.exe" https://localhost:80/NR/System/ClientUI/login.asp

   Note This example assumes that Site Manager is connecting to a MCMS 2002 server that resides on the default Web site of the local server and that uses port 80. Your server location and port number may differ.
4. Click OK.

Configure the Server Configuration Application (SCA)

1. Click Start, point to Programs, and then click Microsoft Content Management Server.
2. Right-click SCA, and then click Properties.
3. Change the Target field value. The following is the existing value:

   "C:\Program Files\Internet Explorer\IEXPLORE.EXE" http:\\localhost:7224\NRConfig

   Change this value to the following value:

   "C:\Program Files\Internet Explorer\IEXPLORE.EXE" https:\\localhost:7224\NRConfig

   Note This example assumes that the SCA connects to a MCMS 2002 server that resides on the default administrative Web site of the local server and that uses port 7224. Your server location and port number may differ.
4. Click OK.

Configure the DeveloperTools.xml file

1. Locate and open the <MCMS 2002_Root_Folder>\DevTools\DeveloperTools.xml file.
2. Modify the <CmsVsTools> element by changing the following lines of code.

   <CmsVsTools>
   	<Tool ID="0" Name="Site Manager" Command="C:\Program Files\Microsoft Content Management
              Server\Client\NRClient.exe" Arguments="http://localhost:80/NR/System/ClientUI/login.asp"/>
   	<Tool ID="1" Name="Database Configuration Application" Command="C:\Program Files\Microsoft 
              Content Management Server\Server\bin\NRDCApplication.exe" Arguments=""/>
   	<Tool ID="2" Name="Server Configuration Application" Command="http://localhost:7224/NRConfig" Arguments=""/>
   	<Tool ID="3" Name="Web Author Client" Command="http://localhost/channels" Arguments=""/>
   </CmsVsTools>
   						

   Change this code to the following code.

   <CmsVsTools>
   	<Tool ID="0" Name="Site Manager" Command="C:\Program Files\Microsoft Content Management 
               Server\Client\NRClient.exe" Arguments="https://localhost:80/NR/System/ClientUI/login.asp"/>
   	<Tool ID="1" Name="Database Configuration Application" Command="C:\Program Files\Microsoft 
               Content Management Server\Server\bin\NRDCApplication.exe" Arguments=""/>
   	<Tool ID="2" Name="Server Configuration Application" Command="https://localhost:7224/NRConfig" Arguments=""/>
   	<Tool ID="3" Name="Web Author Client" Command="https://localhost/channels" Arguments=""/>
   </CmsVsTools>
   						

3. Modify the <CmsEnvironment> element by changing the following lines of code.

   <CmsEnvironment>
   	<Server BaseUrl="http://localhost" InstanceId="1"/>
   	<Template QueryString=""/>
   </CmsEnvironment>
   						

   Change this code to the following code.

   <CmsEnvironment>
   	<Server BaseUrl="https://localhost" InstanceId="1"/>
   	<Template QueryString=""/>
   </CmsEnvironment>
   						

4. Save and then close the file.

Configure the WoodGroveNet sample site

1. Locate and open the C:\Program Files\Microsoft Content Management Server\Sample Data\WoodgroveNet\WoodGroveNet.csproj.webinfo file.
2. Modify the <VisualStudioUNCWeb> element by changing the following lines of code.

   <VisualStudioUNCWeb>
       <Web URLPath = "http://localhost/WoodgroveNet/WoodgroveNet.csproj" />
   </VisualStudioUNCWeb>
   						

   Change this code to the following code.

   <VisualStudioUNCWeb>
       <Web URLPath = "https://localhost/WoodgroveNet/WoodgroveNet.csproj" />
   </VisualStudioUNCWeb>
   						

   Note This example assumes that you connect to a MCMS 2002 server that resides on the default Web site of the local server. Your server location may vary.
3. Save and then close the file.

Configure the Authoring Connector

Note You only have to complete this step if you use the MCMS 2002 Authoring Connector component.

1. Create or locate the Microsoft Word document that you want to submit as a Web page, and then save the document.
2. On the File menu in Word, click Send to MCMS.
3. On the Send to MCMS menu, select Create New Page, Update Same Page, or Replace Any Page. If you have not yet saved your work, you are prompted to do so. Click Next.
   
   The Authoring Connector Wizard starts.
4. Click to select the Change server name and path check box, and then click Next.
5. On the Default MCMS Server page, type the full SSL path of the server to which you want to submit your document in the Server name and path box, and then click Next. For example, type the following:

   https://servername/mcms/cms/officewizard/oc.aspx

6. Continue to use the wizard to submit your document. The steps will be different depending on the task that you selected.

For more information about the MCMS 2002 Authoring Connector, see the "Authoring Content with Word 2002" topic in the MCMS 2002 documentation.

Rebuild the WoodGroveNet solution

1. In Microsoft Visual Studio .NET, locate and then open the following file:

   C:\Program Files\Microsoft Content Management Server\Sample Data\WoodgroveNet\WoodGroveNet.sln

2. On the Build menu, click Build Solution.
3. Click Start, click Run, type IISRESET, and then click OK.

Problem when more that one SSL site is created by using the same TCP port but by using different IIS host names

When you have more than one SSL site on one MCMS 2002 computer, IIS needs either a different IP address or different port numbers for differentiation with IIS host header mapping. MCMS 2002 includes a host header mapping feature that makes the use of host headers that are possible and lets you use more than one SSL site on one MCMS 2002 computer.

For more information about how to host more than one SSL site on one MCMS 2002 computer, click the following article number to view the article in the Microsoft Knowledge Base: