[On-premise/hybrid only]{class="badge yellow" title="Applies to on-premise and hybrid deployments only"}

File and resource management file-and-resmanagement

Limit upload file format limiting-uploadable-files

Use the uploadWhiteList attribute to restrict the file types available for upload on the Adobe Campaign server.

This attribute is available within the dataStore element of the serverConf.xml file. All the parameters available in the serverConf.xml are listed in this section.

The default value of this attribute is .+ and lets you upload any file type.

To limit the possible formats, replace the attribute value by a valid java regular expression. You can enter several values by separating them by a comma.

For example: uploadWhiteList=“.*.png,.*.jpg” will let you upload PNG and JPG formats on the server. No other formats will be accepted.

You can also prevent important files from being uploaded by configuring the Web Server. Learn more

The uploadWhiteList attribute restricts the file types available for upload on the Adobe Campaign server. However, when the publication mode is Tracking server(s) or Other Adobe Campaign server(s), the uploadWhitelist attribute must also be updated on those servers.

Proxy connection configuration proxy-connection-configuration

You can connect the Campaign server to an external system through a proxy, using a File Transfer workflow activity for example. To achieve this, you need to configure the proxyConfig section of the serverConf.xml file through a specific command. All parameters available in the serverConf.xml are listed in this section.

The following proxy connections are possible: HTTP, HTTPS, FTP, SFTP. Please note that starting 20.2 Campaign release, the HTTP and HTTPS protocol parameters are no longer available. Those parameters are still mentioned below as they remain available in previous builds - including 9032.

Only the basic authentication mode is supported. NTLM authentication is not supported.
SOCKS proxies are not supported.

You can use the following command:

nlserver config -setproxy:[protocol]/[serverIP]:[port]/[login][:‘https’|'http’]

protocol parameters can be ‘http’, ‘https’ or ‘ftp’.

If you are setting FTP on the same port as HTTP/HTTPS traffic, you can use the following:

nlserver config -setproxy:http/

The ‘http’ and ‘https’ options are only used when the protocol parameter is ‘ftp’ and indicate if the tunneling on the specified port will be performed over HTTPS or over HTTP.

If you use a different ports for FTP/SFTP and HTTP/HTTPS traffic over proxy server, you should set the ‘ftp’ protocol parameter.

For example:

nlserver config -setproxy:ftp/’http’

Then enter the password.

HTTP connections are defined in the proxyHTTP parameter:

<proxyConfig enabled=“1” override=“localhost*” useSingleProxy=“0”>
<proxyHTTP address=“" login=“user” password=“*******” port=“8080”/>

HTTPS connections are defined in the proxyHTTPS parameter:

<proxyConfig enabled=“1" override=“localhost*” useSingleProxy=“0">
<proxyHTTPS address=“” login=“user” password=“******” port=“8080"/>

FTP/FTPS connections are defined in the proxyFTP parameter:

<proxyConfig enabled=“1" override=“localhost*” useSingleProxy=“0">
<proxyFTP address=“” login=“user” password=“******” port=“5555" https=”true”/>

If you use the same proxy for several connection types, only the proxyHTTP will be defined with useSingleProxy set to “1” or “true”.

If you have internal connections that should not go through the proxy, add them in the override parameter.

If you want to temporarily disable the proxy connection, set the enabled parameter to “false” or “0”.

If you need to use the iOS HTTP/2 connector through a proxy, the following HTTP proxy modes are supported:

  • HTTP without authentication
  • HTTP basic authentication

To activate the proxy mode, the following change must be done in the serverconf.xml file:

<nmac useHTTPProxy="true">

For more information on this iOS HTTP/2 connector, refer to this page.

Manage public resources managing-public-resources

To be publicly available, the images used in emails and public resources linked to campaigns must be present on an externally accessible server. They can then be available to external recipients or operators. Learn more.

Public resources are stored in the /var/res/instance directory of the Adobe Campaign installation directory.

The matching URL is: http://server/res/instance where instance is the name of the tracking instance.

You can specify another directory by adding a node to the conf-<instance>.xml file to configure storage on the server. This means adding the following lines:

    <dataStore hosts="media*" lang="fra">
      <virtualDir name="images" path="/var/www/images"/>
     <virtualDir name="publicFileRes" path="$(XTK_INSTALL_DIR)/var/res/$(INSTANCE_NAME)/"/>

In this case, the new URL for the public resources given in the upper part of the window of the deployment wizard should point to this folder.