SAP Bulk Extract connection

To access your data in SAP Bulk Extract, create a connection asset for it. This connection is available for the DataStage service only.

Use SAP Bulk Extract to extract data from SAP data repositories by using SQL queries.

Supported SAP applications

  • SAP ERP 6.0 EHP6, EHP7 & EHP8
  • S/4 HANA 2020, S/4 HANA 2021, S/4 HANA 2022, S/4 HANA 2023

Prerequisite

To run the job, install the package Remote Function Module on the SAP Application server and configure the SAP user account with the necessary authorization. Install the SAP server components.

The SAP Bulk Extract connection requires the JAR file sapjco3.jar and libsapjco3.so, which can be found through the SAP Market Place.

See Importing JDBC drivers in the IBM Software Hub documentation for the procedure and required permissions to upload the JAR file to Cloud Pak for Data. Important: By default, uploading JDBC driver files is disabled and users cannot view the list of JDBC drivers in the web client. An administrator must enable users to upload or view JDBC drivers in the IBM Software Hub documentation.

The SNC support is enabled by downloading the SAP cryptographic library. To enable SNC configuration, refer to SNC configuration technote.

Create a connection to SAP Bulk Extract

To create the connection asset, you need the following connection details:

  • JAR file - sapjco3.jar & libsapjco3.so, which can be downloaded through the SAP Market Place
  • Application server - Host name or IP address of the SAP server
  • System number - SAP system number
  • SAP router - Consists of IP address and port number that describes the stations of a connection that is required between two hosts. Syntax: (/H/host/S/service/W/pass)*
  • SAP username and password (or X.509 certificate) - Username and password that is connected to the SAP server
  • Client number - SAP client number

To create an asset with the Load Balancing connection type, you need the following connection details:

  • Message server - Hot name of the SAP message server
  • Group - Group name of the SAP applications server
  • System number or ID - Name of the SAP system

To create an asset with an SNC connection type, you need the following connection details:

  • SNC name (Optional) - Specifies Client PSE or Certificate name that is generated on the client side (server tier) with respect to a partner server (SAP server).
  • SNC partner name - Specifies Server PSE or Certificate name that is generated on the SAP Server.
  • SNC QOP - Specifies the quality of protection for SNC connection. By default, QOP is set to 3. Following are the possible values of this field:
    • 1: authentication only
    • 2: integrity protection
    • 3: integrity and authentication
    • 8: default
    • 9: maximum

An RFC destination and program ID details are automatically generated by default. To specify your own destination and program ID, deselect Create RFC Destination Automatically or Auto Generate RFC Destination name.

For Credentials, you can use secrets if a vault is configured for the platform and the service supports vaults. For information, see Using secrets from vaults in connections.

Choose the method for creating a connection based on where you are in the platform

In a project
Click Assets > New asset > Prepare data > Connect to a data source. See Adding a connection to a project.

In the Platform assets catalog
Click New connection. See Adding platform connections.

In a deployment space
Click Import assets > Data access > Connection. See Adding data assets to a deployment space.

Next step: Add data assets from the connection

Federal Information Processing Standards (FIPS) compliance

This connection can be used on a FIPS-enabled cluster (FIPS tolerant); however, it is not FIPS-compliant.

Restrictions

You can use this connection only for source data. You cannot write to data or export data with this connection.

Running SQL statements

You can enter the Table Name and Condition Clauses in the stage editor to automatically generate an SQL query. To write your own query, deselect Generate SQL Query and manually provide an SQL query in the stage editor.

Migration from the traditional DataStage connector

See Migrating connections.

Parent topic: Supported connections