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 another way to restart TRIRIGA service without BAT files?


To keep TRIRIGA from dropping servers, I have to restart the TRIRIGA service every night. Does anyone else have to do this? If so, how are you doing it?

I execute the “shutdown.bat” then the “run.bat” via Control-M. The location of these two BAT files are: D:\Tririga_3.5.1\wlp\bin. But the “binserver.bat” file does not exist: D:\Tririga_3.5.1\wlp\binserver.bat start tririgaServer. I’m using the WebSphere Liberty Profile (WLP) and it’s set up as a Windows service as well. Can I just restart the Windows service instead of the BAT files? Why doesn’t the “binserver.bat” exist?

The “run.bat” file seems to work just fine, but my Control-M job gets hung up. So I would like to find another way to restart the service if possible.

[Admin: This post is related to the 06.16.16 post about restarting TRIRIGA on WAS Liberty Profile in Windows, and the 04.28.16 post about running a WAS Liberty Profile as a Windows service.]

Continue reading

How do you activate GC tracing for WebSphere Liberty (WLP)?


How do I activate Garbage Collection (GC) tracing for my IBM TRIRIGA application running on WebSphere Liberty Profile (WLP)? I need to start tracing GC for WLP to check if there are performance or stability issues due to GC runs.

[Admin: This post is related to the 09.29.14 post about tracing WebSphere GC runs for a TRIRIGA server.]

Continue reading

Finding a TRIRIGA shutdown issue with WebSphere Liberty Profile


There is a potential issue with the shutdown process for TRIRIGA. This is specific to versions prior to TRIRIGA 3.5.1 running under Windows with WebSphere Liberty Profile (WLP). We have found that the “shutdown.bat” file may not end the session. If you encounter this issue, you can resolve it by adding the path as described below.

In TRIRIGA 3.5.1, for both the “run.bat” and “shutdown.bat”, we include a step to change directory (cd) to the location of the “server.bat” file as described below. (In Microsoft Notepad, there are no spaces or carriage returns between the rows.)

@echo offset JAVA_HOME=/home/tririga/jdk1.8.0_91cd /d /home/tririga/351x_23001/wlp/binserver.bat stop tririgaServer

It looks like this in other viewers:

run.bat:

@echo off
set JAVA_HOME=/home/tririga/jdk1.8.0_91
echo JAVA_HOME : %JAVA_HOME%
echo CLASSPATH : %CLASSPATH%
cd /d /home/tririga/351x_23001/wlp/bin
server.bat start tririgaServer

shutdown.bat:

@echo off
set JAVA_HOME=/home/tririga/jdk1.8.0_91
cd /d /home/tririga/351x_23001/wlp/bin
server.bat stop tririgaServer

However, in previous TRIRIGA versions, that path is not included:

TRIRIGA 3.4.2 (shutdown.bat):

@echo off
set JAVA_HOME=/home/tririga/jdk1.7.0_80
server.bat stop tririgaServer

TRIRIGA 3.5 (shutdown.bat):

@echo off
set JAVA_HOME=/home/tririga/jdk1.7.0_80
server.bat stop tririgaServer

If you encounter an issue where the “shutdown.bat” file is not working, you can resolve the issue by adding the path to the “server.bat” file similar to the example below.

TRIRIGA 3.5 (shutdown.bat):

@echo off
set JAVA_HOME=/home/tririga/jdk1.7.0_80
cd /d /your_path_to_tririga/wlp/bin
server.bat stop tririgaServer

[Admin: Oddly, this post is repeated in the 08.24.16 post by Support. This post is also related to the 06.16.16 post about restarting TRIRIGA on WebSphere Liberty Profile.]

Continue reading

How do you configure IIS and SSO on TRIRIGA 3.4.2 with WAS Liberty?


Does anyone know how to configure IIS and SSO on TRIRIGA Platform 3.4.2 with WebSphere Liberty Profile (embedded)? We have just upgraded our TRIRIGA Platform to 3.4.2 and run into difficulty in configuring IIS. Our application and process servers are on Windows Server 2012 and our database is on SQL Server 2012.

[Admin: This post is related to the 07.22.15 post about an issue with IIS SSO, WAS Liberty, and TRIRIGA 3.4.2.]

Continue reading

IV82559: Expression editor for Start tasks does not appear


The expression editor for the Start task does not display for the following workflows. These can be found under: triContract > triRealEstateContract.

  • triOwnedProperty – Synchronous – Map Template Data to Parent
  • triOwnedProperty – Synchronous – Apply Template
  • triOwnedProperty – Synchronous – Create Sale Term Smart Record

In TRIRIGA platform releases prior to 3.4.2, the Start task displays without issue, but does not display in 3.4.2 and 3.5. There is no information in the log files, and it happens under WebSphere 8.5.5.7 and WebSphere Liberty Profile (WLP) application servers. Object-migrating (OMing) the workflows from a good environment, and also removing the Start conditions and OMing the workflows does not resolve the issue. The only workaround is to rebuild the workflows from scratch.

As a temporary fix, you can rebuild the workflows from scratch. Moving forward, all workflows should now show the expression editor properly when opening up the Start task details.

Continue reading