The SESSION_HISTORY table uses 500GB of disk space in our production environment. What is the best way to clean it up?
You would want to make appropriate backups and test this thoroughly, but this is something that can be done via the Platform Maintenance Scheduler (formerly Cleanup Agent) in the IBM TRIRIGA Admin Console. You can develop SQL to do the cleanups as they meet your business requirements, add that as a new cleanup command at the bottom section of the window, and then add a new Cleanup Schedule event in the top section of the window to have it run periodically.
This may be something that you want to reach out to a business partner for assistance with, depending on your skill and comfort level in implementing such a change. If so, you can search the IBM PartnerWorld portal.
[Admin: To see other related posts, use the Sessions tag or History tag.]
Our client is experiencing logout issues when using Perceptive apps on their iPad.
The link to the Perceptive app is passing through a DMZ, and upon initial login, the users are able to navigate the apps on the iPad without issue. But when a new session is started on their desktop, they are logged out of their current session on the iPad. After the users log back in, there are 2 consistent behaviors: (1) the iPad log constantly force-closes the session on the desktop or (2) there is a back and forth between the desktop and iPad sessions.
We’re unsure of how, or if, SSO is playing a part in this, or if we’ve missed a setting that will enable both sessions to stay open for as long as the timeout setting allows. We have attempted to use this solution (IV96586), but have not seen improvement.
When one SSO session is opened, it will log out the user from any other locations. I would ask users to stick with one device and avoid using multiple devices. If they need to use the apps and their desktops simultaneously, then you should provide them with a link to the UX apps for their desktops.
[Admin: This post is related to the 06.10.17 post about the UX session timeout on the iPad. To see other related posts, use the Timeout tag.]
If you attempt to revise a project from the Schedule tab, where the Gantt chart is visible, your session is expired and you receive an invalid session error. The issue was observed in Internet Explorer and Chrome, but not in Firefox.
An analysis from a Fiddler trace shows that when revising the project in Chrome, this POST to GanttDataUpload.jsp seems to kill the session. In Firefox, for whatever reason, this POST doesn’t occur, and the state transition is successful. To confirm that this is the scenario you are experiencing, use the following technote to run a Fiddler trace and check for the same GanttDataUpload.jsp call: IBM TRIRIGA using Fiddler for tracing web browser traffic.
As a temporary fix, use Firefox. When the record is in a read-only state, no Save action should be called on the Gantt. Moving forward, we resolved the session-kill issue when the user performs a Revise action on a project in the Schedule tab.
[Admin: This post is related to the 08.18.15 post about using Fiddler to trace TRIRIGA web traffic. To see other related posts, use the Gantt tag or Fiddler tag.]
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.]
Event: July 27, 2017, 12:00 PM to 8:00 PM Pacific Time (Topgolf in Roseville, CA)
I want to invite you to a free one-day Facilities Management event at Topgolf in Roseville, CA, outside of Sacramento, CA. Whether you are an IBM TRIRIGA or IBM Maximo user, these sessions will provide you with best practices to implement into your organization. Session topics include:
- Using Projects to Assemble Financial Data
- Making the Most of Key Performance Indicators to Measure What Matters
- Using Facility Condition Assessment to Manage Your Assets & Maintenance Budgets
- Capturing Required Inspection Data Electronically to Ensure Organizational Compliance
- Asking the Experts
- Networking Made Easy with Topgolf
This event has a limited number of seats so first come first served! Please RSVP here. Download the PDF agenda here. If you have any questions, please reach out to us at email@example.com.
[Admin: This post is related to the 02.06.15 post about exploring the TRIRIGA user group community. To see other related posts, use the Community tag.]
In TRIRIGA 18.104.22.168, the user’s session was terminated by the server due to a missing security token on the request when interacting with forms and large queries.
We needed to add a TRIRIGA security token to two locations in the reporting engine. Moving forward, we resolved an issue that could cause a user’s session to be terminated if the user interacts with an editable query before the query has finished loading.
[Admin: To see other related posts, use the Tokens tag or Editable tag.]
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.]