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 evaluating script in TRIRIGA not BIRT Designer

In the BIRT report, I use a script to retrieve data. In the BIRT designer, everything is working fine, but TRIRIGA gives an error. Does anyone know what might be the problem?

2017-03-29 10:38:55,774 WARN [org.eclipse.birt.report.engine.script.internal.ScriptExecutor](WebContainer : 6) There are errors evaluating script "importPackage(Packages.java.lang);
ReferenceError: "DataRequestSession" is not defined. (/report/method[@name="beforeFactory"]#8)
org.eclipse.birt.report.engine.api.EngineException: There are errors evaluating script "importPackage(Packages.java.lang);

[Admin: To see other related posts, use the BIRT tag or search “BIRT script error“.]

Continue reading

Why aren’t images being displayed in BIRT report?

Is there a bug in TRIRIGA 3.5.1 or BIRT 4.6 that is neither displaying images in the report in Eclipse, nor when the report is imported into TRIRIGA? I am using a TRIRIGA-scripted data source and not a JDBC data source. The reason I ask is because I have tried to get the triImageIM field displayed as an image in the BIRT report, but it does not work. I have tried the following options:

  • 1. Bind the triImageIM field to an Image element using Dynamic Image.
  • 2. Bind the triImageIM field to an Image element using URI.
  • 3. I have also tried changing the data type to BLOB as well as used getNativeValue() method.
  • 4. I have also tried to get the Image from the Documents data set, but it still does not work.

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

Continue reading

How do you install BIRT Designer 4.6.0 with TRIRIGA 3.5.1 and later?

Starting in TRIRIGA 3.5.1, a new BIRT engine was introduced with your TRIRIGA installation. This is BIRT engine version 4.6.0.

To customize or create new reports, as well to convert your old BIRT 4.3.1 reports, you need the same BIRT Designer version. This Designer runs on the Neon Eclipse platform and you can use your current Java 1.8 with it (in older designers, you needed a Java 1.6, 32-bit, to make it work). This new version is optimized for Mac (in older versions, a lot of manual steps were needed). Also, you can have it as an application now. For Windows, it remains a folder in the location of your choice.

Another often-raised topic is about “upgrading from 4.3.1 to 4.6.0”. The fact is you can have both installed in your machine. They are separate installations. The caveat here is that you cannot use the same workspace for 4.6.0, if you already have 4.3.1 installed, so you just need to rename the workspace used for the first time.

So let’s start with what you need…

[Admin: This post is related to the 08.19.16 post about failing to connect with 3.5.1, and the 08.18.16 post about getting an HTTP Error 500.]

Continue reading

ValuD: Is TRIRIGA OOB reporting good for your business needs?

In this era of big data and predictive analytics, the Facilities Management industry has undergone a sea change in terms of data management and utilization… In such a scenario, the question arises as to whether the in-app reporting features offered by these tools, like the Report Manager offered by IBM TRIRIGA, are comprehensive enough for the purposes of strategic management and analysis. In order to analyze whether IBM TRIRIGA ad-hoc reporting capabilities can satisfy the reporting requirements of your business, you first need to recognize its scope and limitations…

The idea behind ad-hoc reporting is to enable users to create their own report. They should be able to decide on the fields, sorting, or grouping that they might require in their report. By letting the user decide on these criteria, ad-hoc reports ensure that a significant portion of the development time is freed, since the developer no longer needs to produce reports based on individual report requirements.

By and large, IBM TRIRIGA ad-hoc reporting, in itself, should be comprehensive enough for most businesses. But on the other hand, if extensive formatting is what you need, the IBM TRIRIGA ad-hoc report manager may not be enough. IBM TRIRIGA has sought to overcome this limitation by integrating with Eclipse BIRT. Business Intelligence and Reporting Tools (BIRT) is an open source reporting and business intelligence tool which IBM TRIRIGA advanced reporting uses to create data visualizations and reports. Using an IBM TRIRIGA plugin for the BIRT application, you get to experience the power of data mining and predictive analytics, right there, in your IBM TRIRIGA Report Manager…

[Admin: This post is related to the 09.28.16 post by ValuD about when to use OOB in-app reporting versus BIRT reporting.]

Continue reading

IV88018: Eclipse BIRT Designer fails to connect with TRIRIGA 3.5.1

The BIRT plugin that comes with TRIRIGA and 3.5.2 installs fine in Eclipse 4.3.1, but the connection to TRIRIGA fails. After installing BIRT Designer all-in-one with Eclipse Kepler version 4.3.1 as recommended in the Compatibility Matrix for 3.5.1, we went ahead and pointed to your TRIRIGA URL to install the 3.5.1 BIRT plugin version 1.0.1v201607281127: http:// <server>:<port>/<context>/eclipse. But when connecting to the /remote URL for 3.5.1, a connection error is thrown.

As a temporary fix, upgrade to the 2016 version of Eclipse (4.6) and the corresponding newer BIRT plugins, and you will able to use to the newer TRIRIGA 3.5.1 plugin. To render reports, a platform upgrade to 3.5.1 and later will need to be also upgraded to the 2016 version of Eclipse (4.6) and the corresponding newer BIRT plugins. This is a documentation APAR. We will update the Compatibility Matrix to reflect the use of the new correct version of Eclipse/BIRT.

Continue reading

Getting an HTTP Error 500 when previewing BIRT form reports

I recently upgraded to TRIRIGA platform 3.5.1 and installed Eclipse Kepler 4.3.1 per the 3.5 Reporting User Guide. I can import, create and preview a query report.

But when I import and create a form report, I get an error when trying to preview using View Report as PDF. HTTP ERROR: 500 Problem accessing /viewer/preview. Reason: Server Error. Powered by Jetty. Trying to preview in Web Viewer gets the same error except: Problem accessing /viewer/frameset. I have recreated this in multiple environments, including an OOB install of TRIRIGA 3.5.1. Please advise.

If you upgrade the BIRT Designer to version 4.6 that runs with Java 8, this issue should go away. We will be updating our Support Matrix to state that Designer 4.6 is required for preview to work… Are you running the Windows operating system for your application server? If you are, you will want to apply the Fix Pack which is available on Fix Central. It has a fix specific to BIRT and Windows OS.

Continue reading