Lab: Build Multi-Integration Workflow (ServiceNow + Ansible + DNS)

VCF 9.0Intermediatevcap-advanced⏱ 120 min

Objectives

Create event-driven multi-step workflow: deployment request → ServiceNow CR → Ansible config → DNS registration → Monitoring tags.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

Standard VCF lab environment for Advanced VCF 9.0 Automation

Tasks

Task 1 Lab: Build Multi-Integration Workflow (ServiceNow + Ansible + DNS)

Create event-driven multi-step workflow: deployment request → ServiceNow CR → Ansible config → DNS registration → Monitoring tags.

Step 1

Create ABX action "create-servicenow-cr" that creates change request in ServiceNow

Step 2

Subscribe to "com.vmware.cac.deployment.created" event with blocking action above

Step 3

Create ABX action "trigger-ansible-playbook" that configures deployed VMs

Step 4

Subscribe to "com.vmware.cac.compute.machine.created" with non-blocking Ansible action

Step 5

Create ABX action "register-dns" that creates A and PTR records

Step 6

Add to post-provision pipeline

Step 7

Create ABX action "tag-monitoring" for Datadog/New Relic integration

Step 8

Test with cloud template deployment and verify all integrations execute

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

Workflow orchestration without error handling between integration points

Fix: A workflow that calls ServiceNow → VCF Automation → Ansible sequentially fails silently if step 2 errors. Implement: try/catch at each step, rollback logic (if VCF Automation deploys but Ansible config fails, flag for manual review), and notification on partial completion.

Credential management across multiple integrations

Fix: Each integration (ServiceNow, Ansible, VCF Automation) requires separate credentials. Hardcoding credentials in workflow scripts creates security risk and maintenance burden. Use a credential vault (HashiCorp Vault, CyberArk) or VCF Automation encrypted properties for all integration credentials.

Not testing the complete workflow end-to-end before production use

Fix: Individual integration tests pass but the combined workflow fails due to: data format mismatches between systems, timing dependencies, or permission issues in downstream systems. Always run end-to-end tests with production-like data.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

Multi-system orchestration demonstrates enterprise integration skills. VCDX designs that show workflow automation across ITSM, infrastructure, and configuration management score highest on manageability.

⚠ Known Pitfalls (from Community KB)

Orchestrating without error handling — a failure in step 3 of 5 leaves partially configured resources.

Using shared service accounts across integrations — audit trail becomes impossible.

Mark complete