Skip to Content

During out migration project there was a requirement to pull data into SAP using PI from our AS400.  Historically connection anything to the iSeries has been difficult as best (e.g.  MS SQL to AS400 via linked servers…).  So now we had to figure out how to do it inside of PI.

Things you’ll need:

JDBC connection to AS400 – jt400.jar file from – http://sourceforge.net/projects/jt400/

com.sap.aii.adapter.lib.sda PI install file – Can be found in the JAVA_OSINDEP_J2EE_INST folder of the PI 7.10 installation media

7 zip – http://www.7-zip.org/

Steps:

  1. Install 7 zip (you really can use an archiving program of your choice, as long as it can open SDA files).
  2. Save the jt400.jar file from the jt400 project and save it locally
  3. Grab the com.sap.aii.adapter.lib.sda file from the JAVA_OSINDEP_J2EE_INST folder of your PI 7.10 installation media and save it locally
  4. Tip:  Before getting the sda file, check with BASIS Team or PI Team if any other external drivers have been deployed in the past using this method.
    If the answer is yes, then get the _latest_modified_version_ of the sda file, and edit that, otherwise you will lose the libraries which have already been deployed.
  5. Open the SDA in 7 zip.
  6. Untitled picture.png
  7. Browse down to the lib folder
  8. Untitled picture.png
  9. Copy the jt400.jar file into that folder.
  10. Untitled picture.png
  11. In 7 zip, go in to the server folder now (up one level then server folder) and edit the provider.xml file.
  12. Untitled picture.png
  13. Add an entry for jt400.jar
  14. Untitled picture.png
  15. Once you’ve finished updating the sda file, copy it to your PI EPS IN folder.
  16. You’ll need to run JSPM now, but you’re going to have to run it with a command line switch.  The reason for this is that com.sap.aii.adapter.lib.sda hass already been installed and what you’re basically doing is reinstalling the same version again.  JSPM won’t allow this unless you launch it with the following command.
  17. go -config=/jspm/forceMode=true -config=/jspm/deployVersionRule=updateAll
  18. Now once JSPM loads go to Hot Fixes.
  19. You should now see sap.com/com.sap.aii.adapter.lib available as a hot fix.  You can see that the current version and the target version are the same.
  20. Untitled picture.png
  21. It should finish without issues.
  22. Untitled picture.png
  23. Now your PI developers can create a communication channel utilizing the new jdbc drivers.
  24. Untitled picture.png
  25. When you have completed the task, put the latest version of the sda file in a safe place for the next time either libraries need to be added or updated so that the wrong file is not used

There are some very useful OSS Notes on this subject:

1770206 – PI  How to extract the archive for deploying 3rd party drivers.pdf

1770304 – PI How to prepare the com.sap.aii.adapter.lib.sda for deployment.pdf

1829286 – PI How to check which drivers are installed for the JMS and JDBC Adapters.pdf

1770206 – PI  How to extract the archive for deploying 3rd party drivers.pdf

1138877 – PI 7.1 How to Deploy External Drivers JDBC JMS Adapters


To report this post you need to login first.

3 Comments

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

  1. Andy Silvey

    Hi Tony,

    this is an excellent blog showing all of the principle steps for deploying external drivers into PI.

    If I can add a few more tips which I gained from doing this…

    a) ref: Your item #2 Grab the sda file

    • Grab the com.sap.aii.adapter.lib.sda file from the JAVA_OSINDEP_J2EE_INST folder of your PI 7.10 installation media and save it locally

    Tip:  before getting the sda file, check with BASIS Team or PI Team if any other external drivers have been deployed in the past using this method.

    If the answer is yes, then get the _latest_modified_version_ of the sda file, and edit that, otherwise you will lose the libraries which have already been deployed.

    b) When you have completed the task, put the latest version of the sda file in a safe place for the next time either libraries need to be added or updated so that the correct version of the file is used.

    c) There are some very useful OSS Notes on this subject:

    1770206 – PI  How to extract the archive for deploying 3rd party drivers.pdf

    1770304 – PI How to prepare the com.sap.aii.adapter.lib.sda for deployment.pdf

    1829286 – PI How to check which drivers are installed for the JMS and JDBC Adapters.pdf

    1770206 – PI  How to extract the archive for deploying 3rd party drivers.pdf

    1138877 – PI 7.1 How to Deploy External Drivers JDBC JMS Adapters

    All the best,

    Andy.

    (0) 

Leave a Reply