Personalization explains how to work with the personalization feature. This document is about the module.
Personalization refers to adapting content to a particular user according to his or her personal preferences, needs and capabilities. In order to do so, you first select a set of traits of a visitor or a visit, then compose rules using these traits to define what content is presented to which visitors and when. Magnolia EE Pro 5.3+
Magnolia's Personalization feature consist of four modules.
- Integration : Core personalization support for creating page variants and fields for selecting traits and audiences.
- Traits: Example traits country, date and visitor.
- Preview app : App for testing content delivery by impersonating a visitor.
- Segmentation app: App for grouping visitors into segments.
- Personas app: App for creating hypothetical visitors who represent your target audience.
- Samples: Example personas and segments.
Personalization is an Enterprise Edition Pro feature. You can download all the modules from Magnolia's Nexus repository.
Create a backup of your system before you install a module. Uninstalling a module is not as simple as removing the .jar file. Modules add and change configurations and may change the content. Try new modules in a test environment first. A module consists of a JAR file and may include dependent JAR files. Modules are responsible for updating their own content and configurations across versions. Be sure to keep only one version of each module and its dependencies.
To install a module:
- Stop the application server.
- Copy the module JAR files into the
WEB-INF/libdirectory. The location of this directory depends on the application server.
- Restart the server.
- Go to the AdminCentral URL.
- Start the Web update process.
- Click Start up Magnolia.
Repeat the steps for each author and public instance.
To uninstall a module, remove the module JAR file from the
/WEB-INF/lib folder and restart Magnolia.
However, this is rarely enough. Modules add and modify configuration during installation. The use of a module also changes content. Removing all of these changes is difficult without knowing the installation tasks in detail.
To test a module, use the embedded Derby database and take a backup of your
repositories folder. Install the module and try it. When you are done testing, remove the module JAR and restore the
repositories folder from the backup. This way you can go back to square one.
We also recommend that you segregate the development and production environments. Take regular backups for disaster recovery so you can revert to a prior state in a routine fashion.