Products | Versions |
---|---|
TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | 7.3.1 |
When deploying the TIBCO Adapter application in the TIBCO Administrator using the RV transport for repository, the following error could occur on application startup:
Environment variables successfully set SLF43: Class path contains multiple SLF4J bindings. SLF4J: Found binding in (jar: file:/opt/tibco/adapter/adr3/7.3/lib/slf4j-nop-1.7.31.jar!/org/slf4j/impl/Staticlogger@inder.classl SLF4J: Found binding in jar: file: /opt/tibco/pci/5.12/11b/log4j-slf4J-1mp1-2.17.1.jar!/org/slf4j/impl/StaticloggerBinder.classi SLF4J: Found binding in ljar: file:/opt/tibco/tpcl/5.12/l1b/slf4j-log4j12-1.7.31.Jar!/org/sifAj/impt/StaticLogger@inder.class] SLF4): Found binding in ljar:file:/opt/tibco/tpci/5.12/11b/stf4J-simple-1.7.31.jar!/org/sl74]/impt/StaticLoggerBinder.class] SLF4J: See http://www.s1f4j.org/codes.html#multiple bindings for an explanation. SLF4J: Actual binding is of type [org. slf4j. helpers .NOPLoggerFactory] Processing /tibco/private/adapter/SAPADAPTERConfiguration/ESISAPAdapterConfiguration/SAPAdapter... com. tibco.sdk.MException: "Invalid url: /tibco/private/adapter/<adapter configuration name>. "
To resolve this issue:
Run the traUpgradeManager utility present inside <TIBCO_HOME>/tra/5.12/bin folder and use the below command to update all the tra files under Adapter home(<TIBCO_HOME>/adapter/).
Command to be used
./traUpgradeManager -path <TIBCO_HOME>/adapter/ -rv <RV_HOME_PATH>
for Example
./traUpgradeManager -path /opt/tibco/adapter/ -rv /opt/tibco/tibrv/8.6/
Redeploy the application, and verify if the issue is resolve.
If issue persists after applying above steps, edit the adapter template tra file (usually the file in the adapter's bin folder with the same file name as adapter binary but with extension type .sh, for example, adr3.tra), appending '%RV_HOME%/lib/tibrvj.jar' as the first variable for tibco.env.STD_CP_EXT.
for Example:
tibco.env.STD_CP_EXT=%RV_HOME%/lib/tibrvj.jar\:%TIB_SDK_DIR%/hotfix/lib\:%TIB_SDK_DIR%/lib\:%TRA_HOME%/hotfix/lib\:%TRA_HOME%/lib\:%TPCL_HOME%/lib\:%RV_HOME%/lib\:%EMS_HOME%/lib
After update the template tra file, redeploy the application and verify if the issue is resolved.