Connectors and Connections > Data Ingestion and Replication connection properties > SAP OData V2 connection properties
  

SAP OData V2 connection properties

Create an SAP OData V2 connection to securely read from or write to OData V2-compliant applications in SAP deployed in the cloud or on-premises.

Prepare for authentication

You can configure basic, API key, authorization code, and client credentials authentication types to access OData V2-compliant applications in SAP.
Before you configure the connection properties, you need to keep the authentication details handy based on the authentication type that you want to use.

Basic

To connect to SAP OData V2 services using basic authentication, you need the SAP account user name and password.
Get the required details from the SAP application to which you want to connect.
For more information about basic authentication in SAP, see Basic authentication in the SAP documentation.

Connect to SAP OData V2

Let's configure the SAP OData V2 connection properties to connect to SAP OData V2 services, and read from or write to OData V2-compliant applications in SAP.

Before you begin

Before you get started, you'll need to configure the SAP system and get the relevant configuration details from your SAP account based on the authentication type that you want to configure.
Check out Prerequisites to learn more about the configuration prerequisites.

Prerequisites

To connect to SAP OData V2 services, the SAP administrator needs to configure the SAP user account in the SAP system.
Additionally, when you configure the connection properties, you need to complete the authentication prerequisites.

Connection details

The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run tasks.
Select a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
Service Type
The service type of the OData V2 application endpoint to which you want to connect.
Select one of the following service types from the list:
  • - Default. Connects to a specific SAP service.
  • - SAP Gateway Catalog. Connects to the SAP catalog service that provides a list of all available services on SAP Gateway.
Default is Default.
Service URL
The service URL for the selected service type.
If you select the Default service type, enter the root URL of the service in the following format:
http://<Host name of the SAP server>:<Port number>/sap/opu/odata/sap/<Service name>/
For example, if you want to connect to the ZALL_DATATYPE_SRV service in SAP when the host name is http://invs15con01.informatica.com and port number is 8081, enter the following service URL:
http://<Host name of the SAP server>:<Port number>/sap/opu/odata/sap/ZALL_DATATYPE_SRV/
If you select the SAP Gateway Catalog service type, enter the service URL in the following format:
http://<Host name of the SAP server>:<Port number>/sap/opu/odata/IWFND/<Catalog service name>
For example, if you want to connect to the CATALOGSERVICE;v=2 catalog service in SAP when the host name is abcd01con02.example.com and port number is 8081, enter the following service URL:
http://abcd01con02.example.com:8081/sap/opu/odata/IWFND/CATALOGSERVICE;v=2

Authentication types

You can configure basic, API key, authorization code, and client credentials authentication types to access OData V2-compliant applications in SAP.
Select the required authentication method and then configure the authentication-specific parameters.

Use the serverless runtime environment

In Data Ingestion and Replication, you can use a serverless runtime environment hosted on Azure to connect to the SAP S4/HANA database with SAP OData V2 connector.
Before you configure a SAP OData V2 connection using the serverless runtime environment, perform the following tasks:
Add the JDBC driver as a JAR file in the Azure container in your Azure account
Perform the following steps:
  1. 1Create the following structure for the serverless agent configuration in Azure: <Supplementary file location>/serverless_agent_config/
  2. 2Add the JDBC driver files in the Azure container in the following location in your Azure account:
    3. <Supplementary file location>/serverless_agent_config/odp
Configure the .yml serverless configuration file
Perform the following steps to configure the .yml serverless configuration file in the serverless runtime environment:
  1. 1Copy the following code snippet to a text editor and specify the driver file name:
    2. version: 1
    agent:
    databaseIngestion:
    autoDeploy:
    odp:
    jdbc:
    drivers:
    - fileCopy:
    sourcePath: odp/<file_name>.jar
    where the sourcePath is the directory path of the driver files in Azure.
  2. 2Ensure that the syntax and indentations are valid, and then save the file as serverlessUserAgentConfig.yml in the following Azure location: <Supplementary file location>/serverless_agent_config
    3. When the .yml file runs, the JDBC driver files are copied from the Azure location to the following serverless agent directory: <AGENT_DIR>/ext/connectors/thirdparty/infa.odp