SAP HANA

The SAP Hana connector lets you perform insert, delete, update, and read operations on SAP Hana database.

Supported versions

SAP HANA version 2.0 SPS04 and later

Before you begin

Before using the SAP Hana connector, do the following tasks:

  • In your Google Cloud project:
    • Ensure that network connectivity is set up. For information about network patterns, see Network connectivity.
    • Grant the roles/connectors.admin IAM role to the user configuring the connector.
    • Grant the following IAM roles to the service account that you want to use for the connector:
      • roles/secretmanager.viewer
      • roles/secretmanager.secretAccessor

      A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. For more information, see Creating a service account.

    • Enable the following services:
      • secretmanager.googleapis.com (Secret Manager API)
      • connectors.googleapis.com (Connectors API)

      To understand how to enable services, see Enabling services.

    If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.

For information about creating a SAP HANA database, see Quickstart with SAP HANA For more information about SAP HANA, see SAP HANA platform overview

Configure the connector

Configuring the connector requires you to create a connection to your data source (backend system). A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following steps:

  1. In the Cloud console, go to the Integration Connectors > Connections page and then select or create a Google Cloud project.

    Go to the Connections page

  2. Click + CREATE NEW to open the Create Connection page.
  3. In the Location section, choose the location for the connection.
    1. Region: Select a location from the drop-down list.

      For the list of all the supported regions, see Locations.

    2. Click NEXT.
  4. In the Connection Details section, complete the following:
    1. Connector: Select SAP Hana from the drop down list of available Connectors.
    2. Connector version: Select the Connector version from the drop down list of available versions.
    3. In the Connection Name field, enter a name for the Connection instance.

      Connection names must meet the following criteria:

      • Connection names can use letters, numbers, or hyphens.
      • Letters must be lower-case.
      • Connection names must begin with a letter and end with a letter or number.
      • Connection names cannot exceed 49 characters.
    4. Optionally, enter a Description for the connection instance.
    5. Optionally, enable Cloud logging, and then select a log level. By default, the log level is set to Error.
    6. Service Account: Select a service account that has the required roles.
    7. Optionally, configure the Connection node settings:

      • Minimum number of nodes: Enter the minimum number of connection nodes.
      • Maximum number of nodes: Enter the maximum number of connection nodes.

      A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.

    8. Database: The name of the SAP HANA database.
    9. BrowsableSchemas: This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
    10. Include System Objects: Set IncludeSystemObjects to True to fetch Hana System schema and tables.
    11. Include Table Types: If set to true, the provider will report the types of individual tables and views.
    12. Session Variables: A comma-separated list of session variables to set on the current connection.
    13. Optionally, click + ADD LABEL to add a label to the Connection in the form of a key/value pair.
    14. Click NEXT.
  5. In the Destinations section, enter details of the remote host (backend system) you want to connect to.
    1. Destination Type: Select a Destination Type.
      • Select Host address from the list to specify the hostname or IP address of the destination.
      • If you want to establish a private connection to your backend systems, select Endpoint attachment from the list, and then select the required endpoint attachment from the Endpoint Attachment list.

      If you want to establish a public connection to your backend systems with additional security, you can consider configuring static outbound IP addresses for your connections, and then configure your firewall rules to allowlist only the specific static IP addresses.

      To enter additional destinations, click +ADD DESTINATION.

    2. Click NEXT.
  6. In the Authentication section, enter the authentication details.
    1. Select an Authentication type and enter the relevant details.

      The following authentication types are supported by the SAP Hana connection:

      • Username and password
    2. To understand how to configure these authentication types, see Configure authentication.

    3. Click NEXT.
  7. Review: Review your connection and authentication details.
  8. Click Create.

Configure authentication

Enter the details based on the authentication you want to use.

  • Username and password
    • Username: Username for connector
    • Password: Secret Manager Secret containing the password associated with the connector.

Basic authentication connection type

The following table lists the sample configuration values for the basic authentication connection type. Refer to the connection creation interface in the console to know the mandatory and optional fields.

Field name Details
Location us-central1
Connector SAP HANA
Connector version 1
Connection Name sap-hana-db-conn
Enable Cloud Logging Yes
Service Account SERVICE_ACCOUNT_NAME@serviceaccount
Database S19
BrowsableSchemas GOOGLEUSER
Include Table Type Yes
Enable Verbose Logging 5
Minimum number of nodes 2
Maximum number of nodes 50
Destination Type Host address
host 1 192.0.2.0/24
port 1 31015
Username User name
Password password
Secret version 1

Entities, operations, and actions

All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.

  • Entity: An entity can be thought of as an object, or a collection of properties, in the connected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.

    However, it is possible that a connector doesn't support or have any entities, in which case the Entities list will be empty.

  • Operation: An operation is the activity that you can perform on an entity. You can perform any of the following operations on an entity:

    Selecting an entity from the available list, generates a list of operations available for the entity. For a detailed description of the operations, see the Connectors task's entity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in the Operations list.

  • Action: An action is a first class function that is made available to the integration through the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case the Actions list will be empty.

Actions

This section lists the actions supported by the connector. To understand how to configure the actions, see Action examples.

EMPLOYEE_PROCEDURE_HANA action

This action returns data of an Id.

Input parameters of the EMPLOYEE_PROCEDURE_HANA action

Parameter Name Data Type Required Description
ID Integer True Type ID which need to passed in procedure

For example on how to configure the EMPLOYEE_PROCEDURE_HANA action, see Examples.

ExecuteCustomQuery action

This action allows you to perform specific tasks. For example, HANADB enables you to execute a custom SQL query.

Input parameters of the ExecuteCustomQuery action

Parameter Name Data Type Required Description
query String True Query string that needs to be executed.
queryParameters Array, Null True Query parameters to be passed in order.
maxRows Number, Null False Maximum number of rows to be returned.
timeout Number, Null False Number of seconds to wait for the query execution.

For example on how to configure the ExecuteCustomQuery action, see Examples.

Action examples

Example - EMPLOYEE_PROCEDURE_HANA

  1. In the Configure connector task dialog, click Actions.
  2. Select the EMPLOYEE_PROCEDURE_HANA action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "ID":1
    }
    
  4. If the action is successful, the EMPLOYEE_PROCEDURE_HANA task's connectorOutputPayload response parameter will have a value similar to the following:

     [{
    "EMP_ID": 1.0,
    "NAME": "Komal",
    "CITY": "UP",
    "SALARY": 7500.0,
    "DEPARTMENT": "IT" 
    }]
    

Example - ExecuteCustomQuery Join_GroupBy

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT CUSTOMER.COMPANY, SUM(ORDERS.AMOUNT) AS Total
    FROM ORDERS
    INNER JOIN CUSTOMER
    ON ORDERS.CUSTOMER_ID = CUSTOMER.ID
    GROUP BY CUSTOMER.COMPANY"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    "COMPANY": "google India",
    "TOTAL": 1560.0
    },{
    "COMPANY": "IBM India",
    "TOTAL": 4500.0
    }]
    

Example - ExecuteCustomQuery Join

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT ID, NAME, AGE, AMOUNT FROM CUSTOMERS JOIN ORDERS ON CUSTOMERS.ID = ORDERS.CUSTOMER_ID"
      }]
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
      "ID": 3.0,
      "NAME": "Kaushik",
      "AGE": 23.0,
      "AMOUNT": 3000.0
    }, {
      "ID": 3.0,
      "NAME": "Kaushik",
      "AGE": 23.0,
      "AMOUNT": 1500.0
    }, {
      "ID": 2.0,
      "NAME": "Khilan",
      "AGE": 25.0,
      "AMOUNT": 1560.0
    }, {
      "ID": 4.0,
      "NAME": "Chaitali",
      "AGE": 25.0,
      "AMOUNT": 2060.0
    }]
    

Example - ExecuteCustomQuery Groupby_Having_Count

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT COUNT(ID), CITY FROM GCP_HANA_CUSTOM GROUP BY CITY HAVING COUNT(ID) > 1"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

     [{
      "COUNT(ID)": 2.0,
      "CITY": "Delhi"
    }] 
    

Example - ExecuteCustomQuery GroupBy

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT COUNT(ID), CITY FROM GCP_HANA_CUSTOM GROUP BY CITY"
    }
    
  4. This example will update the ExecuteCustomQuery records. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
      "COUNT(ID)": 1.0,
      "CITY": "Kolkata"
    }, {
      "COUNT(ID)": 1.0,
      "CITY": "Katihar"
    }, {
      "COUNT(ID)": 1.0,
      "CITY": "Bangalore"
    }, {
      "COUNT(ID)": 2.0,
      "CITY": "Delhi"
    }]
    

Example - ExecuteCustomQuery GroupBy_OrderBy

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT COUNT(ID), CITY FROM GCP_HANA_CUSTOM GROUP BY CITY ORDER BY COUNT(ID) DESC"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
      "COUNT(ID)": 2.0,
      "CITY": "Delhi"
    }, {
      "COUNT(ID)": 1.0,
      "CITY": "Kolkata"
    }, {
      "COUNT(ID)": 1.0,
      "CITY": "Bangalore"
    }, {
      "COUNT(ID)": 1.0,
      "CITY": "Katihar"
    }]
    

Example - ExecuteCustomQuery Insert_Table

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "INSERT INTO CUSTOMER VALUES (3, 'IBM India')"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery SUM_AggFunc

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT SUM(SALARY) FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

     [{
    "SUM(SALARY)": 12000.0
    }] 
    

Example - ExecuteCustomQuery AVG_AggFunc

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT AVG(SALARY) FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    "AVG(SALARY)": 3000.0
    }] 
    

Example - ExecuteCustomQuery MAX_AggFunc

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT MAX(SALARY) FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

     [{
    "MAX(SALARY)": 6500.0
    }] 
    

Example - ExecuteCustomQuery MIN_AggFunc

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT MIN(SALARY) FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    "MIN_SALARY": 1500.0
    }]
    

Example - ExecuteCustomQuery COUNT_AggFunc

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT COUNT(*) FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    "COUNT(*)": 4.0
    }]
    

Example - ExecuteCustomQuery CreateTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "CREATE TABLE CUSTOMER (ID INT NOT NULL,COMPANY VARCHAR (20))"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery AlterTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "ALTER TABLE GCP_HANA_CUSTOM ADD CONSTRAINT test PRIMARY KEY (ID)"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery TruncateTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "TRUNCATE TABLE GCP_HANA_RENAME"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery DropTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "DROP TABLE GCP_HANA_DROP"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery RenameTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "RENAME TABLE GCP_HANA_CUSTOM1 TO GCP_HANA_RENAME"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery UpdateTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "UPDATE CUSTOMERS SET ADDRESS = 'Pune' WHERE ID = 3"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Example - ExecuteCustomQuery SELECT_DATA_Table

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "SELECT * FROM CUSTOMERS"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
      "ID": 1.0,
      "NAME": "Ramesh",
      "AGE": 32.0,
      "ADDRESS": "Ahmedabad",
      "SALARY": 2000.0
    }, {
      "ID": 2.0,
      "NAME": "Khilan",
      "AGE": 25.0,
      "ADDRESS": "Delhi",
      "SALARY": 1500.0
    }, {
      "ID": 4.0,
      "NAME": "Chaitali",
      "AGE": 25.0,
      "ADDRESS": "Mumbai",
      "SALARY": 6500.0
    }]
    

Example - ExecuteCustomQuery DeleteTable

  1. In the Configure connector task dialog, click Actions.
  2. Select the ExecuteCustomQuery action, and then click Done.
  3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "query": "DELETE FROM CUSTOMERS WHERE ID = 3"
    }
    
  4. If the action is successful, the ExecuteCustomQuery task's connectorOutputPayload response parameter will have a value similar to the following:

    [{
    }]
    

Entity operation examples

This section shows how to perform some of the entity operations in this connector.

Example - List all the employees

This example lists all the employees in the Employee entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Employee from the Entity list.
  3. Select the List operation, and then click Done.
  4. Optionally, in Task Input section of the Connectors task, you can filter your result set by specifying a filter clause. Specify the filter clause value always within the single quotes ('). For example, City='Bangalore'. You can also specify multiple filter conditions by using the logic operators. For example, City='Bangalore' and region='asia-south2'.

Example - Get a record

This example gets a record with the specified ID from the Employee entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Employee from the Entity list.
  3. Select the Get operation, and then click Done.
  4. In the Task Input section of the Connectors task, click EntityId and then enter 12294 in the Default Value field.

    Here, 12294 is a primary key value in the Employee entity.

Example - Create a record in Hana_unicode

This example creates a record in the Hana_unicode entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Hana_unicode from the Entity list.
  3. Select the Create operation, and then click Done.
  4. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "ID": 2.0,
    "UNICODEDATA": "Unicode データ型はグローバル化されたデータの保存に使用されます",
    "TEST": "Test7"
    }

    If the integration is successful, your connector task's connectorOutputPayload field will have a value similar to the following:

    {
    "ID": 2.0,
    "UNICODEDATA": "Unicode データ型はグローバル化されたデータの保存に使用されます",
    "TEST": "Test7"
    }

Example - Create a record in Languages

This example creates a record in the Languages entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Languages from the Entity list.
  3. Select the Create operation, and then click Done.
  4. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "ID": 5,
    "ARABICTEXT": "مرحبا",
    "GERMANTEXT": "Günther",
    "HINDITEXT": "नमस्ते",
    "ENGLISHTEST": "Test1"
    }

    If the integration is successful, your connector task's connectorOutputPayload field will have a value similar to the following:

    {
    "ID": 5.0,
    "ARABICTEXT": "مرحبا",
    "GERMANTEXT": "Günther",
    "HINDITEXT": "नमस्ते",
    "ENGLISHTEST": "Test1"
    }

Example - Update a record

This example updates a record in the Employee entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Employee from the Entity list.
  3. Select the Update operation, and then click Done.
  4. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
    {
    "SALARY": 9000.0
    }
  5. Click entityId, and then enter 12294 in the Default Value field.

    If the integration is successful, your connector task's connectorOutputPayload field will have a value similar to the following:

    {
    "SALARY": 9000.0
    }

Example - Delete a record

This example deletes the record with the specified ID in the Employee entity.

  1. In the Configure connector task dialog, click Entities.
  2. Select Employee from the Entity list.
  3. Select the Delete operation, and then click Done.
  4. In the Task Input section of the Connectors task, click entityId and then enter 10001 in the Default Value field.

Use terraform to create connections

You can use the Terraform resource to create a new connection.

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

To view a sample terraform template for connection creation, see sample template.

When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:

Parameter name Data type Required Description
database STRING False The name of the SAP HANA database.
browsable_schemas STRING False This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
include_system_objects BOOLEAN False Set IncludeSystemObjects to True to fetch Hana System schema and tables.
include_table_types BOOLEAN False If set to true, the provider will report the types of individual tables and views.
session_variables STRING False A comma-separated list of session variables to set on the current connection.
enable_logging ENUM False Enables verbosity for logging during a connection by selecting a level between 1 (least verbose) and 5 (most verbose). This feature can aid in troubleshooting error messages or other unexpected behavior. However, please be aware that this option will log all communication details, including requests, responses, and SSL certificates, between the connector and backend. Therefore, it is not advisable to utilize this function in a live production environment. Supported values are: 1, 2, 3, 4, 5

Use the SAP Hana connection in an integration

After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.

  • To understand how to create and use the Connectors task in Apigee Integration, see Connectors task.
  • To understand how to create and use the Connectors task in Application Integration, see Connectors task.

Get help from the Google Cloud community

You can post your questions and discuss this connector in the Google Cloud community at Cloud Forums.

What's next