Titan CMS online support, find help and get answers

Adding New Titan Sites to IIS

  • Published: October 05, 2008
  • |
  • Updated: May 10, 2011
  • |
  • Version: 9

This article describes how to create and configure a new site in IIS (Internet Information Services).  As part of the Titan CMS installation process, a globe will be created for you in the workstation as well as a site in IIS.  This article should be used for any subsequent globes that are created.


Titan CMS websites are hosted on the Microsoft IIS 7.0 platform.  When you want to reach one of the globes in your workstation via a URL (e.g. www.mywebsite.com), you must create a site in IIS that is coupled to that globe in your Titan CMS Workstation. If you have multiple globes in your Workstation, you will need to create a separate site in IIS for each globe that is accessible via a unique domain or subdomain.

This article will provide instructions on how to create a new site in IIS and configure that website to point to a particular globe in the workstation. In certain situations you may not need to create a brand new site in IIS.  Rather, you may be able to modify an existing site. For more information on the relationship between Titan CMS globes and IIS sites, and how to identify these situations, please see Relationship Between IIS Sites and Titan CMS Globes. For information on creating new websites in Titan CMS, please see How to Create a New Website.


Important: This article assumes you have a working knowledge of IIS, as well as XML.  It also assumes you are able to access the web server either locally or remotely.

  1. If the globe for which you are creating a new IIS site does not yet exist, refer to your Titan CMS User’s Guide for instructions on how to create a new globe.  If it already exists, proceed to step 2.
  2. Note the DocID of the home page for the globe to which the new IIS site will point.  Typically, this is the globe itself but it may be a page further down in the tree.  To do this, log in to the Workstation, and navigate to the Web Content Management screen.  Hover your mouse over the home page.  A box will pop up that contains the page’s friendly URL as well as a number in brackets.  This number is the DocID of the page.
  3. Log on to the web server.  This can be done locally or by utilizing a Remote Desktop connection.  Once you are logged on, open the IIS manager.  You can do this one of two ways:
    • Open the control panel and click on Administrative tools (you may have a shortcut to this in your Start menu).  Then, click on “Internet Information Services Manager.”
    • Navigate to Start Menu>Run.  Type INETMGR into the dialog and hit enter.
  4. Click on the Sites node in the left navigation area.  A list of all IIS sites will appear in the right pane.
  5. Identify an IIS site that is being used for an existing globe in the workstation.  There are two IIS sites created by default as part of the initial Titan CMS installation; one for the workstation, and one for the display-side.  You need to identify the IIS site that is being used for the display-side.  This can be done a couple different ways:
    • If you know the URL being used for the existing globe, you can look at the Binding column in the right pane.  This will list the URL for that site (multiple URLs can be added to a single site in IIS).
    • Typically the Name column will help to indicate what the site is used for.
    • You can check the home directory for the site.  This is used as the root of the website.  You can do this by clicking on the site and then clicking Basic Settings under the Actions area in the right column.  The Physical Path field will note the home directory path.  A site used for the display-side will typically use a folder named “Display” (E.G. C:\inetpub\wwwroot\Titan\Display), while a workstation site will typically use a fodler named “Wkst” (E.G. C:\inetpub\wwwroot\Titan\Wkst).

      Important: You must make sure to identify a site that is used for the actual display of your content.  If you identify a site used for the workstation or another purpose your new site will not operate correctly. If you are unsure of how to identify the appropriate site, contact the Titan CMS support team.
  6. We now need to clone the existing Display website. Unfortunately, in IIS 7.0, there is no convenient way to do this from IIS Manager.  We need to use a command-line tool called APPCMD to do this.
    1. Open a Command Window (START, RUN, CMD)
    2. Type CD %windir%\system32\inetsrv
    3. Type APPCMD LIST SITE “(Client) Site Name” /config /XML > C:\temp\ClientSiteConfig.xml
    4. Edit the XML file using NotePad and perform the following edits:
      1. Change the “SITE.NAME” and “name” values
      2. Change the “SITE.ID” and “id” values to one that doesn’t exist yet
      3. Change the “bindings” and “bindingInformation” items with the new host header data
      4. Change the paths for the virtual directories (new Titan instances only)
      5. (Optional) Change the “applicationPool” name
      6. Save the file as NewSiteConfig.xml
    5. Import the new IIS 7 site from the newly edited XML file using the command:

      Appcmd add site /IN < C:\temp\NewSiteConfig.xml
  7. The new site will now appear in the list of websites in IIS Manager.
  8. Click on the new website, then click the Default Document icon in the center-right panel. Under Actions click the ADD link and add the following information: display/router.aspx?DocID=[pageDocID].  Replace [pageDocID] with the DocID that you noted in step 1.
  9. Log in to the workstation, and go to the Titan Administration screen.  Navigate to Global Parameters>AppID=xx>Common Site Configuration in the left navigation area.  A list of application variables will appear in the right pane.

    Important: In the following steps you will be modifying application variables. Modifying application variables to the wrong values can, at the very worst, cause your workstation and/or website to crash. At the very least, make notes of what values you are changing and keep a copy of the original values in case they need to be switched back. However, it is recommended that you back up your AppControlData database before continuing.
  10. There are two application variables that you should modify: DisplayRefreshUrls and WkstRefreshUrls.  Both of these application variables contain simple XML data.
  11. Find the DisplayRefreshUrls parameter in the right pane.  Hit the plus sign to expand the node.  You need to add another <URL> node to the list.  It should take the form of <URL>http://[My New URL]/utilities/refreshnav.aspx</URL>.   Replace [My New URL] with the URL you used in the ServerBindings attribute in step 9.  Make sure this new <URL> node is placed between the root <URLs> node.
  12. Find the WkstRefreshUrls parameter in the right pane.  Hit the plus sign to expand the node.  You need to add another <URL> node to the list.  It should take the form of <URL>http://[My New URL]/utilities/refreshappvars.aspx</URL>.   Replace [My New URL] with the URL you used in the ServerBindings attribute in step 9.  Make sure this new <URL> node is placed between the root <URLs> node.
  13. Hit the Save button in the global toolbar area, and your new site is now configured.
 Related Documents

Knowledge Base Article: Relationship Between IIS Sites and Titan Globes

Knowledge Base Article: How to Create a New Website


Official Microsoft IIS Site