This document describes how to install the Workflow HeatMap package, which enables Adobe Campaign administrators to monitor workflows on a daily basis.
Note:
The Workflow HeatMap is available by default in Adobe Campaign Classic starting 18.10 release. The procedure below only applies if you require this feature for any build from 8700 and prior to 8977 (18.10).
The Workflow HeatMap package is available for hosted, on-premise and hybrid Adobe Campaign Classic deployments. It can only be installed by a system administrator (or set up by Adobe for hosted mode).
For hybrid and on-premise deployments, the installation is handled by the customer and must be tested on a dev/staging environment before moving to production.
To request the package:
- Customers running Adobe Campaign Classic through a hosted deployment must ask Adobe to install this package by opening a ticket to Customer Care.
- Customers running Adobe Campaign Classic through an on-premise or hybrid deployment can request this package by opening a ticket to Customer Care.
Once installed, the Campaign Workflow HeatMap page replaces the existing workflow monitoring page and collects various indicators from the xtkWorkflowTask table to generate the map.
The Adobe Campaign Workflow HeatMap consists in a color-coded graphical representation of all the workflows that are running on a specific day.
It enables the platform administrators to have a quick overview on all the concurrent workflows, which allows them to monitor the load on the instance and plan workflows accordingly.
For more on this, refer to the detailed documentation.
When you first access Worfklow HeatMap the following pop-up window will appear. This agreement allows the transfer and storage in the United States allowing Adobe Campaign. For more on this, refer to this page.
Once the package is downloaded to your server(s), extract the content and copy-paste the datakit and web folders to your [installation folder].
Caution:
If you have more than one server, the package needs to be installed on all servers before proceeding to the next step.
Once the package is downloaded to your server(s), extract the content and copy the datakit and web folders to the [usr/local/neolane/nl6] folder:
neolane@hostname:~$ cd /usr/local/neolane/nl6/ neolane@hostname:~/nl6$ tar -xvf HeatMap.tar datakit/ datakit/nms/ datakit/nms/deu/ datakit/nms/deu/package/ datakit/nms/deu/package/heatmap.xml datakit/nms/deu/strings/ datakit/nms/deu/strings/heatmap.xml datakit/nms/eng/ datakit/nms/eng/package/ datakit/nms/eng/package/heatmap.xml datakit/nms/eng/strings/ datakit/nms/eng/strings/heatmap.xml datakit/nms/fra/ datakit/nms/fra/package/ datakit/nms/fra/package/heatmap.xml datakit/nms/fra/strings/ datakit/nms/fra/strings/heatmap.xml datakit/nms/jpn/ datakit/nms/jpn/package/ datakit/nms/jpn/package/heatmap.xml datakit/nms/jpn/strings/ datakit/nms/jpn/strings/heatmap.xml datakit/xtk/ datakit/xtk/eng/ datakit/xtk/eng/jssp/ datakit/xtk/eng/jssp/production.jssp datakit/xtk/eng/jssp/workflowOverview.jssp web/ web/heatmap.css web/lib/ web/lib/d3.js web/lib/moment.js neolane@hostname:~/nl6$
Caution:
If you have more than one server, the package needs to be installed on all servers before proceeding to the next step.
Once the installation is done on all servers, a post-upgrade is recommended to force the regeneration of all schemas. For more on this, refer to the Adobe Campaign documentation.
nlserver config -postupgrade -check -instance:<instance_name> && nlserver config -postupgrade -instance:<instance_name> -force
It is required to restart the Adobe Campaign application servers. Once done, clear the client console local cache, then disconnect and reconnect.
