How did we improve lease and platform performance?


Improvements in IBM TRIRIGA Performance

By Rick Rhea & Jay Manaloto

What has the IBM TRIRIGA performance team been up to? Over the last few years and last few releases, our performance team has focused on areas that aren’t normally covered by our standard benchmark tests, and on tools that can help customers to resolve performance issues on their own. If you’re interested, here are a few of our recent improvements in lease and platform performance.

  • Lease Benchmark Testing: Not only are database server and process server resources especially important, but using multiple process servers improves performance.
  • New Recommended Indexes: Several additional indexes were identified and added to the best practices to obtain the best response times and resource utilization of the database server.
  • Lease Journal Entries: By redesigning journal entry processing with parallel and batch processing, and multiple process servers, our test results took only about 2.5 hours instead of over 90 hours.
  • Platform Enhancements: Dynamic workflows can now pass and return parameters, the Query task can now return the number of records instead of the actual records, and the Trigger Action task can now run the asynchronous event that occurs after the transition by a user other than the currently logged-in user.
  • BIRT Reporting & Lease Disclosure Reports: In Version 3.6.1, the reporting was modified to improve running on a separate BIRT server, and to avoid the problematic “params.displayText”.
  • Performance Analyzer Tool: In Version 3.5.3, this tool was introduced to allow a customer to run specific logging types without using the Admin Console, and to view easy-to-read reports.
  • Module Level Associations, Early Adopter Feature: In Version 3.7.0, the platform was enhanced to support Module Level Associations (MLA) tables where the records in the IBS_SPEC_ASSIGNMENTS table are distributed into smaller tables that are created by module type.

By applying the above finding and tools, our recent IBM TRIRIGA 10.7.0 / 3.7.0 release has demonstrated a significant improvement in performance over previous releases. But we’re not done yet! Our performance team will continue to dig deeper into weaker areas or potential opportunities to make our products stronger or faster. So stay tuned for any upcoming developments!

Note: For future releases, “Module Level Assignments” will be renamed “Module Level Associations”.

References:

[Admin: This post is related to the 07.27.17 post about the Performance Analyzer. To see other related posts, use the Performance tag.]

Continue reading

Why are BIRT report parameters failing in TRIRIGA 3.5.2?


I’m seeing an issue with report parameters in BIRT. I’ve added a report parameter and bound it to a filter condition. The report runs perfectly in Eclipse. But when I uploaded the same to TRIRIGA, it’s giving me errors while the report is rendering, after entering the parameters. Surprisingly, null checks have been implemented using a script at the table level as well as on the filters, so that optional parameters are dealt with. Here’s the exception trace…

This may be related to a known issue resolved in APAR IV96587. Try the most recent fix pack and see if it resolves the issue.  If it does not, I would put in a PMR.

[Admin: This post is related to the 11.13.15 post and 07.03.15 post about having issues with BIRT report parameters. To see other related posts, use the BIRT tag.]

Continue reading

Getting an error when running report in TRIRIGA not BIRT designer


I exported the .rpt and the properties file from BIRT report designer, zipped it, and then saved it in the TRIRIGA Document Manager under the respective object (in this case, triProject). I then modified and updated my query report as “External”, and then in the “Options” tab, pointed to the ZIP file from BIRT. However, when I run the report to view the BIRT report, I get a MID error. Meanwhile, the BIRT report works fine when I run it in BIRT report designer.

[Admin: This post is related to the 03.29.17 post about getting an error when evaluating script in TRIRIGA but not BIRT designer, and the 05.11.16 post about running a BIRT report ZIP. To see other related posts, use the BIRT tag.]

Continue reading

What are the different chart-type and metric-type reports in TRIRIGA?


In TRIRIGA, I can see only 4 main types of chart reports: (1) pie, (2) bar, (3) lined, and (4) stacked bar, and these are two-dimensional. Are there any other chart type reports apart from these? And how can we report on multi-dimensional (more than two-dimensional) chart reports?

TRIRIGA ships with the following chart types in the table below. TRIRIGA also integrates with the BIRT and Crystal Reports engines, which have very robust reporting options. Note that as of the TRIRIGA 3.5.0 platform, anything that says “linear gauge”, will render as a circular gauge.

Name/Description Type
3D Doughnut Pie
3D Pie Pie
Bubble Bubble
Circular Bar Gauge Circular Gauge
Circular Gauge Circular Gauge
Doughnut Pie
Horizontal Grouped Bar (%) Bar (%)
Horizontal Grouped Bar Bar
Horizontal Linear Bar Gauge Linear Gauge
Horizontal Linear Tank Gauge Linear Gauge
Horizontal Stacked Bar Bar
Line/Vertical Grouped Bar Combo Line-Bar Combo
Line/Vertical Stacked Bar Combo Line-Bar Combo
Line Line
Pie Pie
Pyramid Pyramid
Spline Line
Vertical Grouped Bar (%) Bar (%)
Vertical Grouped Bar Bar
Vertical Linear Bar Gauge Linear Gauge
Vertical Linear Tank Gauge Linear Gauge
Vertical Stacked Bar Bar
Circular Bar Gauge (%) Circular Gauge (%)
Circular Gauge (%) Circular Gauge (%)
Horizontal Linear Bar Gauge (%) Linear Gauge (%)
Horizontal Linear Tank Gauge (%) Linear Gauge (%)
Vertical Linear Bar Gauge (%) Linear Gauge (%)
Vertical Linear Tank Gauge (%) Linear Gauge (%)

[Admin: The “Metric” type offers more options in addition to the “Chart” type. This post is related to the 04.17.17 post and 03.04.16 post about displaying a stacked bar chart, and the 04.05.17 post about displaying a mix of bars and stacked bars.]

Continue reading

How do you export a BIRT 4.5.0 report to SpudSoft Excel format?


I am designing a BIRT 4.5.0 report which has some images in it. While trying to export the report with the SpudSoft Excel Emitter, it results in an HTML page. My requirement is to export it into a multiple-sheet workbook. That’s why I went with SpudSoft. Any suggestions on how to get the Excel format via the SpudSoft option?

[Admin: To see other related posts, use the BIRT tag or Excel tag.]

Continue reading

Is there a way for summary report drilldown to show specific lines?


I have a summary report that has two BOs, grouped first by project, and then by cost code, and summed by amount.

When the report runs, it shows the totals as expected. When I click one of the lines in the report, I expect to see a tabular report showing, for that project, cost code, and amount, the values that contribute to the total only. Instead, all the projects and all the cost codes are displayed, as well as what I want to see. Is there a way in a summary report to click on a line and see only the lines that make up the total?

Unfortunately, it is not possible to configure the report to do what you are expecting here. You may want to develop a BIRT report to accomplish this. You could look at hierarchical reports as an option as well, but you might lose some of the summary options. You might want to submit a request for enhancement (RFE) on this.

[Admin: To see other related posts, use the Summary tag or Drilldown tag.]

Continue reading → 

IV96379: BIRT “Export Report” option defaults to PostScript


With TRIRIGA 3.5.2.1 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 3.4.2.5 production version, it is defaulted to “Excel”. We want this export report option to be defaulted to “Excel” in TRIRIGA 3.5.2.1 as well. Only after upgrading from 3.4.2.5 to 3.5.2.1, 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.]

Continue reading

Why doesn’t canceling the BIRT request stop the report process?


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

Continue reading

How do you fix failure to export reports to Excel due to timeout?


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

Continue reading