Ready to get started?

Download a free trial of the SAP SuccessFactors Driver to get started:

 Download Now

Learn more:

SAP SuccessFactors Icon SAP SuccessFactors JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SAP SuccessFactors.

Connect to SAP SuccessFactors Data from a Connection Pool in Jetty



The SAP SuccessFactors JDBC Driver supports connection pooling: This article shows how to connect faster to SAP SuccessFactors data from Web apps in Jetty.

The CData JDBC driver for SAP SuccessFactors is easy to integrate with Java Web applications. This article shows how to efficiently connect to SAP SuccessFactors data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for SAP SuccessFactors in Jetty.

Configure the JDBC Driver for Salesforce as a JNDI Data Source

Follow the steps below to connect to Salesforce from Jetty.

  1. Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:

    java -jar ../start.jar --add-to-startd=jndi
  2. Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.
  3. Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the SAP SuccessFactors data source at the level of the Web app, in WEB-INF\jetty-env.xml.

    <Configure id='sapsuccessfactorsdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="sapsuccessfactorsdemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="sapsuccessfactorsdemo"/></Arg> <Arg>jdbc/sapsuccessfactorsdb</Arg> <Arg> <New class="cdata.jdbc.sapsuccessfactors.SAPSuccessFactorsDriver"> <Set name="url">jdbc:sapsuccessfactors:</Set> <Set name="User">username</Set> <Set name="Password">password</Set> <Set name="CompanyId">CompanyId</Set> <Set name="Url">https://api4.successfactors.com</Set> </New> </Arg> </New> </Configure>

    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.
  4. Configure the resource in the Web.xml:

    jdbc/sapsuccessfactorsdb javax.sql.DataSource Container
  5. You can then access SAP SuccessFactors with a lookup to java:comp/env/jdbc/sapsuccessfactorsdb: InitialContext ctx = new InitialContext(); DataSource mysapsuccessfactors = (DataSource)ctx.lookup("java:comp/env/jdbc/sapsuccessfactorsdb");

More Jetty Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.