The server configuration file
- Topics:
- Installation
- Instance Settings
The overall configuration of Adobe Campaign is defined in the serverConf.xml file, located in the conf directory of the installation directory. This section lists all the different nodes and parameters of the serverConf.xml file.
The first parameters are inside the shared node. These are related to the instance. They are potentially used by all the nlserver commands (nlserver web, nlserver wfserver, etc.). The other sections are related to a specific nlserver sub-command.
Shared parameters
Other parameters
authentication
Here are the different parameters of the authentication node:
XTK
Here are the different parameters of the authentication > XTK node:
dataStore
Here are the different parameters of the dataStore node. This is where the server data sources are defined.
proxyAdjust
Here are the different parameters of the dataStore > proxyAdjust node. URLs matching the regular expression are regenerated based on the URL defined in urlBase.
dataSource
Here are the different parameters of the dataStore > dataSource node.
In the dataStore > dataSource > dbcnx node, configure the connection settings:
In the dataStore > dataSource > sqlParams node, configure the SQL parameters:
In the dataStore > dataSource > pool node, configure the parameters of associated connections pool:
virtualDir
Here are the different parameters of the dataStore > virtualDir node. This is the configuration of the virtual directory to real directory mapping.
For additional information, refer to Managing public resources.
Here is the default configuration:
<virtualDir name="images" path="$(XTK_INSTALL_DIR)/var/res/img/"/>
<virtualDir name="formCache" path="$(XTK_INSTALL_DIR)/var/$(INSTANCE_NAME)/formCache/"/>
<virtualDir name="publicFileRes" path="$(XTK_INSTALL_DIR)/var/res/$(INSTANCE_NAME)"/>
preprocessCommand
Here are the different parameters of the dataStore > preprocessCommand node. These are the authorized commands for pre-processing of the ‘Load file’ workflow activity.
Here is the default configuration:
<preprocessCommand command="" label="None" name="none"/>
<preprocessCommand command="zcat "$fileName"" label="Decompression" name="zcat"/><preprocessCommand command="gpg --decrypt "$fileName"" label="Decrypt" name="gpg"/>
dnsConfig
Here are the different parameters of the dnsConfig (DNS configuration) node.
For additional information, refer to this section.
parameters of the first network interface declared in Windows
not defined in UNIX. Defines the domain name servers (DNS)
used by the MTA to get the Mail Exchanger declared for
a domain.
exec
Here are the different parameters of the exec (command execution) node.
For additional information, refer to Restricting authorized external commands.
htmlToPdf
Here are the different parameters of the htmlToPdf node. This is the configuration of the service for converting web pages into PDF documents.
Example for phantomjs:
phantomjs - -ignore-ssl-errors=true '$(XTK_INSTALL_DIR)/bin/htmlToPdf.js' '-out:{outPdf}' '-post:{postFile}' '-url:{originUrl}' -sessiontoken:{sessiontoken} -format:{format} -orientation:{orientation} -marginTop:{marginTop} -marginLeft:{marginLeft} -marginRight:{marginRight} -marginBottom:{marginBottom}
ims
Here are the different parameters of the ims node. This is the configuration for Campaign connecting to another service using IMS.
JavaScript
Here are the different parameters of the javaScript node. This is the configuration of the JavaScript interpreter.
For additional information, refer to the Reporting documentation.
mailExchanger
Here are the different parameters of the mailExchanger node. This is the configuration of the SMTP server.
module
Here are the different parameters of the module node. This is the configuration for the namespaces restrictions module xtk.
monitoring
Here are the different parameters of the monitoring node. This is the monitoring service configuration.
ooconv
Here are the different parameters of the ooconv node. This is the configuration of the document conversion server.
proxyConfig
Here are the different parameters of the proxyConfig node. This is the configuration of proxy parameters.
For additional information, refer to Proxy connection configuration.
HTTP Proxy / Secure proxy
In the proxyConfig > HTTP Proxy / Secure proxy node, configure the following parameters.
For additional information, refer to Proxy connection configuration.
threadPool
Here are the different parameters of the threadPool node.
urlPermission
Here are the different parameters of the urlPermission node. This is the list of URLs that the Javascript code can access.
List of domains and regular expressions specifying whether a URL encountered in the Javascript code can or cannot be used by the Adobe Campaign server.
If the URL cannot be found, the default action is carried out, according to the default mode specified.
For additional information, refer to Outgoing connection protection.
cusHeaders
This node allows you to add specific headers in requests performed when uploading a file from an external server. Content Delivery Networks (CND) can ask for a specific header in order to trust the requester. These headers can be used to improve the trust on Campaign requests, particulary when downloading personalized documents for each recipient at delivery execution step. A high number of resource download requests can be interpreted as a DDos attack. dnsPattern allows you to to set specific header names and values for different CDNs based on their domain name.
<!-- List of custom headers added to request.
-->
<cusHeaders>
<!-- Pattern of DNS name or domain
value : dnsPattern: All or part of the URL's domain to verify, * is a wild card Default: -->
<dnsPattern value="">
<!-- Header Name and Value
headerName : Header Name
headerValue : Header Value -->
<headerDef headerName="" headerValue=""/>
</dnsPattern>
</cusHeaders>
url
For each URL, add a url node with the following parameters:
For additional information, refer to Outgoing connection protection.
If a record satisfies dnsSuffix but not urlRegEx, the following record is examined.
For example, to authorize access to all of the URLs of the domain business.com, we can define two records:
dnsSuffix=“business.com” urlRegEx=“http://.*”
and
dnsSuffix=“business.com” urlRegEx=“https://.*”
Here is the default configuration:
<url dnsSuffix="api.omniture.com" urlRegEx="https://api.omniture.com/genesis/i/3.1.*" />
<url dnsSuffix="omniture.com" urlRegEx="https://api[1-5].omniture.com/genesis/i/3.1.*" />
<url dnsSuffix="marketing.adobe.com" urlRegEx="https://.*" />
<url dnsSuffix="fcm.googleapis.com" urlRegEx="https://fcm.googleapis.com/fcm/send.*" />
<url dnsSuffix="graph.facebook.com" urlRegEx="https://.*" />
<url dnsSuffix="api.line.me" urlRegEx="https://api.line.me/.*" />
<url dnsSuffix="api.twitter.com" urlRegEx="https://api.twitter.com/1.1.*" />
<url dnsSuffix="adobeid-na1.services.adobe.com" urlRegEx="https://.*" />
<url dnsSuffix="adobeid-na1-stg1.services.adobe.com" urlRegEx="https://.*" />
<url dnsSuffix="localhost" urlRegEx="http://localhost:8080/nms/jsp/.*" />
<url dnsSuffix="localhost" urlRegEx="http://localhost:8080/nl/jsp/.*" />
<url dnsSuffix="localhost" urlRegEx="http://localhost:8080/xtk/jsp/.*" />
xtkJobs
Here are the different parameters of the xtkJobs node. This is the configuration of the server jobs.
archiving
Here are the different parameters of the archiving node. This is the configuration of the executed archiving operations in the background.
For additional information, refer to Activating email archiving (on premise).
inMail
Here are the different parameters of the inMail node. This is the configuration of the inbound Email management module.
msgDump
In the inMail > msgDump node, configure the following parameters. This is the configuration of the dump of processed messages.
interactiond
Here are the different parameters of the interactiond node. This is the configuration of the write daemon for inbound Interaction events.
For additional information, refer to Interaction - Data buffer.
mta
Here are the different parameters of the mta node. This is the configuration of delivery agents.
[
: <port> ]
. See Coordinates of the statistics server.cache
In the cache node, configure the following parameters. This is the local file cache configuration.
relay
In the mta > relay node, configure the following parameters. This is the configuration of the mail server for the message delivery.
The list will be handled in the same way as a list of MX returned by a MX DNS query, usually the first MX is used as long as it is available, then the next one is used, and so on.
For additional information, refer to SMTP relay.
master
In the mta > master node, configure the following parameters. This is the configuration of the main server.
For additional information, refer to this section.
child
In the mta > child node, configure the following parameters. This is the configuration of child servers.
For additional information, refer to Email sending optimization.
In the mta > child > smtp node, configure the following parameters. This is the configuration of SMTP sessions.
In the mta > child > smtp > IPAffinity node, configure the following parameters. This is the configuration of the management of affinities with IP addresses for optimized outgoing SMTP traffic.
For additional information, refer to List of IP addresses to use and Managing outbound SMTP traffic with affinities.
In the mta > child > smtp > IP node, configure the following parameters.
For additional information, refer to List of IP addresses to use.
nmac
Here are the different parameters of the nmac node. This is the configuration of for push notification deliveries.
relay
Here are the different parameters of the nmac > relay node. This configures the use of a relay for the message delivery (ios http2 connector).
pipelined
Here are the different parameters of the pipelined node. This is the configuration of the event processing module for Pipeline Services.
repair
Here are the different parameters of the repair node. This is the configuration of the database repair module.
securityZone
Here are the different parameters of the securityZone node.
For additional information, refer to Define security zones.
Here is the default configuration:
<securityZone allowDebug="false" allowHTTP="false" allowSQLInjection="false" label="Public Network" name="public">
<subNetwork name="all" label="All addresses" mask="*" proxy="127.0.0.1, ::1"/>
<securityZone allowDebug="true" allowHTTP="false" allowSQLInjection="false" label="Private Network (VPN)"
name="vpn" showErrors="true">
<securityZone allowDebug="true" allowEmptyPassword="false" allowHTTP="true" allowUserPassword="false"
allowSQLInjection="false" label="Private Network (LAN)" name="lan" sessionTokenOnly="true"
showErrors="true">
<subNetwork name="lan1" label="Lan 1" mask="192.168.0.0/16" proxy="127.0.0.1, ::1"/>
<subNetwork name="lan2" label="Lan 2" mask="172.16.0.0/12" proxy="127.0.0.1, ::1"/>
<subNetwork name="lan3" label="Lan 3" mask="10.0.0.0/8" proxy="127.0.0.1, ::1"/>
<subNetwork name="localhost" label="Localhost" mask="127.0.0.0/8" proxy="127.0.0.1, ::1"/>
<subNetwork name="lan6" label="Lan (IPv6)" mask="fc00::/7" proxy="127.0.0.1, ::1"/>
<subNetwork name="lan6b" label="Lan (IPv6)" mask="fe80::/10" proxy="127.0.0.1, ::1"/>
<subNetwork name="localhost6" label="Localhost (IPv6)" mask="::1/128" proxy="127.0.0.1, ::1"/>
</securityZone>
</securityZone>
</securityZone>
subNetwork
Here are the different parameters of the securityZone > subNetwork node.
For additional information, refer to Define security zones.
sms
Here are the different parameters of the sms node. This is the configuration of the inbound SMS management module.
netsize
Here are the different parameters of the sms > netsize node.
stat
Here are the different parameters of the stat node. This is the configuration of the MTA statistics module.
syslogd
Here are the different parameters of the syslogd node. This is the configuration of the Log management module.
tracking
Here are the different parameters of the tracking node. This is the configuration of the tracking server.
trackinglogd
Here are the different parameters of the trackinglogd node. This is the configuration of the tracking log writing daemon.
web
Here are the different parameters of the web node. This is the configuration of the Web Module.
For additional information, refer to this section.
jsp
Here are the different parameters of the web > jsp node. This is the configuration of the parameters used by the JSPs.
The web > jsp > classpath node contains the list of all class paths to use when starting JVM. Here is the default configuration:
'$(XTK_INSTALL_DIR)/tomcat-X/bin/bootstrap.jar
$(XTK_INSTALL_DIR)/tomcat-X/bin/tomcat-juli.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/tomcat-coyote.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/tomcat-util.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/tomcat-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/servlet-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/jsp-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/el-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/annotations-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/catalina.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/websocket-api.jar
$(XTK_INSTALL_DIR)/tomcat-X/lib/tomcat7-websocket.jar
$(XTK_INSTALL_DIR)/java/lib/pdfbox-2.0.4.jar
$(XTK_INSTALL_DIR)/java/lib/FontBox-0.1.0.jar
$(XTK_INSTALL_DIR)/java/lib/AGJavaEndpoint.22.jar
$(XTK_INSTALL_DIR)/java/lib/NSGConstants.jar
$(XTK_INSTALL_DIR)/java/lib/smpp.jar
$(XTK_INSTALL_DIR)/java/lib/nlweb.jar
$(XTK_INSTALL_DIR)/java/lib/jcaptcha-all.jar
$(XTK_INSTALL_DIR)/java/lib/apns-1.0.0.Beta6-jar-with-dependencies.jar
$(XTK_INSTALL_DIR)/java/lib/commons-collections-3.2.2.jar
$(XTK_INSTALL_DIR)/java/lib/jcommon-1.0.16.jar
$(XTK_INSTALL_DIR)/java/lib/jfreechart-1.0.13.jar
$(XTK_INSTALL_DIR)/java/lib/barcode4j-light.jar
$(XTK_INSTALL_DIR)/java/lib/zxing.jar
$(XTK_INSTALL_DIR)/java/lib/raztec.jar
$(XTK_INSTALL_DIR)/java/lib/gson-2.7.jar
$(XTK_INSTALL_DIR)/java/lib/alpn-api-1.1.3.v20160715.jar
$(XTK_INSTALL_DIR)/java/lib/netty-all-4.1.6.Final.jar
$(XTK_INSTALL_DIR)/java/lib/netty-tcnative-boringssl-static-1.1.33.Fork22.jar
$(XTK_INSTALL_DIR)/java/lib/pushy-0.8.1.jar
$(XTK_INSTALL_DIR)/java/lib/slf4j-api-1.7.21.jar
$(XTK_INSTALL_DIR)/java/lib/slf4j-simple-1.7.21.jar'
jssp
Here are the different parameters of the web > jssp node. This is the configuration of the parameters used by the JSSPs.
The web > jsp > classpath node contains the list of all class paths to use when starting JVM.
relay
Here are the different parameters of the web > relay node. This is the configuration of the relay for HTTP requests between two zones.
For additional information, refer to this section.
Add a web > relay > url node for each URL to relay (insert order defines priority) with the following parameters.
For additional information, refer to Dynamic page security and relays and section.
Here is the default configuration:
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true"
status="normal" targetUrl="http://localhost:7781" timeout="" urlPath="/pipelined/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="false" urlPath="/view/*"/>
<url IPMask="" deny="true" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="false" urlPath="*ooconv.jsp*"/>
<url IPMask="" deny="true" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="false" urlPath="/res/*.jsp*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="*/sc.jssp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="*/interactionProposal.jssp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="*/zoneJson.jssp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/nms/jsp/barcode.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/nms/jsp/captcha.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/nms/jsp/webForm.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/xtk/jsp/zoneinfo.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="*/facebookCallback.jssp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/nl/jsp/m.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/nl/jsp/s.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="/nms/jsp/*.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="/xtk/jsp/*.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="/nl/jsp/*.jsp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="*.jssp"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="true" urlPath="/webApp/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="/report/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="blacklist" httpAllowed="false" urlPath="/jssp/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="false" urlPath="/strings/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/interaction/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/barcode/*"/>
<url IPMask="" deny="" hostMask="" relayHost="true" relayPath="true" targetUrl="http://localhost:8080"
timeout="" status="normal" httpAllowed="true" urlPath="/lineImage/*"/>
<url IPMask="" deny="" hostMask="" relayHost="false" relayPath="false" targetUrl=""
timeout="" status="spare" httpAllowed="true" urlPath="/favicon.*"/>
<url IPMask="" deny="" hostMask="" relayHost="false" relayPath="false" targetUrl=""
timeout="" status="spare" httpAllowed="true" urlPath="/*.md"/>
<url IPMask="" deny="" hostMask="" relayHost="false" relayPath="false" targetUrl=""
timeout="" status="spare" httpAllowed="true" urlPath="/*.png"/>
<url IPMask="" deny="" hostMask="" relayHost="false" relayPath="false" targetUrl=""
timeout="" status="spare" httpAllowed="true" urlPath="/*.jpg"/>
Add a web > relay > responseHeader node for each HTTP header to add to replies forwarded to the relay.
For additional information, refer to Managing HTTP headers.
Here is the default configuration:
<responseHeader name="X-XSS-Protection" value="1; mode=block"/>
redirection
Here are the different parameters of the web > redirection node. This is the configuration of the redirection module.
For additional information, refer to this section.
Here are the different parameters of the web > redirection > spareServer node.
For additional information, refer to Redundant tracking.
spamCheck
Here are the different parameters of the web > spamCheck node. This is the configuration the Email anti-spam scoring evaluation parameters.
For additional information, refer to Configuring SpamAssassin.
wfserver
Here are the different parameters of the wfserver node. This is the workflow process configuration.
For additional information, refer to High availability workflows and affinities.