adobe campaign v6.1 - installation guide · n the adobe campaign installation steps in the...

Installation GuideTechnical Documentation

Adobe Campaign v6.1

2017, Adobe System Incorporated

All rights reserved.

Published by Adobe Systems Inc.

Terms of use | Privacy Center

A trademark symbol (, , etc.) denotes an Adobe trademark.

All third-party trademarks are the property of their respective owners. Updated Information/Additional Third Party Code Information available athttp://www.adobe.com/go/thirdparty

Neolane, an Adobe Company18 rue Roger Simon Barboux, 94110 Arcueil - France+33 1 41 98 35 35www.adobe.com

http://www.adobe.com/misc/terms.htmlhttp://www.adobe.com/privacy.htmlhttp://www.adobe.com/go/thirdparty

Adobe Campaign v6.1 - Installation Guide

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7General architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Presentation layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Logical application layer . . . . . . . . . . . . . . . . . . . . . . . . . . 8Persistence layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hosting models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 13

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14PostgresSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Java Development Kit - JDK . . . . . . . . . . . . . . . . . . . . . . . . 15OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Exporting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SpamAssassin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Messaging server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Communication between processes . . . . . . . . . . . . . . . . . . . . . 17Database access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18External access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Integration with Adobe Experience Manager . . . . . . . . . . . . . . . . . . 18Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3. Deployment types . . . . . . . . . . . . . . . . . . . . . . . . 21

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Standalone deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . 23

Standard deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Adobe Campaign v6.1 - Installation Guide | 3

Table of Contents

Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . 28Enterprise deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . 33

Mid-sourcing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 37Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . 38

Power Booster and Power Cluster . . . . . . . . . . . . . . . . . . . . . . . 38Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Eligible applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Matrix of architectural recommendations . . . . . . . . . . . . . . . . . . . . 39Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4. Installation for Windows . . . . . . . . . . . . . . . . . . . . . . 41

Before the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Executing the installation program . . . . . . . . . . . . . . . . . . . . . . 42Summary installation testing . . . . . . . . . . . . . . . . . . . . . . . . 45First start-up of the server . . . . . . . . . . . . . . . . . . . . . . . . . 45Password for the internal identifier . . . . . . . . . . . . . . . . . . . . . . 46Starting Adobe Campaign services . . . . . . . . . . . . . . . . . . . . . . 46Installing LibreOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Integration into a Web server . . . . . . . . . . . . . . . . . . . . . . . . . 47Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Configuring the IIS Web server . . . . . . . . . . . . . . . . . . . . . . . 47

Client console availability . . . . . . . . . . . . . . . . . . . . . . . . . . 52Installing the client console . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 5. Installation for Linux . . . . . . . . . . . . . . . . . . . . . . . 55

Before the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Software prerequisites for Linux . . . . . . . . . . . . . . . . . . . . . . . 55Implementation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Distribution based on RPM (RHEL, CentOS and SUSE) packages . . . . . . . . . . . . 58Distribution based on APT (Debian) . . . . . . . . . . . . . . . . . . . . . . 59Parameter personalization . . . . . . . . . . . . . . . . . . . . . . . . . 60Installation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62First start-up of the server . . . . . . . . . . . . . . . . . . . . . . . . . 62Password for the internal identifier . . . . . . . . . . . . . . . . . . . . . . 63

Integration into a Web server . . . . . . . . . . . . . . . . . . . . . . . . . 63Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Configuring the Apache Web server with Debian . . . . . . . . . . . . . . . . . 64Configuring Apache web server in RHEL . . . . . . . . . . . . . . . . . . . . 65Launching the Web server and testing the configuration . . . . . . . . . . . . . . 66

Client console availability . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 6. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Creating an instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Creating an instance and logging on . . . . . . . . . . . . . . . . . . . . . 68Creating and configuring the database . . . . . . . . . . . . . . . . . . . . . 70

Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Internal identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Enabling processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

4

Delivery settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Deploying an instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Deployment wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 81General parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Email channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Managing bounced emails . . . . . . . . . . . . . . . . . . . . . . . . . 85Tracking configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 86Mobile channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Regional settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Access from the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . 92Managing public resources . . . . . . . . . . . . . . . . . . . . . . . . . 94Purge data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Installing packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Campaign Standard Packages . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 7. Additional configurations . . . . . . . . . . . . . . . . . . . . . 101

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Server side configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Defining security zones . . . . . . . . . . . . . . . . . . . . . . . . . . 102Default Tomcat port . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Mapping a folder in Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 108Personalizing delivery parameters . . . . . . . . . . . . . . . . . . . . . . 108Dynamic page security and relays . . . . . . . . . . . . . . . . . . . . . . 110Restricting authorized external commands . . . . . . . . . . . . . . . . . . . 111Managing HTTP headers . . . . . . . . . . . . . . . . . . . . . . . . . 111Redundant tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Managing public resources . . . . . . . . . . . . . . . . . . . . . . . . 112High availability workflows . . . . . . . . . . . . . . . . . . . . . . . . 112Automatic process restart . . . . . . . . . . . . . . . . . . . . . . . . . 114Limiting uploadable files . . . . . . . . . . . . . . . . . . . . . . . . . 114

Instance configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Configuration when using Microsites / pURLs . . . . . . . . . . . . . . . . . . 114LDAP/Adobe Campaign configuration . . . . . . . . . . . . . . . . . . . . 116

Email deliverability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Operating principle . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Controlling the delivery output . . . . . . . . . . . . . . . . . . . . . . . 123Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Email sending optimization: recommendations . . . . . . . . . . . . . . . . . 128

Time zone management . . . . . . . . . . . . . . . . . . . . . . . . . . 131Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuring SpamAssassin . . . . . . . . . . . . . . . . . . . . . . . . . 133Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Installing on a Windows machine . . . . . . . . . . . . . . . . . . . . . . 133Installing on a Linux machine . . . . . . . . . . . . . . . . . . . . . . . 135

Mid-sourcing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Steps for installing and configuring an instance . . . . . . . . . . . . . . . . . 136Deploying a mid-sourcing server . . . . . . . . . . . . . . . . . . . . . . 137Multiplexing the mid-sourcing server . . . . . . . . . . . . . . . . . . . . . 138Configuring tracking on a mid-sourcing server . . . . . . . . . . . . . . . . . 140

Interaction - Data buffer . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 8. Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Command lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Creating an instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Declaring a database . . . . . . . . . . . . . . . . . . . . . . . . . . 145


Creating new instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

6

Table of ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7General architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Presentation layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Logical application layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Persistence layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hosting models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Introduction

This document details:

n the recommendations (databases, operating systems, Web servers, etc.) related to deploying Adobe Campaignin the Recommendationschapter.

n the types of infrastructure to be implemented for the given examples in the Deployment typeschapter.

n the Adobe Campaign installation steps in the Installation for Windowsand Installation for Linux chapters.

n the steps necessary to create and configure an English, French or Japanese instance and its database in theConfiguration chapter.

n the additional configurations of the server instance based on your configuration in the Additional configurationschapter.

Note:

As a software vendor, we specify compatible hardware and software infrastructures. The hardware recommendationsgiven here are for informational purposes only and are based on our experience. Adobe shall not be liable for anydecisions made based on them. It will also depend on your business rules and practices and the criticality and requiredperformance levels of the project.

General architecture

Adobe Campaign is based on a service-oriented architecture (SOA) and comprises several functional modules.

These modules can be deployed on one or more computers, in single or multiple instances, depending on constraintsin terms of scalability, availability and service isolation.


CHAPTER1

Overview

installation-v6.1-en.pdf#nameddest=mancini-72installation-v6.1-en.pdf#nameddest=CST-78809installation-v6.1-en.pdf#nameddest=CST-19573installation-v6.1-en.pdf#nameddest=CST-19536installation-v6.1-en.pdf#nameddest=CST-19331installation-v6.1-en.pdf#nameddest=CST-78801

The scope of deployment configurations is therefore very broad, and spans a single, central computer through toconfigurations including multiple dedicated servers over multiple sites.

Warning:

If not explicitly stated otherwise, installation, updates and maintenance on all components of an Adobe Campaignplatform are the responsibility of the machine administrator(s) hosting them. This includes implementing theprerequisites for Adobe Campaign applications as well as complying with the compatibility matrix betweencomponents (refer to Compatibility [page 13]).

The usual layers of a multi-tier application are also present:

Presentation layerThe application can be accessed in different ways, depending on the users' needs: Rich client, Thin client or APIintegration.

n Rich client: The main user interface of the application is a rich client, in other words, a native application (Windows)that communicates with the Adobe Campaign application server solely with standard internet protocols (SOAP,HTTP, etc.). This console provides great user-friendliness for productivity, uses very little bandwidth (throughthe use of a local cache) and is designed for easy deployment. This console can be deployed from an internetbrowser, can be updated automatically and does not require any specific network configuration because it onlygenerates HTTP(S) traffic.

n Thin client: Certain parts of the application can be accessed via a simple Web browser using an HTML userinterface, including the reporting module, delivery approval stages, functionalities of the Distributed Marketingmodule (central/local), instance monitoring, etc. This mode makes it possible to include Adobe Campaignfunctionalities in an intranet or an extranet.

n Integration via the APIs: In certain cases, the system can be called from external application using the WebServices APIs exposed via the SOAP protocol.

Logical application layerAdobe Campaign is a single platform with different applications that combine to create an open and scalablearchitecture. The Adobe Campaign platform is written on a flexible application layer and is easily configurable tomeet a companys business needs. This accommodates the growing needs of the enterprise from a functionalperspective as well as from a technical perspective. The distributed architecture ensures linear system scalabilityscaling from thousands of messages to millions of messages.

Adobe Campaign relies on a set of server-side processes that work together.

8

The main processes are:

Application server (nlserver web)

This process exposes the full range of Adobe Campaign functionality via Web Services APIs (SOAP - HTTP+ XML). Furthermore, it can dynamically generate the Web pages used for HTML-based access (reports,Web forms, etc). To achieve this, this process includes an Apache Tomcat JSP server. This is the processto which the console connects.

Workflow engine (nlserver wfserver)

It executes the workflow processes defined in the application.

It also handles periodically executed technical workflows, including:

n Tracking: Recovering and consolidating tracking logs. It enables you retrieve the logs from theredirection server and create the aggregate indicators used by the reporting module.

n Cleanup: Database cleaning. Used to purge old records and avoid the database growing exponentially.

n Billing: Automatic sending of an activity report for the platform (database size, number of marketingactions, etc.).

Delivery Server (nlserver mta)

Adobe Campaign has native email broadcast functionality. This process functions as an SMTP mail transferagent (MTA). It performs "one-to-one" personalization of messages and handles their physical delivery.It functions using delivery jobs and handles automatic retries. In addition, when tracking is enabled, itautomatically replaces the URLs so that they point to the redirection server.

This process can handle the customization and automatic sending to a third-party router for SMS, faxand direct mail.

Redirection server (nlserver webmdl)

For email, Adobe Campaign automatically handles open and click tracking (transactional tracking at theWeb site level is a further possibility). To achieve this, the URLs incorporated in the email messages arerewritten in order to point to this module, which registers the passing of the internet user before redirectingthem to the required URL.

To guarantee highest availability, this process is fully independent from the database: the other serverprocesses communicate with it using SOAP calls (HTTP, HTTP(S) and XML) only. Technically, thisfunctionality is implemented in an extension module of a HTTP server (ISAPI extension in IIS, or a DSOApache module, etc.) and is available in Windows only.

Other more technical processes are also available:

Managing bounce emails (nlserver inMail)

This process enables you to automatically pick up email from mailboxes configured to receive bouncedmessages that are returned in case of delivery failure. These messages then undergo rule-based processingto determine the reasons for non-delivery (unknown recipient, quota exceeded, etc.) and to update thedelivery status in the database.

All these operations are fully automatic and preconfigured.

SMS delivery status (nlserver sms)

This process polls the SMS router to collect progress status and update the database.

Writing log messages (nlserver syslogd)

This technical process captures log messages and traces generated by the other processes and writesthem to the hard disk. This makes ample information available for diagnosis in case of problems.

Writing tracking logs (nlserver trackinglogd)

This process saves to disk the tracking logs generated by the redirecting process.

Writing inbound events (nlserver interactiond)

This process ensures the recording to the disk of inbound events, within the framework of Interaction.

Supervising modules (nlserver watchdog)

This technical process acts as a master process which spawns the others. It also monitors them andrelaunches them automatically in case of incidents, thus maintaining maximum system uptime.


Overview

Statistics server (nlserver stat)

This process maintains statistics on the number of connections, the messages sent for each mail serverwhich messages are sent to, as well as their limitations (highest number of simultaneous connections,messages per hour/ and or connection). It also lets you federate several instances or machines if theyshare the same public IP addresses.

Note:

The complete list of Adobe Campaign modules is available in the Production guide.

Persistence layerThe database is used as a persistence layer and contains almost all the information managed by Adobe Campaign.This includes both functional data (profiles, subscriptions, content, etc.), technical data (delivery jobs and logs, trackinglogs, etc.) and work data (purchases, leads).

The reliability of the database is of utmost importance because the majority of Adobe Campaign components requireaccess to the database in order to perform their tasks (with the notable exception of the redirection module).

The platform comes predefined with a marketing centered data mart or can easily sit atop an existing data mart andschema using any of the major Relational Database Management Systems (RDBMS). All data within the data martis accessed by the Adobe Campaign platform via SQL calls from Adobe Campaign to the database. Adobe Campaignalso provides a full complement of Extract Transform and Load (ETL) tools to perform data import and export ofdata into and out of the system.

Hosting models

Adobe Campaign offers a choice of three hosting models, providing flexibility and freedom to choose the best model,or models to suit business needs:

n On-premise: Adobe Campaign can be deployed on premise, with all components of the solution installed andconfigured in your data centers.

10

production-v6.1-en.pdf#nameddest=ACY-20042

n Hosted: Fully hosted solution, with all data and communications hosted in Adobes data centers.

n Hybrid: Adobe provides cloud-based messaging services, whilst you host the data-specific components solution including integration components on your premises.


Overview

Table of ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14PostgresSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Java Development Kit - JDK . . . . . . . . . . . . . . . . . . . . . . . . . 15OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Exporting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SpamAssassin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Messaging server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Communication between processes . . . . . . . . . . . . . . . . . . . . . . . 17Database access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18External access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Integration with Adobe Experience Manager . . . . . . . . . . . . . . . . . . . . 18Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Introduction

This chapter lists all the recommendations related to installing and configuring Adobe Campaign.

Compatibility

The compatibility matrix is available in the Technical Resources section at the following address:http://support.neolane.net/doc/AC6.1/en/technicalResources/technicalResources.html

This matrix includes all versions of the systems and components supported for Adobe Campaign v6.1.

Note:

Regular evolutions mean this matrix will be updated regularly. We therefore recommend you systematically checkcompatibility before implementing or migrating your systems and components.


CHAPTER2

Recommendations

http://support.neolane.net/doc/AC6.1/en/technicalResources/technicalResources.html

Database

The database server can run on any given operating system regardless of the operating system used by the applicationserver or servers, as long as there is network connectivity between them.

Warning:

The operating system of the database server is not important so long as connectivity with the different componentsof Adobe Campaign is available.

Microsoft SQL ServerThe native client must be installed on the Adobe Campaign application servers.

You can check for the native client on the server via the ODBC driver configuration panel, under SQL Native Client(for SQL Server 2005 clients), or SQL Server Native Client 10.0 (for SQL Server 2008 and 2008 R2 clients), or SQLServer Native Client 11.0 (for SQL Server 2012 clients).

The following access DLLs must be present:

n sqlncli.dll for the SQL Server 2005 client,

n sqlncli10.dll for the SQL Server 2008 and 2008 R2 clients.

n sqlncli11.dll for the SQL Server 2012 client.

Access DLLs are found on the Microsoft website.

Note:

Access to Microsoft SQL Server from an application server running in Linux is not supported.

OracleThe NLS_NCHAR_CHARACTERSET and NLS_CHARACTERSET parameters need to be correctly properly configuredin order for the database to work in Unicode or ANSI.

Adobe Campaign uses default Oracle encoding. Using other encoding may trigger compatibility issues: in this case,please contact technical support.

To find out about your encoding, use the following sqlplus command:

SELECT * FROM nls_database_parameters;

n For a Unicode installation, the encodings supported are:

NLS_NCHAR_CHARACTERSET AL16UTF16NLS_CHARACTERSET AL32UTF8

n For an ANSI installation (non-unicode), only the following encoding is supported:

NLS_CHARACTERSET WE8MSWIN1252

To log on to sqlplus, use the Oracle user profile:

su - oracle sqlplus [login] [password]

Note:

You can also refer to Oracle Client in Linux [page 62].

14

PostgresSQLWe recommend that you install the UTF-8 support when installing the database engine. This way you will be ableto create Unicode databases.

Application server

Warning:

The required database access layers must be installed on the server and accessible from the Adobe Campaignaccount.

Java Development Kit - JDKThe dynamic Web page generator uses JSP 1.2 technology. For this, a Tomcat engine (from Apache) is included inthe application. It requires a Java Development Kit (JDK), installed on all servers which the Adobe Campaignapplication is installed on.

You must first install a JDK on the computers on which you wish to run the Adobe Campaign application server(nlserver web process) because it incorporates a servlet container, Apache Tomcat, used to generate dynamic Webpages (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 the Compatibility matrix.

Note:

n It can be installed using the appropriate JDK version already used by other applications on the machine.

n When installing, you are not required to perform the integration with the Web browsers.

n On a machine which only executes delivery agents (nlserver mta process) or the workflow server (nlserverwfserver process), installing a JDK isn't necessary.

To download Java JDK, connect to:http://www.oracle.com/technetwork/java/javase/downloads/index.html and download the latestrevision of version 6. Warning: you must download a JDK, not a JRE.

Warning:

To preserve platform operation performance and ensure compatibility with the installed version, you must disableautomatic JDK update functions in Windows and Linux.

To install the JDSL in a Linux environment, it is preferable to use a package manager.

In Debian 7 and 8, use the following command:

aptitude install openjdk-7-jdk

For RHEL 6, use the following command:

yum install java-1.8.0-openjdk

For RHEL 7, use the following command:

yum install java-1.8.0-openjdk

OpenSSLIn Linux, OpenSSL must be installed. The versions supported by Adobe Campaign are OpenSSL 1.0.1 and OpenSSL0.9.8. Sub-versions 0.9.8g to 0.9.8o are accepted.


Recommendations

https://helpx.adobe.com/campaign/kb/compatibility-matrix.htmlhttp://java.sun.com/http://java.sun.com/

Note:

For RHEL 6 and CentOS 6, openSSL 1.0 is required.

Exporting reportsAdobe Campaign lets you export platform reports in Microsoft Excel and Adobe PDF format. For the Microsoft Excelformat, Adobe Campaign uses LibreOffice. For the Adobe PDF format, Adobe Campaign uses the PhantomJSconverter. PhantomJs is included in the factory package and LibreOffice must be installed on the machine(s) whichthe Adobe Campaign application server is executed on (nlserver web process).

Note:

For Linux, you will need to add fonts. For more on this, refer to Fonts [page 56].

SpamAssassinSpamAssassin lets you assign a score to emails in order to determine whether a message risks to be considered asundesirable by anti-spam tools used on reception. Installation is optional.

Warning:

The qualification of emails as undesirable by SpamAssassin is based entirely on filtering and scoring rules. Theserules therefore have to be updated at least once a day in order for your SpamAssassin installation and its integrationinto Adobe Campaign to be fully functional and to guarantee the relevance of scores assigned to your deliveriesbefore sending. This update is the responsibility of the server administrator hosting SpamAssassin.

The minimum supported versions are: 3.2.5 and 3.3.2.

SpamAssassin requires a HTTP internet access (tcp/80).

Note:

Installation and configuration stages for SpamAssassin are presented in Configuring SpamAssassin [page 133].

Messaging server

Adobe Campaign handles outbound email natively, however a traditional email server is required to receive incomingmessages linked to returned email (from mailer daemons). The mailboxes configured on this server will beautomatically processed by the application.

All servers configured for POP3 access can be used to receive return mail if they preserve the SMTP "Message-ID"headers when picking up the mail. For example, implementations using Qmail, SendMail and Microsoft Exchangeare currently in production. However, some installations of Lotus Notes/domino revealed an issue with the maintainingof "Message-Id" headers.

Warning:

This mail server may have to handle heavy loads: In initial phases, typical lists can produce up to 10% bounce rates(if you send 100,000 messages, expect to receive 10,000 bounces).

That's why we recommend against using your company messaging server for this task as it can be strongly impacted.

It is advisable to configure a specific sub-domain of your DNS and a dedicated server for bounce mail.

16

Network configuration

Communication between processesCertain processes of the application need to communicate with others or to access the LAN and internet. This meansthat some TCP ports need to be open for these processes.

Note:

Use the embedded Apache Tomcat port as a priority (8080 by default) for internal communications between thevarious application servers of an Adobe Campaign platform.

Delivery server

For the delivery server (nlserver mta), the following ports must be open:

CommentsDestinationPorts

SMTP traffic for e-mail broadcasting.Anywhere25/tcp (smtp)

DNS queries.DNS servers53/udp (domain)

Used to send SMS traffic to the NetSize SMS router [option].SMS gateway38000/tcp (default port)

Accessing the statistics server.Statistics server7777/udp

Inbound mail

For the inbound mail recovery process (nlserver inMail), the following ports must be open:


POP3 traffic to pick up bounce messages.Internal mail server110/tcp (pop3)

SMTP traffic to send remaining bounce messages that are not automatic-ally processed by the pre-defined rules.

Internal mail server25/tcp (smtp)

Application server

For the application server (nlserver web), the following ports must be open:


HTTP or HTTPS traffic (including for the deliverability offer).Anywhere80/tcp (http)

443/tcp (https)

Warning:

When several application servers of an Adobe Campaign platform need to communicate with each other, werecommend using the port of the Apache Tomcat server (by default: 8080) rather than that of the HTTP port of theWeb server which redirection module integration was carried out with. This means the port needs to be open betweenthese servers.

SMS delivery status

To track SMS deliveries (nlserver sms), the following port must be open:


Queries the delivery queue status managed by the NetSize SMS gateway[option].

SMS gateway38000/tcp (default port)

Rich client

For the Adobe Campaign rich client (nlclient), the following ports must be open:


Recommendations


SOAP traffic (HTTP).Application server80/tcp (http)

443/tcp (https)

Database accessAll components that use the database must be able to connect to it. This is the case for most components, with theexception of the redirection server, which can work alone, and the thin Win32 client, which uses HTTP (or HTTPS)only to communicate with the application server.

The default ports are the following:

DestinationPort (default)Database type

Database server.1521/tcpOracle

5432/tcpPostgreSQL

1433/tcpMicrosoft SQL Server

50000/tcpDB2

External accessIn addition, certain components must be accessible from the public internet so that e-mail campaigns executeddirectly from Adobe Campaign can be viewed. This means that some ports need to be open for components.

Redirection server

LocationListening port

Anywhere. Each click on a tracked link generates a HTTP request on the server.80/tcp (http)

443/tcp (https)

External Web server

This server hosts Web forms, mirror pages, etc. The following ports need to be open:


Anywhere. Necessary when Web forms are managed directly from the Adobe Campaign platformor when mirror pages are used.

80/tcp (http)

443/tcp (https)

Internal application server (Web)


All computers executing the thin client or rich client.80/tcp (http)

443/tcp (https)

Integration with Adobe Experience ManagerIntegration between Adobe Campaign and Adobe Experience Manager requires opening several ports if the installationis "on-premise". For more information on configuring this integration, refer to the detailed documentation.

DescriptionListening port

AEM connection to Adobe Campaign80

18

integrations#mancini-77

Adobe Campaign connection to AEM's "authoring" and "publishing" instances. The ports to openmay be different from the default ports, depending on your AEM configuration.

4502

4503

BandwidthAnother key parameter of the network configuration to take into account. It is almost always outbound and muchin demand during e-mail broadcasts. Here are a few examples of configurations based on our experience:

n 1 Mb/s for 10,000 emails per hour (average size of 30 Kb)

n 8 to 10 Mb/s for 100,000 emails per hour (average size of 30 Kb)

Tip:

If you have constraints in terms of bandwidth, it is possible to schedule campaigns to run during the night whendemand is lower.


Recommendations

Table of ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Standalone deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . . 23

Standard deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . . 28

Enterprise deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . . 33

Mid-sourcing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installation and configuration steps . . . . . . . . . . . . . . . . . . . . . . . 38

Power Booster and Power Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 38Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Eligible applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Matrix of architectural recommendations . . . . . . . . . . . . . . . . . . . . . 39Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Introduction

The modular design of Adobe Campaign enables a wide range of deployment configurations, from standalone setups(all components on one machine) to enterprise deployments with fully redundant and distributed architecture usingmultiple servers. All depends on the required level of performance and security.

Note:

In case of a configuration on multiple computers, you don't have to use the same operating system throughout: forinstance, you could use a redirection server on Linux + Apache with delivery servers on Windows.

Standalone deployment

This configuration includes all components on the same computer:


CHAPTER3

Deployment types

n application process (web),

n delivery process (mta),

n redirection process (tracking),

n workflow process and scheduled tasks (wfserver),

n bounce mail process (inMail),

n statistics process (stat).

Overall communication between the processes is carried out according to the following schema:

This type of configuration can be run when managing lists of fewer than 100,000 recipients and with, for example,the following software layers:

n Linux,

n Apache,

n PostgreSQL,

n Qmail.

As the volume grows, a variant of this architecture moves the database server to another computer for betterperformance.

Note:

An existing database server may also be used if it has sufficient resources.

Features

Advantages

n Fully standalone and low configuration cost (no billable licenses required if the open-source software listedbelow is used).

n Simplified installation and network configuration.

22

Disadvantages

n A critical computer in case of incident.

n Limited bandwidth when broadcasting messages (in our experience, around several tens of thousands of mailsper hour).

n Potential slowing of the application when broadcasting.

n The application server must be available from the outside (whilst being located in the DMZ, for example) sinceit hosts the redirection server.

Installation and configuration steps

Prerequisites

n JDK,

n Web server (IIS, Apache),

n Access to a database server,

n Bounce mailbox accessible via POP3,

n Creation of two DNS aliases:

n the first exposed to the public for tracking and pointing to the computer on its public IP;

n the second alias exposed to internal users for console access and pointing to the same computer.

n Firewall configured to open STMP (25), DNS (53), HTTP (80), HTTPS (443), SQL (1521 for Oracle, 5432 forPostgreSQL, etc.) ports. For further information, refer to Database access [page 18].

In the following examples, the parameters of the instance are:

n Name of the instance: demo

n DNS mask: console.campaign.net* (only for client console connections and for reports)

n Database: campaign:demo@dbsrv

Installing and configuring (single machine)

Apply the following steps:

1 Follow the installation procedure for the Adobe Campaign server: nlserver and thirdparty packages onLinux or setup.exe on Windows.

For more on this, refer to Before the installation [page 55] (Linux) and Before the installation [page 41] (Windows).

2 Once the Adobe Campaign server is installed, start the application server (web) using the command nlserverweb -tomcat (the Web module enables you to start Tomcat in standalone Web server mode listening on port8080) and to make sure Tomcat starts correctly:

12:08:18 > Application server for Adobe Campaign Version 6.X (build XXXX) of DD/MM/YYYY12:08:18 > Starting Web server module (pid=28505, tid=-1225184768)...12:08:18 > Tomcat started12:08:18 > Server started

Note:

The first time the Web module is executed it creates the config-default.xml and serverConf.xml files inthe conf directory under the installation folder.

Press Ctrl+C to stop the server.

For more on this, refer to the following sections:

n For Linux: First start-up of the server [page 62],

n For Windows: First start-up of the server [page 45].

3 Change the internal password using the command:

nlserver config -internalpassword

For more on this, refer to Internal identifier [page 79].

4 Create the demo instance with the DNS masks for tracking (in this case, tracking.campaign.net) and accessto client consoles (in this case, console.campaign.net). There are two ways of doing this:


Deployment types

n Create the instance via the console:

For more on this, refer to Creating an instance and logging on [page 68].

or

n Create the instance using command lines:

nlserver config -addinstance:demo/tracking.campaign.net*,console.campaign.net*

For more on this, refer to Creating an instance [page 145].

5 Edit the config-demo.xml file (created in the previous step next to config-default.xml) and make surethe mta (delivery), wfserver (workflow), inMail (bounce mails) and stat (statistics) processes are enabled. Thenconfigure the address of the statistics server:

For more on this, refer to Enabling processes [page 80].

6 Edit the serverConf.xml file and specify the delivery domain, then specify the IP (or host) addresses of theDNS servers used by the MTA module to answer MX type DNS queries.

Note:

The nameServers parameter is only used in Windows.

For more on this, refer to Server configuration [page 79].

7 Copy the client console setup program (setup-client-6.XX, YYYY .exe) to the /datakit/nl/eng/jspfolder.


n For Linux: Client console availability [page 52],

n For Windows: Client console availability [page 52].

8 Follow the Web server integration procedure (IIS, Apache) described in the following sections:

n For Linux: Integration into a Web server [page 63],

n For Windows: Integration into a Web server [page 47].

9 Start the website and test redirection using the URL: http://tracking.campaign.net/r/test.The browser must display the following message:

24

http://tracking.campaign.net/r/test


n For Linux: Launching the Web server and testing the configuration [page 66],

n For Windows: Launching the Web server and testing the configuration [page 50].

10 Start the Adobe Campaign server (net start nlserver6 in Windows, /etc/init.d/nlserver6start in Linux) and run the command nlserver pdump once more to check for presence of all enabledmodules.

12:09:54 > Application server for Adobe Campaign Version 6.X (build XXXX) of DD/MM/YYYYsyslogd@default (7611) - 9.2 MBstat@demo (5988) - 1.5 MBinMail@demo (7830) - 11.9 MBwatchdog (27369) - 3.1 MBmta@demo (7831) - 15.6 MBwfserver@demo (7832) - 11.5 MBweb@default (28671) - 40.5 MB

Note:

This command also lets you know the version and build number of the Adobe Campaign server installed on thecomputer.

11 Test the nlserver web module using the URL: http://console.campaign.net/nl/jsp/logon.jspThis URL enables you to access the download page for the client setup program.

Enter the internal login and associated password when you reach the access control page.




12 Start the Adobe Campaign client console (from the previous download page or launched directly on the serverfor a Windows installation), set the server connection URL to http://console.campaign.net and connect usingthe internal login.


Deployment types

http://tracking.campaign.net/r/testhttp://console.campaign.net

Note:

Refer to Creating a new connection [page 68] and Internal identifier [page 79].

The database creation wizard appears when you log in for the first time:

Follow the steps in the wizard and create the database associated with the connection instance.

For more on this, refer to Creating and configuring the database [page 70].

Once the database is created, log off.

13 Log back on to the client console using the admin login without a password and start the deployment wizard(Tools > Advanced menu) to finish configuring the instance.

For more on this, refer to Deploying an instance [page 81].

The main parameters to set are the following:

n Email delivery: sender and reply addresses and the error mailbox for bounce mail.

n Tracking: Populate the external URL used for redirection and the internal URL, click Registration on thetracking server(s) and then validate it on the demo instance of the tracking server.

26

For more on this, refer to Tracking configuration [page 86].

Note:

As the Adobe Campaign server is used both as the application server and the redirection server, the internalURL used to collect tracking logs and transfer URLs is a direct internal connection to Tomcat(http://localhost:8080).

n Bounce management: Enter the parameters to handle bounce mail (do not take the Unprocessed bouncemails section into account).

n Access from: Provide the two URLs for reports, Web forms and mirror pages.

Standard deployment

For this configuration, three computers are required:

n An application server inside the LAN for the end users (preparing campaigns, reporting, etc.),

n Two frontal servers in the DMZ behind a load balancer.

The two servers in the DMZ handle tracking, mirror pages and delivery and are redundant for high availability.


Deployment types

The application server in the LAN serves the end users and performs all recurrent processes (workflow engine). Thus,when peak loads are reached on the frontal servers, the application users are not impacted.

The database server can be hosted on a separate computer from these three. It is otherwise for the application serverand database server to share the same computer within the LAN as long as the operating system is supported byAdobe Campaign (Linux or Windows).

General communication between servers and processes is carried out according to the following schema:

This type of configuration can handle a large number of recipients (500,000 to 1,000,000) as the database server(and the available bandwidth) is the main limiting factor.

Features

Advantages

n Failover functionality: the ability to switch processes to one computer in case of a hardware problem on theother.

n Better overall performance, since the MTA and redirection functions can be deployed on both of the computersbehind a load balancer. With two active MTAs and enough bandwidth, it is possible to achieve broadcast ratesin the region of 100,000 mails per hour.


Prerequisites

n JDK on all three computers,

n Web server (IIS, Apache) on both frontals,

28

n Access to a database server on all three computers,


n Creation of two DNS aliases:

n the first exposed to the public for tracking and pointing to the load balancer on a virtual IP address (VIP)and which is then distributed to the two frontal servers,

n the second exposed to the internal users for access via the console and pointing to the same applicationserver.

n Firewall configured to open STMP (25), DNS (53), HTTP (80), HTTPS (443), SQL (1521 for Oracle, 5432 forPostgreSQL, etc.) ports. For further information, refer to section Database access [page 18]

Installing and configuring (standard deployment)

Installing the application server

Follow the steps to install a standalone instance from the Adobe Campaign application server to the creation of thedatabase (step 12). Refer to Installing and configuring (single machine) [page 23].

Since the computer is not a tracking server, do not take the integration with the Web server into account.



n DNS mask: console.campaign.net* (only for client console connections and for reports)

n Language: English


Installing the two frontal servers

Note:

The installation and configuration procedure is identical on both computers.

The steps are as follows:

1 Install the Adobe Campaign server.For more on this, refer to Before the installation [page 55] (Linux) and Before the installation [page 41] (Windows).

2 Follow the Web server integration procedure (IIS, Apache) described in the following sections:



3 Create the demo instance. There are two ways of doing this:



or


nlserver config -addinstance:demo/tracking.campaign.net*



Deployment types

Note:

The name of the instance is the same as that of the application server.

The connection to the server with the nlserver web module (mirror pages, unsubscription) will be made fromthe URL of the load balancer (tracking.campaign.net).

4 Change the internal to the same as the application server.For more on this, refer to Internal identifier [page 79].

5 Link the database to the instance:

nlserver config -setdblogin:PostgreSQL:campaign:demo@dbsrv -instance:demo

6 In the config-default.xml and config-demo.xml files, enable the web, trackinglogd and mta modules.For more on this, refer to Enabling processes [page 80].

7 Edit the serverConf.xml file and populate:

n the DNS configuration of the MTA module:

Note:


For more on this, refer to Delivery settings [page 81].

n the redundant tracking servers in the redirection parameters:

For more on this, refer to Redundant tracking [page 111].

8 Start the website and test the redirection from the URL: http://tracking.campaign.net/r/testThe browser should display the following messages (depending on the URL redirected by the load balancer):

or




9 Start the Adobe Campaign server.

10 In the Adobe Campaign console, connect using the admin login without a password and launch the deploymentwizard.

For more on this, refer to Deploying an instance [page 81].

Configuration is identical to a standalone instance apart from the configuration of the tracking module.

11 Populate the external URL (that of the load balancer) used for redirection and the internal URLs of the two frontalservers.

30


For more on this, refer to Tracking configuration [page 86].

Note:

We use the existing instance of the two tracking servers created previously and use the internal login.

Enterprise deployment

This is the most complete configuration. It builds on the standard configuration for greater security and availability:

n dedicated redirection servers behind a HTTP or TCP load balancer, for scalability and availability,

n two application servers for improved throughput and failover capability (fault tolerance) and which are isolatedin the LAN.


Deployment types


With this type of configuration, the expected throughput can exceed 100,000 mails per hour with appropriatebandwidth and tuning.

Features

Advantages

n Optimized security: Only those servers that need to be exposed to the outside are installed on the computer inthe DMZ.

n High availability easier to ensure: Only the computer visible from the outside needs to be managed with highavailability in mind.

Disadvantages

Higher hardware and administration costs.

Recommended equipment

n Application servers: 2 Ghz quad-core CPU, 4 GB RAM, software RAID 1 80 GB SATA hard drive.

n Redirection servers: 2 Ghz quad-core CPU, 4 GB RAM, software RAID 1 80 GB SATA hard drive.

Note:

It is possible to reuse an existing load balancer for traffic to the redirection servers.

32


Prerequisites

n JDK on both application servers,

n Web server (IIS, Apache) on both frontals,

n Access to a database server on both application servers,


n Creation of two DNS aliases on the load balancer:

n the first exposed to the public for tracking and pointing to the load balancer on a virtual IP address (VIP)and which is then distributed to the two frontal servers;

n the second exposed to the internal users for access via the console and pointing to a load balancer on avirtual IP address (VIP) and which is then distributed to the two application servers.

n Firewall configured to open STMP (25), DNS (53), HTTP (80), HTTPS (443), SQL (1521 for Oracle, 5432 forPostgreSQL, etc.) ports. For further information, refer to section Database access [page 18]

Installing and configuring (company deployment)

Application server 1



n DNS mask: tracking.campaign.net*, console.campaign.net* (the application server handles the URLs for clientconsole connections and reports and for mirror pages and unsubscription pages)

n Language: English


The steps for installing the first server are:

1 Follow the installation procedure for the Adobe Campaign server: nlserver and thirdparty packages onLinux or setup.exe on Windows.

For more on this, refer to Before the installation [page 55] (Linux) and Before the installation [page 41] (Windows).

2 Once the Adobe Campaign server is installed, start the application server (web) using the command nlserverweb -tomcat (the Web module enables you to start Tomcat in standalone Web server mode listening on port8080) and to make sure Tomcat starts correctly:

12:08:18 > Application server for Adobe Campaign Version 6.X (build XXXX) of DD/MM/YYYY12:08:18 > Starting Web server module (pid=28505, tid=-1225184768)...12:08:18 > Tomcat started12:08:18 > Server started

Note:

The first time the Web module is executed it creates the config-default.xml and serverConf.xml files inthe conf directory under the installation folder.

Press Ctrl+C to stop the server.




3 Change the internal password using the command:

nlserver config -internalpassword

For more on this, refer to Internal identifier [page 79].

4 Create the demo instance with the DNS masks for tracking (in this case, tracking.campaign.net) and accessto client consoles (in this case, console.campaign.net). There are two ways of doing this:


Deployment types



or


nlserver config -addinstance:demo/tracking.campaign.net*,console.campaign.net*


5 Edit the config-demo.xml file (created via the previous command and located next to the config-default.xmlfile), check that the mta (delivery), wfserver (workflow), inMail (rebound mails) and stat (statistics) processesare enabled, then configure the address of the app statistics server:


6 Edit the serverConf.xml file and specify the delivery domain, then specify the IP (or host) addresses of theDNS servers used by the MTA module to answer MX type DNS queries.

Note:

The nameServers parameters is only used in Windows.


7 Copy the client console setup program (setup-client-6.0.XX, YYYY .exe) to the /datakit/nl/eng/jspfolder.




8 Start the Adobe Campaign server (net start nlserver6 in Windows, /etc/init.d/nlserver6start in Linux) and run the command nlserver pdump once more to check for presence of all enabledmodules.

12:09:54 > Application server for Adobe Campaign Version 6.X (build XXXX) of DD/MM/YYYYsyslogd@default (7611) - 9.2 MBstat@demo (5988) - 1.5 MBinMail@demo (7830) - 11.9 MB

34

watchdog (27369) - 3.1 MBmta@demo (7831) - 15.6 MBwfserver@demo (7832) - 11.5 MBweb@default (28671) - 40.5 MB

Note:

This command also lets you know the version and build number of the Adobe Campaign server installed on thecomputer.

9 Test the nlserver web module using the URL: http://console.campaign.net/nl/jsp/logon.jsp.This URL enables you to access the download page for the client setup program.

Enter the internal login and associated password when you reach the access control page.




Application server 2

Apply the following steps:

1 Install the Adobe Campaign server,

2 Copy the files of the instance you created onto application server 1

Note:

We keep the same instance name as the application server 1.

3 Change the internal to the same as application server 1.

4 Link the database to the instance:

nlserver config -setdblogin:PostgreSQL:campaign:demo@dbsrv -instance:demo


Deployment types


5 Edit the config-demo.xml file (created via the previous command and located next to the config-default.xmlfile), check that the mta (delivery), wfserver (workflow), inMail (rebound mails) and stat (statistics) processesare enabled, then configure the address of the app statistics server:


6 Edit the serverConf.xml file and populate the DNS configuration of the MTA module:

Note:



7 Start the Adobe Campaign servers.For more on this, refer to the following sections:



Frontal servers

Note:

Installation and configuration procedures are identical on both computers.

The steps are as follows:

1 Install the Adobe Campaign server,

2 Comply with the Web server integration procedure (IIS, Apache) described in the following sections:



3 Copy the config-demo.xml and serverConf.xml files created during installation. In the config-demo.xmlfile, activate the trackinglogd process and deactivate the mta, inmail, wfserver and stat processes.

4 Edit the serverConf.xml file and populate the redundant tracking servers in the parameters of the redirection:

5 Start the website and test the redirection from the URL: http://tracking.campaign.net/r/testThe browser should display the following messages (depending on the URL redirected by the load balancer):

or


36





Mid-sourcing deployment

This configuration is an optimal intermediate solution between a hosted (ASP) configuration and internalization.The outward-facing execution components are carried out on a "mid-sourcing" server hosted at Adobe Campaign.

Warning:

To set up this type of deployment, you need to acquire the appropriate option. Please check your license contract.


n The execution and bounce management modules are disabled on the instance.

n The application is configured to perform message execution on a remote "mid-sourced" server that is drivenusing SOAP calls (over HTTP or HTTPS).

Features

Advantages

n Simplified server configuration: It is not necessary for the customer to configure outward-facing modules (mtaand inMail).

n Limited use of bandwidth: Since execution is performed by the mid-sourcing server, only sufficient bandwidthis required to send personalization data to the mid-sourcing server.


Deployment types

n High availability is no longer an internal issue: The problem is shifted to the mid-sourcing server (redirection,mirror pages, execution servers, etc.).

n The database does not leave the company: Only data necessary to assemble the messages are sent to themid-sourcing server (HTTPS can be used for this).

n This type of deployment can be a solution for high volume architectures (many recipients in the database), witha significant delivery throughput.

Disadvantages

n Slight delay in viewing message-execution information and for reporting functionality due to the time it takesto get information back from the mid-sourcing server.

n Surveys and web forms remain on the client platform.

Recommended equipment

n Application server: 2 Ghz quad-core CPU, 4 GB RAM, software RAID 1 80 GB SATA hard drive.

n Database server: 3 GHz bi-quad core CPUs , minimum 4 GB RAM, hardware RAID 10 15000RPM SAS hard drive,the number depending on the size and expected performance of the database.

Note:

Redirection and mid-sourcing are separate elements, however the tracking server will, in general, be shared withthe mid-sourcing servers.


Prerequisites

n JDK on the application server.

n Access to a database server on the application server.

n Firewall configured to open HTTP (80) or HTTPS (443) ports to the mid-sourcing server.

Installing and configuring (mid-sourcing deployment)

Refer to Mid-sourcing server [page 136].

Power Booster and Power Cluster

OverviewAdobe Campaign provides you with two sets of pre-packaged architectural options for dimensioning your deployment:

n Power Booster

This option provides support for a single additional execution instance decoupled from the primary AdobeCampaign application instance. Dedicated execution instances can be hosted remotely or by a third party. Whenimplemented, email execution, tracking, mirror pages, and bounce messages are handled independently of thecentral application functions.

n Power Cluster

This option provides support for 2 to N clustered execution instances decoupled from the primary AdobeCampaign application instance in relation to a given application. Clusters can be hosted remotely, in distributeddeployments, and by third parties. In addition to the benefits of process isolation, the Adobe Campaign Power

38

Cluster option enables redundancy and scale out strategies using commodity hardware for simplified evolutionof SLA or performance.

Eligible applicationsThe Power Booster and Power Cluster options can be used by the following applications:

n Campaign

n Leads

n Delivery

n Message Center

Matrix of architectural recommendations

Power ClusterPower BoosterStandard architecture

Over 100 million emails per month30 to 100 million emails per monthUp to approximately 30 mil-lion emails per month

Email campaigns and outboundinteractions

Over 50,000 per dayUp to 50,000 per dayUp to several thousand perday

Transactional messages

24/7/365 service possible24/7 except maintenance windowsand downtimes for the execution in-stance

That of the primary databaseAvailability

Data mart is isolated from frontal, internet-facing components

Data mart is isolated from frontal, in-ternet-facing components

Data mart is potentially ac-cessible from the public inter-net

Security

Marketing on premise with execution in thecloud; execution in different geos possible

Marketing on premise with executionin the cloud possible

All on one site (can be onpremise or in the cloud)

Deployment template

Recommendations

n An execution instance must be dedicated to a service. You cannot install a package for a service which youhaven't subscribed to. For instance, if you subscribe to the Power Booster option for the Message Center service,you may only install the Execution of transactional messages package on the dedicated execution instance.Please check your license agreement.

n Since dedicated instances (or clusters) are Adobe Campaign instances, recommendations are the same as for amain instance. For more on this, refer to the Production guide.

n To properly configure the instance from a database/hardware components point of view, please contact AdobeCampaign Professional Services.


Deployment types

production-v6.1-en.pdf#nameddest=ACY-18864

Table of ContentsBefore the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Executing the installation program . . . . . . . . . . . . . . . . . . . . . . . 42Summary installation testing . . . . . . . . . . . . . . . . . . . . . . . . . 45First start-up of the server . . . . . . . . . . . . . . . . . . . . . . . . . . 45Password for the internal identifier . . . . . . . . . . . . . . . . . . . . . . . 46Starting Adobe Campaign services . . . . . . . . . . . . . . . . . . . . . . . 46Installing LibreOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Integration into a Web server . . . . . . . . . . . . . . . . . . . . . . . . . . 47Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Configuring the IIS Web server . . . . . . . . . . . . . . . . . . . . . . . . . 47

Client console availability . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Installing the client console . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Before the installation

The technical configuration and software needed to install Adobe Campaign is presented in the Compatibility matrix.

The Adobe Campaign server installation process for multi-instance usage is described below in Installing the server[page 42].

The main steps are as follows:

1 Install the application server, refer to Executing the installation program [page 42].

2 Integrate with a Web server (optional, depending on the components deployed), refer to Configuring the IISWeb server [page 47].

Once the installation steps are complete, you need to configure the instances, the database and the server. For moreon this, refer to Introduction [page 67].

Note:

When Adobe Campaign is deployed to a Windows environment, users with the necessary access rights can use UNCsyntax (Universal.Uniform Naming Convention) for access paths during file manipulation on the network.


CHAPTER4

Installation for Windows

http://support.neolane.net/doc/AC6.1/en/technicalResources/technicalResources.html

Installing the server

Executing the installation program

Warning:

For a Windows 32 bit platform, install Adobe Campaign 32 bit. For a Windows 64 bit platform, install Adobe Campaign64 bit.

The installation steps for the Adobe Campaign server are the following:

1 Execute the file setup.exe.

2 Select the installation type.

Several installation types are available:

n Installation of an application server: Install the Adobe Campaign application server and the client console.

n Minimal installation (Network): Installation of the client computer from the network. Only a limited numberof DLLs will be installed on the computer, if necessary, and all the other components will be used from anetwork drive.

n Installation of a client: Installation of the required components for the Adobe Campaign client.

n Custom installation: The user chooses the elements to be installed.

42

Select Installation of an application server, and go through the different steps as shown below:

3 Select the installation directory:



4 Click Finish to start the installation:

The progress bar shows how far the installation is:

44

Once the installation is complete, a message appears to let you know:

Once the installation is complete, start Adobe Campaign to create the configuration files. Refer to First start-upof the server [page 45].

Summary installation testingYou can test the initial installation using the following command:

nlserver pdump

Note:

If Adobe Campaign isn't started, the response is:

No task

First start-up of the serverOnce the installation test is complete, open a command prompt via Start>Programs> Adobe Campaign and enterthe following command:

nlserver web

[Adobe Campaign v6] is the access path to the Adobe Campaign installation directory. These files are used toconfigure the Adobe Campaign server modules.

The following information is displayed:

15:30:12 > Application server for Adobe Campaign Version 6.X (build XXXX) dated DD/MM/YYYY15:30:12 > Web server start (pid=664, tid=4188)...15:30:12 > Creation of server configuration file '[INSTALL]\bin\..\conf\serverConf.xml' server via '[INSTALL]\bin\..\conf\fra\serverConf.xml.sample



15:30:12 > Creation of server configuration file '[INSTALL]\bin\..\conf\config-default.xml' server via '[INSTALL]\bin\..\conf\models\config-default.xml15:30:12 > Server started15:30:12 > Stop requested (pid=664)15:30:12 > Web server stop (pid=664, tid=4188)...

Press Ctrl+C to stop the process, then enter the following command:

nlserver start web


12:17:21 > Application server for Adobe Campaign Version 6.X (build XXXX) dated DD/MM/YYYY12:17:21 > Start of the 'web@default' ('nlserver web -tracefile:web@default -instance:default -detach -tomcat -autorepair') task in a new process 12:17:21 > Application server for Adobe Campaign Version 6.0.1 (build 6633) dated 02/04/201112:17:21 > Web server start (pid=29188, tid=-1224824320)...12:17:21 > Generation of configuration changes '[INSTALL]\bin\..\conf\serverConf.xml.diff' between '[INSTALL]\bin\..\conf\serverConf.xml' and '[INSTALL]\bin\..\conf\fra\serverConf.xml.sample'12:17:22 > Tomcat started12:17:22 > Server started

To stop it, enter:

nlserver stop web


12:18:31 > Application server for Adobe Campaign Version 6.X (build XXX) of DD/MM/YYYY12:18:31 > Stop requested for 'web@default' ('nlserver web -tracefile:web@default -instance:default -detach -tomcat -autorepair', pid=29188, tid=-1224824320)...12:18:31 > Stop requested (pid=29188)12:18:31 > Web server stopped (pid=29188, tid=-1224824320)...

Password for the internal identifierThe Adobe Campaign server defines a technical login called internal that has all rights on all instances. Just afterinstallation the login does not have a password. It is mandatory to define one.

See section Internal identifier [page 79].

Starting Adobe Campaign servicesTo start the Adobe Campaign services, you can use the service manager or enter the following at the command line(with the appropriate rights):

net start nlserver6

If you need to stop the Adobe Campaign processes later on, use the command:

net stop nlserver6

Installing LibreOfficeDownload LibreOffice, for example from https://www.libreoffice.org/download/libreoffice-fresh/ and follow theregular installation steps.

Add the following environment variable:

OOO_BASIS_INSTALL_DIR="C:\Program Files (x86)\LibreOffice 5\"

46

https://www.libreoffice.org/download/libreoffice-fresh/

Integration into a Web server

OverviewAdobe Campaign includes Apache Tomcat which acts as the entry point in the application server via HTTP (andSOAP).

You can use this integrated Tomcat server to serve HTTP requests.

In this case:

n the default listening port is 8080. To change it, refer to Default Tomcat port [page 108].

n The client consoles then connect using a URL such as http://:8080.

However, for security and administration reasons, we recommend using a dedicated Web server as the main entrypoint for HTTP traffic when the computer that is running Adobe Campaign is exposed on the Internet and you wishto open access to the console outside of your network.

A Web server also lets you guarantee data confidentiality with the HTTPs protocol.

Likewise, you must use a Web server when you wish to use the tracking functionality, which is only available as aWeb server extension module.

Configuring the IIS Web serverThe configuration procedure for an IIS Web server is mostly graphical. It involves using a Web site (already createdor pending creation) to access the resources of the Adobe Campaign server: Java (.jsp) files, stylesheets (.css, .xsl),images (.png), the ISAPI DLL for redirection, etc.

The following sections detail configuration in IIS 7. Configuration for IIS8 is basically the same.

Warning:

If the Web IIS server is not already installed on your computer, you can install it via the Add > Remove Programs> Enable or disable Windows functionalities menu.

In IIS 7, in addition to standard services, you need to install the ISAPI Extensions and ISAPI filters.

Configuration steps

Apply the following configuration steps:

1 Open the IIS via the Control panel>Administrative tools>Services menu.



http://machine:8080

2 Create and configure the site (Adobe Campaign, for example) depending on the parameters of your network(TCP connection port, DNS host, IP address).

You must at least specify the name of the site and the access path to the virtual directory. Since the path foraccessing the Website directory isn't used, you can use the C:\inetpub\wwwroot directory.

3 A VBS script enables you to automatically configure the resources used by the Adobe Campaign server on thevirtual directory we have just created. To launch it, double click the iis_neolane_setup.vbs file located inthe [INSTALL]\tomcat-7\conf folder, where [INSTALL] is the path for accessing the Adobe Campaigninstallation folder.

Note:

In case of a Windows server 2008/IIS7 installation, you must be logged in as an administrator to run the VBSscript or execute the script as administrator.

Click OK if the Web server is used as a tracking redirection server, otherwise click Cancel.

48

Note:

When multiple sites are already configured on the Web server, an intermediate page is displayed to specify towhich Web site the installation applies: enter the number linked to the site and click OK.

A confirmation message should be displayed:

4 In the Content View tab, make sure the Web site is correctly configured with the Adobe Campaign resources:

Note:

If the tree isn't displayed, restart the IIS.

Managing rights

You must next configure the security settings for the ISAPI DLL and for the resources in the Adobe Campaigninstallation directory.

To do this, apply the following steps:



1 Select the Features View tab and double-click the Authentication link.

2 In the Directory Security tab of the Web site, make sure that anonymous access is enabled. If necessary, clickthe Edit link to change the settings.

Launching the Web server and testing the configuration

You must now test whether the configuration is correct.

To do this, apply the following procedure:

1 Restart the IIS server using the iisreset command line

2 Test the tracking module by inserting the following URL into a Web browser:http:///r/test

The browser should display the following response:

50

http://votre serveur Adobe Campaign/nl/jsp/logon.jsp

Note:

To test for the presence of the redirection module, run the following command line:

nlserver pdump

It must return the following information:

12:00:33 > Application server for Adobe Campaign Version 6.X (build XXXX) of DD/MM/YYYYwebmdl@default (1644) - 18.2 Mo

You can also make sure the ISAPI DLL is correctly loaded.

To do this, apply the following steps:

1 Edit the ISAPI filters for the Adobe Campaign site by clicking the Driver mapping icon.

2 The check the content of the ISAPI filter:

Additional configurations

Changing the upload file size limit

When configuring the IIS Web server, a limit of approximately 28 MB is automatically for set files that are uploadedto the server.

This may have an impact in Adobe Campaign, particularly if you would like to upload files that are larger than thislimit.



For example, if you use a Data loading (file) type activity in a workflow to import a 50 MB file, an error will stop theworkflow from executing correctly.

In this case, you must increase this limit:

1 Open the IIS via the Start > (Control panel) > Administration tools menu.

2 In the Connections pane, select the site created for your Adobe installation, then double-click on RequestFiltering in the main pane.

3 In the Actions pane, select Edit Feature Settings to be able to edit the value in the Maximum authorized contentsize (bytes) field.

For example, to authorize uploading files of 50 MB, you must specify a value of more than "52428800" bytes.

Note:

For more information on this IIS option, refer to the "How To" section of the official documentation.

Configuring http error message display

If you use a 6.1 version IIS server, generated error messages may be difficult to read due to an undesired HTML codebeing displayed in the message.

To fix this and display the error correctly, apply the following configuration:

1 Open the IIS via the Start > Control Panel > Administrative tools menu.

2 In the Connections pane, select the site created for your Adobe Campaign installation, then double-clickConfiguration editor in the main pane.

3 In the Section drop-down list, select system.webServer > httpErrors.

4 Select the PassThrough value at the existingResponse line.

Client console availability

For Adobe Campaign users to be able to log on to the instance you have created and configured, they need to usethe client console.

When the computer used to start an Adobe Campaign application server (nlserver web) receives user connectionsfrom the client console, you can configure it to make the setup program for the Adobe Campaign rich client availablevia an HTML interface.

To do this, you must:

1 Recover the package that contains the console installation program.This file is called setup-client-7.X.XXXX.exe, where X is the sub-version of Adobe Campaign and XXXX isthe build number.

2 Copy and paste this package into the Adobe Campaign installation folder, under /datakit/nl/eng/jsp.


The final users may then download the console installation program via a Web browser thanks to the following URL:

http://:>port number>/nl/jsp/logon.jsp

This page requires a login and password defined in the application.

To download and install the console, refer to Installing the client console [page 53].

52

http://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimitshttp://votre serveur Adobe Campaign/nl/jsp/logon.jsp

Whenever a new version of the client console is available, you are invited to download it.

Note:

In the prompt that is displayed, Adobe recommends leaving the option No longer ask this question unselected tomake sure that all users are alerted when a new version of the console is available.

If you select this option and choose not to download the latest version, no other user will be informed of new availableversions.

To reset this prompt, follow the steps below:

1 Open Registry Editor using the regedit command from the Start > Run menu.

2 Search for the \HKEY_CURRENT_USER\Software\Neolane\NL_6\nlclient node and expand it.

3 Delete the confAdvisedUpgrade entry and close Registry Editor.

Warning:

Only system administrators comfortable with editing the Registry should make these changes.

Installing the client console

The Adobe Campaign console installation procedure is detailed below.

Before you install the Adobe Campaign console, check the prerequisites listed in the Compatibility matrix.

To install the Adobe Campaign console, apply the following steps:

1 Open a Web browser and download the console from the following address:http://:/nl/jsp/logon.jsp.

2 In the identification window, enter your login and password.

Note:

If necessary, use the credentials of the internal account defined during instance creation.



http://support.neolane.net/doc/AC6.1/en/technicalResources/technicalResources.htmlhttp://machine/nl/jsp/logon.jsp

3 Click the Download link on the installation page.

4 Download and save the setup-client-xxx.exe file.

5 Execute the downloaded file on a computer on Windows: The installation starts up.

6 Once the installation program has finished, start the console from the Windows Start menu (in the AdobeCampaign program group).

Note:

n On Windows, you can launch the nlclient.exe file directly from the [INSTALL]/bin directory on a Windowsserver, where [INSTALL] is the access path for the Adobe Campaign installation folder.

n To create a new connection, refer to Creating a new connection [page 68].

54

Table of ContentsBefore the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Software prerequisites for Linux . . . . . . . . . . . . . . . . . . . . . . . . 55Implementation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Distribution based on RPM (RHEL, CentOS and SUSE) packages . . . . . . . . . . . . . . 58Distribution based on APT (Debian) . . . . . . . . . . . . . . . . . . . . . . . 59Parameter personalization . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62First start-up of the server . . . . . . . . . . . . . . . . . . . . . . . . . . 62Password for the internal identifier . . . . . . . . . . . . . . . . . . . . . . . 63

Integration into a Web server . . . . . . . . . . . . . . . . . . . . . . . . . . 63Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Configuring the Apache Web server with Debian . . . . . . . . . . . . . . . . . . . 64Configuring Apache web server in RHEL . . . . . . . . . . . . . . . . . . . . . . 65Launching the Web server and testing the configuration . . . . . . . . . . . . . . . . 66

Client console availability . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Before the installation

Software

adobe campaign v6.1 - installation guide · n the adobe campaign installation steps in the...

Documents