Connect to SAP Ariba Procurement Data and Transfer Data in Talend

This article shows how you can easily integrate the CData JDBC driver for SAP Ariba Procurement into your workflow in Talend. This article uses the CData JDBC Driver for SAP Ariba Procurement to transfer SAP Ariba Procurement data in a job flow in Talend.

Connect to SAP Ariba Procurement in Talend as a JDBC Data Source

You can follow the procedure below to establish a JDBC connection to SAP Ariba Procurement:

1. Add a new database connection to SAP Ariba Procurement data: To add a new connection, expand the Metadata node, right-click the Db Connections node, and then click Create Connection.
2. In the resulting wizard, enter a name for the connection.

3. On the next page, select Generic JDBC from the DB Type menu and enter the JDBC URL.

   In order to connect with SAP Ariba Procurement, set the following:

   • ANID: Your Ariba Network ID.
   • ANID: Specify which API you would like the provider to retrieve SAP Ariba data from. Select the Buyer or Supplier API based on your business role (possible values are PurchaseOrdersBuyerAPIV1 or PurchaseOrdersSupplierAPIV1).
   • Environment: Indicate whether you are connecting to a test or production environment (possible values are TEST or PRODUCTION).

   Authenticating with OAuth

   After setting connection properties, you need to configure OAuth connectivity to authenticate.

   • Set AuthScheme to OAuthClient.
   • Register an application with the service to obtain the APIKey, OAuthClientId and OAuthClientSecret.

     For more information on creating an OAuth application, refer to the Help documentation.

   Automatic OAuth

   After setting the following, you are ready to connect:

   APIKey: The Application key in your app settings. OAuthClientId: The OAuth Client Id in your app settings. OAuthClientSecret: The OAuth Secret in your app settings.

   When you connect, the provider automatically completes the OAuth process:

   1. The provider obtains an access token from SAP Ariba and uses it to request data.
   2. The provider refreshes the access token automatically when it expires.
   3. The OAuth values are saved in memory relative to the location specified in OAuthSettingsLocation.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the SAP Ariba Procurement JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.saparibaprocurement.jar

   Fill in the connection properties and copy the connection string to the clipboard.

   A typical JDBC URL is below:

   jdbc:saparibaprocurement:ANID=AN02000000280;API=PurchaseOrdersBuyerAPI-V1;APIKey=wWVLn7WTAXrIRMAzZ6VnuEj7Ekot5jnU;AuthScheme=OAuthClient;InitiateOAuth=GETANDREFRESH
4. Enter the path to the cdata.jdbc.saparibaprocurement.jar file, located in the lib subfolder of the installation directory.
5. Right-click the connection and then click Retrieve Schema.
6. Click Next with the default options to select the tables you want to import.
7. Finish the wizard with the default options.

Output the Orders Table to a Flat File

You can follow the procedure below to transfer the Orders table to a flat file output component:

1. In the Table Schemas node, drag the tables to the workspace.
2. In the dialog that is displayed, select the tJDBCInput component.
3. Next, drag a tFileOutputDelimited component from the Business Intelligence tab of the Palette into the workspace.
4. Right-click the Orders tJDBCInput component and drag a vector to the output file.

Run the project to transfer the data.