Home
Implementation Guides
Implementation Guide for Red Hat JBoss Enterprise Application Platform
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.
Load balancing
For load balancing, there is a single listener that executes commands related to Campaign flowchart and Optimize sessions. In comparison to Campaign flowchart, an Optimize session requires a significantly better hardware configuration, which exceeds the minimum recommendation, for successful execution.

Implementation Guides
- Implementation Guide for Apache Tomcat
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
  - 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.
      - Load balancing
        For load balancing, there is a single listener that executes commands related to Campaign flowchart and Optimize sessions. In comparison to Campaign flowchart, an Optimize session requires a significantly better hardware configuration, which exceeds the minimum recommendation, for successful execution.
      - Listener integration
        Prior to Unica 12.0 release, Campaign and Optimize were separate products. Users having both Campaign and Optimize had to run separate listeners. The Campaign listener unica_aclsnr to run flowcharts and Optimize listener unica_acolsnr to run the Optimize session.
    - Scaling Interact containers
  - Deployment monitoring
    The Kubernetes Dashboard is a web-based user interface to monitor deployments.
  - 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.
  - 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.
  - 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 Oracle WebLogic Server

Load balancing

For load balancing, there is a single listener that executes commands related to Campaign flowchart and Optimize sessions. In comparison to Campaign flowchart, an Optimize session requires a significantly better hardware configuration, which exceeds the minimum recommendation, for successful execution.

About this task

This newly introduced single listener helps the master listener to decide the node on which it should send the execution of the flowcharts or sessions, considering the loadBalanceWeight. We recommend that you avoid executing Optimize sessions on a node, configured to execute Campaign flowcharts. Similarly, we recommend that you avoid setting up a node with a significantly higher configuration of hardware for executing flowcharts. Using the new flag, the master listener can utilize the available resources in an appropriate way.

Choose an appropriate listenerType during installation based on the hardware, or configuration, or your requirements.

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.