Installation of Unica Link in Native Mode
Dependencies
bash
(Bourne Again SHell)ksh
(KornShell)libnsl
- GNU
sed
- MongoDB server
Native System Configuration
- changing the temporary directory, or
- removing
noexec
from the /tmp directory.
Changing the Link Temporary Directory
To change the Link temporary directory, complete the following steps:
- Create a new directory. Ensure that the
noexec
option is not used for mounting of the location. - Check the output of the mount. For example, run the following
commands:
mkdir /opt/hiptmp
chmod 777 /opt/hiptmp
- Add a new line to
tomcat-context/install/restapi/tomcat/setenv.sh to
specify the new directory. For
example:
export JAVA_OPTS="$JAVA_OPTS Djava.io.tmpdir=/opt/hiptmp"
- For the long and short workers, modify the existing lines in
config.yaml. For
example:
longTaskProcessJvmOptions="-Xmx2g -Djava.io.tmpdir=/opt/hiptmp" shortTaskProcessJvmOptions="-Djava.io.tmpdir=/opt/hiptmp"
- Restart Link.
Changing the Mount Option for /tmp
The /tmp directory must be mounted with noexec
.
To verify, run the following commands:
mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,relatime)
If /tmp directory is already mounted with
noexec
, you can change the mount option for
/tmp directory. To change the the mount option for /tmp
directory, complete the following steps:
- Ensure that you are using root user privileges.
- Edit /etc/fstab and remove noexec from the mount options of /tmp.
- Either:
- Reboot the system, or
- Run the following
command:
mount -o remount /tmp
Configuration
To configure most properties of Link, use the file config.yaml.
Review the config.yaml file before you perform the installation to confirm that all default options are as expected.
To reconfigure after installation, update those files, and restart Link.
You will notice several directories specified in the configuration files. If you, or the group you install as, lack Read/Write access to these directories, contact a system administrator to create the directories and transfer ownership.
Tomcat (REST API + Server): HTTPS 8443, HTTP 8080
UI Client: HTTPS 4443
Installation
- The following commands are intended for a quick-start scenario:
- Use the following command to generate
configuration:
./Link configure -–generate
- Change the Unica Journey/Unica Campaign/Unica Platform properties under <Link installer>/ integration-context/apps/ and place the connectors under <Link installer>/ integration-context/connectors.
- Enable the Unica application to embed the Link UI. Customize the
Link configuration by changing the value of the
contentSecurityPolicy parameter in
<Link installer>/Config.yaml file. The
value is list of URLs that point to Unica journey and Unica Campaign
web application servers. For example, the URLs can be
http://ipaddress:port or
http://hostname:port which point to Unica
journey and Unica Campaign web application servers.
If the URLs are not set correctly, Unica cannot access link in iframe and you will see error while loading link in iframe.
-
./Link configure --type native --integration unica
-
./Link install
- Change the kafkalink properties under <Link-install>/integration-context/install/.
- Either start all components or continue to the troubleshooting
section for any errors.
./Link start
- Use the following command to generate
configuration:
- When Link is up and running, navigate to the location that is set for the
environment variable files and create a new folder
tmp.
Refer to the file config.yaml, present in the installation location, to see the folder path that is set for the files parameter. The default path is /opt/hip-rest. If the default path is /opt/hip-rest, the tmp folder file path is /opt/hip-rest/tmp.