AS400 JDBC on PI
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/
- Install 7 zip (you really can use an archiving program of your choice, as long as it can open SDA files).
- Save the jt400.jar file from the jt400 project and save it locally
- 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.
- Open the SDA in 7 zip.
- Browse down to the lib folder
- Copy the jt400.jar file into that folder.
- In 7 zip, go in to the server folder now (up one level then server folder) and edit the provider.xml file.
- Add an entry for jt400.jar
- Once you’ve finished updating the sda file, copy it to your PI EPS IN folder.
- 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.
- go -config=/jspm/forceMode=true -config=/jspm/deployVersionRule=updateAll
- Now once JSPM loads go to Hot Fixes.
- 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.
- It should finish without issues.
- Now your PI developers can create a communication channel utilizing the new jdbc drivers.
- 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: