Unica Journey configuration properties
The Unica Journey has additional properties on the Configuration page that perform important functions that you must specify. See the Unica Journey User Guide to learn more about what they do and how to set them.
Setting the Link and Deliver configuration properties
You can configure Unica Journey to connect to the Unica Link by using Link Configuration under the path Affinium|Journey|Link_Configurations.
Set the following Unica Link configuration properties under the Journey > Link_Configurations category manually:
- Link_URL: Specify Unica Link design server URL Ensure that it does not have the trailing /. Example: http://<FQDN>:<PORT>
- Link_Data_Source_User: Specify the Platform user which stores the credentials to Unica Link design server.
- Link_Data_Source_Name: Specify the datasource name which has the credentials information.
Also, You can configure Unica Journey to connect to theUnica Deliver by using Deliver Configuration under the path Affinium|Journey|Deliver_Configurations.
- Deliver_URL: Specify the
Unica Deliver TMS server URL.
For example:
http://<UNICA_DELIVER_HOST>/delivertms/services/TMS
. - Deliver_Partition: Specify the partition name in Campaign where Deliver TMS is configured.
You can use the following configurations to enable Unica Link and Unica Deliver integrations:
You can navigate under Platform configuration settings:
Settings for 'Journey' (Affinium|Journey)
Link_Configured - This configuration defines whether Unica Link is integrated with Unica Journey (for email/SMS/CRM channels).
Possible values - Yes/ No
Yes - Enables Unica Link integration with Journey
Deliver_Configured - This configuration defines whether Unica Deliver is integrated with Unica Journey for email.
Possible values - Yes/ No
Yes - Enables Unica Deliver integration with Journey
You are required to restart Journey web and engine components.
Platform_Configured - This configuration defines whether Unica Platform is integrated with Unica Journey
Following Platform APIs should be disabled for integrating Journey:
- Authentication = Disable all
- Datasource = Disable all
- User details = Disable all
- Get Configuration Property = Disable all
- Configuration = Disable all
- Login = Disable all
- User roles permission = Disable all
- User details = Disable all
- License = Disable all
- Get installed applications = Disable all
- Settings for 'Authentication'
(Affinium|suite|security|apiSecurity|manager|managerAuthentication)
- API URI - /authentication/login
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Disabled
- Settings for 'User'
(Affinium|suite|security|apiSecurity|manager|managerUser)
- API URI - /user/partitions/*
- Block API access - Disabled
- Secure API access over HTTPS - Disabled
- Require authentication for API access - Enabled
- Settings for 'Policy'
(Affinium|suite|security|apiSecurity|manager|managerPolicy)
- API URI - /policy/partitions/*
- Block API access - Disabled
- Secure API access over HTTPS - Disabled
- Require authentication for API access - Enabled
- Settings for 'Configuration'
(Affinium|suite|security|apiSecurity|manager|Configuration)
- API URI - /datasource/config
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Enabled
- Settings for 'Datasource'
(Affinium|suite|security|apiSecurity|manager|Datasource)
- API URI - /datasource
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Disabled
- Settings for 'Login' (Affinium|suite|security|apiSecurity|manager|Login)
- API URI - /authentication/v1/login
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Disabled
- Settings for 'User roles permissions'
(Affinium|suite|security|apiSecurity|manager|managerGetRolesPermission)
- API URI - /policy/roles-permissions
- Block API access - Disabled
- Secure API access over HTTPS - Disabled
- Require authentication for API access - Enabled
- Settings for 'User details'
(Affinium|suite|security|apiSecurity|manager|managerGetUserDetails)
- API URI - /user/user-details
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Enabled
- Settings for 'Get configuration property'
(Affinium|suite|security|apiSecurity|manager|managerGetConfigProperty)
- API URI - /configuration/get
- Block API access - Disabled
- Secure API access over HTTPS - Enabled
- Require authentication for API access - Disabled
- Settings for 'License'
(Affinium|suite|security|apiSecurity|manager|managerLicense)
- API URI - /license/*
- Block API access - Disabled
- Secure API access over HTTPS - Disabled
- Require authentication for API access - Disabled
How to generate encrypted password
- Navigate to <JOURNEY_WEB_HOME>/tools/.
- Set
JAVA_HOME
in JourneyEncryptionUtility .JAVA_HOME=<UNICA_HOME>/jre export JAVA_HOME
- If you are using Linux operating system, convert JourneyEncryptionUtility to Unix
mode using the following command:
dos2unix JourneyEncryptionUtility
- Run JourneyEncryptionUtility
with the following command:
JourneyEncryptionUtility <PASSWORD TEXT>
- JourneyEncryptionUtility
prompts the password in encrypted mode on the console output.
Use this password in the application.properties and other places before starting applications. Run this tool multiple times to generate different encrypted passwords. In cases where database password is expired or changed you require to use this utility to create new encrypted password.
Update the Journey Web and Journey Engine application properties
You are required to set passwords in encrypted format in application.properties files, This is a manual process. The following procedure provide the following steps to perform updates.
Update journey.xml used in Tomcat deployment
Journey deployment XML
file needs to have encrypted password for Journey system tables. You can encrypt the
password using JourneyEncryptionUtility
and specify the journey.xml file for field "password".
Verify and update the path forUpdate Journey Web - application.properties file
- Update encrypted password for following properties:Run Unica Platform's clientDetailsUtility to generate client details for Journey as below. On Linux system, use .sh file instead of .bat.
- Navigate to PLATFORM_HOME\tools\bin directory. If you have Platform installed on different machine, you can execute this command on the machine where Platform is installed.
- Execute command as - clientDetails -a
Journey. This generates the ClientID and ClientSecret.
The following is an
example.
C:\Unica\Platform\tools\bin>clientDetails.bat -a Journey
- Add the ClientID and ClientSecret in Journey Web application
properties.
C:\Unica\Platform\tools\bin>echo off
WARN com.unica.manager.configuration.ConfigurationManager - Local cache is turned off. Default behavior implies based on Hibernate cache parameter value
ClientID: 885345
ClientSecret: IfnKG2eqniVnaT8
AppName: Journey
ClientSecret and ClientId generated successfully!!
- Encrypt the ClientSecret using Journeys password encryption utility, JourneyEncryptionUtility. It should not be blank.
- Use generated ClientID and ClientSecret in Journey Web's
application.properties:
platform.clientId=ClientID
generated in above step.platform.clientSecret= encrypted ClientSecret
in above step. - Below mentioned properties are used to start Platform and
Journey parallelly. Platform must be started before journey
start; some application server takes more time than usual to
start the platform. These properties are used while starting
journey, it will try to connect platform in specified retry
number and time interval.
platform.connect.retry.number
: number of retries to connect platformplatform.connect.retry.interval
: retry interval time for connect to platform in millisecondsValues of these properties are different based on which application server is used. For Tomcat default values will work and for Websphere Application Server (WAS) need to increase time interval between retries.
Update Journey Engine - application.properties file
- Generate encrypted password for the following properties and mention in the
application.properties file:
journey.datasource.password
journey.report.datasource.password
- If you are using Windows, perform the following sub-steps.
- Modify
JOURNEY_HOME/KafkaStandalone/config/zookeeper.properties
under to update "dataDir" parameter path to include double forward slash (\\) instead of back slash (/). - Modify
JOURNEY_HOME/KafkaStandalone/config/server.properties
to update "log.dirs" parameter path to include double forward slash (\\) instead of back slash (/).
- Modify
- spring.entity.files.upload.defaultPath=C:\\wasfp4MsSql\\Journeys\\Files\\
- spring.ignite.storage.path=C:\\wasfp4MsSql\\Journeys\\Web\\ignite
Journey engine properties file changes -
- journey.datasource.password = <encrypted pwd>
- journey.report.datasource.password= <encrypted pwd>