With TRIRIGA Anywhere, I was wandering is there any way to track the date/time when the asset barcode was read with a mobile device?
In our TRIRIGA Anywhere app, a user cannot login if the region is set to Panama on his/her iPhone. We can add a new Language to the system “Languages” list (e.g. “Panamanian”). A row can be inserted into the LANGUAGE_DETAIL table with LANGUAGE_ID referencing the LIST_VALUE_ID that was produced by adding the list value. This results in “Panamanian” being displayed in the Language Manager.
However, even though the LANGUAGE_DETAIL record indicates a value of “en_PA”, it is presented as “en_US” in the manager. It is possible to change the locale code and click “Save”, but appears to only accept the previously defined values. For example, changing any of the values to “en_GB” and saving works correctly. If an unrecognized code is entered (such as “en_PA”), it reverts to “en_US” upon saving. I’m not certain if there is a table somewhere that stores the “supported” region codes, or if it just uses the supported list of Java locales.
Can anyone help with settings in the TRIRIGA application for first-time login to the TRIRIGA Anywhere app? We are getting an error in the log:
com.tririga.platform.integration.oslc.oslc.oslc request dispatcher impl large thread pool...
I installed MobileFirst Server, set up TRIRIGA Anywhere, installed MobileFirst Studio on Eclipse Mars 2, and made some changes in the Work Task Management application. After updating and viewing the result in a simulator, I attempted to export the Android application, but it gave me some errors. I need some help from someone who worked on the TRIRIGA Anywhere app and MobileFirst Platform.
Mani Sanjeevi: Apologies to the TRIRIGA folks! There was one request posted in our TRIRIGA group that has been addressed immediately and deleted from the group.
TRIRIGA Anywhere users can be handled like any other TRIRIGA users. When sizing the TRIRIGA environment, include TRIRIGA Anywhere users in the overall concurrent user count and follow the appropriate sizing guidelines for the TRIRIGA application and database servers:
However, it is recommended to add a separate process server to the environment specifically to handle the OSLC calls for TRIRIGA Anywhere. This server can be sized similarly to the standard process server as outlined in the above links for each environment.
In addition, TRIRIGA Anywhere requires a MobileFirst server. To size this server, follow the guidelines from the document: Scalability and Hardware Sizing for MobileFirst Platform Foundation 7.1. Other TRIRIGA Anywhere performance recommendations can be found in the TRIRIGA Best Practices for System Performance [PDF] white paper.
We are experiencing an IBM TRIRIGA Anywhere issue, where the timeout value specified in our configuration is being ignored and an error is resulting.
There might be near-term iFix. Note that this is not an IBM TRIRIGA Application Platform APAR. It should be an IBM MobileFirst APAR.