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

Introduction

Goal

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

Background

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:hst/hst:hosts:
  hst:defaultcontextpath: (empty string)

CMS Configuration

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

/hippo:configuration/hippo:frontend/cms/cms-services/hstRestProxyService:
  rest.uri: http://127.0.0.1/_cmsrest
  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.

Bloomreach Experience Manager

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

/hippo:configuration/hippo:frontend/cms/hippo-targeting/experience-optimizer-perspective:
  targeting.rest.url: /_targeting