How to resolve issue when using SAP Adapter 7.2.0 with the SAP JCo Library version 3.0.15 and 3.0.16.
book
Article ID: KB0083758
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions
7.2.0
Description
When using the SAP JCo Library version 3.0.15 or 3.0.16 with the SAP adapter version 7.2.0. The below error might be encountered in the adapter logs -
"Exception in main thread "main" java.lang.IllegalArgumentException: Meta data equal to null is not allowed for field QNAME with type TABLE in meta data instance IMPORTS".
Issue/Introduction
While using the SAP JCo Library 3.0.15 or higher version with the SAP Adapter 7.2.0 an exception occurs in the main thread for Illegal argument . In such scenario, please apply the Hotfix-01 available at support.tibco.com to overcome the problem of the JCo compatibility.
Environment
SAP Adapter version 7.2.0 and SAP JCo Library version 3.0.15 or 3.0.16
Resolution
The solution below works for both the SAP JCo Library 3.0.15 and 3.0.16. The solution is shared below -
In order to resolve the illegal thread error due to the JCo compatibility with Adapter, Please apply the HotFix-01 available at "support.tibco.com".
Also you can use the below mentioned manual solution to overcome the illegal thread error although we strongly recommend to apply HotFix-01 in the above scenario.
The customer needs to add the following properties in the adr3.tra for the SAP repository - adr3.saprepository adr3.saprepository.appserver adr3.saprepository.client adr3.saprepository.language adr3.saprepository.password adr3.saprepository.username adr3.saprepository.sysnr
example for reference - adr3.saprepository ON adr3.saprepository.appserver xx.xxx.xx.xx adr3.saprepository.client xxx adr3.saprepository.language E adr3.saprepository.password ******** adr3.saprepository.username abc adr3.saprepository.sysnr 00
Note - 1. The TRA property adr3.saprepository.password contains the password for the SAP user id. It is not recommended that passwords be maintained in clear text in files. The passwords should be obfuscated. Run the obfuscate tool along with the SAP password and then enter in the TRA file. The following is an example of what it should look like.