Install the Translations Add-On 1.03

Introduction |  Install  | Configure | Release Notes  | Upgrade to 2.0

This section assumes you are using Maven to manage your Bloomreach Experience Manager project.

Add a dependency to the CMS module

Add the following dependency to your project cms pom.xml file:

    <dependency>
      <groupId>com.onehippo.cms7</groupId>
      <artifactId>translations-addon-bom</artifactId>
      <type>pom</type>
    </dependency>

Use dependency management in your root pom to set the version of the Translations add-on. You can find the latest tagged version in the release notes. Add the following to the dependencyManagement secion of you root pom:

    <dependency>
      <groupId>com.onehippo.cms7</groupId>
      <artifactId>translations-addon-bom</artifactId>
      <version>${translations-addon.version}</version>
      <type>pom</type>
    </dependency>

add the translations-addon.version to the properties section of the root pom:

<translations-addon.version>1.03.04</translations-addon.version>

Install the latest Settings Management add-on from Forge

The translations add-on depends on the Forge Settings Management add-on. Follow the installation guide of the forge add-on, version 0.5.0.

Add Activemq dependencies to the project

In the dependencyManagement section of your project's root pom, add:

<dependency>
  <groupId>org.apache.activemq</groupId>
  <artifactId>activemq-client</artifactId>
  <version>5.11.0</version>
  <scope>runtime</scope>
  <exclusions>
    <exclusion>
      <artifactId>slf4j-api</artifactId>
      <groupId>org.slf4j</groupId>
    </exclusion>
  </exclusions>
</dependency>

and add the following to the dependencies section of the root pom. If you do not have a dependencies section, create it.

<dependencies>
  <dependency>
    <groupId>org.apache.activemq</groupId>
    <artifactId>activemq-client</artifactId>
  </dependency>
</dependencies>

You can now build your project to include all the plugins and new dependencies. The addon will need to connect to ActiveMQ, so first follow the confguration instructions below to start activeMQ.

Configure for local testing/development

Add the JNDI resources for the translation queue in your conf/context.xml within the <Context> tag :

            <Resource auth="Container"
                      name="jms/ConnectionFactory"
                      type="org.apache.activemq.ActiveMQConnectionFactory"
                      description="JMS Connection Factory"
                      factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                      brokerURL="tcp://localhost:61616"
                      brokerName="MyActiveMQBroker"/>

            <Resource auth="Container"
                      name="jms/TRANSLATION.OUTBOUND"
                      type="org.apache.activemq.command.ActiveMQQueue"
                      description="JMS queue"
                      factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                      physicalName="TRANSLATION.OUTBOUND"/>

            <Resource auth="Container"
                      name="jms/TRANSLATION.INBOUND"
                      type="org.apache.activemq.command.ActiveMQQueue"
                      description="JMS queue"
                      factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                      physicalName="TRANSLATION.INBOUND"/>

You can start a self-contained ActiveMQ instance at tcp://localhost:61616 by running

mvn -Pactivemq-local

from the connectors module of the Translations adddon: /connectors/

Then, start the Local mirror connector by running

mvn -Pconnector.run

from the Local mirror connector module of the Translations addon: /connectors/local-mirror-connector

Last, start your project by running:

mvn -Pcargo.run