Package Workflow Process Management with Separate Authoring and Delivery Distributions
This Bloomreach Experience Manager feature requires a standard or premium license. Please contact Bloomreach for more information.
As of Bloomreach Experience Manager 14.4.0, Camunda BPM engine is no longer used to manage the review state of projects. This documentation page applies to Bloomreach Experience Manager 14.3 and older. See Upgrade 14.3 to 14.4 and Remove Camunda for details.
Introduction
Goal
Package Workflow Process Management with separate distributions for the authoring and delivery applications.
Background
Bloomreach Experience Manager's system architecture supports a deployment model in which the authoring application runs in its own container, separately from the delivery application. This requires creating separate authoring and delivery distributions from the implementation project. This pages provides additional instructions for adding Workflow Process Management to these distributions.
Instructions
- Create separate distributions for the authoring and delivery applications.
- In platform/pom.xml, add the following dependency:
<dependency> <groupId>com.onehippo.cms7</groupId> <artifactId>hippo-addon-wpm-platform-dependencies</artifactId> <type>pom</type> </dependency>
- In src/main/assembly/webapps-without-cms-component.xml, add the following after the </files> closing element:
<dependencySets> <dependencySet> <useProjectArtifact>false</useProjectArtifact> <outputDirectory>webapps</outputDirectory> <outputFileNameMapping>bpm.war</outputFileNameMapping> <includes> <include>com.onehippo.cms7:hippo-addon-wpm-camunda:war</include> </includes> </dependencySet> </dependencySets>
- Build and package using Maven as described at the bottom of Create Separate Distributions for the Authoring and Delivery Applications.
- Deploy as described in Deploy the Authoring and Delivery Web Applications Separately.