2/12/25, 2:49 AM

Prerequisites
You are connecting to a supported version of SAP BusinessObjects Business Intelligence platform. For information on supported versions, see System Requirements
and Technical Prerequisites.

You have completed ONE of the following setup options:

Performed setup using the SAP Analytics Cloud Agent Simple Deployment Kit. For more information, see SAP Analytics Cloud Agent Simple Deployment Kit.

Performed a manual setup of the following required components:

1. The Cloud Connector is installed. For more information, see Installing the Cloud Connector.

2. The SAP Analytics Cloud agent is installed. For more information, see Installing SAP Analytics Cloud Agent.

3. The Cloud Connector is configured. For more information, see Configuring the Cloud Connector.

4. The SAP Analytics Cloud agent is configured in SAP Analytics Cloud. For more information, see Configuring SAP Analytics Cloud Agent.

Procedure

1. From the side navigation, choose Connections (Add Connection) .

The Select a data source dialog will appear.

2. Expand Acquire Data and select SAP Universe.

3. In the New SAP Universe Connection dialog, enter the following information:

a. A name and a description for the connection.

b. In the Connection Information section, select the Location of your Cloud Connector from the list.

c. Enter a System, User Name, Password.

For the System name, enter the Central Management Server name and port: cms_machinename(:cms_port). For example, my_cms.my_company:6400.

d. Select the Authentication Type: Enterprise, LDAP, Windows AD, or SAP.

4. Choose Create.

The new connection is added to the list of connections on the Connections screen.

5. If you want to create a model based on this connection, see Import Data to Your Model.

Import Data Connection to a Google BigQuery System

How to create a connection that allows you to import models from a Google BigQuery system.

Prerequisites
You need to have a Google account that has access to a BigQuery project.

 Note
External data sources, including Google Drive, Google Cloud BigTable, and Google Cloud Storage, are not supported as a BigQuery data source. For Google Drive data, you
can choose the Google Drive data source instead.

 Note
If your SAP Analytics Cloud system is hosted on a data center located within China, this feature is not available.

Procedure

1. From the side navigation, choose Connections (Add Connection) .

The Select a data source dialog will appear.

2. Expand Acquire Data and select Google BigQuery.

You may be requested to allow offline access to your account when your device is turned off. You'll need to allow access for SAP Analytics Cloud to be able to access
your BigQuery projects.

3. In the New Google BigQuery Connection dialog, enter a name and a description for the connection.

4. Sign in to your Google BigQuery account.

 Note
If you're unable to create a connection when using Microsoft Edge, please check your Trusted Sites (Control Panel > Internet Options > Security > Trusted Sites >
Sites), and do one of the following:

Remove https://*.sapbusinessobjects.cloud/ from your Trusted Sites.

This is custom documentation. For more information, please visit SAP Help Portal. 315
 2/12/25, 2:49 AM
Or

Add about:blank and https://accounts.google.com/ to your Trusted Sites. To add about:blank, you'll need to clear the “Require server verification
(https:) for all sites in this zone” option temporarily, but you can re-enable it afterward.

You may need to restart your computer after making this change.

5. Choose a BigQuery project from the list, and then select OK.

The new connection is added to the list of connections on the Connections screen.

6. If you want to create a model based on this connection, see Import Data to Your Model.

 Note
(Beta) Select the Enable users to schedule for story publishing option if you want to let your users schedule the publishing of stories. For details on scheduling, see
Schedule a Publication.

Import Data Connection to Google Drive

How to create a connection that allows you to import models from Google Drive.

Prerequisites

You need to have access to a Google account.

 Note
If your SAP Analytics Cloud system is hosted on a data center located within China, this feature is not available.

Procedure

1. From the side navigation, choose Connections (Add Connection) .

The Select a data source dialog will appear.

2. Expand Acquire Data and select Google Drive.

3. Choose a Google account to connect to.

If your Google account doesn't appear in the list, select Use another account.

 Note
If you're unable to create a connection when using Microsoft Edge, please check your Trusted Sites (Control Panel > Internet Options > Security > Trusted Sites >
Sites), and do one of the following:

Remove https://*.sapbusinessobjects.cloud/ from your Trusted Sites.

Or

Add about:blank and https://accounts.google.com/ to your Trusted Sites. To add about:blank, you'll need to clear the “Require server verification
(https:) for all sites in this zone” option temporarily, but you can re-enable it afterward.

You may need to restart your computer after making this change.

4. In the Connect to Google Account dialog, enter a name and a description for the connection.

5. Select OK to create the connection.

The new connection is added to the list of connections on the Connections screen.

6. If you want to create a model based on this connection, see Import Data to Your Model.

 Note
Select the Enable users to schedule for story publishing option if you want to let your users schedule the publishing of stories.

Import Data Connection to OData Services

You can create a connection that allows you to import data from both on-premise and cloud data sources using generic OData services. It is possible to request a customized
OData data source solution.

Prerequisites
You have completed ONE of the following setup options:

This is custom documentation. For more information, please visit SAP Help Portal. 316
 2/12/25, 2:49 AM

 Note
This is only required for on-premise OData services.

Performed setup using the SAP Analytics Cloud Agent Simple Deployment Kit. For more information, see SAP Analytics Cloud Agent Simple Deployment Kit. You must
also perform steps 6-12 of Configuring the Cloud Connector.

Performed a manual setup of the following required components:

1. The Cloud Connector is installed. For more information, see Installing the Cloud Connector.

2. The Cloud Connector is configured. For more information, see Configuring the Cloud Connector.

The SAP Analytics Cloud agent doesn't need to be installed during the configuration process.

Context

 Note
SAP Analytics Cloud supports OData Version 4.0. Logical Operators (such as Equal, Greater than or equal, and logical Or) are supported. The Not operator (logical
negation), arithmetic operators, and arithmetic functions are not supported.

While OData exposes one-to-many navigation, SAP Analytics Cloud cannot follow these relationships because doing so would distort the measures at the parent
level. OData v4.0 supports Lambda operators “any” and “all”, which can reduce the collection of children to a single Boolean value. For this to work, both the server
and SAP Analytics Cloud must support OData v4.0.

Supported OData Authorization request formats:

Authorization Code Request

The data service must accept the token request as URL encoded.

The data service must accept an Authorization header with the client ID and client secret encoded as a base 64 string.

The data service must accept as a body parameter grant_type: authorization_code.

Scopes are optional, but if supported, the data service must accept them as a body parameter scope: <SCOPE1 SCOPE2 SCOPE3...>. The scopes are sent as
a string.

Example:

curl -X POST \
<Token URL> \
-H 'Accept: */*' \
-H 'Authorization: Basic <BASE 64 Encoded String>' \
-d grant_type=authorization_grant

-d code=<Authorization code>

-d redirect_uri=<Redirect URI>

The response must be of content type JSON, and include in the response body the following parameters as top level JSON objects: access_token,
refresh_token, and token_type. It may contain other parameters.

Example:

{
"access_token": "<ACCESS TOKEN>",

"refresh_token": <REFRESH TOKEN>",

"token_type": "Bearer",
"expires_in": 0,
"scope": ""
}

Note that if the required parameters are returned in arrays or as nested parameters, they may not be processed correctly.

Incorrect Example:

"authorization"

{
"access_token": "<ACCESS TOKEN>",

"refresh_token": <REFRESH TOKEN>",

"token_type": "Bearer",
"expires_in": 0,
"scope": ""
}
}

Client Credentials

The data service must accept the token request as URL encoded.

The data service must accept an Authorization header with the client ID and client secret encoded as a base 64 string.

This is custom documentation. For more information, please visit SAP Help Portal. 317
 2/12/25, 2:49 AM
The data service must accept as a body parameter grant_type: client_credentials.

Scopes are optional, but if supported, the data service must accept them as a body parameter scope: <SCOPE1 SCOPE2 SCOPE3...>. The scopes are sent as
a string.

Example:

curl -X POST \
<Token URL> \
-H 'Accept: */*' \
-H 'Authorization: Basic <BASE 64 Encoded String>' \
-d grant_type=client_credentials

The response must be of content type JSON, and include in the response body the following parameters as top level JSON objects: access_token, and
token_type. It may contain other parameters.

Example:

{
"access_token": "<ACCESS TOKEN>",
"token_type": "Bearer",
"expires_in": 0,
"scope": ""
}

Note that if the required parameters are returned in arrays or as nested parameters, they may not be processed correctly.

Incorrect Example:

"authorization"

{
"access_token": "<ACCESS TOKEN>",
"token_type": "Bearer",
"expires_in": 0,
"scope": ""
}
}

Basic

The data service must accept an Authorization header with the user name and password encoded as a base 64 string.

Embedded Complex types are not supported.

Procedure

1. From the side navigation, choose Connections (Add Connection) .

The Select a data source dialog will appear.

2. Expand Acquire Data and select OData Services.

3. In the New OData Services Connection dialog, enter a name for the connection.

4. Optionally, you can select the following options:

Connect to an On-Premise OData service: Make sure to complete the prerequisites before connecting to an On-Premise source using a generic OData driver. If
this option is not selected, the driver will connect to cloud OData data sources.

Connect to an SAP OData service: When you select this option, specific SAP metadata is respected. This metadata specifies default behaviors based on SAP
OData services guidelines; for example, filterable and sortable are by default true, if not claimed to be false, and support basic filter operators.

 Note
Advanced features of customized OData data sources, such as SAP Hybris Cloud for Customer and SAP Business ByDesign Analytics, are only available using
customized data source types. These features are not available using generic OData services. It is highly recommended to use the relevant customized data source
types, if available, for your data service to leverage full capability of the data connector. It is possible to request a customized OData data source solution.

5. If you are connecting to an on-premise OData service, select the Location of your Cloud Connector from the list.

6. Enter the Data Service URL published during your configuration.

 Note
You may add extra URL parameters in the Data Service URL field, to accommodate data-source-specific constraints on authentication. For example, you may pass in
the saml2=disabled parameter to disable SAML, or sap-system-login-basic_auth=X to disable custom login. All the parameters entered in the Data
Service URL field (anything following "?" in the URL) are only used in the authentication flow, and are ignored in the data queries.

To add parameters to the URL, use the & separator between parameters.

 Note

This is custom documentation. For more information, please visit SAP Help Portal. 318
 2/12/25, 2:49 AM
To successfully create a connection, a document that describes the services metadata must exist and be accessible at {the URL you enter in the Data
Service URL field}/$metadata.

7. Select the authentication type.

The following authentication types are available:

Basic Authentication

OAuth 2.0 Client Credentials

OAuth 2.0 Authorization Code

Client Certification

No Authentication

8. Provide the authentication details based on the authentication type you selected:

For Basic Authentication, enter the User Name and Password of the user you want to import data from.

For OAuth 2.0 Client Credentials, enter the OAuth Client ID, Secret, Token URL and Scope (if required) of the application you want to access.

For OAuth 2.0 Authorization Code, enter the OAuth Client ID, Secret, Token URL, Authorization URL and Scope (if required) of the application you want to
access. Before the connection is created, you will be redirected to the Authorization URL of your application where you can authorize SAP Analytics Cloud to
access your data.

For Client Certification, you must provide the X.509 certificate which contains the public/secret key certificate.

 Note
If you want to share the credential details, select the option Share these credentials when sharing this connection. Otherwise, users will need to enter their own
credentials in order to use the connection. If you don't share your credentials, users will be able to edit their credentials at any time without having to start a data
acquisition process.

9. Choose Create.

The new connection is added to the list of connections on the Connections screen.

10. If you want to create a model based on this connection, see Import Data to Your Model.

 Note
Select the Enable users to schedule for story publishing option if you want to let your users schedule the publishing of stories.

Import Data Connection to SAP Integrated Business Planning

You can create a direct OData connection that allows you to import data from SAP Integrated Business Planning.

Prerequisites
To allow SAP Analytics Cloud to import data from SAP Integrated Business Planning (IBP), you need to perform several setup steps in SAP Integrated Business Planning, like
creating a communication arrangement. For a complete list of the prerequisites in SAP Integrated Business Planning, please follow the prerequisites section described on the
SAP Integrated Business Planning documentation..

SAP Integrated Business Planning uses PKCS #12 pem file format for X.509 certificate authentication, whereas the X.509 certificate in SAP Analytics Cloud only accepts PKCS
#8 pem file. If you would like to use X.509 certificate authentication in SAP Analytics Cloud, you must convert your certificate generated in SAP Integrated Business Planning
first.

1. If the PKCS12 file is base64 encoded, decode the P12 file to a PFX using the command line (Cygwin or Git Bash must be installed first). Otherwise, skip to step 3.

base64 --decode certificate.p12 > certificate.pfx;

2. Use OpenSSL to convert to pem file:

openssl pkcs12 -in certificate.pfx -out certificate.pem -nodes

3. If the PKCS12 file is not base64 encoded, convert the certificate directly using OpenSSL:

openssl pkcs12 -in certificate.p12 -out certificate.pem -nodes

Context

 Note
While OData exposes one-to-many navigation, SAP Analytics Cloud cannot follow these relationships because doing so would distort the measures at the parent level.
OData v4.0 supports Lambda operators “any” and “all”, which can reduce the collection of children to a single Boolean value. For this to work, both the server and SAP
Analytics Cloud must support OData v4.0.

This is custom documentation. For more information, please visit SAP Help Portal. 319
 2/12/25, 2:49 AM
Procedure
1. From the side navigation, choose Connections (Add Connection) .

The Select a data source dialog will appear.

2. Expand Acquire Data and select SAP Integrated Business Planning.

3. In the New SAP Integrated Business Planning dialog, enter a name for the connection.

4. Enter the Data Service URL published during your configuration.

 Note
You may add extra url parameters in the Data Service URL field, to accommodate data-source-specific constraints on authentication. For example, you may pass in
the saml2=disabled parameter to disable SAML, or sap-system-login-basic_auth=X to disable custom login. All the parameters entered in the Data
Service URL field (anything following "?" in the url) are only used in the authentication flow, and are ignored in the data queries.

5. Select the authentication type:

Basic Authentication: authenticate using username and password credentials.

Client Certificate: authenticate using a X.509 certificate.

 Note
If you want to share the credential details, select the option Share these credentials when sharing this connection. Otherwise, users will need to enter their own
credentials in order to use the connection. If you don't share your credentials, users will be able to edit their credentials at any time without having to start a data
acquisition process.

6. Depending on the authentication method you have selected, enter your username and password in the dedicated field, or click Select File to upload your certificate.

 Note
Select the Enable users to schedule for story publishing option if you want to let your users schedule the publishing of stories.

Next Steps
You’re now ready to import data from SAP Integrated Business Planning into SAP Analytics Cloud and create models.

Import Data Connection to an SQL Database

You can create a connection that allows you to import data from an on-premise SQL database (JDBC + Freehand SQL).

Prerequisites

You have completed ONE of the following setup options:

Performed setup using the SAP Analytics Cloud Agent Simple Deployment Kit. For more information, see SAP Analytics Cloud Agent Simple Deployment Kit.

 Note
JDBC drivers must be installed using the instructions in the Post-Setup Guide included in the kit.

Performed a manual setup of the following required components:

1. The Cloud Connector is installed. For more information, see Installing the Cloud Connector.

2. The SAP Analytics Cloud agent is installed. For more information, see Installing SAP Analytics Cloud Agent.

3. JDBC drivers must be installed.

4. The Cloud Connector is configured. For more information, see Configuring the Cloud Connector.

5. The SAP Analytics Cloud agent is configured in SAP Analytics Cloud. For more information, see Configuring SAP Analytics Cloud Agent.

6. You have installed a JDBC driver. If you haven't already installed a JDBC driver, follow these steps:

a. Download JDBC drivers for the databases that you want to connect to, and then place the downloaded jar file(s) in an appropriate folder. The jar files can
be in any location on your machine as long as the properties file includes the correct file locations (see the next step). For information about supported
databases, see System Requirements and Technical Prerequisites.

 Note
You must use a Simba JDBC driver for the explicitly defined Amazon Redshift, Amazon EMR, Apache Hadoop Hive, Cloudera Impala, Apache Spark,
and Hortonworks Data Platform.

If you want to use an alternate JDBC driver (such as Amazon) for Amazon Redshift, Amazon EMR, Cloudera Impala, Apache Spark, and Hortonworks
Data Platform, please use Generic JDBC datasource.

This is custom documentation. For more information, please visit SAP Help Portal. 320