Prerequisites to install Campaign on Linux prerequisites-of-campaign-installation-in-linux
Software prerequisites software-prerequisites
This section details the preliminary configurations steps required before installing ÃÛ¶¹ÊÓƵ Campaign.
The technical and software configuration required for installing ÃÛ¶¹ÊÓƵ Campaign is detailed in the Compatibility matrix.
As a reminder, the following components need to be installed and correctly configured:
- Apache, refer to Compatibility matrix,
- Java JDK and OpenJDK, refer to Java Development Kit - JDK,
- Libraries, refer to Libraries,
- Database access layers, refer to Database access layers,
- LibreOffice, refer to Installing LibreOffice for Debian and Installing LibreOffice for CentOS,
- Fonts, refer to Fonts for MTA statistics and Fonts for Japanese instances.
Libraries libraries
To install ÃÛ¶¹ÊÓƵ Campaign in Linux, please make sure you have the required libraries.
-
Library C must be able to support TLS (Thread Local Storage) mode. This mode is active in most cases except with some kernels for which Xen support has been disabled.
To check this, you can use the uname -a | grep xen command for example.
If the command does not return an empty line, it means configuration is correct.
-
You must have OpenSSL version 1.0.2 or higher.
For RHEL distributions, version 1.0 of OpenSSL is required.
-
To use ÃÛ¶¹ÊÓƵ Campaign, you need to have the libicu library installed.
SELinux selinux
When used, the SELinux module must be properly configured.
To do this, log on as root and enter the following command:
echo 0 >/selinux/enforce
In addition to this, in the /etc/sysconfig/httpd file, the following line was added to reference the ÃÛ¶¹ÊÓƵ Campaign environment configuration script:
. ~neolane/nl6/env.sh
In RHEL and CentOS, compatibility issues with the client layers of databases were noted when SELinux is enabled. To be sure ÃÛ¶¹ÊÓƵ Campaign is able to operate correctly, we recommend disabling SELinux.
Apply the following process:
-
Edit the file /etc/selinux/config
-
Modify the SELINUX line as follows:
SELINUX=disabled
Fonts for MTA statistics fonts-for-mta-statistics
In order for reports on MTA statistics (nms/fra/jsp/stat.jsp) to be displayed correctly, add fonts.
In Debian, add the command:
apt install xfonts-base xfonts-75dpi ttf-bitstream-vera ttf-dejavu
Use the following command for RHEL:
dnf install xorg-x11-fonts-misc xorg-x11-fonts-75dpi dejavu-lgc-sans-fonts dejavu-sans-fonts dejavu-sans-mono-fonts dejavu-serif-fonts
Fonts for Japanese instances fonts-for-japanese-instances
Fonts of specific characters are necessary for the Japanese instances in order to export the reports to PDF format.
In Debian, add the command:
apt install fonts-ipafont
For RHEL, add the following command:
dnf install epel-release # if required
dnf install vlgothic-fonts
Installing LibreOffice for Debian installing-libreoffice-for-debian
For Debian, the following configurations are required:
-
Install the following standard packages:
code language-none apt-get install libreoffice-writer libreoffice-calc libreoffice-java-common -
Install the following fonts (optional but highly recommended for Japanese instances):
code language-none apt-get install fonts-ipafont
Installing LibreOffice for CentOS installing-libreoffice-for-centos
The following configurations are necessary with CentOS:
yum install libreoffice-headless libreoffice-writer libreoffice-calc
Database access layers database-access-layers
The access layers for the database engine you are using must be installed on your server and be accessible via the ÃÛ¶¹ÊÓƵ Campaign account. Versions and installation modes may vary depending on the database engine used.
The supported pilot version are detailed in the Compatibility matrix.
Also check the general Database section.
PostgreSQL postgresql
ÃÛ¶¹ÊÓƵ Campaign supports all versions of the PostgreSQL client libraries from version 9.6: libpq.so.5.
Using PostgreSQL with ÃÛ¶¹ÊÓƵ Campaign also requires installing the corresponding pgcrypto libraries.
Oracle oracle
Retrieve the library version for 64-bit Debian, i.e.: libclntsh.so, libclntsh.so.19.1, libclntsh.so.18.1, libclntsh.so.12.1, libclntsh.so.11.1 or libclntsh.so.10.1.
You can obtain a Linux RPM package from the Oracle Technology Network.
Troubleshooting and best practices
Problems can appear after an Oracle client or a server update, change of version or at the first installation of the instance.
If you notice on the client console that there are unexpected time lags (one or more hours) in logs, workflow last processing, next processing, and so on, there might be a problem between the library of the Oracle client and the Oracle Server. To avoid such problems
-
Make sure to use the full client.
Various problems have been identified when using the Oracle Instant Client version. In addition, it is impossible to change the Timezone file on instant client.
-
Make sure that the client version and the database server version are the same.
Mixing versions despite Oracle’s compatibility matrix and recommendation to align client and server versions is known to cause problems.
Also check ORACLE_HOME value to make sure it points to the expected client version (in case several versions are installed on the machine).
-
Make sure the client and the server use the same timezone file.
Implementation steps implementation-steps
ÃÛ¶¹ÊÓƵ Campaign installations for Linux must be carried out in the following sequence: server installation followed by instance configuration.
The installation process is described in this chapter. The installation steps are as follows:
- Step 1: Installing the application server, refer to Installing packages with Linux.
- Step 2: Integrating with a Web server (optional, depending on the components deployed).
Once the installation steps are complete, you need to configure the instances, the database and the server. For more on this, refer to About initial configuration.