Prerequisite for using SAP Automation Pilot with Operation Automation are the following:
An end point in SAP Cloud ALM Landscape Management pointing to the SAP Automation Pilot tenant is required to request the list of commands, trigger a new executions and check the status of executions. Proceed as follows to create the endpoint:
If the Automation Pilot service is already known to Landscape Management, skip these steps and proceed directly with the end point creation. Otherwise, define the Autopilot cloud service as below:
a. Use Case: Operation Automation
b. Root Url: https://<...>.autopilot.ondemand.com (overwrite existing data if required)
c. Authentication type: Basic Authentication
d. Enter service user name including account prefix (T....) and password
6 Select Save
The registration step is required to make the relevant Automation Pilot commands known to SAP Cloud ALM for Operations as Operation Flows.
Perform the following for each Automation Pilot command that should be triggered automatically from SAP Cloud ALM for Operations.
As a result, the new Automation Pilot command will appear in the list of registered operation flows.
Operation flows of type Automation Pilot can be triggered automatically for SAP BTP events.
If the operation flow should be triggered automatically from an event, for example an alert, you need to define an event processing rule.
Input Mapping and Definition of Input References
The SAP Automation Pilot command that is triggered from SAP Cloud ALM might require a set of input values.
The following input values are transferred from the triggering SAP BTP event automatically to the SAP Automation Pilot command:
If the Automation Pilot command requires additional input values, you need to define an input in the Automation Pilot containing the required name-value pairs and register the command together with the correct input in SAP Cloud ALM