Server-Side Connectors

This article describes how to set up the Adobe Campaign connector in your Customer Data Hub account.

In this article:

Table of Contents Placeholder

Requirements

Adobe Campaign Account
SOAP API Credentials
Contact your Adobe representative for your credentials.
Whitelist the IP addresses of the AudienceStream servers

If the IP addresses are not whitelisted by Adobe, the trace feature displays the following error: Action Failure: Error: received non-successful http response status = 403

Connector Actions

Action Name	AudienceStream	EventStream
Send Custom SOAP Request	✓	✗

Configure Settings

Go to the Connector Marketplace and add a new Adobe Campaign Connector. Read the Connector Overview article for general instructions on how to add a Connector.

This Connector uses Adobe Campaign's SOAP log on method to connect to the SOAP API. Refer to Adobe Campaign's Connectivity documentation for more information.

To configure your vendor, follow these steps:

In the Configure tab, provide a title for the Connector instance.
Enter the SOAP API username and password that you received from Adobe for your account.
Enter the SOAP API endpoint that you received from Adobe for your account. Only include the domain.
Example: If the server path is http://example.com/nl/jsp/soaprouter.jsp, only enter "example.com" in this field.
Provide additional notes about your implementation.
Click Establish Connection to verify the API connectivity.

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
SOAPAction Header Value	This parameter is required Example: `xtk:workflow#PostEvent`.
SOAP Request Body Template Variables	Provide template variables as data input for "SOAP Request Body Template" (Learn more) Name nested template variables with the dot notation, for example: `items.name`. Nested template variables are typically built from data layer list attributes
SOAP Request Body Template	Required. Provide SOAP Request Body Template to be sent. (Learn more) Templates are injected by name with double curly braces into supported fields, for example: `{{SomeTemplateName}}` A session token is required for Adobe Campaign API calls, ensure to include it in the template where appropriate. Use the reserved (predefined and populated automatically for you) template keyword `{{sessionToken}}` to have this token included in the template.
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.

Refer to Adobe Campaign v6.1 Configuration Guide for additional help.

Additional Notes

A SOAP Request Body template is required.
- To inject a template into the supported fields, simply wrap its name in double curly braces, for example {{SomeTemplateName}}.
- See the Templates Guide for common syntax and extensions.
A session token is required for Adobe Campaign API calls
- Ensure that you include it in the template where appropriate.
- Use the reserved template keyword {{sessionToken}} to have this token included in the template.
- A reserved keyword is predefined and populated automatically for you.
Template variables are optional.
- To name nested template variables, use the dot notation, for example items.name.
- Nested template variables are typically built from data layer list Attributes.
- See the Template Variables Guide for details.

Usage Example

Here's a sample configuration for sending a PostEvent SOAP request.

Parameter - Option	Description
SOAPAction Header Value	Configure Custom Value of "xtk:workflow#PostEvent"
SOAP Request Body Template Variables	Map Custom Value of `workflow1000` To `strWorkflowId` Map Custom Value of `importTask2000` To `strActivity`
SOAP Request Body Template	<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="urn:xtk:workflow"> <SOAP-ENV:Header /> <SOAP-ENV:Body> <ns0:PostEvent> <ns0:sessiontoken>{{sessionToken}}</ns0:sessiontoken> <ns0:strWorkflowId>{{strWorkflowId}}</ns0:strWorkflowId> <ns0:strActivity>{{strActivity}}</ns0:strActivity> </ns0:PostEvent> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
SOAP Response Error Identifier	Configure Custom Value of `SOAP-ENV:Fault`

Example Request

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:ns0="urn:xtk:workflow">
	<SOAP-ENV:Header />
	<SOAP-ENV:Body>
		<ns0:PostEvent>
			<ns0:sessiontoken>EXAMPLE_TEALIUM_POPULATED_TOKEN</ns0:sessiontoken>
            <ns0:strWorkflowId>workflow1000</ns0:strWorkflowId>
            <ns0:strActivity>importTask2000</ns0:strActivity>
		</ns0:PostEvent>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Example Response

<?xml version='1.0'?>
	<SOAP-ENV:Envelope xmlns:xsd='http://www.w3.org/2001/XMLSchema'
		xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:ns='urn:xtk:workflow'
		xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'>
		<SOAP-ENV:Body>
			<PostEventResponse xmlns='urn:xtk:workflow'
				SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'></PostEventResponse>
		</SOAP-ENV:Body>
	</SOAP-ENV:Envelope>

Example Error Response

If the SOAP Call Response's HTTP status is 200-299 or otherwise includes any of the "SOAP Response Error Identifier" values, the Action is deemed as a failure. In this example, the Action will be marked as failure because the response contains the identifier "SOAP-ENV:Server".

<?xml version='1.0'?>
	<SOAP-ENV:Envelope xmlns:xsd='http://www.w3.org/2001/XMLSchema'
		xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'>
		<SOAP-ENV:Body>
			<SOAP-ENV:Fault>
				<faultcode>SOAP-ENV:Server</faultcode>
				<faultstring xsi:type='xsd:string'>SOP-330011 Error while executing
					the method 'PostEvent' of service 'xtk:workflow'.</faultstring>
			</SOAP-ENV:Fault>
		</SOAP-ENV:Body>
	</SOAP-ENV:Envelope>