Application server application-server
The required database access layers must be installed on the server and accessible from the ÃÛ¶¹ÊÓƵ Campaign account.
Java Development Kit - JDK jdk
Java Development Kit, or JDK, is a software development kit. It is the foundational component that enables Java application and Java applet development.
The dynamic Web page generator uses JSP technology. For this, a Tomcat engine (from Apache) is included in the application. It requires a Java Development Kit (JDK), installed on all servers which the ÃÛ¶¹ÊÓƵ Campaign application is installed on.
You must first install a JDK on the computers on which you wish to run the ÃÛ¶¹ÊÓƵ Campaign application server (nlserver web process) because it incorporates a servlet container, Apache Tomcat, used to generate dynamic Web pages (reports, Web forms, etc).
The application has been approved for the Java Development Kit (JDK) developed by Oracle as well as for OpenJDK.
The supported versions are detailed in Campaign Compatibility matrix.
-
Starting v7.4.1, Campaign requires at least Java JDK 11. If your Campaign server is installed in a Windows environment, the Java Runtime (JRE) is no longer detected automatically. The JRE_HOME environment variable must be set to the folder where Campaign can locate the
bin/server/jvm.dllfile. For example, if your JDK 11 is installed under theC:\Program Files\Java\jdk-11folder, your JRE_HOME must beC:\Program Files\Java\jdk-11. -
Starting v7.4.1, Tomcat 10.1 is the default version.
Recommendations
When installing and upgrading your Java Development Kit, apply the following recommendations:
-
Java Development Kit can be installed using the appropriate JDK version already used by other applications on the machine.
-
When installing the JDK, the integration with the Web browsers is not required.
-
On a machine which only executes delivery agents (nlserver mta process) or the workflow server (nlserver wfserver process), installing a JDK is not required.
-
When upgrading your Java version, you first need to uninstall the previous version. Both versions of Java installed in the same machine can cause conflicts.
As an On-premise customer, you can check the
LD_LIBRARY_PATHenvironment variable is set to the latest version (for ex. java11). If it is set to a previous version (for ex. Java8), then it needs to be updated. For JDK 11, the path to locate JDK libraries is/usr/lib/jvm/java-11-openjdk-amd64/lib.
Installation steps
Java Development Kit is platform-specific: separate installers are needed for each operating system.
To download JDK, connect to .
To install the JDSL in a Linux environment, ÃÛ¶¹ÊÓƵ recommends to use a package manager.
For Debian, use the following command:
apt install openjdk-11-jdk-headless
For RHEL, use the following command:
dnf install java-11-openjdk-headless
Export reports exporting-reports
You can use ÃÛ¶¹ÊÓƵ Campaign to export reports into Microsoft Excel and ÃÛ¶¹ÊÓƵ PDF.
-
For the Microsoft Excel format, ÃÛ¶¹ÊÓƵ Campaign relies on LibreOffice.
-
For the ÃÛ¶¹ÊÓƵ PDF format, ÃÛ¶¹ÊÓƵ Campaign uses the PhantomJS converter. PhantomJs is included in the factory package and LibreOffice must be installed on the machine(s) which the ÃÛ¶¹ÊÓƵ Campaign application server is executed on (nlserver web process).
SpamAssassin spamassassin
SpamAssassin lets you assign a score to emails in order to determine whether a message risks to be considered as undesirable by anti-spam tools used on reception. Installation is optional.
The qualification of emails as undesirable by SpamAssassin is based entirely on filtering and scoring rules. These rules therefore have to be updated at least once a day in order for your SpamAssassin installation and its integration into ÃÛ¶¹ÊÓƵ Campaign to be fully functional and to guarantee the relevance of scores assigned to your deliveries before sending. This update is the responsibility of the server administrator hosting SpamAssassin.
The minimum supported version is: 3.4
SpamAssassin requires a HTTP internet access (tcp/80).
Installation and configuration stages for SpamAssassin are presented in Configuring SpamAssassin.