HST Multi-lingual, multi-channel, and multi-domain setup

Introduction

Out of the box, Bloomreach Experience Manager's delivery framework (HST) provides support for a multi-language, multi-channel, multi-domain, and multi-site setup. Everything is supported through HST configuration. Things like cross-domain, cross-channel, cross-language and cross-site linking are also supported out-of-the-box. Links between documents belonging to different sites or languages are resolved automatically and can even be links to a different domain!

HST scales easily to many sites, channels and translations: Some Bloomreach Experience Manager projects run 500 channels (including translations), and local tests go up to 1500 channels without performance degradation.

Channels Perspective

The Channel Manager can be used to create new channels from within the CMS. A 'channel' in the Channels Perspective can be a subsite, a translated site, a mobile site and more. Behind the scenes, the Channel Manager creates and modifies HST configuration.

The various child pages describe how to manually achieve what the Channel Manager does automatically. This information is relevant when developing a blueprint. A blueprint contains various HST configuration parts that are copied when a new channel is created. As a developer, you will most likely first create and test these configuration parts manually before making them part of a blueprint.

Terminology

• Multi-language: To have translated channels, each serving the same content in a different language.

• Multi-site: To have multiple site webapps.

• Multi-domain: To have multiple domains (different hosts) configured in the HST configuration.

• Multi-channel: To have multiple channels serving content from the same webapp.

Depending on the needs, a channel can require some custom HST configuration. For example, a French channel would have its own unique sitemap (French URLs) and site menu, but can share the configuration for components and templates with the English version.