Skip to Content

How to Deploy JMS driver to PI Server

For any scenario connecting PI to JMS server, we need to deploy the jms drivers to the server.

Follow the below steps and get it done

Steps:-

Prepare the JMS provider file as follows:

1. Copy the external drivers from the provider directory to a separate directory.

2. Add the files to the lib directory of the archive com.sap.aii.adapter.lib.sda with the help of a zip program.

This file is available at directory:

DATA_UNITS\JAVA_J2EE_OSINDEP_J2EE_INST on the SAP NetWeaver 7.10 PI Java installation DVD.

Or on the server at:

Drive:\PIInst\nw7.0widEHP1 Java based sw comp\DATA_UNITS\JAVA_J2EE_OSINDEP_J2EE_INST

Open this SDA file with winrar:

than add the jms jar files in the lib folder.

3. Then to modify the provider.xml file in the server directory of the archive com.sap.aii.adapter.lib.sda, proceed as follows:

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

<jars>

<jar-name>lib/<name>.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.

*

4. Use the JSPM tool to deploy com.sap.aii.adapter.lib.sda.

          a. Put the edited com.sap.aii.adapter.lib.sdafile in the JSPM inbox. At this location Drive:\usr\sap\trans\EPS\in

          b. Run JSPM by clicking on go.bat file at this location: Drive:\usr\sap\XD1\DVEBMGS00\j2ee\JSPM

          c. Enter user name and password for J2EE_admin

          d. Select ‘HotFixes’ option as the package type.

          e. Select the current version of the file.

          f. Click start and continue with steps on screen.

          g. In sometime, we get the confirmation for the deployment.

          h.  Restart AS Java. JMS driver has been installed successfully.

General Error

1. Unable to find the sda file in the hot fixes

Cause

This behavior is by design. Normally users want to update their system to a newer version. JSPM filters the inbox directory content and shows only updates applicable to this system. Still in some special cases you may need to redeploy an SCA with the same version.

Solution:

If you want to redeploy an SCA with the same version and all contained SDAs regardless of their versions,

start JSPM with this command line:

go -config=/jspm/forceMode=true -config=/jspm/deployVersionRule=updateAll

and if want to deploy from higher to lower version than use command

go -config=/jspm/forceMode=true -config=/jspm/deployVersionRule=updateLowerOnly

2. Dependency Validation error

Cause

This error is because of service packages version. PI server doesn’t have the update service pack deployed which is causing dependency error for the hotfixes.

Solution:

Deploy the latest service pack on the PI server.

====================================================

*N.B.,

7.1+ JSPM is replaced by SUM

====================================================

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply