Integrations - BloomReach Experience - Open Source CMS



Hippo CMS understands that you are dealing with an existing enterprise architecture. Rather than trying to be a solution for everything, Hippo CMS is designed to be the web content management piece that will fit into your existing puzzle.



Banner image
  • RESTful Services

    Hippo CMS’s delivery tier provides a higher level integration point through its support for the Java API for RESTful Services (JAX-RS) and Java Architecture for XML Binding (JAXB) open standards, enabling content to be exposed as well as created or imported through REST endpoints. This opens up almost unlimited possibilities including Content-as-a-Service scenarios.

  • Search Platform Integration

    The delivery tier provides integration points at framework level for enterprise search platforms such as Solr or Elasticsearch, enabling seamless aggregation and delivery of content from any source inside your enterprise architecture.

  • Event Bus

    The content repository provides an Event Bus, which allows any application to subscribe to workflow events, for example, to trigger updating your enterprise search platform of choice whenever content is published or taken offline.

  • JCR 2.0 API

    Hippo CMS’s content repository exposes the full JCR 2.0 API, providing low-level access to content structures. This is, in fact, the interface used by the Hippo CMS authoring application and delivery tier. However, for integrations, we recommend using one of the higher-level integration points described above.

  • Content Integration Example

    A simple but powerful example of content integration using some of the integration points described above is presented in our Elasticsearch Lab.


Bannercollection image
  • Relevance Collectors

    The main data integration point provided by Hippo CMS’s delivery tier is the Relevance Collector interface. Collectors collect data about visitors while they browse your sites. The data is aggregated into visitor profiles and matched to personas used to configure relevant content delivery.

    Collectors can use any data source that is available during request processing, including external web services. This enables matching of the visitor profile against other data about customers and leads that are available in your enterprise architecture, further enriching the profile and optimizing control over relevance and conversion.


  • REST Endpoint

    All data collected about your visitors is available to your other applications via a secure RESTful web service. This is, in fact, the interface used by the CMS application to render the Experience Optimizer.

  • Data Integration Example

    A simple but powerful example of data integration using a relevance collector for the Pardot marketing automation platform is presented in our Marketing Automation Lab.

  • RESTful Services

    Our delivery tier’s support for CaaS-based content delivery through RESTful services using the JAX-RS and JAXB open standards practically enables integration with any frontend technology or framework.

    Your frontend framework of choice - whether it is a modern Single-Page Application design using client-side technology such as AngularJS, a classic server-side architecture like PHP or .NET, or a native mobile app - has full access to all content and CMS features through REST. It is entirely up to the framework on how to aggregate and render content, whether it’s server-side, client-side, or a hybrid solution.

    This enables you to leverage both your organization’s existing stack and expertise as well as the powerful features of Hippo CMS’s delivery tier, with a scalable architecture that is ready for future generations of frontend technologies too.


  • Container Level Integration

    Hippo CMS’s delivery tier also provides container level integration with almost any other Java-based web application framework including Spring Web MVC, Struts, Tiles, and Wicket or even very basic servlets. This type of integration enables leveraging useful features of the delivery tier such as URL-content mappings, content beans, link rewriting, session pooling and the query API while leaving the content aggregation and page rendering to the framework of choice.

    This type of integration is particularly suited to hybrid solutions where Hippo CMS provides individual parts of larger aggregated web pages.

  • Frontend Integration Example

    Two simple but powerful examples of frontend integration using content delivery through RESTful services are presented in our Angular JS and Mobile Labs.