7.8.3 release notes - Enterprise Java Content management system - Hippo CMS

7.8.3 release notes

May 31, 2013

Hello everyone,

I am happy to announce the General Availability of Hippo CMS 7.8.3. This update marks the General Availability of the Relevance Module and the Upgrade Pack but also contains several new features and improvements in general.

I have summarized the improvements and their availability for you below to give you a more detailed view of what this update contains. Don’t hesitate to get in touch with me if you have any questions.

I wish you all great success in implementing and using this great new release!

Oscar Scholten - Product Manager

Availability

All functionality described in this announcement is available in the Hippo Community Edition, with the exception of the Relevance Module (Targeting add-on). This release marks the General Availability of the Relevance Module for all customers and partners to start new projects using this module and use it in production.

New Functionality

Targeting data persistence

The main new feature in the 7.8.3 update is the capability for the Relevance Module to track visitors over multiple visits and channels and to persist the data it collects. In previous releases, the data that was available for targeting consisted of information collected during the visitor’s current visit to the site only. This new functionality enables the targeting engine to progressively build up a profile of the visitor, spanning multiple visits. The accumulated information and also all individual visits can be analysed in the Real-time Visitor Analysis panel, enabling marketers to better understand the behavior of visitors on their web site.

The data is persisted in a new data store based on the NoSQL database CouchBase. This data store replaces the Memcache data store that was available in previous releases.

Device Preview

A second, smaller feature introduced in this update is a Device Preview capability for the Channel Manager. This enables webmasters to preview their channels in the context of another device, for instance an iPad or a mobile phone. By default, we ship with several standard device skins (desktop, iPad landscape & portrait, iPhone landscape & portrait), but it is straight-forward to add additional device skin previews if needed.

Upgrade pack

As part of this release, we provide documentation and tooling for upgrading 7.7 projects to 7.8.3. In the community documentation you will find a new upgrade trail of steps required to upgrade your project. For enterprise customers we also have tooling available to automate several steps of this process.

Other improvements

In this update, we have implemented several smaller improvements, including:

  • Improved Content Delivery Network support during development: the Hippo Delivery Tier has been enhanced so it can be configured to process several of the tags used for Edge Side Includes. Developers can now more swiftly develop for projects that use edge side includes, as they no longer have to set up a separate caching proxy server. In production environments, the processing of ESI tags can be configured to be handled by the caching proxy using a simple configuration switch.
  • Seamless HTTPS support: before this update, the Hippo Delivery Tier (HST) was scheme agnostic, requiring the use of additional plugins such as the httpsfilter if certain URLs needed to be served over HTTPS. From this release onwards, it is possible to configure whether a page should be served over HTTP or HTTPS as part of the HST configuration stored in the repository. The link rewriter has also been adapted to support cross http/https links seamlessly, also across hosts and channels.
  • Orderable valves: from this update onward, custom valves can be injected into an existing pipeline, controlling where it should be injected. Before, a custom valve could only be appended (added after the last one) to either the list of initialization, processing or cleanup valves. If you want to benefit from this new capability, you will need to extend your custom valve from the HST’s org.hippoecm.hst.container.valves.AbstractOrderableValve and add some additional configuration.
  • Score explanation for Targeting: for developers, we have added logging functionality that records for each request the different scores and inputs the Targeting Module uses to decide which configuration is used to render a component. The logging functionality is enabled through a few simple configuration steps.
  • Improved loading time for the CMS: a new mechanism of loading the individual perspectives has been implemented, which significantly lowers the time needed to login to the CMS. Developers that have developed their own perspective can easily adjust their perspective to use the new lazy loading mechanism.
  • Repository scheduling service: the Hippo Repository now exposes a scheduling service that can be used to schedule jobs with the repository. The scheduler is cluster aware, and makes sure that a scheduled job is executed on one of the cluster node. Developers can use this new scheduling service to create and manage custom jobs.
  • Daemon modules: the Hippo Repository now provides the ability to declare and configure so called "daemon modules" that can be implemented to extend the functionality of the repository. Daemon modules are singleton components whose lifecycle is managed by the repository. Developers can now develop their own daemon modules and benefit from the standardized configuration mechanism.

Other important changes

We have implemented two important changes in the repository startup procedure:

  • By default, the repository does not bootstrap automatically after the initial bootstrap. If you are upgrading your project or deploying a new version this means you need to explicitly enable bootstrap processing in order to make sure the repository is updated with the latest packaged configurations.
  • The repository is no longer by default available over RMI. If you want to access the repository over RMI, you have to make a small configuration change.

New Project

To try out the new functionality of Hippo CMS 7.8.3 using the maven archetype see instructions on the Hippo Trail.

You can also check out and run the Hippo Go Green demo:

  • svn co http://svn.onehippo.org/repos/hippo/hippo-demos/hippo-go-green/tags/hippogogreen-3.07.03
  • cd hippogogreen-3.07.03
  • mvn install
  • mvn -P cargo.run
  • open the cms and site in a browser at http://localhost:8080/cms and http://localhost:8080/site, respectively

Hippo Certified Stack

Hippo CMS 7.8.3 works with Java 6 and 7 and Apache Tomcat 6 and 7. Note that to run on Java 7, compilation against Java 6 is required.

We have updated the Community and Enterprise stack, see System Requirements.

We have tested using the following browser versions:

  • Internet Explorer: 8, 9 and 10 (in Desktop Mode)
  • Firefox: 20
  • Chrome: 25
  • Safari: 6

Known issues

Currently, there are a few known issues, including:

7.8.3 release notes

May 31, 2013

Hello everyone,

I am happy to announce the General Availability of Hippo CMS 7.8.3. This update marks the General Availability of the Relevance Module and the Upgrade Pack but also contains several new features and improvements in general.

I have summarized the improvements and their availability for you below to give you a more detailed view of what this update contains. Don’t hesitate to get in touch with me if you have any questions.

I wish you all great success in implementing and using this great new release!

Oscar Scholten - Product Manager

Availability

All functionality described in this announcement is available in the Hippo Community Edition, with the exception of the Relevance Module (Targeting add-on). This release marks the General Availability of the Relevance Module for all customers and partners to start new projects using this module and use it in production.

New Functionality

Targeting data persistence

The main new feature in the 7.8.3 update is the capability for the Relevance Module to track visitors over multiple visits and channels and to persist the data it collects. In previous releases, the data that was available for targeting consisted of information collected during the visitor’s current visit to the site only. This new functionality enables the targeting engine to progressively build up a profile of the visitor, spanning multiple visits. The accumulated information and also all individual visits can be analysed in the Real-time Visitor Analysis panel, enabling marketers to better understand the behavior of visitors on their web site.

The data is persisted in a new data store based on the NoSQL database CouchBase. This data store replaces the Memcache data store that was available in previous releases.

Device Preview

A second, smaller feature introduced in this update is a Device Preview capability for the Channel Manager. This enables webmasters to preview their channels in the context of another device, for instance an iPad or a mobile phone. By default, we ship with several standard device skins (desktop, iPad landscape & portrait, iPhone landscape & portrait), but it is straight-forward to add additional device skin previews if needed.

Upgrade pack

As part of this release, we provide documentation and tooling for upgrading 7.7 projects to 7.8.3. In the community documentation you will find a new upgrade trail of steps required to upgrade your project. For enterprise customers we also have tooling available to automate several steps of this process.

Other improvements

In this update, we have implemented several smaller improvements, including:

  • Improved Content Delivery Network support during development: the Hippo Delivery Tier has been enhanced so it can be configured to process several of the tags used for Edge Side Includes. Developers can now more swiftly develop for projects that use edge side includes, as they no longer have to set up a separate caching proxy server. In production environments, the processing of ESI tags can be configured to be handled by the caching proxy using a simple configuration switch.
  • Seamless HTTPS support: before this update, the Hippo Delivery Tier (HST) was scheme agnostic, requiring the use of additional plugins such as the httpsfilter if certain URLs needed to be served over HTTPS. From this release onwards, it is possible to configure whether a page should be served over HTTP or HTTPS as part of the HST configuration stored in the repository. The link rewriter has also been adapted to support cross http/https links seamlessly, also across hosts and channels.
  • Orderable valves: from this update onward, custom valves can be injected into an existing pipeline, controlling where it should be injected. Before, a custom valve could only be appended (added after the last one) to either the list of initialization, processing or cleanup valves. If you want to benefit from this new capability, you will need to extend your custom valve from the HST’s org.hippoecm.hst.container.valves.AbstractOrderableValve and add some additional configuration.
  • Score explanation for Targeting: for developers, we have added logging functionality that records for each request the different scores and inputs the Targeting Module uses to decide which configuration is used to render a component. The logging functionality is enabled through a few simple configuration steps.
  • Improved loading time for the CMS: a new mechanism of loading the individual perspectives has been implemented, which significantly lowers the time needed to login to the CMS. Developers that have developed their own perspective can easily adjust their perspective to use the new lazy loading mechanism.
  • Repository scheduling service: the Hippo Repository now exposes a scheduling service that can be used to schedule jobs with the repository. The scheduler is cluster aware, and makes sure that a scheduled job is executed on one of the cluster node. Developers can use this new scheduling service to create and manage custom jobs.
  • Daemon modules: the Hippo Repository now provides the ability to declare and configure so called "daemon modules" that can be implemented to extend the functionality of the repository. Daemon modules are singleton components whose lifecycle is managed by the repository. Developers can now develop their own daemon modules and benefit from the standardized configuration mechanism.

Other important changes

We have implemented two important changes in the repository startup procedure:

  • By default, the repository does not bootstrap automatically after the initial bootstrap. If you are upgrading your project or deploying a new version this means you need to explicitly enable bootstrap processing in order to make sure the repository is updated with the latest packaged configurations.
  • The repository is no longer by default available over RMI. If you want to access the repository over RMI, you have to make a small configuration change.

New Project

To try out the new functionality of Hippo CMS 7.8.3 using the maven archetype see instructions on the Hippo Trail.

You can also check out and run the Hippo Go Green demo:

  • svn co http://svn.onehippo.org/repos/hippo/hippo-demos/hippo-go-green/tags/hippogogreen-3.07.03
  • cd hippogogreen-3.07.03
  • mvn install
  • mvn -P cargo.run
  • open the cms and site in a browser at http://localhost:8080/cms and http://localhost:8080/site, respectively

Hippo Certified Stack

Hippo CMS 7.8.3 works with Java 6 and 7 and Apache Tomcat 6 and 7. Note that to run on Java 7, compilation against Java 6 is required.

We have updated the Community and Enterprise stack, see System Requirements.

We have tested using the following browser versions:

  • Internet Explorer: 8, 9 and 10 (in Desktop Mode)
  • Firefox: 20
  • Chrome: 25
  • Safari: 6

Known issues

Currently, there are a few known issues, including: