Verifying that SharePoint and MCMS are Functioning Correctly

Now that we’ve created a virtual server, created a portal inside, and configured it to present MCMS content, let’s test both applications to make sure we’ve covered all bases.

Open a new browser and navigate to the portal root at http://portal.tropicalgreen.net/. If you see the portal homepage, then SharePoint is working. If it’s not working, go back and retrace your steps.

Next, navigate to:

http://portal.tropicalgreen.net/www.tropicalgreen.net/PlantCatalog/

If you see our Tropical Green plant catalog page, MCMS is working. If you don’t see our plant catalog homepage, there’s likely an issue with the excluded managed paths. Verify the last step.

You’ll notice the last URL we tested looks quite strange as it contains two domains. The code from the first book Building Websites with Microsoft Content Management Server (Packt Publishing, January 2005, ISBN 1-904811-16-7), which we’ll assume you’re using, contains two top level channels: international.tropicalgreen.net and www.tropicalgreen.net . The first book implemented the MCMS Map Channel Names to Host Header Names option, which is why these channels have domains for their names. Unfortunately the Map Channel Names to Host Header Names feature is not supported when MCMS and SharePoint are running on the same virtual server. Therefore we have to disable this option and then the name of the top level channel we need to test ( www.tropicalgreen.net ) needs to be included in the URL. Usually you would change the channel structure in such a situation so that the domain name is not included in the URL.

If you continue to have problems, refer to Microsoft Knowledge Base article #835248: http://support.microsoft.com/?id=835248 .