Create an SAP S/4HANA connection to an Edge or Collibra Cloud site

To integrate SAP S/4HANA assets, you first need to prepare Edge. The integration communicates with your SAP S/4HANA system using the Remote Function Call (RFC) protocol.

Ensure that you have completed all the prerequisites in your SAP S/4HANA and Collibra environments. Once you have created a connection, you can then proceed with metadata ingestion.

Do you use a vault?

You can use a vault to add your data source information to your Edge site connection.

Check the connection property table below to see which information is available for your vault.

Vaults are not available for Collibra Cloud sites.
No vault
AWS Secrets Manager
Azure Key Vault
CyberArk Vault
Google Secret Manager
HashiCorp Vault
  
To use your vault, do the following:
  1. In the Value Type field, select Vault Key.
  2. Enter the query value to identify the secret in your vault.
    Example 
    Note The Query must be a string containing the properties required to identify the secret. Each property must be separated by a semicolon (;). For example: Safe=<SafeName>;Folder=<FolderName>;Object=<ObjectName>

    If a property is a folder with sub-folders, use a backslash (\) to define the folder path. For example: Folder=Root\Top Secrets\More Secrets

    For more information about query formats and supported properties, go to the CyberArk Credential Provider documentation.

To use your vault, do the following:
  1. In the Value Type field, select Vault Key.
  2. Enter the required information:
    Secret Engine Type
    Select one of the following:
    • Key Value
    • Database
    Engine Path
    The engine path to your vault where the value is stored.
    Secret Path
    The secret path to your vault where the value is stored.
    Field
    If your Secret Engine Type is Key Value, enter the name of the field to your vault where the value is stored.
    Role
    If your Secret Engine Type is Database, enter the role specified in the Database engine.
    Example 

To use your vault, do the following:
  1. In the Value Type field, select Vault Key.
  2. Enter the required information:
    Vault Name
    The name of your Azure Key Vault in your Azure Key Vault service where the value is stored.
    Secret Name
    The name of the secret in your vault where the value is stored.
    Example 

To use your vault, do the following:
  1. In the Value Type field, select Vault Key.
  2. Enter the required information:
    Secret Name
    The name of the secret in your vault where the value is stored.
    Field
    If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass.
    Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field.
    Example 

To use your vault, do the following:
  1. In the Value Type field, select Vault Key.
  2. Enter the name of the secret in your vault where the value is stored.
    Example 

Prerequisites

In your Collibra environment

  • To use the SAP S/4HANA integration, you must have Collibra Platform 2026.07 or newer, and either:
    • Edge 2026.6.35 or newer
    • Edge 2026.3.126 or newer
  • You have downloaded the JDBC driver for the SAP ERP JAR file. To download the driver, go to the Driver for S/4HANA integration listing on Collibra Marketplace.
  • You either created and installed an Edge site or were granted a Collibra Cloud site.
  • You have added a vault to your Edge site.
    Note  Vaults are not supported on Collibra Cloud sites.
  • If your data source connection requires a file from your vault, the file must be encoded into Base64 and stored as a regular secret in your vault.
  • You have a global role that has the Manage connections and capabilities global permission, for example, Edge integration engineer.

In your SAP S/4HANA environment

  • The SAP Java Connector files (sapjco3.jar and libsapjco3.so) are available to upload.
  • You have a running SAP S/4HANA system.
  • An SAP user with the authorizations that the SAP S/4HANA driver needs to call its function modules and read table data. Go to the Set up SAP S/4HANA documentation for the full list of required authorizations.

Steps

  1. Open a site.
    1. On the main toolbar, click Products icon → Cogwheel icon Settings.
      The Settings page opens.
    2. In the tab pane, click Edge.
      The Sites tab opens and shows a table with an overview of your sites.
    3. In the table, click the name of the site whose status is Healthy.
      The site page opens.
  2. In the Connections section, click Create connection.
    The Create connection page appears.
  3. Select the SAP S/4HANA connection to connect to SAP S/4HANA.
  4. Enter the required information.
    FieldDescriptionRequiredAvailable for vaults?
    Name

    The name of the Edge or Collibra Cloud site connection for SAP S/4HANA.

    		 Yes No
    Description

    The description of the connection.

    		 No No
    Vault The vault where you store your data source values. No No
    Driver jarUpload the SAP ERP JAR file from the JDBC driver you downloaded. To download the driver, go to the Driver for S/4HANA integration listing on Collibra Marketplace. Yes No
    Driver class nameThe fully qualified name of the JDBC driver: cdata.jdbc.saperp.SAPERPDriver. This is available by default. Yes No
    Username

    The username of the SAP S/4HANA user to be used for basic authentication.

    		 Yes Yes
    Password

    The password of the SAP S/4HANA user to be used for basic authentication.

    		 Yes Yes
    SAP Java Connector

    The SAP Java Connector JAR file sapjco3.jar required by the SAP S/4HANA driver. Click Upload to upload the JAR file.

    The SAP S/4HANA connection requires the SAP Java Connector (JCo) files sapjco3.jar and the native library libsapjco3.so. SAP provides these files. Edge runs on Red Hat Linux, so you can download the Linux on x86_64 64bit version.

    To download the SAP Java Connector files:

    1. Go to the SAP Software Center. You will need your SAP credentials to log in.
    2. Click the Support Packages & Patches tab.
    3. Find SAP JCo in one of the following ways:
      • In By Alphabetical Index (A-Z), click J, and then click the SAP JCO entry.
      • In By Category, click SAP Connectors, and then click SAP JCO.
    4. Select the listed SAP JCO version.
    5. In the platform dropdown list, select Linux on x86_64 64bit.
    6. Download the package, for example sapjco31P_13-70004517.zip.
    7. Extract the archive. It contains sapjco3.jar and libsapjco3.so.
    		 Yes No
    SAP Java Connector native libraryThe SAP Java Connector native library libsapjco3.so required by the SAP S/4HANA driver.

    Click Upload to upload the Shared Object file.

    The SAP S/4HANA connection requires the SAP Java Connector (JCo) files sapjco3.jar and the native library libsapjco3.so. SAP provides these files. Edge runs on Red Hat Linux, so you can download the Linux on x86_64 64bit version.

    To download the SAP Java Connector files:

    1. Go to the SAP Software Center. You will need your SAP credentials to log in.
    2. Click the Support Packages & Patches tab.
    3. Find SAP JCo in one of the following ways:
      • In By Alphabetical Index (A-Z), click J, and then click the SAP JCO entry.
      • In By Category, click SAP Connectors, and then click SAP JCO.
    4. Select the listed SAP JCO version.
    5. In the platform dropdown list, select Linux on x86_64 64bit.
    6. Download the package, for example sapjco31P_13-70004517.zip.
    7. Extract the archive. It contains sapjco3.jar and libsapjco3.so.
    		 Yes No
    Connection string

    Enter the JDBC connection string.

    • You can either:
      • Include all parameters inline, for example jdbc:saperp:ConnectionType=JCo;Host=saps4hana1.example.net;SystemNumber=02;Client=101
      • Or, provide the base jdbc:saperp: for SAP S/4HANA and add the parameters as individual properties in the Property field.

    To also profile, classify, and request sample data, add the following parameters to the connection string above:

    • TableMode=All: This makes all table types, including views, visible to the driver. By default, only transparent tables are visible. Additionally, this setting doesn't affect the table filtering configured in the integration settings; metadata ingestion uses the table filtering mode specified there.
    • Other='CustomizedDefaultCatalogName=S4HANA;CustomizedDefaultSchemaName=S4HANA;': This matches the profiling, classification, and sampling results to the Database and Schema assets created during SAP S/4HANA ingestion. Without this parameter, the driver uses its default Database and Schema names, which don't match the asset names that the integration created during ingestion.
    • By default, classification and sampling use the first N rows returned by the data source. Profiling processes all rows by default. To limit profiling to a specific number of rows, add MaxRows=<number> to the connection string, for example MaxRows=1000. Like the TableMode parameter, the MaxRows parameter only affects profiling and not metadata ingestion.

    Example jdbc:saperp:ConnectionType=JCo;Host=saps4hana1.example.net;SystemNumber=02;Client=101;Other='CustomizedDefaultCatalogName=S4HANA;CustomizedDefaultSchemaName=S4HANA;';MaxRows=1000;TableMode=All

    		 Yes Yes
    Property

    If you entered only the base jdbc:saperp: in the Connection string field, add the connection parameters in the Property field as a Name and Value pair. For example:

    • Name: ConnectionType; Value: JCo
    • Name: Host; Value: saps4hana1.example.net
    • Name: SystemNumber; Value: 02
    • Name: Client; Value: 101

    No

    		 Yes
  5. Click Create.
    The connection is added to the Edge or Collibra Cloud site.

What's next

You can now add the SAP S/4HANA capability to an Edge or Collibra Cloud site.