Ready to get started?

Learn more about CData Connect Cloud or sign up for free trial access:

Free Trial

Connect to Live SAP SuccessFactors Data in PostGresSQL Interface through CData Connect Cloud



Create a live connection to SAP SuccessFactors in CData Connect Cloud and connect to your SAP SuccessFactors data from PostgreSQL.

There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect Cloud, you gain database-like access to live SAP SuccessFactors data from PostgreSQL. In this article, we walk through the process of connecting to SAP SuccessFactors data in Connect Cloud and establishing a connection between Connect Cloud and PostgreSQL using a TDS foreign data wrapper (FDW).

CData Connect Cloud provides a pure SQL Server interface for SAP SuccessFactors, allowing you to query data from SAP SuccessFactors without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc.) directly to SAP SuccessFactors, leveraging server-side processing to return the requested SAP SuccessFactors data quickly.

Connect to SAP SuccessFactors in Connect Cloud

CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.

  1. Log into Connect Cloud, click Connections and click Add Connection
  2. Adding a Connection
  3. Select "SAP SuccessFactors" from the Add Connection panel
  4. Selecting a data source
  5. Enter the necessary authentication properties to connect to SAP SuccessFactors.

    You can authenticate to SAP Success Factors using Basic authentication or OAuth with SAML assertion.

    Basic Authentication

    You must provide values for the following properties to successfully authenticate to SAP Success Factors. Note that the provider will reuse the session opened by SAP Success Factors using cookies. Which means that your credentials will be used only on the first request to open the session. After that, cookies returned from SAP Success Factors will be used for authentication.

    • Url: set this to the URL of the server hosting Success Factors. Some of the servers are listed in the SAP support documentation (external link).
    • User: set this to the username of your account.
    • Password: set this to the password of your account.
    • CompanyId: set this to the unique identifier of your company.

    OAuth Authentication

    You must provide values for the following properties, which will be used to get the access token.

    • Url: set this to the URL of the server hosting Success Factors. Some of the servers are listed in the SAP support documentation (external link).
    • User: set this to the username of your account.
    • CompanyId: set this to the unique identifier of your company.
    • OAuthClientId: set this to the API Key that was generated in API Center.
    • OAuthClientSecret: the X.509 private key used to sign SAML assertion. The private key can be found in the certificate you downloaded in Registering your OAuth Client Application.
    • InitiateOAuth: set this to GETANDREFRESH.
    Configuring a connection (Salesforce is shown)
  6. Click Create & Test
  7. Navigate to the Permissions tab in the Add SAP SuccessFactors Connection page and update the User-based permissions. Updating permissions

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

  1. Click on your username at the top right of the Connect Cloud app and click User Profile.
  2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
  3. Give your PAT a name and click Create.
  4. Creating a new PAT
  5. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Build the TDS Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).

  1. You can clone and build the git repository via something like the following view source: sudo apt-get install git git clone https://github.com/tds-fdw/tds_fdw.git cd tds_fdw make USE_PGXS=1 sudo make USE_PGXS=1 install Note: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG= after USE_PGXS=1 at the make commands.
  2. After you finish the installation, then start the server: sudo service postgresql start
  3. Then go inside the Postgres database psql -h localhost -U postgres -d postgres Note: Instead of localhost you can put the IP where your PostgreSQL is hosted.

Connect to SAP SuccessFactors data as a PostgreSQL Database and query the data!

After you have installed the extension, follow the steps below to start executing queries to SAP SuccessFactors data:

  1. Log into your database.
  2. Load the extension for the database: CREATE EXTENSION tds_fdw;
  3. Create a server object for SAP SuccessFactors data: CREATE SERVER "SAPSuccessFactors1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'SAPSuccessFactors1');
  4. Configure user mapping with your email and Personal Access Token from your Connect Cloud account: CREATE USER MAPPING for postgres SERVER "SAPSuccessFactors1" OPTIONS (username 'username@cdata.com', password 'your_personal_access_token' );
  5. Create the local schema: CREATE SCHEMA "SAPSuccessFactors1";
  6. Create a foreign table in your local database: #Using a table_name definition: CREATE FOREIGN TABLE "SAPSuccessFactors1".ExtAddressInfo ( id varchar, zipCode varchar) SERVER "SAPSuccessFactors1" OPTIONS(table_name 'SAPSuccessFactors.ExtAddressInfo', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "SAPSuccessFactors1".ExtAddressInfo ( id varchar, zipCode varchar) SERVER "SAPSuccessFactors1" OPTIONS (schema_name 'SAPSuccessFactors', table_name 'ExtAddressInfo', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "SAPSuccessFactors1".ExtAddressInfo ( id varchar, zipCode varchar) SERVER "SAPSuccessFactors1" OPTIONS (query 'SELECT * FROM SAPSuccessFactors.ExtAddressInfo', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "SAPSuccessFactors1".ExtAddressInfo ( id varchar, col2 varchar OPTIONS (column_name 'zipCode')) SERVER "SAPSuccessFactors1" OPTIONS (schema_name 'SAPSuccessFactors', table_name 'ExtAddressInfo', row_estimate_method 'showplan_all');
  7. You can now execute read/write commands to SAP SuccessFactors: SELECT id, zipCode FROM "SAPSuccessFactors1".ExtAddressInfo;

More Information & Free Trial

Now, you have created a simple query from live SAP SuccessFactors data. For more information on connecting to SAP SuccessFactors (and more than 100 other data sources), visit the Connect Cloud page. Sign up for a free trial and start working with live SAP SuccessFactors data in PostgreSQL.