MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 11 · Automation

Error handling and logging

Lesson 128 of 201 · 14 min

What a command returns on failure, and how to test it. Add exit-code checking after each step, logging with timestamps, and notification on failure. Demonstrate a failure producing a readable log and an alert — and show a script that fails SILENTLY, for contrast. THIS LESSON IS THE DIFFERENCE BETWEEN A SCRIPT AND AN AUTOMATION. A script does the thing. An automation does the thing, tells you when it could not, and leaves evidence. NOTIFICATION ON FAILURE IS NOT OPTIONAL. If nobody is told, the automation is a liability. WRITE LOGS A COLLEAGUE COULD READ AT 3AM. Timestamps, step names, plain-language outcomes. You will be that colleague. The silent failure demonstration should be uncomfortable. That is the point.

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 11 · Automation

  1. 1Three tools, one questionFree preview
  2. 2Job Scheduler
  3. 3Installing and configuring the automation utility
  4. 4Authentication and credential handling
  5. 5The command surface
  6. 6Scripting patterns: backup and export
  7. 7Scripting patterns: data load and refresh
  8. 8Error handling and logging
  9. 9Scheduling and service accounts
  10. 10REST APIs and when to reach for them
  11. 11The integration agent
  12. 12What breaks
  13. 13Lab: automate it, and write the runbook