When a BIRT report has a record with multiple entries and its exported
to PDF, the users do not see all entries. To resolve this issue,
navigate to the report settings. Under the Property Editor in Eclipse,
change the Layout Preference to Auto. See screenshot below:
Thanks for the info Kenny!
Showing posts with label tririga. Show all posts
Showing posts with label tririga. Show all posts
Thursday, June 23, 2016
Wednesday, February 11, 2015
Upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0 to the most current application and platform releases
Upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0 to the most current application and platform releases
To upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0, you must upgrade TRIRIGA, TRIRIGA Application Platform, apply object migration packages, and run patch helpers.
Check the release notes for the packages you are installing for details about new features and fixes for the release. Refer to the release version summary table for a summary of the TRIRIGA releases available.
- Shut down the application server.
- Upgrade the platform to IBM® TRIRIGA Application Platform version 3.4 as described in the IBM TRIRIGA Application Platform version 3 Upgrade Installation Guide.
- Start the server and ensure the server startup processes are running.
- Apply the TRIRIGA version 10.1 minor release cumulative package.
- Restart the application server.
- Apply the TRIRIGA version 10.2 minor release package.
- Restart the application server.
- Update DateTime system fields from VARCHAR to NUMERIC
- Apply the TRIRIGA version 10.3 minor release package.
- R epublishing Business Objects for Localization
- Apply the TRIRIGA version 10.3.1 mod release package.
- Apply the TRIRIGA version 10.3.2 mod release package.
- Apply the TRIRIGA version 10.4 minor release package
- Apply the TRIRIGA version 10.4.1 mod release package.
- Importing Patch Helper Records.
Taken from https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Upgrade%20from%20TRIRIGA%20version%2010.0%20and%20TRIRIGA%20Application%20Platform%20version%203.0%20to%20the%20most%20current%20application%20and%20platform%20releases
Wednesday, October 22, 2014
IBM TRIRIGA CAD Integrator Tutorials
Check out the new video tutorials on YouTube about IBM TRIRIGA CI
http://www.youtube.com/playlist?list=PLiD3_RDV00Je4i5UEzoWrTJgz_GW2gbCZ
IBM TRIRIGA Performance Best Practices
Over the last few months I have seen an increase in performance related tickets that have come into the TRIRIGA call center. The vast majority of those tickets were resolved by following all of the recommendations outlined in the Performance Best Practices Guide and the document can be found at:
With this entry I will discuss two of the most common items from that document the I have seen.
1. Workflow instance saving.
By Default, TRIRIGA ships with this value being set to 'Errors Only' in the TRIRIGAWEB.properties file and this is also the recommended setting for production environments. This is a very important setting since enabling workflow instance saving can cause a tremendous amount of additional overhead from a performance perspective. Additionally, the cleanup agent may run longer than expected or run into a normal workday if there is a significant amount of data that needs to be removed. Keep in mind that this setting can be enabled and disabled from the TRIRIGA Admin Console without the need of a restart.
2. Production Mode
Production mode is also another way to improve performance and is also recommended to be enabled in production environments. This setting enables data from the database to be cached in memory.
The Performance Best Practices Guide has more great information on these settings as well as additional recommendations that will provide a positive performance impact to most any environment.
Taken from https://www.ibm.com/developerworks/community/blogs/8eeee156-f1f3-45ec-970c-53b17ccb452a/entry/tririga_performance_best_practices?lang=en
Subscribe to:
Posts (Atom)
