Introduction

   Journey Manager (JM) Previously known as Transact Manager (TM). |   System Administrator |   v20.05 This feature was updated in v20.05.

Before you can start using Journey Manager, you must correctly install and configure it. This is easy to do by following this documentation, which is designed and written for product evaluators, administrators, as well as developers. However, to install Journey Manager on CentOS Linux, Oracle Linux, Red Hat Enterprise Linux or Microsoft Windows operating systems, you should be familiar with your target operating system and its administration.

The installation documentation is version specific, because each installer may require some additional steps to be performed before, during or after the installation or upgrade process. This online documentation is for Journey Manager version 20.05. For the previous versions of Journey Manager, see the installation guides listed below:

Release Version Installation Guide

20.05

tm_installation_guide_v20.05.pdf

19.11

tm_installation_guide_v19.11.pdf

19.05

tm_installation_guide_v19.05.pdf

18.11

tm_installation_guide_v18.11.pdf

18.05

tm_installation_guide_v18.05.pdf

17.10

tm_installation_guide_v17.10.pdf

5.1

tm_installation_guide_v5.1.pdf

4.3

tm_installation_guide_v4.3.pdf

As you might know, Avoka is now a part of Temenos, so the product names have been changed. This includes Transact Manager, which has been re-branded as Journey Manager and the change has been applied in the previous release 19.5.0. The modules have also been re-branded, so Transact Maestro has become Journey Maestro and so on.

The user interfaces have been re-branded, however, to ensure a smooth upgrade for our client base, the following items retain the Avoka Transact names in the 20.5.0 release:

  • Installer file name: avoka-tm-setup-20.5.0-win-x64.jar or avoka-tm-setup-20.5.0-linux-x64.jar
  • Default installation directory: /opt/avoka/transact/manager or C:/avoka/transact/manager
  • Default database schema and user names: txmanager
  • Service names: Avoka Transaction Manager (Windows ) or txmanager (Linux)
  • Module names and the corresponding WAR files names: Transact Manager or tm-manager.war
  • Code module paths to ensure that existing custom Groovy scripts work, for example, Fluent API com.avoka.tm.vo.Txn

Next