Page tree
Skip to end of metadata
Go to start of metadata


In this Wiki, we will take a look at the JDBC Adapter driver requirements for SAP Process Integration or SAP Process Orchestration integrations to third party databases.


We will provide details on what parts of this integration are responsibility for the SAP Support team and the customer team(s).


The PI JDBC Adapter can be used to connect with any third party Database, provided some necessary prerequisites are met. One of these is the deployment of the required database driver to enable the connection. 
The JDBC Driver handles the connection between the PI/PO system and the third party database. 
The JDBC Driver is third party software belonging to the database vendor i.e. it is outside SAP area of responsibility.
The JDBC Driver must be compatible with the database it is connecting to and the Java version the PI/PO system is running on. 

If making a connection to a third party database, it is essential to verify with the database vendor which driver they recommend which fits your requirements i.e. compatible with your Java version (Java 8 in PO 7.5) and also compatible with the database version your are connecting to. 

Customer responsibilities:

The customer must ensure they do the following:

  1. source the correct DB driver/jar file to connect to the third party Database version. 
  2. identify the correct Driver name parameter and connection string parameter required by the DB vendor to connect to their DB
  3. verify with the DB vendor that this driver is compatible with the Java version that your PI/PO system is running on. See KBA 1615198 PI JDBC and JMS Adapter driver's JRE compatibility 

SAP side configurations:

When you have obtained the necessary driver, this must be deployed to the PI/PO system by following the very specific steps in KBA 2513069 Guided Answers - How to deploy the external drivers for Axis/JDBC/JMS Adapter.
In short, you must

  • extract the file from the SAPXI3RDPARTY.SCA file (which you can download from the SAP Launchpad) or obtain from the file system where the PI system software is deployed
  • then package the driver jar files in the file (change the file extension to .zip) 
  • update the Provider.xml with the driver name
  • deploy the file

Outline steps are as follows: 
- download the SAPXI3RDPARTY.SCA
- change the extension to
- extract the contents
- go to (in DEPLOYARCHIVES folder)
- change the extension to
- place the third party jar file in the (lib folder) 
- update the Provider.xml (in server folder) 
- change the extension of ->
- deploy the via SUM (or Telnet)

If you encounter problems with the deployment of the driver, you can contact SAP Support. 

If contacting SAP Support:

If you are contacting SAP Support for a JDBC Adapter driver related query, provide the following details: 

  1. The DB vendor and version that you are connecting to e.g. MS SQL Server 2019 or Oracle 19c.
  2. State if you have contacted the DB vendor to verify with them the exact driver/jar file required to connect to their specific DB version.
  3. The name of the driver/jar file you have deployed to connect to this DB. 
  4. The driver name parameter and DB connection string parameter maintained in the JDBC Communication Channel
  5. Screenshots of the steps you have followed to deploy the driver (as per KBA 2513069 Guided Answers - How to deploy the external drivers for Axis/JDBC/JMS Adapter).
  6. Provide the XPI Inspector Example 50 (By Channel) trace for the involved JDBC Channel. Select the additional option SAP System State. Just start/stop the XPI tool to collect parameter information. See the SAP note 1514898 XPI Inspector for troubleshooting SAP Process Orchestration / Integration, for details on using the XPI tool (user guide is attached to the note).


  1. What is the SAPXI3RDPARTY.SCA? 
    A: this is an empty wrapper file which contains the empty sda files for deploying third party drivers used to enable connections to third party applications using the PI JDBC Adapter, JMS Adapter or SOAP AXIS Adapter
  2. Do I need to deploy the SAPXI3RDPARTY.SCA file?
    A: No, you will only ever deploy the adapter specific sda files e.g.
  3. If there are already drivers deployed in these sda files, what precautions do I need to take? 
    A: you need to be aware that when deploying a new driver/jar file, you also need to package and deploy all previously existing jar files. Refer to KBA 1816456 PI: Deploying new JMS/JDBC drivers overwrites existing deployed drivers. for details
  4. How can I know if there are drivers already deployed? 
    A: Check the Classloader location in the NetWeaver Administrator (NWA) as per KBA 1829286 Checking the drivers installed for the JMS and JDBC Adapters
  5. Where can I find the file (or any of the other driver/jar file related *.sda files) in the PI/PO file system? 
    A: This is available in the directory path \usr\sap\<SID>\<instance>\j2ee\cluster\bin\ext

See Also:

SAP Note 831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 / PI 7.3 JDBC Adapter -> Q. 13

KBA 1681420 Location of PI JDBC Driver for Microsoft Access DB

  • No labels