Skip to main content
Version: 26

SAP Cloud Connector Integration

Avantra can monitor SAP Cloud Connector (SCC) instances, giving visibility into subaccount connections, performance, memory usage, and certificate status.

Prerequisites​

To enable Avantra to monitor SAP Cloud Connector, some settings must be made in SCC.

  • If using LDAP-based user management for SAP Cloud Connector, the API user should have the role sccmonitoring. Otherwise, the default Administrator user should be used.
warning

You need to configure Basic Authentication in SCC first, then use those credentials in the steps below.

Create a SAP Cloud Connector Cloud Service in Avantra​

The next step is to create a cloud service for SAP Cloud Connector.

  1. Navigate to System > Cloud Services.
  2. Click New.
  3. Select SAP Cloud Connector from the Service Type dropdown.
  4. Define a Service.
  5. Select a Customer.
  6. Select a System Role.
  7. Click New. This creates the service.
  8. Double-click the newly created service to open its Properties panel.
  9. Under SAP Cloud Connector Info, select a Monitoring Server, as it is required for the service to work.
  10. Fill in the remaining parameters as needed, making sure to populate the SCC URL.
  11. You can tick the Trust all SSL Certificates checkbox, or, to trust only a specific certificate authority, leave it unchecked and provide an Authority Certificate instead. Without one of these, Avantra cannot communicate with the SAP Cloud Connector.
  12. Click Apply to save.

Adding the credentials​

After creating the Basic Authentication credentials in SCC, you must configure these credentials in Avantra.

  1. Click the Credentials tab.
  2. Check the Basic Auth Credentials checkbox. If left empty, a name is generated.
  3. Enter the Username and Password that you created in SCC.
  4. Click Apply to save.

Monitoring a primary/secondary (HA) pair​

If your SAP Cloud Connector is deployed in a High Availability configuration with a primary and secondary node, repeat the steps above to create a separate Cloud Service in Avantra for each node's URL. The two Cloud Services can use the same or different Basic Auth credentials, as Avantra reads the role directly from each SCC instance on every check cycle.

On the node currently acting as secondary (shadow role), only the Health Check runs normally and all other checks report an Unknown status. If the nodes fail over, there is nothing to reconfigure in Avantra, each Cloud Service's checks update automatically to reflect its node's current role on the next check cycle.

warning

Avantra retries a configured credential on every check cycle, even after SAP Cloud Connector has rejected it. If the credential doesn't match SCC, the check reports the authentication failure, but Avantra keeps attempting the same login on schedule. Depending on your SCC lockout policy, repeated failed logins can lock the user account. Correct the credential in Avantra as soon as an authentication failure is reported.