Installation Overview

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

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

More often than not, Manager is installed on cloud so you don't need to do it yourself. However, we recommend getting familiar with this documentation as it helps you understand some product features and performance considerations as well as how to upgrade your product to newer versions.

Each major release of Manager comes with its own installation guide describing specific steps you must perform before, during and after installation or upgrade. The installation guides are PDF documents named jm_installation_guide_v<MANAGER-MAJOR-VERSION>.pdf, for example, jm_installation_guide_v21.11.pdf.

Download the JM Installation Guide PDF

We've replaced the Manager Installation online documentation with a PDF version. Here's how you can get a copy of the PDF.

  • You can download the installation guide from the same location where the initial release of a major version of Manager downloads are hosted. For example, the installation guide for Manager 21.11 can be found in the 21.11.0 directory. We do not update the installation guide for minor and maintenance releases of Manager.
    Download

    Registered members of our resources website can request access to download Journey Platform products and documentation for supported Journey Platform releases.

  • If you have access to the Temenos instance of Microsoft Teams, you can download the JM Installation Guide PDF from Teams. Follow these steps to download the version you need:
    1. Login to Microsoft Teams.
    2. Select the Temenos Journey Manager (TJM) team.
    3. Select the Temenos Document Share channel.
    4. Select Files and browse to the JM Installation (INTERNAL USE ONLY) folder.
    5. Download the JM Installation Guide PDF (jm_installation_guide_v21.11.pdf).
  • Otherwise, contact us to request a copy of the JM Installation Guide PDF.

Plan the Installation

You need to plan the installation or upgrade of Manager carefully before you run installer in your environment or ask the cloud team to install it for you. There's no cover-it-all plan for every environment or configuration, but we have combined the best practices into a simple check list below. We strongly recommend reviewing it and commencing the installation only if all items of the list are satisfied.

The installation plan check list:

  1. Ensure you have read and understood this installation guide. If something is unclear or your need more information, contact your Customer Service or Support.
  2. Compile and build your current application packages and execute unit tests in a local IDE or on a build server using Journey SDK of the same Journey Manager version you are planning to install or upgrade to. Groovy compiler can reveal potential issues and thus provides you with more confidence to move on the next step of the upgrade.
    Important

    If any compilation or build errors arise, resolve them before commencing the installation. Resolutions may include the product configuration, Groovy scrips corrections, or cloud hosting configuration. For more information, contact your Customer Service or Support.

  3. Review all release notes of your current and target Manager versions, understand them, and analyze the impact on your existing solution. In some cases, you may need to review your current solution, for example, due to critical library updates.
  4. Ensure the back up and rollback procedures for your organizations, form spaces, forms, services, service connections work as expected, so you can restore them from back-ups.
  5. Plan ahead to upgrade all your environments to the same target Manager version.
    Important

    We don't recommend deploying any application packages in to a production environment until your test, staging, UAT, and production environments run the same Manager version.

Next, learn about Journey Manager features.