Adobe Campaign Classic Architect Master flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Three-tier architecture

Adobe Campaign Classic separates the presentation layer (client/Web UI), the application layer (campaign, workflow, and web modules), and the data layer (the RDBMS).

MTA process role

The Message Transfer Agent handles outbound delivery, applying connection settings and IP reputation; it can run on a separate server from the marketing application.

Tracking server purpose

The tracking server receives redirect and open requests from recipients' browsers, records them in the tracking log, and must be reachable from the public internet.

Message Center architecture

Real-time transactional messaging requires a dedicated execution instance with its own MTA and a transactional message template linked to a routing.

nmsRecipient schema

The core recipient schema holding subscriber data; it is extended with custom fields and linked to subscriptions, broad logs, and tracking logs.

Schema extension element

A schema extends another via the extends attribute in srcSchema or the Extend tab; new fields are added as element nodes under the target schema.

autopk attribute

The @autopk attribute on a schema key enables an automatic numeric primary key; without it the primary key is a generated 32-character string.

Reverse link revLink

The @revLink attribute on a join defines the reverse link on the target schema, enabling navigation from the target back to the source.

Database structure wizard

The Database Structure wizard compares schema definitions to the physical database and generates and applies the SQL DDL statements.

Query activity

The primary targeting activity; its targeting dimension is set by the schema selected in the activity properties, and it filters records.

Enrichment activity

Adds data from a linked or unrelated table via a join or sub-query; the added data is available to downstream workflow activities.

Fork and AND-join

The Fork activity creates parallel branches; the AND-join activity waits for all incoming transitions before continuing the workflow.

Scheduler activity

Triggers a workflow on a recurring schedule; the External signal activity instead resumes a workflow when an external process calls the signal.

Technical workflows

Internal workflows identified by @internal="true" that handle cleanup, tracking, and billing; they must not be deleted from the instance.

SOAP API WSDL

The SOAP API is described by the WSDL at /nl/jsp/xtk.wsdl and exposes session, queryDef, persist, and workflow schemas for integration.

xtkQueryDef operations

The query definition schema supports select, get, and getIfExists operations, with where, orderBy, and lineCount elements controlling the result set.

xtkPersist operations

The persist schema supports insert, update, and delete operations, controlled by the @operation attribute, for writing data via the API.

External signal trigger

The External signal activity can be triggered via the SOAP API by calling xtk:workflow PostEvent with the workflow ID and signal name.

JSSP web applications

JavaScript Server Pages host web applications under /nl/jsp/; the application is declared in the web module and uses the page directive.

MTA throughput formula

Messages per hour equals threads per MTA multiplied by messages per second per thread multiplied by 3600; per-thread rate depends on the receiving MTA.

Tracking log growth

The nmsTrackingLog table grows fastest; the cleanup technical workflow purges it according to the retention period set in the deployment wizard.

Index necessity

Indexes on the targeting dimension and on the broad log's delivery ID are critical; missing indexes cause full table scans and slow targeting.

Delivery waves

Wave scheduling distributes sending over time to avoid overwhelming the MTA and the receiving MTAs, improving deliverability and throughput.

Security zones

Security zones restrict operator access to specific folders and to specific IP addresses; an operator can belong to multiple zones.

Named rights

Granular permissions such as admin, workflow, delivery, and schema, assigned to operators or groups to control access to platform functions.

Admin named right

The admin right grants full access and bypasses folder restrictions; it should be limited to a small set of trusted operators.

Audit trail attribute

The @logAuditTrail attribute on a schema enables recording of operator actions on that schema's records in the audit log.

Deployment wizard

Configures the instance's database connection, MTA, web, tracking, and security settings; it is run per instance and per environment.

Package export

Exports schemas, workflows, delivery templates, and other objects to an XML package that is imported into the target environment.

Environment promotion path

Objects move from development to staging to production; each environment has its own database and its own nlserver instance.

JavaScript NLWS API

Server-side JavaScript API exposing session, queryDef, and persist objects, usable in web applications and in workflow JavaScript activities.

Computed schema fields

The condition element defines a computed boolean field and the compute element defines a computed string field within a schema definition.