Home
Implementation Guides
Implementation Guide for Apache Tomcat
Scaling Unica containers
Scaling a deployment ensures creation and scheduling of new Pods. Scaling increases the number of Pods to the new required state. Kubernetes also supports autoscaling of Pods.
Scaling Journey engine containers
In Kubernetes, Journey engine are defined as StatefulSets.

Implementation Guides
- Implementation Guide for Apache Tomcat
  - Cloud Native Unica Overview
  - Docker, Kubernetes, and Helm
    In this release, we have implemented Cloud Native Unica using Docker, Kubernetes, and Helm.
  - ELK Overview
    The ELK Stack is a collection of three open-source products: Elasticsearch, Logstash, and Kibana.
  - Pre-installation configurations
    Before installing or upgrading to Cloud Native Unica, you should complete some configurations.
  - Cloud Native Unica Helm release architecture
    The following is a diagrammatic representation of the Cloud Native Unica Helm release architecture:
  - Helm chart configuration
    Before you start the installation or upgrade of Cloud Native Unica, you should configure the appropriate configMap YAML files.
  - Installation and verifying the installation
  - Post installation configurations
    The following topics contain details about post installation configurations related to the products of Unica.
  - Migration of on-premises applications to Cloud Native Unica
  - Cloud Native Unica upgrade
    To upgrade an earlier version of Cloud Native Unica to a newer version, complete the following steps:
  - Scaling Unica containers
    Scaling a deployment ensures creation and scheduling of new Pods. Scaling increases the number of Pods to the new required state. Kubernetes also supports autoscaling of Pods.
    - Scaling Listener containers
      Listeners are defined as StatefulSets in Kubernetes. Each Pod in a StatefulSet derives its hostname from the name of the StatefulSet and the ordinal of the Pod.
    - Scaling Interact containers
    - Scaling Journey engine containers
      In Kubernetes, Journey engine are defined as StatefulSets.
  - Using Red Hat OpenShift
    You can use OpenShift to develop and runcontainerized applications. OpenShift allows applications, and the data centers that support them, to expand from just a few machines and applications to thousands of machines that serve millions of clients.
  - Deployment monitoring
    The Kubernetes Dashboard is a web-based user interface to monitor deployments.
  - Product utilities
    You can execute all the utilities of the Unica products in their assigned pods.
  - Using secret to avoid passwords in plain text
    To use a secret to avoid using passwords in plain text, complete the following steps:
  - Using AWS Secrets and Configuration Provider with Kubernetes Secret Store CSI Driver
    AWS Secrets Manager securely retrieves secrets from the AWS Secrets Manager for Amazon Elastic Kubernetes Service (Amazon EKS) Kubernetes pods.
  - Enabling Multicast using Weave-Net CNI plugin on AWS EKS cluster
    You can enable multicasting on AWS EKS cluster only for Kubernetes versions 1.21 or above,
  - FAQs and troubleshooting
    This section covers the frequently asked questions and troubleshooting issues.
  - Uninstalling the chart
  - Appendix: Description of Helm chart parameters
    The following topics contain description of the parameters present in the configMap YAML files:
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
- Implementation Guide for Oracle WebLogic Server

Scaling Journey engine containers

In Kubernetes, Journey engine are defined as StatefulSets.

Each Pod in a StatefulSet derives its hostname from:

the name of the StatefulSet, and
the ordinal of the Pod.

The service manages the Pod domain and the format is as follows:

$(service name).$(namespace).svc.cluster.local

Example:

The Journey engine pod is regitered in the following format:

journey-0.listener.default.svc.cluster.local

In the Helm chart, you can configure these pods in the journey-configMap.yaml file.

Like a Deployment, a StatefulSet manages the Pods that are based on identical container specifications.

Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods.

The location of Journey Engine shared home is $HOME_DIR/Journey/Engine.

For the scaled instances of StatefulSet, journey-0, journey-1, journey-2,..journey-n, each instance has a file system mapped on the mount location.

Example:

$HOME_DIR/Journey/journey-0

In a Journey engine, by default, clustering is enabled. As soon as the engine starts, it creates journey-0, which is a copy of the engine folder. As you keep scaling the Journey engine, it creates folders named journey-0, journey-1, journey-2,..journey-n.

The logs for each pod will also be generated as journey-0, journey-1, journey-2,..journey-n.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.