This article covers a Hippo CMS version 7.7. There's an updated version available that covers our most recent release.

HST-2 Channel Manager 


The channel manager allows a webmaster to manage multiple channels inside the CMS. A ‘channel’ can be any HST site, like a website, mobile site, REST API, etc. Each channel is tied to one mount inside an HST host group. A mount references the channel it belongs to. Mounts without a channel are not shown in the channel manager.

The CMS shows an overview of all available channels. Each channel can be previewed inside the CMS. When the hst:cmseditlink tag is used, the preview shows a button next to each rendered document that opens the CMS editor for that document. The template composer can be used inside the same preview, allowing a webmaster to drag-drop components to containers inside the page.

Developers can also define channel-wide properties in Java interfaces. These properties can be edited inside the CMS and shown in the overview of all available channels. HST components can easily access these properties via the Java interfaces.

Besides managing existing sites, the channel manager can also create new sites from blueprints defined by developers. A webmaster only needs to click 'Add channel', select the blueprint to use, and provide a name and URL for the new channel.

Define available channels

To show an HST mount as a channel in the channel manager, you must create a ‘hst:channel’ node for it that contains the name of the channel and (possibly) the channel properties and the interface name to access them.

For example, we have a channel called 'example' with the URL ''. The HST host configuration would contain the mount


To show this channel in the channel manager:

  1. Create the container node hst:channels if it does not exist yet:

    /hst:hst/hst:channels (type hst:channels)
  2. Create the new channel node:

    /hst:hst/hst:channels/example (type hst:channel)
    - hst:name = Example
  3. In the mount node, refer to the created channel node by setting the property 'hst:channelpath':

    - hst:channelpath = /hst:hst/hst:channels/example
  4. Save changes

The channel manager overview will now show the channel with the name ‘Example’ with the URL ‘'.

Channel manager host group

The HST allows multiple host groups (e.g. to distinguish different DTAP environments). Which host group is used by the channel manager is determined by the property 'hst:channelmanagerhostgroup' of the node '/hst:hst/hst:hosts'. By default:

- hst:channelmanagerhostgroup = dev-localhost

Each environment that needs a different host group needs a matching hst:channelmanagerhostgroup property.

Channel manager CMS location

The HST needs to know the URL of the CMS in order to create the right preview mounts automatically. This is specified in the property ‘hst:cmslocation’ of the host group node. For example:

- hst:cmslocation = http://localhost:8080/cms

Channel manager site portnumber

The Channel manager creates live and preview URLs through Java API calls, which are HttpServletRequest agnostic. Therefore, if the site (application) URLs need to be accessed over a port, the Channel manager needs to be informed about the port.
If the site URLs are accessed through some proxy which listens to port 80 or 443 and delegates to the application container on a different port, then, you do not need to add the default port.
The port is configured for an entire host group, and set on the host group node. So, assume a development hostgroup through which sites are accessed on port 8080 and a production hostgroup for which sites are accessed over port 80. Then the configuration might be something like:

- hst:cmslocation = http://localhost:8080/cms
- hst:defaultport = 8080

- hst:cmslocation =

Thus, no portnumber for the production site URLs.


By default, all users have read-only access to the channel manager. They can see the channel overview and preview existing channel. All users in the group 'webmaster' can also create new channels and edit existing ones. Admin users can always do everything.

For example, the following delta-XML in your hippoecm-extension.xml file adds the user 'editor' to the group 'webmaster':

<sv:node sv:name="hippogogreen-group-webmaster-includes-editor">
  <sv:property sv:name="jcr:primaryType" sv:type="Name">
  <sv:property sv:name="hippo:contentroot" sv:type="String">
  <sv:property sv:name="hippo:sequence" sv:type="Double">
  <sv:property sv:name="hippo:contentpropadd" sv:multiple="true" sv:type="String">


How do I get the 'Add Channel' button?

The 'Add Channel' button will only be shown if:

  1. There is at least one blueprint defined

  2. The user is allowed to create new channel (see the previous section on authorization)

How do I remove the '_cmsinternal' suffix from the preview URLs in the CMS?

When you preview a channel by clicking 'preview' in the channel manager, the URL will by default end with '_cmsinternal'.
The page 'Getting rid of the _cmsinternal in the site preview links from the channel manager' explains when and how this part can be removed.

How do I remove a channel

In the current version of Hippo CMS, it is possible to remove a channel from the channel manager using the CMS console. It is not possible to do this directly from the CMS UI. To remove a channel from the channel manager, perform the following steps:

  • Log in on the console
  • In the left hand tree, navigate to "/hst:hst/hst:channels" and delete the node corresponding to your channel
  • Deleting just this node only removes the channel from the channel manager; if you also want to delete the underlying site, perform the following additional steps:
    • Delete the configuration of the channel: navigate to "/hst:hst/hst:configurations" and delete the node corresponding to your channel
    • Delete the links to the content of the channel: navigate to "/hst:hst/hst:sites" and delete the node and the "-preview" node corresponding to your channel
  • Click "White changes to repository" to persist your changes

Removing the channel manager

The channel manager can be removed entirely from your project by removing the following artifacts from the pom.xml in the cms module:



Since the channel manager relies on the HST, it has to be removed when you wan to run the CMS without the HST.