Home
Implementation Guides
Implementation Guide for Oracle WebLogic Server
Appendix: Description of Helm chart parameters
The following topics contain description of the parameters present in the configMap YAML files:
Content Integration configurations
To configure Content Integration for Cloud Native Unica, make the necessary modifications to the assetpicker-configMap.yaml file.

Implementation Guides
- Implementation Guide for Apache Tomcat
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
- Implementation Guide for Oracle WebLogic Server
  - 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.
  - 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:
    - Common configurations
      To configure the common configurations, make the necessary modifications to the common-configMap.yaml file.
    - Campaign configurations
      To configure Campaign for Cloud Native Unica, make the necessary modifications to the campaign-configMap.yaml file.
    - Centralized Offer Management configurations
      To configure Centralized Offer Management for Cloud Native Unica, make the necessary modifications to the offer-configMap.yaml file.
    - Collaborate configurations
      To configure the Collaborate for Cloud Native Unica, make the necessary modifications to the collaborate-configMap.yaml file.
    - Contact Central configurations
      To configure Contact Central for Cloud Native Unica, make the necessary modifications to the contactcentral-configMap.yaml file.
    - Content Integration configurations
      To configure Content Integration for Cloud Native Unica, make the necessary modifications to the assetpicker-configMap.yaml file.
    - Director configurations
      To configure Director for Cloud Native Unica, make the necessary modifications to the director-configMap.yaml file.
    - Insights Reports configurations
      To configure Insights Reports reports for Cloud Native Unica, make the necessary modifications to the birt-configMap.yaml file.
    - Interact configurations
      To configure Interact for Cloud Native Unica, make the necessary modifications to the interact-configMap.yaml file.
    - Journey configurations
      To configure the Journey server for Cloud Native Unica, make the necessary modifications to the journey-configMap.yaml file.
    - Journey web configurations
      To configure the Journey web server for Journey, make the necessary modifications to the journeyweb-configMap.yaml file.
    - Kafka configurations
      To configure the Kafka server for Journey, make the necessary modifications to the kafka-configMap.yaml file.
    - Plan configurations
      To configure Plan for Cloud Native Unica, make the necessary modifications to the plan-configMap.yaml file.
    - Platform configurations
      To configure Platform for Cloud Native Unica, make the necessary modifications to the platform-configMap.yaml file.
    - Sub-chart configuration in Helm charts
    - values.yaml driven configurations

Content Integration configurations

To configure Content Integration for Cloud Native Unica, make the necessary modifications to the assetpicker-configMap.yaml file.

To access the assetpicker-configMap.yaml file, navigate to /unica/templates/ in the Unica charts folder. Open the file and make modifications to the following parameters:

Table 1. Application server-related parameters of Content Integration
Parameter name	Parameter description
ASSET_HOST_NAME	The system host name of Content Integration.
ASSET_MANAGEMENT_PORT	The management port number for the Content Integration system.
ASSET_MANAGEMENT_HTTPS_PORT	The management HTTPS port number for the Content Integration system.
ASSET_AJP_PORT	The AJP port number for the Content Integration system.
ASSET_HTTP_PORT	The HTTP port number for the Content Integration system.
ASSET_HTTPS_PORT	The HTTPS port number for the Content Integration system.
ASSET_RECOVERY_ENV_PORT	The recovery environment port number of the Content Integration system.
ASSET_STATUS_MANAGER_PORT	The status manager port number of the Content Integration system.
PRODUCT_OPTS_ASSET	Product specific options for Content Integration.
ASSET_PRODUCT_NAME	The name assigned ofr the Content Integration
ASSET_WAR_NAME	The name of the `WAR` file.
ASSET_APPLICATION_NAME	The name of the main application. For example, `Unica`.
ASSET_DOMAIN_USERNAME	The domain username for Content Integration.
ASSET_DOMAIN_PASSWORD	The domain password for Content Integration.

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.