This article covers a Bloomreach Experience Manager version 11. There's an updated version available that covers our most recent release.

Configure Hippo to use a Delivery Application deployed as ROOT.war



Configure the Channels and Audiences perspectives to use a delivery application deployed as ROOT.war.


By default Hippo's delivery application (a.k.a. HST) is packaged as site.war and deployed on the context path /site. If your delivery application is deployed as ROOT.war some changes to the application's runtime configuration are required to make the Channels and Audiences perspectives work correctly.

Application Configuration

HST Configuration

Using the Console browse to the node /hst:hst/hst:hosts and set hst:defaultcontextpath to '' (empty string). Do not remove the property. If you do, the site works but won't show up in the channel manager.

  - hst:defaultcontextpath = (empty string)
Make sure the hst:defaultcontextpath property is present with an empty value! 

CMS Configuration

Using the Console browse to the node /hippo:configuration/hippo:frontend/cms/cms-services/hstRestProxyService and set the following properties:

  - rest.uri  =
  - context.path = (empty string)​​

Web files

If you are using web files, in general the name of a bootstrapped web file bundle must be the same as the context path of the application in which the web files are used. However, when the application runs without context path (ROOT.war), the web file bundle site is used. Thus in case of ROOT.war deployment, make sure your web file bundle is still called site.

Hippo DX

This change only applies to users of Hippo DX with the Relevance Module.

At the node /hippo:configuration/hippo:frontend/cms/hippo-targeting/experience-optimizer-perspective set the following property:

  - = /_targeting
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?