Integration into a Web server for Windows
Adobe Campaign includes Apache Tomcat which acts as the entry point in the application server via HTTP (and SOAP).
You can use this integrated Tomcat server to serve HTTP requests.
In this case:
- the default listening port is 8080. To change it, refer to Configuring Tomcat .
- The client consoles then connect using a URL such as https:// .
However, for security and administration reasons, we recommend using a dedicated Web server as the main entry point for HTTP traffic when the computer that is running Adobe Campaign is exposed on the Internet and you wish to 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 a Web server extension module.
If you do not use the tracking functionality, you can perform a standard installation of Apache or IIS with a redirection to Campaign. The tracking Web server extension module is not required.
Configuring the IIS Web server
The configuration procedure for an IIS Web server is mostly graphical. It involves using a Web site (already created or 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.
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.
Apply the following configuration steps:
- Open the IIS via the Control panel > Administrative tools > Services menu.
- 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 for accessing the Website directory is not used, you can use the following directory.
- A VBS script enables you to automatically configure the resources used by the Adobe Campaign server on the virtual directory we have just created. To launch it, double click the iis_neolane_setup.vbs file located in the [INSTALL]\tomcat-7\conf folder, where [INSTALL] is the path for accessing the Adobe Campaign installation folder.In case of a Windows server 2008/IIS7 installation, you must be logged in as an administrator to run the VBS script or execute the script as administrator.Click OK if the Web server is used as a tracking redirection server, otherwise click Cancel .When multiple sites are already configured on the Web server, an intermediate page is displayed to specify to which Web site the installation applies: enter the number linked to the site and click OK .A confirmation message should be displayed:
- In the Content View tab, make sure the Web site is correctly configured with the Adobe Campaign resources:If the tree is not displayed, restart the IIS.
You must next configure the security settings for the ISAPI DLL and for the resources in the Adobe Campaign installation directory.
To do this, apply the following steps:
- Select the Features View tab and double-click the Authentication link.
- In the Directory Security tab of the Web site, make sure that anonymous access is enabled. If necessary, click the 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:
- Restart the IIS server using the iisreset command line.
- Test the tracking module by inserting the following URL into a Web browser:
https://<computer>/r/testThe browser should display the following response:
<redir status='OK' date='YYYY/MM/DD HH:MM:SS' build='XXXX' host='myserver.mydomain.com' localHost='localhost'/>
To test for the presence of the redirection module, run the following command line:
It must return the following information:
12:00:33 > Application server for Adobe Campaign Classic (7.X YY.R build XXX@SHA1) of DD/MM/YYYY webmdl@default (1644) - 18.2 Mo
You can also make sure the ISAPI DLL is correctly loaded.
To do this, apply the following steps:
- Edit the ISAPI filters for the Adobe Campaign site by clicking the Driver mapping icon.
- The check the content of the ISAPI filter:
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 uploaded to the server.
This may have an impact in Adobe Campaign, particularly if you would like to upload files that are larger than this limit.
For example, if you use a Data loading (file) type activity in a workflow to import a 50 MB file, an error will stop the workflow from executing correctly.
In this case, you must increase this limit:
- Open the IIS via the Start > (Control panel) > Administration tools menu.
- In the Connections pane, select the site created for your Adobe installation, then double-click on Request Filtering in the main pane.
- In the Actions pane, select Edit Feature Settings to be able to edit the value in the Maximum authorized content size (bytes) field.For example, to authorize uploading files of 50 MB, you must specify a value of more than "52428800" bytes.
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 code being displayed in the message.
To fix this and display the error correctly, apply the following configuration:
- Open the IIS via the Start > Control Panel > Administrative tools menu.
- In the Connections pane, select the site created for your Adobe Campaign installation, then double-click Configuration editor in the main pane.
- In the Section drop-down list, select system.webServer > httpErrors .
- Select the PassThrough value at the existingResponse line.