With TRIRIGA 22.214.171.124 and BIRT 4.3.1 on Windows Server 2012 R2, we see that the “Export Report” option in a BIRT report defaults to “PostScript”, whereas in the current TRIRIGA 126.96.36.199 production version, it is defaulted to “Excel”. We want this export report option to be defaulted to “Excel” in TRIRIGA 188.8.131.52 as well. Only after upgrading from 184.108.40.206 to 220.127.116.11, we are seeing this change.
The BIRT engine did not sort the export options by default. Moving forward, the list of format options when exporting a BIRT report are now in alphabetical order, with the default being Excel XLS.
[Admin: To see other related posts, use the Export tag or BIRT tag.]
When a BIRT report is launched in TRIRIGA on the Reports tab or elsewhere, a Progress Bar popup appears with a “Cancel” button.
- 1. If I click “Cancel”, will that kill the Select statement that is running against the database on the database server?
- 2. If I click “Cancel”, will that release the database connection that is used when a BIRT report starts to run?
The answer to both questions is “No”. The thread will be consumed until the Select statement is complete. There is no messaging included in the log that the Select process was orphaned due to user interaction. The process simply continues to run until the results are retrieved and then stops. So, effectively:
- 1. No, canceling a request will not kill the Select statement.
- 2. No, the thread remains unaware that the request was canceled.
When the results are returned, the thread will process them, and then hit the canceled thread. There may be a message in the log warning about an IO socket being disconnected, or some other exception dealing with the dead connection.
[Admin: To see other related posts, use the Thread tag or BIRT tag.]
There are many installation scenarios that can cause TRIRIGA reports, especially BIRT reports, to fail to export due to timeout. Microsoft Excel exports are often the ones that you can observe because all of the file formatting happens during export.
Let’s focus on WebSphere Liberty installations, but this recommendation can be used for other web servers with some tweaks. Mostly, this is related to timeout settings, especially for HTTPS (SSL/TLS) connections. A good troubleshooting test is to perform the same action in a non-HTTPS (HTTP) connection. Does the report export? If so, take note of the time needed to export it and plan to extend the timeout in the HTTPS connection to at least double the time.
Refer to the IBM Knowledge Center > WebSphere Liberty > HTTP Endpoint topic. Look for the “sslOptions”, and also double-check the “httpOptions”, for timeouts.
[Admin: This post is related to the 04.20.17 post about setting the TRIRIGA session expiration warning in the portal. To see other related posts, use the Timeout tag.]
During our penetration test, a vulnerability was identified that related to the leakage of sensitive information. This vulnerability exists application-wide.
We needed to make the errors from BIRT into MID errors, and send the stack trace to the log. Moving forward, we resolved an issue when running BIRT reports that, in some situations, a technical stack trace would be displayed to the end user when an error occurred.
[Admin: To see other related posts, use the Stack Trace tag or Vulnerability tag.]
Here are several lists of reports delivered with the as-shipped TRIRIGA solution:
I have set up single sign-on (SSO) with SiteMinder and Liberty, and both seem to be working fine. However, after login, when I attempt to access BIRT reports, I get the following in the DevTools security window:
Mixed Content: The page at 'https://hostname/html/en/default/platform/mainpage/mainpage.jsp' was loaded over HTTPS, but requested an insecure resource 'http://hostname/birt/frameset?_docId=2816263&_la…tem__triPaymentLineItem_-_Report_-_Future_Rent_Obligation_Detail.rptdesign'. This request has been blocked; the content must be served over HTTPS.
Similarly, when I attempt to open a record and navigate the tabs, I get the following:
Mixed Content: The page at 'https://hostname/WebProcess.srv?objectId=750000&…TypeId=10002490&action=Edit&managerType=query&altGuiListId=-1&inline=false' was loaded over HTTPS, but requested an insecure form action 'http://hostname/WebProcess.srv?objectId=880000&a…false&undeletable=false&requiredNotSet=0&requiredTabList=&requiredField=-1'. This request has been blocked; the content must be served over HTTPS.
In the first case, the report never displays, and in the second case, the record appears to entirely hang. Have any of you seen this before? Any ideas how to fix it?
[Admin: This post is related to the 08.20.15 post about getting a mixed content security error with Esri ArcGIS, and the 06.18.15 post about GIS mixed content messages. To see other related posts, use the SiteMinder tag or SSO tag.]
I have a TRIRIGA SaaS client, and administrators of my client have several questions about TRIRIGA SaaS services:
- 1. What are the differences of the functions between TRIRIGA on SaaS and TRIRIGA on premise? Please provide a list of the differences.
- 2. Can we use mail notifications to other users from TRIRIGA on SaaS?
- 3. Can we make and incorporate BIRT reports into TRIRIGA on SaaS?
[Admin: This post is related to the 05.24.16 post by ValuD about SaaS with TRIRIGA, and the 11.13.15 post about TRIRIGA SaaS in the Cloud Shop.]