Show Menu
TOPICS×

Enterprise deployment

This is the most complete configuration. It builds on the standard configuration for greater security and availability:
  • dedicated redirection servers behind a HTTP or TCP load balancer, for scalability and availability,
  • two application servers for improved throughput and failover capability (fault tolerance) and which are isolated in the LAN.
General communication between servers and processes is carried out according to the following schema:
With this type of configuration, the expected throughput can exceed 100,000 mails per hour with appropriate bandwidth and tuning.

Features

Advantages

  • Optimized security: Only those servers that need to be exposed to the outside are installed on the computer in the DMZ.
  • High availability easier to ensure: Only the computer visible from the outside needs to be managed with high availability in mind.

Disadvantages

Higher hardware and administration costs.

Installation and configuration steps

Prerequisites

  • JDK on both application servers,
  • Web server (IIS, Apache) on both frontals,
  • Access to a database server on both application servers,
  • Bounce mailbox accessible via POP3,
  • Creation of two DNS aliases on the load balancer:
    • 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,
    • the second exposed to the internal users for access via the console and pointing to a load balancer on a virtual IP address (VIP) and which is then distributed to the two application servers.
  • Firewall configured to open STMP (25), DNS (53), HTTP (80), HTTPS (443), SQL (1521 for Oracle, 5432 for PostgreSQL, etc.) ports. For further information, refer to section Database access .
If your application servers point to a single database instance, after importing a standard package on one instance, the schema contained in the package is not loaded on the other instance.
If your application servers point to a single database instance, after changing schema on one instance, the schema is not loaded on the other instance.
To recover these issues, you need to reboot ‘web@default‘ process on the second instance where error occurred.

Installing and configuring the application server 1

In the following examples, the parameters of the instance are:
  • Name of the instance: demo
  • DNS mask: tracking.campaign.net*, console.campaign.net* (the application server handles the URLs for client console connections and reports and for mirror pages and unsubscription pages)
  • Language: English
  • Database: campaign:demo@dbsrv
The steps for installing the first server are:
  1. Follow the installation procedure for the Adobe Campaign server: nlserver package on Linux or setup.exe on Windows.
  2. Once the Adobe Campaign server is installed, start the application server (web) using the command nlserver web -tomcat (the Web module enables you to start Tomcat in standalone Web server mode listening on port 8080) and to make sure Tomcat starts correctly:
    12:08:18 >   Application server for Adobe Campaign Classic (7.X YY.R build XXX@SHA1) of DD/MM/YYYY
    12:08:18 >   Starting Web server module (pid=28505, tid=-1225184768)...
    12:08:18 >   Tomcat started
    12:08:18 >   Server started
    
    
    The first time the Web module is executed it creates the config-default.xml and serverConf.xml files in the conf directory under the installation folder. All the parameters available in the serverConf.xml are listed in this section .
    Press Ctrl+C to stop the server.
    For more on this, refer to the following sections:
  3. Change the internal password using the command:
    nlserver config -internalpassword
    
    
    For more on this, refer to Internal identifier .
  4. Create the demo instance with the DNS masks for tracking (in this case, tracking.campaign.net ) and access to client consoles (in this case, console.campaign.net ). There are two ways of doing this:
  5. Edit the config-demo.xml file (created via the previous command and located next to the config-default.xml file), check that the mta (delivery), wfserver (workflow), inMail (rebound mails) and stat (statistics) processes are enabled, then configure the address of the app statistics server:
    <?xml version='1.0'?>
    <serverconf>  
      <shared>    
        <!-- add lang="eng" to dataStore to force English for the instance -->    
        <dataStore hosts="tracking.campaign.net*,console.campaign.net*">      
          <mapping logical="*" physical="default"/>    
        </dataStore>  </shared>  
        <mta autoStart="true" statServerAddress="app">
        <wfserver autoStart="true"/>  
        <inMail autoStart="true"/>  
        <sms autoStart="false"/>  
        <listProtect autoStart="false"/>
    </serverconf>
    
    
    For more on this, refer to Enabling processes .
  6. Edit the serverConf.xml file and specify the delivery domain, then specify the IP (or host) addresses of the DNS servers used by the MTA module to answer MX type DNS queries.
    <dnsConfig localDomain="campaign.com" nameServers="192.0.0.1, 192.0.0.2"/>
    
    
    The nameServers parameters is only used in Windows.
    For more on this, refer to Campaign server configuration .
  7. Copy the client console setup program ( setup-client-7.XX , YYYY.exe for v7 or setup-client-6.XX , YYYY.exe for v6.1) to the /datakit/nl/eng/jsp folder.
    For more on this, refer to the following sections:
  8. Start the Adobe Campaign server ( net start nlserver6 in Windows, /etc/init.d/nlserver6 start in Linux) and run the command nlserver pdump once more to check for presence of all enabled modules.
    12:09:54 >   Application server for Adobe Campaign Classic (7.X YY.R build XXX@SHA1) of DD/MM/YYYY
    syslogd@default (7611) - 9.2 MB
    stat@demo (5988) - 1.5 MB
    inMail@demo (7830) - 11.9 MB
    watchdog (27369) - 3.1 MB
    mta@demo (7831) - 15.6 MB
    wfserver@demo (7832) - 11.5 MB
    web@default (28671) - 40.5 MB
    
    
    
    This command also lets you know the version and build number of the Adobe Campaign server installed on the computer.
  9. Test the nlserver web module using the URL: https://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.
    For more on this, refer to the following sections:

Installing and configuring the 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.
    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
    
    
  5. Edit the config-demo.xml file (created via the previous command and located next to the config-default.xml file), check that the mta (delivery), wfserver (workflow), inMail (rebound mails) and stat (statistics) processes are enabled, then configure the address of the app statistics server:
    <?xml version='1.0'?>
    <serverconf>  
      <shared>    
        <!-- add lang="eng" to dataStore to force English for the instance -->    
        <dataStore hosts="tracking.campaign.net*,console.campaign.net*">      
          <mapping logical="*" physical="default"/>    
        </dataStore>  </shared>  
        <mta autoStart="true" statServerAddress="app">
        <wfserver autoStart="true"/>  
        <inMail autoStart="true"/>  
        <sms autoStart="false"/>  
        <listProtect autoStart="false"/>
    </serverconf>
    
    
    For more on this, refer to Enabling processes .
  6. Edit the serverConf.xml file and populate the DNS configuration of the MTA module:
    <dnsConfig localDomain="campaign.com" nameServers="192.0.0.1, 192.0.0.2"/>
    
    
    The nameServers parameter is only used in Windows.
    For more on this, refer to Campaign server configuration .
  7. Start the Adobe Campaign servers.
    For more on this, refer to the following sections:

Installing and configuring the frontal servers

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.xml file, 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:
    <spareServer enabledIf="$(hostname)!='front_srv1'" id="1" url="https://front_srv1:8080"/>
    <spareServer enabledIf="$(hostname)!='front_srv2'" id="2" url="https://front_srv2:8080"/>
    
    
  5. Start the website and test the redirection from the URL: https://tracking.campaign.net/r/test
    The browser should display the following messages (depending on the URL redirected by the load balancer):
    <redir status="OK" date="AAAA/MM/JJ HH:MM:SS" build="XXXX" host="tracking.campaign.net" localHost="front_srv1"/>
    
    
    or
    <redir status="OK" date="AAAA/MM/JJ HH:MM:SS" build="XXXX" host="tracking.campaign.net" localHost="front_srv2"/>
    
    
    For more on this, refer to the following sections:
  6. Start the Adobe Campaign server.