So hard to deploy a JDBC driver

Question

My PI7.1, I use the "netwaver Administrator" CM->Application Resources to deploy the jdbc driver of postgre, it told me the deploy is OK, but the "Status" of the driver is "Unknown".
And when I try to invloke a channel which uses this postgre JDBC driver, it throws exceptions: can not find class org.postgresql.Driver
What should I do !!!  I grep much time in the forum but did not find any clue yet

Answer 1

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1138877
FYI~~
Summary
Symptom
This note describes the procedure for deploying 3rd party drivers on PI 7.1 using JSPM.
Other terms
JMS, JDBC, 3rd Party, Drivers, JSPM, com.sap.aii.adapter.lib, provider.
Reason and Prerequisites
When connecting to 3rd party software using JDBC and JMS adapters, external drivers need to be provided.
These 3rd party drivers need to be bundled in com.sap.aii.adapter.lib.sda provided by the adapter engine installation.
Prior to PI 7.1 this was done using the SDM tool, however, in PI 7.1 JSPM is used to deploy com.sap.aii.adapter.lib.sda.
This note described the steps for deployment using JSPM.
Solution
For the JMS Driver only
Prepare the JMS provider file as follows:
1. Copy the external drivers from the provider directory to a separate directory.
For example the SonicMQ driver file is called client.jar and is located in the lib subdirectory of SonicMQ installation directory.
2. Open the driver file with a zip program and remove the standard JMS classes. These are located in directory javax/jms.
3. Save the modified driver file.
For the JDBC Driver and the JMS Driver
Add the modified driver files to the lib directory of the archive com.sap.aii.adapter.lib.sda with the help of a zip program.
Then to modify the provider.xml file in the server directory of the archive com.sap.aii.adapter.lib.sda, proceed as follows:
1. Extract provider.xml using a zip program and edit it as follows:
a. For each external driver file that needs to be bundled in com.sap.aii.adapter.lib.sda, add the line <jar-name>lib/driver-jar</jar-name> in the <jars> section.
If you want to install the SAP DB JDBC driver and the SonicMQ JMS driver, this section looks like this:
<jars>
<jar-name>lib/sapdbc.jar</jar-name>
<jar-name>lib/client.jar</jar-name>
</jars>
b. Return the changed provider.xml to the archive.
Make sure that the original directory server\ is retained under Path in the zip archive.
2. Add all external driver jars that you have defined in provider.xml to the lib directory in the archive com.sap.aii.adapter.lib.sda.
3. Use the JSPM tool to deploy com.sap.aii.adapter.lib.sda.
a. To start JSPM, run 'go' from the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/ directory.
b. Log on with the AS Java username and password.
c. Select 'HotFixes' option as the package type.
d. Place the com.sap.aii.adapter.lib.sda in Inbox directory.
This will be mentioned in the Select Package Type dialog.
By default this is
<HOST>\sapmnt\trans\EPS\in.
e. Select Next.
f. If no applicable development component(s) are found in the Inbox directory then:
i. Check to see if the Inbox directory is correct and has the com.sap.aii.adapter.lib.sda.
For more information on this refer to 'Detecting and Changing the JSPM Inbox Directory' section of the JSPM documentation.
ii. JSPM does not allow to deploy an SCA/SDA with the same version (release, SP-level, patch-level) as an already deployed component.
In such a case, the com.sap.aii.adapter.lib.sda will not be listed in the Specify Queue dialog box.
To force the deployment of an such SCA/SDA ignoring version rule run the 'go' command as follows:
go -config=/jspm/forceMode=true
-config=/jspm/deployVersionRule=updateAll
For more information on this please refer to SAP Note 1123333.
f. Select the hot fixes to deploy. In this case sap.com/com.sap.aii.adapter.lib and press Next.
g. For more information about deployment procedure, refer to JSPM documentation.
FAQs
Q1.   Where can I find JSPM documentation?
Ans.  Link to the JSPM User Guide on SAP Help Portal:
help.sap.com -> Documentation -> SAP NetWeaver -> SAP NetWeaver 7.0 (2004s) -> choose a language -> SAP Library -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management by Key Capability -> Solution Life Cycle Management by Key Capability -> Software Life Cycle Management -> Software Maintenance -> Java Support Package Manager
Q2.   Where can I find more information on JSPM?
Ans.  Refer to SAP Note 891983
Q3. I am unable to see any SCA/SDA in the Specify Queue dialog box.
OR
I get the message "No applicable development component(s) found in the Inbox directory"
OR
How do I force the deployment of a component ignoring version rules ?
Ans. Refer to SAP Note 1123333.
Q4. Where can I find more information on the JMS Adapter?
Ans.Refer to SAP Note. 856346.
Q5. Where can I find more information on the JDBC Adapter?
Ans. Refer to SAP Note. 831162
Q6. Which external driver files do I need to bundle in the com.sap.aii.adapter.lib.sda?
Ans. Refer to JMS and JDBC Adapter notes mentioned above.
Q7. What are some of the things that have changed with respect to the adapter lib from XI 30 to PI 7.1?
Ans. The library name has changed from aii_af_jmsproviderlib.sda (releases 3.0/7.0) to com.sap.aii.adapter.lib.sda (release 7.1).
The component name has changed from com.sap.aii.af.jmsproviderlib (releases 3.0/7.0) to com.sap.aii.adapter.lib (release 7.1).
Even the directory structure has changed. The com.sap.aii.adapter.lib.sda (release 7.1) has a lib directory in which all the external drivers need to be placed.
This was not present in aii_af_jmsproviderlib.sda (releases 3.0/7.0) and the external drivers were placed in the root directory of the archive
Q8. Can I use the DriverTool (provided with XI 3.0) to bundle the jars in com.sap.aii.adapter.lib.sda?
OR
Is there a new DriverTool for bundling the external jars in com.sap.aii.adapter.lib.sda?
Ans. No. Due to the changes mentioned above, the DriverTool provided with XI 3.0 cannot be used to bundle external drivers in com.sap.aii.adapter.lib.sda.
No. There is no new tool for bundling the external jars in com.sap.aii.adapter.lib.sda. This needs to be done manually as described in the steps above.