Tibco Dose

Issue:   After upgrading the code to 7.2.0 it starts giving error like below Server Exception: Gateway Host: USMTGFCV6574D Gateway Service: sapgw02 Program ID: TIBSAP02 Error Message: java.lang.NullPointerException ****************************************************************************************************************************************** Complete Error: 2019 Mar 29 01:42:25:109 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Application] AER3-000084 Received IDOC Name/Number/Receiving Partner: IDOCNEW-Offer03/000000101654285343/TIBSAP02, Count: 1 2019 Mar 29 01:42:25:341 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Adapter] AER3-000091 Total IDOCs processed: 1 2019 Mar 29 01:42:25:342 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Adapter] AER3-000199 Transaction rolled back 0A16A13406905C9DCF7D033D 2019 Mar 29 01:42:25:344 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Warn [Adapter] AER3-970276 Server Exception: Gatewa...

Requirement: To debug an issue and to check the data flowing through Tibco R3 adapter enable SAP JCo trace. Once the trace is enable it creates JCo tracing files in the specified location. These files have details of the JCo library, versions and JCo paths. It will show a complete trace log of the fields/segments in the adapter and it's tables and the input/output data that is flowing through the adapter. ************************************************************************************************************************************************ Steps: Add below properties in the adr3.tra file to enable SAP JCo trace: ===== java.property.jco.trace_level=8 java.property.jco.trace_path=<The path of the directory where the JCo trace file will be generated> ===== Restart the SAP adapter instance. Once you test, the JCo files will be created in the specified location. *********************************************************************************************...

Issue:  An error occurred while parsing:  The markup in the document following the root element must be well-formed ****************************************************************************************************************************************** Complete Error: <?xml version = "1.0" encoding = "UTF-8"?> <ns0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes"> <StackTrace>Job-24000 Error in [Processes/Offer/NewOfferAdd.process/Parse XML] An error occurred while parsing:  The markup in the document following the root element must be well-formed.. at com.tibco.plugin.xml.XMLParseActivity.for(Unknown Source) at com.tibco.plugin.xml.XMLParseActivity.eval(Unknown Source) at com.tibco.pe.plugin.Activity.eval(Unknown Source) at com.tibco.pe.core.TaskImpl.eval(Unknown Source) at com.tibco.pe.core.Job.a(Unknown Source) at com.tibco.pe.core.Job.k(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCour...

Issue: Mismatch found for service: OfferModfiyServer, thread count: 1, connection count: 30 ****************************************************************************************************************************************** Resolution: For all Inbound Adapter Configurations in code, go to Advanced Tab and configure ThreadCount.  It is better to configure a GV and use in all the adapter configurations. ****************************************************************************************************************************************** Details: The error defines that there is an mismatch in the number of threads and the number of connections used in client connection pool. Here, in my case it says connection count is 30 but the thread count is 1. So I configured the thread count to be 30 and the issue is resolved. ******************************************************************************************************************************...