IV97203: Hierarchical query for buildings with assets ends session


Users navigating to a hierarchical query of building and asset records have experienced user kickout (or timeout) behavior when entering or clearing filters.

We needed to prevent the load of a large hierarchical query with runtime user filters in a portal section that kicks the user out. Moving forward, we resolved an issue that could cause a user’s session to be terminated if the user interacts with an hierarchal query before the query has finished loading.

[Admin: This post is related to the 06.19.17 post about a user session terminated due to a missing security token. 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

How do you set the TRIRIGA session expiration warning in the portal?


The IBM TRIRIGA Application Platform has the ability to notify users on their portal if their session is about to expire. The message will not be displayed on any popups or modal windows, only on the main portal page.

To allow the alert message to be displayed on the portal to a user whose session is about to expire, set SESSION_WARNING_ENABLED=Y in TRIRIGAWEB.properties. By default, it is N. The default alert timeout threshold is 2 minutes before the session is set to expire, as follows: SESSION_WARNING_THRESHOLD=2.

The session expiration timeout itself can be found in the following locations:

  • WebSphere Liberty:
    • Edit wlp/usr/servers/tririgaServer/server.xml.
    • Update the invalidationTimeout value in seconds.
  • WebSphere:
    • In the Websphere Console, navigate to Servers > Application Servers > Your Server > Web Container > Session Management and/or Applications > Enterprise Applications > Your Application > Session Management.
  • Oracle WebLogic:
    • In the WebLogic Console, navigate to Your Domain > Deployments.
    • Expand the tririga-ibs deployment node. Expand the Modules node.
    • Click on the context root node. (The context root was selected during TRIRIGA install. The default name is “/”.)
    • Select the Configurations tab.
    • Enter a value for Session Timeout (in seconds), and Save.
    • You may be asked to select a location for Plan.xml, which will be generated upon saving.
    • You may need to restart the WebLogic Server.

Continue reading