Campaign Configuration and Administration
What you must understand
Administration in Adobe Campaign Classic is mostly about the relationship between the instance, its operators and security zones, and the execution resources that run campaigns. Know the difference between the technical operator (used by workflows and deliveries) and named operators; know how security zones restrict IP ranges and operator access; and know where options (server-wide name/value pairs) live versus target mappings and folders.
Traps that appear in questions
- Instance-level vs. folder-level settings. Many settings (typology rules, target mappings, delivery templates) are folder-scoped, not global. A question that says "applies to the whole instance" is often wrong.
- Options are not variables.
Nms_DefaultRcpSchemaand similar options are read at runtime; changing one does not retroactively fix existing data. - Workflow vs. campaign execution. A recurring campaign (recurring execution) is not the same as a scheduled workflow; know which one owns the delivery.
- Package vs. built-in. Customizations should ship as packages (with a namespace), not hand-edited system schemas.
Rule of thumb
If a setting should travel between environments, it belongs in a package or an option managed through a data package - not in a manually edited system table.
Worked example
A delivery fails with a security-zone error for an operator. The fix is to confirm the operator's security zone and the zone's allowed IP range, not to grant the operator admin rights - admin rights do not bypass zone restrictions.