Let us know how we can help
Sales & Pricing
Speak to a rep about your business needs
Help & Support
See our product support options
General inquiries and locations
Contact us
Control-M + OCI VM
Your OCI VM workflow starts before a virtual machine lifecycle action ever executes — and it can fail when something upstream breaks. An OCI Data Integration task fails before application data is ready. A Terraform workspace run finishes late and misses the compute window. Control-M orchestrates the full chain: OCI data preparation, infrastructure provisioning, OCI VM execution, and downstream application processing.
common workflow issues
Does this sound like your week?
These aren’t edge cases. They’re the normal operating conditions for teams running OCI VM workflows across multiple tools. Here’s how Control-M handles each one.
PROVISIONING DELAY
Terraform finished late. Your OCI VM workload is still waiting.
Control-M coordinates Terraform and OCI VM jobs through explicit dependencies, releasing the VM action only after required upstream work completes successfully. Failed or delayed provisioning stops the dependent flow from advancing, preventing premature execution and reducing manual coordination.
INSTANCE STATE
The instance should be running. Your application job is already waiting.
Control-M executes OCI VM lifecycle actions and monitors their status before releasing dependent work. Start, Stop, Reset, Soft Stop, Soft Reset, Create, Get Details, and Delete become orchestrated workflow steps instead of isolated infrastructure actions.
DATA DEPENDENCY
OCI Data Integration is late. Compute starts before data is ready.
Control-M connects OCI Data Integration and OCI VM jobs in one workflow, so VM execution can wait for the required data task to complete. Complex dependencies prevent downstream processing from starting against incomplete or unavailable data.
CREDENTIAL CHANGE
An OCI API key changed. Your scheduled VM operation failed.
Control-M uses centralized OCI VM connection profiles for authorization, supporting defined authentication parameters or an Agent configuration file. Teams manage OCI endpoints and credentials separately from individual job definitions, reducing duplicated configuration and simplifying controlled credential changes.
SLA RISK
Compute started late. Your 6:00 AM service deadline is slipping.
Control-M places OCI VM operations inside the end-to-end workflow rather than monitoring infrastructure in isolation. SLA management, scheduling criteria, and cross-job dependencies give operations teams earlier visibility into delays that threaten downstream service delivery.
Control‑M + OCI VM
Control‑M + OCI VM
|
API and automation capabilities |
Automation API · Job:OCI VM · JSON job definitions · Create · Start · Stop · Reset · Soft Stop · Soft Reset · Get Details · Delete |
|
Deployment models & infrastructure flexibility |
Control-M SaaS · Control-M self-hosted · Control-M Agent · Linux Agent · Windows Agent · regional OCI endpoints |
|
Security posture |
centralized connection profiles · User OCID · Tenancy OCID · API-key fingerprint · private key · Agent configuration file · OCI regional endpoint |
|
Incident response & MTTR enablement |
status monitoring · job output · cross-job dependencies · failure containment · advanced scheduling · SLA management · workflow rerun |
end-to-end orchestration
One production workflow. Every tool in the stack.
Control-M orchestrates workflows across OCI VM, Terraform, OCI Data Integration, OCI Functions, file transfers, and cloud services in a single job flow — with dependency tracking, SLA visibility, and automated recovery across all of them.
- Cross-tool dependency: Terraform → OCI VM → application job → downstream handoff
- Data-aware triggers: file arrival, API event, OCI Data Integration completion, job result
|
OCI VM |
Create · Start · Stop · Reset · Soft Stop · Soft Reset · Get Details · Delete |
|
Terraform |
trigger workspace · pass variables · monitor run status · coordinate dependencies |
|
OCI Data Integration |
start workspace · run task · monitor status · coordinate downstream jobs |
|
OCI Functions |
invoke function · pass payload parameters · coordinate downstream processing |
|
File transfers |
managed file movement · file arrival dependencies · transfer completion |
|
Cloud services |
cross-platform dependencies · scheduling · monitoring · workflow coordination |
MONITOR WORKFLOWS
Monitor OCI VM operations in workflow context
OCI shows the state of individual compute resources, but production services depend on work before and after the VM action. Control-M brings OCI VM execution into the same operational view as surrounding application and infrastructure workflows:
-
OCI VM execution status
-
Job results and output
-
Cross-platform workflow dependencies
-
Upstream and downstream status
-
Centralized workflow monitoring
SLA ASSURANCE
Keep OCI-dependent workflows on schedule
A running OCI instance does not guarantee the business workflow will finish on time. Control-M connects OCI VM operations with scheduling, dependencies, resource controls, and SLA management so teams can manage the complete service delivery path:
-
End-to-end SLA visibility
-
Advanced scheduling criteria
-
Cross-job dependency control
-
Resource-aware workflow execution
-
Centralized failure visibility
Documentation
Bring order to complex workflows
Learn how Control-M helps teams orchestrate complex processes with greater visibility, coordination, and control.
