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, seeNetwork connectivity.
    • Grant theroles/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. The connector and the service account must belong to the same project. For more information, seeCreating a service account.

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

      To understand how to enable services, seeEnabling 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, seeQuickstart with SAP HANAFor more information about SAP HANA, seeSAP HANA platform overview

Configure the connector

A connection is specific to a data source. Itmeans that if you have many data sources, you must create a separate connectionfor each data source. To create a connection, do the following:

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

    Go to the Connections page

  2. Click+ CREATE NEW to open theCreate Connection page.
  3. In theLocation 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, seeLocations.

    2. ClickNEXT.
  4. In theConnection Details section, complete the following:
    1. Connector: SelectSAP 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 theConnection 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 aDescription for the connection instance.
    5. Optionally, enableCloud logging, and then select a log level. By default, the log level is set toError.
    6. Service Account: Select a service account that has therequired roles.
    7. Optionally, configure theConnection 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. Note: You can customize the connection node values only if you are a Pay-as-you-go customer.
    9. Database: The name of the SAP HANA database.
    10. BrowsableSchemas: This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
    11. Include System Objects: Set IncludeSystemObjects to True to fetch Hana System schema and tables.
    12. Include Table Types: If set to true, the provider will report the types of individual tables and views.
    13. Session Variables: A comma-separated list of session variables to set on the current connection.
    14. Optionally, click+ ADD LABEL to add a label to the Connection in the form of a key/value pair.
    15. ClickNEXT.
  5. In theDestinations section, enter details of the remote host (backend system) you want to connect to.
    1. Destination Type: Select aDestination Type.

      If you want to establish a public connection to your backend systems with additional security, you can considerconfiguring 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. ClickNEXT.
  6. In theAuthentication section, enter the authentication details.
    1. Select anAuthentication 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, seeConfigure authentication.

    3. ClickNEXT.
  7. Review: Review your connection and authentication details.
  8. ClickCreate.

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 nameDetails
Locationus-central1
ConnectorSAP HANA
Connector version1
Connection Namesap-hana-db-conn
Enable Cloud LoggingYes
Service AccountSERVICE_ACCOUNT_NAME@serviceaccount
DatabaseS19
BrowsableSchemasGOOGLEUSER
Include Table TypeYes
Enable Verbose Logging5
Minimum number of nodes2
Maximum number of nodes50
Destination TypeHost address
host 1192.0.2.0/24
port 131015
UsernameUser name
Passwordpassword
Secret version1

Entities, operations, and actions

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

Note: You can view the entities, operations, and actions of a connector in theConnectors task.
  • Entity:An entity can be thought of as an object, or a collection of properties, in theconnected 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 theEntities list will be empty.

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

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

  • Action:An action is a first class function that is made available to the integrationthrough 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 theActions list will be empty.
Note:All entities and actions will have a schema associated with them. For example, an action schema will have the parameter details such as; the parameternames, and its corresponding data type. The schema (metadata) for entities and actions is fetched by the connection atruntime from your backend. If there are any updates to the schema, such updates won't be automatically reflected in your existing connections; you must manually refresh the schema. To refreshthe schema for a connection, open theConnection details page of the connection, and then clickRefresh connection schema.

Actions

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

EMPLOYEE_PROCEDURE_HANA action

This action returns data of an Id.

Input parameters of the EMPLOYEE_PROCEDURE_HANA action

Parameter NameData TypeRequiredDescription
IDIntegerTrueType ID which need to passed in procedure

For example on how to configure theEMPLOYEE_PROCEDURE_HANA action,seeExamples.

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 NameData TypeRequiredDescription
queryStringTrueQuery string that needs to be executed.
queryParametersArray, NullTrueQuery parameters to be passed in order.
maxRowsNumber, NullFalseMaximum number of rows to be returned.
timeoutNumber, NullFalseNumber of seconds to wait for the query execution.

For example on how to configure theExecuteCustomQuery action,seeExamples.

Action examples

Example - EMPLOYEE_PROCEDURE_HANA

  1. In theConfigure connector task dialog, clickActions.
  2. Select theEMPLOYEE_PROCEDURE_HANA action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"ID":1}
  4. If the action is successful, theEMPLOYEE_PROCEDURE_HANA task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT CUSTOMER.COMPANY, SUM(ORDERS.AMOUNT) AS TotalFROM ORDERSINNER JOIN CUSTOMERON ORDERS.CUSTOMER_ID = CUSTOMER.IDGROUP BY CUSTOMER.COMPANY"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT ID, NAME, AGE, AMOUNT FROM CUSTOMERS JOIN ORDERS ON CUSTOMERS.ID = ORDERS.CUSTOMER_ID"  }]}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT COUNT(ID), CITY FROM GCP_HANA_CUSTOM GROUP BY CITY HAVING COUNT(ID) > 1"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

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

Example - ExecuteCustomQuery GroupBy

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault 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, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault 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, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "INSERT INTO CUSTOMER VALUES (3, 'IBM India')"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery SUM_AggFunc

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT SUM(SALARY) FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

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

Example - ExecuteCustomQuery AVG_AggFunc

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT AVG(SALARY) FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

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

Example - ExecuteCustomQuery MAX_AggFunc

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT MAX(SALARY) FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

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

Example - ExecuteCustomQuery MIN_AggFunc

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT MIN(SALARY) FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{"MIN_SALARY": 1500.0}]

Example - ExecuteCustomQuery COUNT_AggFunc

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT COUNT(*) FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

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

Example - ExecuteCustomQuery CreateTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "CREATE TABLE CUSTOMER (ID INT NOT NULL,COMPANY VARCHAR (20))"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery AlterTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "ALTER TABLE GCP_HANA_CUSTOM ADD CONSTRAINT test PRIMARY KEY (ID)"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery TruncateTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "TRUNCATE TABLE GCP_HANA_RENAME"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery DropTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "DROP TABLE GCP_HANA_DROP"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery RenameTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "RENAME TABLE GCP_HANA_CUSTOM1 TO GCP_HANA_RENAME"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery UpdateTable

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "UPDATE CUSTOMERS SET ADDRESS = 'Pune' WHERE ID = 3"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - ExecuteCustomQuery SELECT_DATA_Table

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "SELECT * FROM CUSTOMERS"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter 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 theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query": "DELETE FROM CUSTOMERS WHERE ID = 3"}
  4. If the action is successful, theExecuteCustomQuery task'sconnectorOutputPayload responseparameter will have a value similar to the following:

    [{}]

Example - Insert a JSON array into a DB

To bulk insert data from a JSON array into a SAP HANA database table you can use one of the following methods:

Use a custom query with JSON table

Use theExecute Custom Query feature combined with a SAP HANAJSON_TABLE function. This method uses a single query to parse a JSON array and insert all records simultaneously.

To perform a bulk insert with a custom query, do the following:

  1. Transform your source data into a single JSON string. For example:
    '[ {"id": 701, "name": "Laptop", "email": "EMAIL_ADDRESS"},{"id": 702, "name": "Keyboard", "email": "EMAIL_ADDRESS"}]'
  2. Select the actionExecute Custom Query.
  3. Use anINSERT statement that uses theJSON_TABLE function to parse the input string. For example:
    INSERT INTO YOUR_TABLE_NAME (ID, NAME, EMAIL)SELECT    ID,    NAME,    EMAILFROMJSON_TABLE(?, '$[*]'    COLUMNS (        ID INT PATH '$.id',        NAME NVARCHAR(100) PATH '$.name',        EMAIL NVARCHAR(100) PATH '$.email'    )) AS jt;
  4. Map the Integration variable containing your JSON string to the single bind parameter?.
  5. Execute the query and verify the success of the operation.

Use a For Each Loop task

This method uses Application Integration to loop through the JSON array. For each JSON object in the array, it calls a sub-integration that performs a singleINSERT operation. The iteration happens within the integration itself.

  1. Go to theIntegration and create aFor Each Loop task.
  2. Locate theList to iterate field and assign your input JSON array variable to this field. The loop will now iterate over each object within this array.
  3. UnderSub-integration details, provide theSub-integration name and theAPI trigger ID of the sub-integration you want to call for each iteration.
  4. In theExecution Task section, provide aSub-integration variable name.
  5. In theSub-integration, use anExecute Custom Query or a pre-configured entity configuration to perform theINSERT operation using the data from the incoming JSON object.

Use a stored procedure

This method uses your database to handle looping and insertion. You must create a stored procedure in SAP HANA that can parse a JSON array and insert the data, and then you can use a connectors task in Application Integration to call the procedure and pass the entire JSON array to it.

To use a stored procedure for bulk insertion, do the following:

  1. Create a stored procedure in your SAP HANA database that can parse a JSON array and insert the data.
          {        CREATE PROCEDURE "YOUR_SCHEMA"."SP_INSERT_FROM_JSON" (            IN JSON_STRING CLOB        )        LANGUAGE SQLSCRIPT        SQL SECURITY INVOKER        DEFAULT SCHEMA "YOUR_SCHEMA"        AS        BEGIN            -- Parse JSON string using JSON_TABLE and insert directly into target table            INSERT INTO "YOUR_SCHEMA"."YOUR_TABLE" (ID, NAME, GRADE)            SELECT ID, NAME, GRADE            FROM JSON_TABLE(:JSON_STRING, '$[*]'                COLUMNS (                    ID   INT PATH '$.ID',                    NAME NVARCHAR(100) PATH '$.NAME',                    GRADE FLOAT PATH '$.GRADE'                )            );        END;        }
  2. Use theConnectors task in Application Integration to call the procedure and pass the entire JSON array to it. In theConfigure connector task dialog, clickActions.
  3. Select the created procedure, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a JSON data value similar to the following in theDefault Value field:
          [        { "ID": 1, "NAME": "Alice", "GRADE": 11.11 },        { "ID": 2, "NAME": "Bob", "GRADE": 22.22 }      ]
  5. If the action is successful, the data will be inserted into the database with the response code of200.

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 theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theList operation, and then clickDone.
  4. Optionally, inTask Input section of theConnectors task, you can filter your result set by specifying afilter 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 theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theGet operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickEntityId and then enter12294 in theDefault Value field.

    Here,12294 is a primary key value in theEmployee entity.

Example - Create a record inHana_unicode

This example creates a record in theHana_unicode entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectHana_unicode from theEntity list.
  3. Select theCreate operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"ID":2.0,"UNICODEDATA":"Unicode データ型はグローバル化されたデータの保存に使用されます","TEST":"Test7"}

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

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

Example - Create a record inLanguages

This example creates a record in theLanguages entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectLanguages from theEntity list.
  3. Select theCreate operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"ID":5,"ARABICTEXT":"مرحبا","GERMANTEXT":"Günther","HINDITEXT":"नमस्ते","ENGLISHTEST":"Test1"}

    If the integration is successful, your connector task'sconnectorOutputPayload 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 theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theUpdate operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"SALARY":9000.0}
  5. ClickentityId, and then enter12294 in theDefault Value field.

    If the integration is successful, your connector task'sconnectorOutputPayload 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 theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theDelete operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickentityId and then enter10001 in theDefault Value field.
Note:If your entity has a composite primary key, you can specify afilter clause.

Create connections using Terraform

You can use theTerraformresource to create a new connection.

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

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

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

Parameter nameData typeRequiredDescription
databaseSTRINGFalseThe name of the SAP HANA database.
browsable_schemasSTRINGFalseThis property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
include_system_objectsBOOLEANFalseSet IncludeSystemObjects to True to fetch Hana System schema and tables.
include_table_typesBOOLEANFalseIf set to true, the provider will report the types of individual tables and views.
session_variablesSTRINGFalseA comma-separated list of session variables to set on the current connection.
enable_loggingENUMFalseEnables 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 bothApigee Integration and Application Integration. You can use the connectionin an integration through the Connectors task.

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

Get help from the Google Cloud community

You can post your questions and discuss this connector in the Google Cloudcommunity atCloud Forums.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.