Unica Journey
Release Notes
System Requirements
Installation Guides
Upgrade Guide
Sizing Guide
Administrator's Guide
- An Introduction to Unica Journey
  Unica Journey is a goal-based orchestration solution to craft, execute, and visualize context-driven, personalized, multi-step omnichannel customer experiences.
- New navigation UI
  Unica has introduced New UI.
- Journey Multi Partition
- Clean-up Journey Audiences
- Unica Journey integrations
- Process of Starting and Stopping Journey
- Journey user roles and permissions
  Before you begin using Unica Journey, you should assign roles and permissions to users.
- Journey interaction logging
  Interaction Logging for Journey is executed as a scheduled job. The scheduling parameters are set in application.properties file of the Journey Engine. The following is an example of the setting:
- Journey logging
  In Journey version 12.1.2 and earlier, the property JOURNEY_LOGGING, in the journey_master_config.properties file, was only used for tracing the audience.
- Configuring OptIn Optout functionality
- Journey GDPR
- Kafka authentication using SSL
- Kafka authentication using Kerberos
- Configure Web Application servers Tomcat for SSL
  On every application server on which a Unica application is deployed, configure the web application server to use the certificates you have decided to employ.
- Mailchimp Configuration
  Configuration of Mailchimp as external source with Journey.
- Settings
  Use the settings menu to manage the Journey integrations like Email connectors, SMS connectors, CRM connections, and REST integrations.
System Schema
Tuning Guide
Accelerators
User Guide
Superset Reports
Director
Licensing Guide
PDFs
Notices

Configuring Kafka Server with Kafka SASL_SSL

Update the following server.properties in Kafka server configuration directory.

listeners=SASL_SSL:// <KAFKA_HOST>:<KAFKA_PORT>  
security.inter.broker.protocol=SASL_PLAINTEXT 
sasl.mechanism.inter.broker.protocol=PLAIN 
sasl.enabled.mechanisms=PLAIN 
ssl.keystore.location=/PATH/kafka.server.keystore.jks
ssl.keystore.password=password 
ssl.key.password= password 
ssl.truststore.location=/PATH/kafka.server.truststore.jks 
ssl.truststore.password= password 
ssl.endpoint.identification.algorithm= 
ssl.client.auth=required 
security.inter.broker.protocol=SSL

In case of WebSphere App server
Add following configuration in <Websphere_Location>\profiles<profileName>\properties\wsjaas.conf
```
KafkaClient

{org.apache.kafka.common.security.plain.PlainLoginModule required
username="alice"
password="alice-secret"; }
```
Once you've updated the JAAS configuration, ensure that WebSphere knows about it.
Add this to the JVM arguments:
- Open WebSphere Admin Console.
- Go to Servers > Server Types > WebSphere application servers > Select your server > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties.
- Add a new custom property:
  - Name: java.security.auth.login.config
  - Value: C:\path\to\your\kafka_client_jaas.conf