How to Deploy Jdbc Drivers-ljb2003[1]

5/13/2018 How to Deploy Jdbc Drivers-ljb2003[1] - slidepdf.com

http://slidepdf.com/reader/full/how-to-deploy-jdbc-drivers-ljb20031 1/4

2009/04/22 Page 1 of 4

SAP Note 1138877 - PI 7.1 : How to Deploy External DriversJDBC/JMS Adapters

Note Language: English Version: 4 Validity: Valid Since 2008/04/15

Summary

Symptom This note describes the procedure for deploying 3rd party drivers on PI 7.1

using JSPM.

More TermsJMS, JDBC, 3rd Party, Drivers, JSPM, com.sap.aii.adapter.lib, provider.

Cause and PrerequisitesWhen 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.

SolutionFor 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.



2009/04/22 Page 2 of 4


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 thecom.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 theInbox directory"

OR



2009/04/22 Page 3 of 4


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 incom.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.

Header Data

Release Status: Released for Customer

Released on: 2008/04/15 08:58:47

Original Lang.: English

Priority: Recommendations/additional info

Category: Upgrade information

Main Component: BC-XI-CON-JMS JMS Adapter

Additional Components:

BC-XI-CON-JDB JDBC Adapter

Valid Releases



2009/04/22 Page 4 of 4


Software Component Release From

Release

To

Release

and

Subsequent

SAP-XIAFC 7.10 7.10 7.10

Related Notes

Number Short Text

1123333 Redeploying same component with JSPM

891983 JSPM: Central SAP Note SAP NetWeaver 2004s AS Java

856346 J2EE JMS Adapter: Frequently Asked Questions (FAQ)

831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter

Documents

How to Deploy Jdbc Drivers-ljb2003[1]