One of our customers is trying to apply all the best practices from the TRIRIGA documentation with different recommendations. One of them is regarding:
- ALLOW_SNAPSHOT_ISOLATION: SET ALLOW_SNAPSHOT_ISOLATION should be set to ON
- READ_COMMITTED_SNAPSHOT: SET READ_COMMITTED_SNAPSHOT should be set to ON
Their database department is telling them that if they activate this parameter, they could be doing “dirty reads”. Mainly, if they read and modify in the same tables at the same time. They said that other products control this situation. They wanted to know if TRIRIGA controls it. In case that TRIRIGA controls these situations, they will change it. Can you please confirm if they should set this parameter to ON?
TRIRIGA controls data integrity within the context of the web application. These settings for MS SQL make it behave more like Oracle and DB2, and we recommend that they be set to ON.
When upgrading to TRIRIGA 3.5.2, an error related to importing EsriJS system objects may appear in the server.log:
2016-12-21 15:05:39,826 INFO
[com.tririga.util.startup.upgrade.systemobject.EsriJSOMUpgrade](server.startup : 1) Unable to import EsriJS System Objects, required application dependencies are most likely missing...
If this happens, the following error may appear in the ObjectMigration.log as well:
2016-12-21 15:05:39,825 ERROR [com.tririga.platform.om.service.AbstractOMObjectImportService] [\TRIRIGA GIS Widget View Mode] group 1) Group Import failed - com.tririga.platform.versioning.recorddata.RecordDataVersioningException: Snapshot is not enabled for the Business Object Group, in the Module Group...
This problem appears to be the result of the 3.5.2 upgrade script, that enables snapshot functionality on the Group business object, running after the upgrade script that loads EsriJS components, during the initial 3.5.2 app server startup. The EsriJS upgrade has a Group that it is trying to import, and this is causing Group snapshot functionality to fail, since the necessary snapshot changes have not yet been applied to the Group business object.
The license metric table is not being populated after upgrading to TRIRIGA 3.5.1.
The Concurrent License Agent was prevented from restarting, and was not recording the license metric snapshot value, because of stale data in the agent registry.
[Admin: This post is related to the 03.15.16 post about the Concurrent License Agent.]
IBM TRIRIGA uses either the Tivoli Directory Integrator (TDI) ETL development environment Configuration Editor, or the Pentaho ETL development environment Spoon to generate transform XML files. These transforms, when run through the API, move data from source to destination tables. In IBM TRIRIGA, ETL scripts are used to periodically take snapshots of the transactional data. These snapshots are time stamped and stored in metric fact tables. Metric queries use the information in the metric fact tables to visually display the information in metric charts.
UX Framework: Object Migration
Sandy Garcia, TRIRIGA Platform Developer, presents the new object migration enhancements, which support our classic platform and UX Framework. First, she gives an overview of the classic object migration concepts. Next, she dives deeper into the UX metadata support, after-import workflow, and modified-by support.
UX Framework: Object Labeling
Tom Fitts, TRIRIGA Platform Developer, presents the new object versioning enhancements, which support our classic platform and UX Framework. First, he gives an overview and roadmap of object labeling. Next, he dives deeper into the snapshot (versioning) of UX metadata, object label definitions, and best practices.
[Admin: This post is related to the 12.11.15 post about the UX framework. This post is also related to the UX Articles, UX Videos, and UX Lessons blog pages.]
We are getting questions from the business about the ability of TRIRIGA to capture and store snapshots of data in the database for historical purposes. Is anyone using TRIRIGA to do this? What is the process you’re using? What are the Pros? What are the Cons?