Show TOC

Providing External Drivers for the JDBC and JMS AdaptersLocate this document in the navigation structure


For a scenario involving communication with a database or a messaging system, you need external drivers for the JDBC and JMS adapters. These drivers must be provided as Java archives (JARs) by the provider of the database or messaging system, respectively.

You have to deploy these drivers to enable them to be used by the adapters on the SAP J2EE Server. For this purpose, the Adapter Engine installation provides the archive , to which you have to add the respective driver files.

The SDA file format required for the deployment is basically a Zip-file format that contains additional text files, called descriptors, which describe the deployable library content (the JAR files packed in the SDA). Therefore, adding a JAR file to the archive means adding the JAR file with a Zip tool and adding its name to the <jars> element in the provider.xml file contained in the SDA. For the latter, you need to unzip the provider.xml file from the SDA, add the name to the correct section, and zip it again to the archive with the correct path information. To do so, proceed as described in the following sections.

For the JMS Driver only

Prepare the JMS provider file as follows:

  1. Copy the file from the provider directory to a separate directory (for SonicMQ, for example, this file is called client.jar and is located in the lib subdirectory of the SonicMQ installation).

  2. Open the file with a zip program and remove the standard JMS classes. These are located in directory javax/jms .

  3. Save the modified provider file.

For the JDBC Driver and the JMS Driver

Add the driver to the archive as follows:

  1. Use a Zip program to extract the provider.xml descriptor from the archive.

  2. Edit the provider.xml descriptor by adding the line <jar-name>driver-jar</jar-name> for each provider-specific JAR file in the <jars> section.


    If you want to install the MaxDB JDBC driver and the SonicMQ JMS driver, this section would look like this:





  3. Return the changed provider.xml descriptor to the archive.


    Make sure that the original META-INF\ and server\ directories are retained under Path in the Zip archive (check for the latest Path entry).

  4. Add all JARs (without path information) that you have defined in provider.xml to .

    You find in directory DATA_UNITS\JAVA_J2EE_OSINDEP_J2EE_INST on your SAP NetWeaver 7.1 PI Java installation DVD.

  5. Use the Software Update Manager (SUM) to deploy . See the SUM documentation on SAP Service Marketplace at: published on SAP site > Software Logistics Toolset 1.0 > Software Update Manager (SUM).

  6. Restart AS Java. The drivers are now known to the JMS adapter or JDBC adapter and can be used as described.