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. Only basic authentication is applicable for Data Ingestion and Replication.
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 get information from your SAP account based on the authentication type that you want to configure.
Check out Prepare for authentication to learn more about 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.
Type
SAP OData V2
Runtime Environment
The name of the runtime environment where you want to run tasks.
Select a Secure Agent.
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. Only basic authentication is applicable for Data Ingestion and Replication.
Select the required authentication method and then configure the authentication-specific parameters.

Related links

Configure the load balancing connection

You can use basic authentication type in the SAP OData V2 connection to create a load balancing connection when you connect to the SAP server.
When you configure a connection for load balancing, you can connect to the SAP server with the least load at run time. This feature is not applicable for Data Ingestion and Replication.
Before you configure an SAP OData V2 connection that uses basic authentication type for a load balancing connection, you need to perform the prerequisite tasks.
  1. 1Import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation:
  2. Ensure to add the certificate to all the available directories.
  3. 2If there is a jdk directory within the <Secure agent installation directory>\apps folder, navigate to the following directory and import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation:
  4. 3Restart the Secure Agent.

Proxy server settings

If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica Intelligent Cloud Services through the proxy server.
You can configure the Secure Agent to use the proxy server on Windows and Linux. You can use the unauthenticated or authenticated proxy server.
Proxy settings is not applicable for Data Ingestion and Replication.
To configure the proxy settings for the Secure Agent, perform the following tasks: