Adobe Campaign Classic Batch Connector Setup Guide | Server-Side Connectors

Connector actions

Action Name	AudienceStream	EventStream
Send Custom SOAP Request	✓	✗

Batch limits

This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

Max number of requests: 200
Max time since oldest request: 10 minutes
Max size of requests: 1 MB

Configure settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

After adding the connector, configure the following settings:

Server Host
- Either Server Host or Server Address is required.
- Example: For the domain, “serverURL” copy and paste serverURL from the following example URL: <https://serverURL/nl/jsp/soaprouter.jsp>
- For authentication, provide username and password as part of SOAP Request Body Prefix.
- For additional information, see Access Management in the Adobe Campaign Classic access management help documentation.
Server Address
- Specify full URL to Adobe Campaign server.
- Either Server Host or Server Address is required.
- If the address is provided, host is ignored.

Action settings - parameters and options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Custom SOAP Request

Parameters

Parameter	Description
SOAP Action	SOAP Action. Example: `xtk:session#Logon` This value will be assigned to SOAPAction HTTP header.
SOAP Request Template Variables	Provide template variables as data input for SOAP Request Body Prefix, SOAP Request Body Data and SOAP Request Body Suffix (see: Template Variables Guide). Name nested template variables with the dot notation. Example: `items.name` Nested template variables are typically built from data layer list attributes.
SOAP Request Body Prefix	Provide a template of the opening portion of SOAP Request. Example: `<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:session"><soapenv:Header/><soapenv:Body><urn:Logon><urn:strLogin>USERNAME</urn:strLogin><urn:strPassword>PASSWORD</urn:strPassword><urn:elemParameters>` Use your Adobe username and password in place of USERNAME and PASSWORD. You can use template variables in the SOAP Request Body Prefix. For additional information, see: Templates Guide
SOAP Request Body Data	Provide a template for the SOAP Request batch item to be sent. You can use template variables in the SOAP Request Body Data.
SOAP Request Body Joiner	A character or string to use between body items when batching. If not specified, empty string will be used.
SOAP Request Body Suffix	Provide a template for the closing portion of SOAP Request. Example: `"</urn:customerId></urn:sendCampaign></soapenv:Body></soapenv:Envelope>` You can use template variables in the SOAP Request Body Suffix.
SOAP Response Error Identifier	If the response contains any of the error strings (OR condition) specified below, it is marked as a failure. By default, an HTTP response status outside 200-299 range is also marked as a failure.