Since early 2016, most browser vendors no longer support the Netscape Plugin Application Programming Interface (NPAPI) architecture. Most Java applet plugins for web browsers rely on NPAPI to render Java applets.
Impact to IBM TRIRIGA applications
The end of NPAPI support prevents the Java applet-based TRIRIGA areas — such as the Gantt, Availability, and Stacking sections — from rendering in IBM TRIRIGA applications on certain browsers.
Areas of TRIRIGA impacted by changes in browser support
The following IBM TRIRIGA areas are impacted. Details on each area follow.
- Gantt section
- Availability section
- Availability Legacy section
- Stacking section
- Other Java applet-based TRIRIGA areas…
[Admin: This post is related to the 04.07.16 post about TRIRIGA compatibility with browsers, and the 07.16.15 post about removing NPAPI support from Chrome.]
The TRIRIGA 3.5.1 compatibility matrix says that WebSphere 126.96.36.199 is supported, but also that “Future fix packs for this version are also supported.” If you run the TRIRIGA 3.5.1 installer with the full version of WebSphere 188.8.131.52 in place, the install works. If you try running with the full version of WebSphere 184.108.40.206 in place, however, the following error occurs:
“WebSphere Problem: WebSphere version is too old. The version of WebSphere that was detected is too old. IBM TRIRIGA Application Platform requires WebSphere version 220.127.116.11 or newer.”
This problem was seen when performing the TRIRIGA 3.5.1 install on Windows. It may exist when running the installer on other operating systems, as well.
Why are you having issues with record transitions in Microsoft Internet Explorer IE11? Having ended support for Compatibility View (Mode) in IE11, requests were made to provide this functionality in the TRIRIGA 3.4.x and 3.5.x release branches. This was done with releases 18.104.22.168 and 22.214.171.124, but simply implementing the change may not completely resolve the issue.
During deployment, a variety of page data is cached at the server level, and this cache is not cleared during the upgrade process. This can result in the compatibility changes not being apparent when a user first accesses the application after upgrade.
Clearing the cached content at the server level will eliminate the cached data as a possible cause.
[Admin: This post is related to the 09.29.14 post about clearing up the TRIRIGA application server cache area.]
Does IBM TRIRIGA support Microsoft Azure? It is not listed in any TRIRIGA Compatibility Matrix.
TRIRIGA supports any cloud offering that supports the same operating systems that the TRIRIGA product supports. The TRIRIGA team will never set up, test, or claim direct support of Microsoft Azure. If Azure supports an operating system that TRIRIGA supports (for example, Windows Server 2012 R2), you can use it. If an issue happens and it only occurs when run on Azure, you should raise the issue with Microsoft, so they can investigate why what should work on the supported operating system directly does not also work through their cloud platform.
[Admin: This post is related to the 01.28.16 post about Amazon Web Services (AWS).]
The BIRT plugin that comes with TRIRIGA 126.96.36.199 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.
The compatibility matrix for TRIRIGA 3.5.1 lists support for WebLogic and WebSphere only. So I’m looking for the pros and cons of each.
From the platform development point of view, we develop on Liberty… Liberty has all the core features that traditional WAS does, but is a much leaner footprint with less “things to go wrong”. If your organization has experience with traditional WAS, you can choose that, but you should still look at deploying with Liberty first. Only choose WebLogic if your organization has expert-level WebLogic developers and administrators, who keep up-to-date on Oracle training.
[Admin: This post is related to the 06.20.16 post about WebSphere Liberty versus traditional WebSphere.]
Where is the information regarding IBM TRIRIGA Application Platform 3.5.1 and IBM TRIRIGA 10.5.1 features, installation, and more?
[Admin: This post is related to the 12.11.15 post about finding 3.5.0 and 10.5.0 information, and the 10.01.15 post about finding 3.4.2 and 10.4.2 information. To see other related posts, search “where is the latest“ or “where can you find“.]