Home
Implementation Guides
Implementation Guide for Apache Tomcat
Pre-installation configurations
Before installing or upgrading to Cloud Native Unica, you should complete some configurations.
Listener Database client setup
To establish an ODBC connection to the database, the Campaign listener requires a database client.

Implementation Guides
- Implementation Guide for Apache Tomcat
  - 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.
    - Avoiding timeout issues
      To avoid timeout issues, perform the following steps.
    - Application server setup
      Cloud Native Unica supports Apache Tomcat®, Red Hat® JBoss® Enterprise Application Platform (EAP), and Oracle® WebLogic Server application servers.
    - Database setup
      You need to set up the database before you begin installation.
    - Listener Database client setup
      To establish an ODBC connection to the database, the Campaign listener requires a database client.
    - Setting up the Cloud Native environment
      You must set up the Cloud Native environment before implementing Cloud Native Unica. The chart that you download uses Helm as a package manager for Kubernetes. The chart is a preconfigured application resource and it deploys Unica suite on a specified Kubernetes cluster. Extract the chart ZIP file to a location in the cloud VM, where you plan to deploy Unica. For reference purposes, this chart contains a placeholder for the database. Unica does not own the database and is not responsible for database management. If required, set a containerized database (the charts and subcharts folders are for reference) as a subchart to the Cloud Native Unica chart. You can use scripts to automate the restoration of database on a container.
    - Cloud Native Unica setup on SSL
      You can configure SSL on Cloud Native Unica setup at the ingress level.
  - 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.
  - 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.
  - 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

Listener Database client setup

To establish an ODBC connection to the database, the Campaign listener requires a database client.

About this task

If you do not have a database client, you must install it. For a seamless installation of the database client, perform the following steps:

Procedure

Place the database client installer at the mount locaction (NFS).
Configure the location of the database client installer in the campaign-configMap.yaml file.
Example: For MariaDB database
In the campaign-configMap.yaml file, locate the MARIADB_CLIENT_INSTALL_SCRIPT parameter. The MARIADB_CLIENT_INSTALL_SCRIPT parameter must be configured with the path of the test scripts to install database client on the listener pod (/docker/unica/mariadb.sh). You can write a set of command in this file to install the client and it is executed during the startup of the listener pod.
```
install /docker/unica/libmaodbc.so /usr/lib64/
yum install -y unixODBC
yum install -y compat-openssl10
```
Example: For Oracle Database
In the campaign-configMap.yaml file, locate the ORACLE_CLIENT_INSTALL_SCRIPT parameter. The ORACLE_CLIENT_INSTALL_SCRIPT parameter must be configured with the path of the test scripts to install database client on the listener pod (/docker/unica/oracle.sh). You can write a set of command in this file to install the client and it is executed during the startup of the listener pod.
```
yum install -y libaio
cp /usr/lib64/libnsl.so.2.0.0 /usr/lib64/libnsl.so.1
```

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.