Configuration Management Lifecycle

You typically move through configuration management in the following order:

  1. Choose a starting point. Start from a system template or an existing user-defined template that matches the make, model, and platform version that you need.
  2. Create your template. Oracle ECP creates the new template as version 1 in Draft.
  3. Edit configuration blocks. Update the blocks that you want to change. Save your changes while the version remains in draft.
  4. Publish the draft. When the configuration is ready, publish the draft. The published version becomes read-only.
  5. Apply the published version. Apply the configuration to one edge node or multiple compatible edge nodes when you are ready.
  6. Monitor the request. Review the activity log to track progress until the operation completes.
  7. Repeat when needed. When you need another revision, create a new draft from the latest published version.

This lifecycle separates preparation from deployment. You can finish your configuration work first and apply it later during the timing window that fits your operations.

For single-edge configuration, Oracle ECP also supports direct updates on one edge node. An edge node configuration can change through a direct single-edge update, a template apply, or a local edge UI change.

If you apply a template to an edge node, Oracle ECP associates that edge node with the published template version. If you later update that edge node directly from the item overview page or the single-edge configuration editor, Oracle ECP removes that association after the update completes.