Why do reports with filters create long URIs in TRIRIGA

It looks like TRIRIGA changed the way that reports are generated. After we enter a user filter and refresh, a very long URI is generated, which causes an error on the IBM HTTP Server: “Request-URI Too Large”. Previously, with an OOB query, the URL might look like: /html/en/default/reportTemplate/viewPageReport.jsp. But now, the URL is excessively long.

It looks like the filter details were sent in as headers to the server. But now, they are included in the URI. This is a major change for a fix pack and I believe that it shouldn’t have been included. This pretty much limits the number of columns and user filters that a report can have. Our environment is hosted by IBM and we don’t have access to the back-end server.

We will be addressing this issue in our next fix pack.

[Admin: This post is related to the 05.26.17 post about getting an error that the URL is too large for queries with filters. To see other related posts, use the Filter 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

Is there a specific port number for CMIS integration with TRIRIGA?

I’m setting up a VPN between TRIRIGA 3.5.2 and FileNet (CMIS integration). Is there a specific port that is used for CMIS like there is for the mail server?

The CMIS integration is done via HTTP. In the TRIRIGAWEB.properties file, you set the URL to the CMIS server service in the property: CMIS_URL. If the value of CMIS_URL is “http”, then it is port 80. If it is “https”, then port 443. Or if the port is defined in the URL, then that’s the port to open. For example, if CMIS_URL is http://filenet.mycompany.com:9080/fncmis/resources/Service , the port is 9080.

[Admin: To see other related posts, use the CMIS tag or ECM tag.]

Continue reading

IV94732: Error messages in the logs about missing favicon.ico

We have noticed through our web server access logs and monitoring tool (Dynatrace) that Chrome ignores the <html> tag for the location of the *.ico file. This is very minor, but CPU cycles are being wasted looking for this resource. Chrome doesn’t cache it either. The issue has to do with SSO and alternative sign on pages, but the easily reproduced step is to go to http://<tririga.server.com>/favicon.ico and it will show a 404 error.

There was no mapping to the favicon.ico directly in the web.xml. Moving forward, when the browser requests the default favicon.ico, the favicon configured in the /userfiles/icons is now sent to the browser, instead of getting a “404 Not Found”.

Continue reading

UX: Where can you find the TRIRIGA UX component documentation?

Component API documentation for developing applications with UX Framework is deployed with your TRIRIGA server. Component documentation can be accessed via the following endpoint:

  • http[s]://[tririga-hostname:port][/context_path]/p/web/doc
  • The [tririga-hostname:port] and [/context_path] are the specific values you’d normally use to access your IBM TRIRIGA environment.

Once at the component documentation page, you can browse or search the TRIRIGA delivered components that are available on your specific platform version using the left-hand panel. Further down in the list, you can find documentation for the available third-party components delivered with the corresponding version of Google Polymer. (This version varies, based on the TRIRIGA platform version. See the Support Matrix for more information.)

In the right hand panel, the documentation provides information about the selected component, generally with sample usage, styling and an API reference. In some cases, there are also demos available. You can toggle between the Doc and the Demo for a component using the buttons in the top right of the page…

[Admin: Similar content is also found in UX Article 2: Implementing UX. This post is related to the 12.11.15 post about the UX framework.]

Continue reading