Home
Implementation Guides
Implementation Guide for Apache Tomcat
Installation and verifying the installation
Log files
Confirm if the required containers are up and running. Upon confirmation, check the logs for all the running services.
Campaign Log Files
To enable the ETL, Engage, and UBX logs within the Campaign logs folder, provide the absolute path in the $CAMPAIGN_HOME/conf/campaign_log4j.properties file.

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.
  - 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
    - Installation
      You can install Unica using Helm charts. Override the following Helm chart values using --set name=value.
    - Verifying the chart
    - Log files
      Confirm if the required containers are up and running. Upon confirmation, check the logs for all the running services.
      - Campaign Log Files
        To enable the ETL, Engage, and UBX logs within the Campaign logs folder, provide the absolute path in the $CAMPAIGN_HOME/conf/campaign_log4j.properties file.
  - 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

Campaign Log Files

To enable the ETL, Engage, and UBX logs within the Campaign logs folder, provide the absolute path in the $CAMPAIGN_HOME/conf/campaign_log4j.properties file.

Example

log4j.appender.ETL.File=/docker/unica/Campaign/logs/ETL.log
log4j.appender.ENGAGE_ETL.File=/docker/unica/Campaign/logs/EngageETL.log
log4j.appender.UBX.File=/docker/unica/Campaign/logs/UBX.log

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.