Tibco Dose

  Issue: X11 Display error for JDBC activity in deployed application.   Complete Error: JDBC plugin evaluation error: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it." Resolution:  Password reset for the DB connection Details: The password for the DB connection is about to expire. If you test the connection from designer it works fine but while running it gives a pop up saying the password is about to expire and asks if you wanna change it. On running the code from designer on local you can choose to act accordingly when the pop up appears and proceed with the process.  But on deployed application, the code does not know how to behave on this pop up since there is no display option setup or configured to handle this.  Resetting the password for the DB connection and updating in the application resolves this issue. *******************************************************************...

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. ******************************************************************************************************************************...

Issue: Exception in parse eval: [Ljava.lang.Object;@124bf39b ****************************************************************************************************************************************** Complete Error: <?xml version = "1.0" encoding = "UTF-8"?> <ns0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes"> <StackTrace>Job-6000 Error in [Processes/ABC.process/Header Group/RenderE1EDL20] Exception in parse eval: [Ljava.lang.Object;@124bf39b. at com.tibco.plugin.parse.RenderActivity.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$JobCourier.a(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source) caused by: java.io.IOException at com.tibco.plugin.parse.Rende...

Once the setup is done, the most important thing is to monitor the connections, communication, transfer of messages and to troubleshoot the issues. This can be done through the means listed below. Monitoring and Troubleshooting: Below are the means available for monitoring and assessment: Rendezvous performance assessment software: It is a tool that measures the performance of RV in a running situation and provides a detailed output report. It consists of two executable programs: Rvperfm and rvperfs : These are the performance assessment tools which measures their capacity to receive messages as part of overall network performance. Rvperfm sends messages to the network and reports the statistics to stdout. Rvperfs listens for messages from rvperfm, gathers and reports statistics to rvperfm at the end of each run. Latency assessment software (rvlat): It is a latency assessment tool that measures the message latency that is the total time taken to send a m...

Virtual Circuit: Virtual circuit (VC) provides exclusive communication between two nodes. Only the two nodes can communicate with each other. The sender can only send messages to opposite node and the receiver can receive messages only from the opposite node. If there is a requirement where transport should be done among specific nodes and no other listener should get the information then VC should be used. Fault Tolerance: When the active program fails, the fault tolerance software directs one of the backup programs to become active and start processing. To configure programs in FT mode below parameters must be configured: Active Goal: It defines the total  number of active members. For example: If the active goal is set as 4, there will be 4 active members those have the highest ranks among all the members. Rank: Each program has a unique rank. If a program has N rank and another program has N+1 rank, then N is a higher rank than N+1. It determines the membe...

Transport: It is the mechanism for sending and delivering messages. There are three main parameters in Tibco RV for transport: network, daemon and service. Service is specific to programs. Multiple programs may be running on a network. Each program has a different service. There can be many services running under a daemon for different programs. Network parameter specifies the interface for multicast communication from a program. A specific network should be selected for  outbound multicast Rendezvous communications. Daemon specifies the port where RV daemon runs. RV communicates through this daemon and hence remote daemon must be specified to support network communications. Tibrvsend and Tibrvlisten: Every Tibco RV installation provides these two utilities for sending and receiving messages on any multicast network. Sample for testing these utilities: tibrvlisten.exe -service 7576 -network 10.21.6.38 -daemon tcp:7500 "TEST" tibrvsend.exe -s...

Features of Tibco RV: Decoupling and Data Independence : In RV the applications are loosely coupled and RV has self-describing data that makes it easy for the applications to share data. Location Transparency : RV is based upon subject based addressing. The data/messages are sent and received over subject; hence the programs can communicate without knowing the network details. Architectural Emphasis on Information Sources and Destinations : RV provides efficient solutions for developing distributed system by emphasis on identifying sources and destinations of information. Reliable Delivery: RV provides reliable delivery of messages and without the need of network details. The information like network details and packet transfer are hidden. Certified Message Delivery: Some applications require more assurance for message delivery. For this RV provides Certified Message (CM) delivery which sends the confirmation for the messages received. Distribu...