Journey Manager (JM) The transaction engine for the platform. | 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,
We've replaced the Manager Installation online documentation with a PDF version. Here's how you can get a copy of the PDF.
21.11.0 directory. We do not update the installation guide for minor and maintenance releases of Manager.
JM Installation (INTERNAL USE ONLY) folder.
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:
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.
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.