Set up SAP Analytics Cloud

To set up SAP Analytics Cloud, you need to do the following:

Warning Because these tasks are performed outside of Collibra, it is possible that the content changes without us knowing. We strongly recommend that you carefully read the source documentation.

Synchronize SAP Analytics Cloud data in SAP Datasphere Catalog

Note You need to be the System Owner of the SAP Analytics Cloud system that you want to synchronize.

  1. In SAP, on the SAP Datasphere homepage, click Catalog > Monitoring.

    The Remote Systems page opens.
  2. Above the list of systems, click +.
    The Create System dialog box appears.
  3. Enter the required information.
    FieldDescription
    System TypeThe type of system you want to synchronize. In this case, SAP Analytics Cloud.
    Name

    The system name of the SAP Analytics Cloud system you want to synchronize.

    Tip To find the system name, on the SAP Analytics Cloud homepage, click System > About. In the About dialog box, you need the value in the System Name field.
    UUID

    The system UUID of the SAP Analytics Cloud system you want to synchronize.

    Tip To find the system UUID, on the SAC homepage, click System > About. In the About dialog box, you need the value in the System UUID field.
  4. Click Authenticate Now.
    All SAP Analytics Cloud data is synchronized to SAP Datasphere.
  5. Click Create.
  6. Select the system you created and click Synchronize System.
  7. Optionally, edit the name of the system and give it a meaningful name.
    The name of the system will be the name of the SAP Tenant asset in Collibra.

Publish all SAP Analytics Cloud assets

Note You need to be a System Administrator in SAP Datasphere Catalog to perform this action.

Collibra Data Lineage can only ingest assets in SAP Datasphere Catalog that are published. Therefore, you need to ensure that all of the SAP Analytics Cloud assets in SAP Datasphere Catalog are published. You need at least one published asset for the APIs to work.

  1. In SAP, on the SAP Datasphere homepage, click Catalog > Catalog.

    The Catalog page opens.
  2. In the filters pane, click on the SAP Analytics Cloud system from which you want to ingest assets. In the following example image, the SAP Analytics Cloud system we want is named "88GRE".

  3. Ensure that all of your SAP Analytics Cloud systems have the status Published. If they are, there's nothing more to do. If they aren't, proceed to the next step.

  4. Click the Assets checkbox, to select all assets.
    Note You can only publish assets that have the functional status Current.
  5. In the Publish Actions drop-down list, click Publish.
Tip 

Configure a new OAuth client

Note You need to be an Administrator in SAP Datasphere to perform this action.

  1. In SAP, toward the bottom of the SAP Datasphere homepage, click System > Administration.

  2. Click App Integration.

  3. In the OAuth Clients section, below the Configured Clients, click Add a New OAuth Client.

    The New OAuth Client dialog box appears.
  4. Enter the required information.
    FieldDescription
    NameThe name of the new OAuth client. This can be anything, as long as it is unique.
    OAuth Client IDThe ID is generated when the OAuth client is created.
    Purpose

    In the drop-down list, select API Access.

    Access

    In the drop-down list, select Catalog User API.

    Authorization GrantIn the drop-down list, select Client Credentials.
    SecretThe secret is generated when the OAuth client is created.
    Token Lifetime

    The amount of time that the server login session remains open while Edge is communicating with SAP Datasphere Catalog.

    During the token lifetime, you need to build your Edge connection, configure your Edge capability, and start the integration. But after that, Collibra Data Lineage keeps the token alive.

    The maximum value is 1440 minutes (1 day).

  5. Click Add.

Ensure that certain endpoints are allowed

Note You need to be an Administrator in SAP Datasphere to perform this action.

Ensure that the following endpoints are allowed:

Endpoint Comments
*.hanacloud.ondemand.com  
*.k8s-hana.ondemand.com  
The token URL: <tenant>.authentication.usxx.hana.ondemand.com
Note In the URL, "uxxx" can also be "euxx".
System URL: <tenant>.usxx.hcs.cloud.sap
Note In the URL, "uxxx" can also be "euxx".