Welcome
Implementation Guides
Implementation Guide for Apache Tomcat
Appendix: Description of Helm chart parameters
The following topics contain description of the parameters present in the configMap YAML files:
Journey configurations
To configure the Journey server for Cloud Native Unica, make the necessary modifications to the journey-configMap.yaml file.

Cloud Native Unica
Release Notes
Getting Started with Cloud Native Unica
Implementation Guides
- Implementation Guide for Apache Tomcat
  - Helm chart configuration
    Before you start the installation or upgrade of Cloud Native Unica, you should configure the appropriate configMap YAML files.
  - FAQs and troubleshooting
    This section covers the frequently asked questions and troubleshooting issues.
  - 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.
    - Audience Central configurations
      To configure Audience Central for Cloud Native Unica, make the necessary modifications to the audiencecentral-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 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.
    - InteractDT configurations
      To configure Interact DT for Cloud Native Unica, make the necessary modifications to the interactDT-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 Cloud Native Unica, 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.
    - Segment Central configurations
      To configure Segment Central for Cloud Native Unica, make the necessary modifications to the segmentcentral-configMap.yaml file.
    - Sub-chart configuration in Helm charts
    - values.yaml driven configurations
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
- Implementation Guide for Oracle WebLogic Server
PDFs
Notices

Journey configurations

To configure the Journey server for Cloud Native Unica, make the necessary modifications to the journey-configMap.yaml file.

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

Table 1. Common parameters of Journey
Parameter name	Parameter description
JOURNEY_HOST_NAME	The system host name of Journey.
JOURNEY_MANAGEMENT_PORT	The management port number for the Journey system.
JOURNEY_MANAGEMENT_HTTPS_PORT	The management `HTTPS` port number for the Journey system.
JOURNEY_AJP_PORT	The `AJP` port number for the Journey system.
JOURNEY_HTTP_PORT	The `HTTP` port number for the Journey system.
JOURNEY_HTTPS_PORT	The `HTTPS` port number for the Journey system.
JOURNEY_RECOVERY_ENV_PORT	The recovery environment port number of the Journey system.
JOURNEY_STATUS_MANAGER_PORT	The status manager port number of the Journey system.
JOURNEY_MIN_HEAP	The maximum heap size allocated for Journey. For example, `1024m`.
JOURNEY_MAX_HEAP	The maximum heap size allocated for Journey. For example, `6614m`.
MIN_ENGINE_MEMORY	Example: `"1g"`
MAX_ENGINE_MEMORY	Example: `"3g"`
DB_TYPE_JOURNEY	The name of the database used by the Journey system. For example, `Oracle`.
DB_DRIVER_CLASS_JOURNEY	The class name of the Journey Database drivers. For example `oracle.jdbc.OracleDriver`.
JOURNEYREPORT_DB_NAME	The database name of the server hosting the Journey Reports. For example, `journeyuser`.

Multicast parameters for Journey



KAFKA_BROKER	Example: `"kafka-0.kafka.default.svc.cluster.local:9092"`
REPLICATION_COUNT	`"1"`
JOURNEY_MULTICAST_IP	Example: `"{{ .Values.journeyMultiCastData.JOURNEY_MULTICAST_IP }}"`
JOURNEY_MULTICAST_PORT	Example: `"{{ .Values.journeyMultiCastData.JOURNEY_MULTICAST_PORT }}"`

Installation parameters for Journey


Parameter name	Parameter description
JOURNEY_INSTALL_COMMAND1 JOURNEY_INSTALL_COMMAND2 JOURNEY_INSTALL_COMMAND3 JOURNEY_INSTALL_COMMAND4 JOURNEY_INSTALL_COMMAND5 JOURNEY_INSTALL_COMMAND6 JOURNEY_INSTALL_COMMAND7 JOURNEY_INSTALL_COMMAND8 JOURNEY_INSTALL_COMMAND9 JOURNEY_INSTALL_COMMAND10 JOURNEY_INSTALL_SCRIPT1 JOURNEY_INSTALL_SCRIPT2	Parameters used for Installation commands and scripts that can be used for customization.