Our customer has seen an issue when installing TRIRIGA 3.5.3 (Linux, Server build number: 276955) on an existing database (on 3.4.2 / 10.4.2). Everything goes well until starting up the server. Generally, TRIRIGA will run a database upgrade on the first startup when a build number difference is detected.
In the OM log, we notice that TRIRIGA tried to import the upgrade OM package… The import process started with the triPlatformObjectLabelManager package, but it failed to import a navigation item, which is newly created for Object Label Manager. I haven’t found any log which can explain this failure. I’ve checked the NAV_ITEM table. This navigation item wasn’t there before the upgrade process. Then all of the other packages are stuck on a pending status. Nothing happens after “Creating package from Zip file”. This behavior causes a lot of SQL update failures.
Meanwhile, on our Dev environment (Windows, Server build number: 279835), the upgrade went very well. You can find the difference in the logs. The OM log was set on “Debug” level on both servers. Note that the build number is slightly different between these two enviroments. Have you seen this kind of issue? Where can I find more details about the navigation item import failure?
[Admin: This post is related to the 02.17.17 post and 05.19.16 post about inconsistent OM validation results. To see other related posts, use the Object Migration tag or Upgrade tag.]
Is it possible to download the imported OM package from the front end or server?
Yes. Go to Tools > Object Migration. Locate the OM package, click the “Copy Package” icon link to the left of the OM name, then in the upper-right, click “Export”. Give it a name, click “Export”, then it will ask you to “Open” or “Save”. I would “Open” the ZIP to see where it was stored. There you have it!
[Admin: To see other related posts, use the Object Migration tag.]
In the IBM TRIRIGA 3.5.3 and 10.5.3 release, the Group object was redesigned to leverage query sections, instead of a single large smart section. The query sections improve the performance and usability of the Members tab by paginating the results, and providing filtering capabilities. These application changes are a part of the IBM TRIRIGA 10.5.3 application upgrade object migration (OM) package, but can be applied to systems running older application versions.
To help anyone who would like to apply the Group enhancements to an environment not running 10.5.3, the Group_Query_Enhancement_10.5.3.zip can be downloaded from this wiki. This is an unsupported object migration (OM) package that includes the Group form, queries, and workflows that were created to enhance the application. This OM package can be imported into an environment running on the 3.5.3 platform release.
Note: This enhancement requires the 3.5.3 platform release for the “Add” and “Delete” functions to work within the query section. There are new custom tasks that are called by workflows that handle the adding and removing of group member records, when users or groups are selected. Before applying this OM to a production system, the OM package should be tested in a test or development environment first.
[Admin: This post is related to the 03.07.16 post about best practices for managing your security groups. To see other related posts, use the Security tag.]
I exported the .rpt and the properties file from BIRT report designer, zipped it, and then saved it in the TRIRIGA Document Manager under the respective object (in this case, triProject). I then modified and updated my query report as “External”, and then in the “Options” tab, pointed to the ZIP file from BIRT. However, when I run the report to view the BIRT report, I get a MID error. Meanwhile, the BIRT report works fine when I run it in BIRT report designer.
[Admin: This post is related to the 03.29.17 post about getting an error when evaluating script in TRIRIGA but not BIRT designer, and the 05.11.16 post about running a BIRT report ZIP. To see other related posts, use the BIRT tag.]
The IBM TRIRIGA Workflow Analysis Utility analyzes workflow performance and process execution. The utility reads IBM TRIRIGA performance logs and displays performance analytics for workflows, including workflow execution time, and process flow (the order in which workflows ran and what triggered them to run).
Download and unzip the WorkflowAnalysisUtility.zip file. Included in the ZIP file is a WFAnalysisUtility.pdf file that contains instructions on how to use the utility. The utility does not require installation, but some configuration might be necessary to get it to run in your environment.
The utility has been updated to use Java 8.
[Admin: This post is related to the 05.27.16 post about the Workflow Agent slowing down, and the 03.13.15 post about an issue with the utility.]
I am looking for additional information on the definitions and use of the Shared Capacity Factor, Emergency Capacity, and Overflow Capacity fields in the space record… I cannot seem to find these terms mentioned in the user guides. Is there any documentation on this topic that I am missing?
[Admin: This post is related to the 12.11.15 post about where to find TRIRIGA user guide PDFs in a single ZIP.]
Is it possible to display a set of stored numbers in a field as a barcode in a BIRT report using TRIRIGA data?
The current TRIRIGA BIRT report engine, 4.3.1, does not support displaying barcodes. However, there is a workaround that is not supported by IBM, and depends on customer report development skills to implement it. Note that we are publishing this information to make clients aware of the possible solution. IBM Support cannot assist in any way with implementing or troubleshooting this solution.
These are the basic steps and implementing it might require some changes depending on your report and environment:
- 1. Use Dynamic Text element, and in the expression, put in the value for the field to be presented as a barcode (i.e. row[“triTask__triWorkTask____triIdTX”] if you want the ID to be presented as a barcode).
- 2. Update the font property to use Code128. This is an open source font and available on the web, in case you do not have it already in your BIRT designer.
- 3. After making all of the changes, save and export the report, making sure the .rptdesign file is in the root of the ZIP file, import it into Document Manager, and test it.
[Admin: This post is related to the 05.11.16 post about running the BIRT report ZIP in TRIRIGA.]