We are looking for an approach to the above issue which will keep the page alive. We have tried alternatives such as explicitly calling a data source. And we are looking at handling session cookies.
The UX app can make sure it does not time out by making a call to a specific end-point. You can make an Ajax call to the following URL, which will update the last access time and keep the session alive:
[Admin: This post is related to the 05.08.17 post about keeping the UX app session alive and connected. To see other related posts, use the Timeout tag.]
When emails are sent to TRIRIGA using Apple’s Mail client, they are not always being interpreted properly on the TRIRIGA end. Some problems include:
- When a rich-text email is sent using Apple’s Mail client and has an attachment, the attachment isn’t seen if the email history is present as part of the email. If the email history is removed, the attachment is seen.
- When a plain text email is sent using Apple’s Mail client and a PNG or JPG attachment is present, the attachment isn’t seen, but the email body has a marker that makes it look like an embedded image should be present (but isn’t).
- When a plain text email is sent using Apple’s Mail client and text exists in the email before the attachment, the text that exists in the email before the attachment isn’t seen. Any text that exists after the attachment is seen.
Apple mail formats the attachments and forwards differently than other mail clients. Moving forward, an issue that cause attachments to be missing and email bodies to lose content when the mail client puts attachments inline, has been resolved.
[Admin: To see other related posts, use the Attachment tag.]
Open CAD Integrator (CI) and attach a simple drawing to TRIRIGA 3.5.2. From CI, edit a space (it opens a browser session). From CI, launch a portal (it opens as a new tab next to the first space). From CI, edit a different space, then another one. Move from one TRIRIGA session to the next making a change to the name. For the main TRIRIGA page, just change tabs or open something else.
Initially, all seems well. But after a couple minutes, you will get this message on each tab or session as you return to them: “Sign In Required. Sorry, your session has either timed out or is no longer active. For security reasons you have been redirected to this page. Please sign in again to continue.” Then when you log back in, you are taken to the home page. Initially, it seemed that as long as one of the tabs remains open, you can open multiple TRIRIGA sessions from CAD Integrator. That does not appear to be the case. And the issue of most concern to Apple.
An issue was identified with SSO configurations and opening records via CI. Moving forward, an issue was resolved that would cause user sessions to time out after 3 minutes of inactivity, if the session was initiated by a CAD Integrator request.
[Admin: This APAR IV94643 is duplicated by APAR IV94555.]
Can you change operating systems? That is, start with Linux and migrate to Windows. Currently, we’re on TRIRIGA 3.3.1 and upgrading to the latest platform, and in the process, we would like to move to Windows Server. A related but hypothetical question: Can you run TRIRIGA with the app server on Linux and the process server on Windows?
TRIRIGA is OS agnostic. You can run a Linux app server and Windows database server, and vice versa. You could even throw AIX in the mix and have that run the process server, or any mix there of. In the lab, we have OS X MacBook Pros with a mixture of Windows and Linux VMs. Personally, I think Linux+Intel is a more stable server platform that has far fewer up-time issues versus Wintel (Windows+Intel). These days, most shops are migrating from Windows to Linux.
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.]
I’m not sure if the supported OS list includes iOS officially. With the advent of iPad Pro devices, the line between iPhone-like devices and computers gets further blurred. After all, an iPad Pro begins to feel a lot like a MacBook Air. There is support for Safari on a computer as well, and generally the move is to become device-agnostic.
But I need to put forth some guidance about iPad Pro devices and TRIRIGA. My initial observation is that some basic functions don’t work correctly, perhaps HTML5 related? For example, rendering the portal. The page starts loading correctly, then the screen jiggers a bit and seems to stabilize, but scroll bars never appear and the user cannot move up or down. I’ve tested in both Safari and Chrome.
Official support of IBM TRIRIGA on iPad is limited to the IBM TRIRIGA UX Framework and Perceptive Applications. Traditional TRIRIGA, portal, and non-UX applications are only supported on Windows and Mac OS X operating systems when running Safari, Chrome, Edge, Firefox, or IE11. Although a lot of non-UX TRIRIGA will load on an iPad, you will run into some limitations as you have noted above…
When you open a new browser window and log into TRIRIGA again, you kill the previous session on the original logged-in tab. This is reproduced in all browsers in Windows and Mac OS (Safari, Chrome, Firefox), and this is working as designed where signing in again closes the previous logged-in sessions. But there is another way to open new tabs and preserve the logged session.
In Firefox, you’re able to right-click, for instance, in the Reports tab and select “Open in a new tab”. Both tabs will have the same active TRIRIGA session, that is, the original session is preserved and you can use both tabs to navigate. When tested in Safari though, it does not work like that. It should, so this was reported as a defect…