You can configure TRIRIGA to use Tivoli Directory Integrator as its ETL runtime engine to run ETLJobItems from within TRIRIGA.
Before you begin
Install Tivoli Directory Integrator, if not already installed, on all the TRIRIGA systems that could run a TDI ETL Job Item. During the TDI install:
- Make note of the installation directory you enter on the Destination panel. You will enter this value later in TRIRIGAWEB.properties.
- Select either installation type. TRIRIGA requires only the TDI Server component.
- When prompted for the location of the Solution Directory, you can select any option. TRIRIGA specifies its own solution directory at runtime. However selecting the option “Use Install Directory” may simplify troubleshooting.
- Make note of the value you enter in the Server Port field on the Server Port Values Panel. You will enter this value later in TRIRIGAWEB.properties.
- Clear the “Start the Configuration Editor” check box on the Install Complete panel.
- Note: This step is very important for TDI/TRIRIGA integration to work. After you have installed Tivoli Directory Integrator, update it with the recommended fix packs (per TRIRIGA support matrix). TDI must be at least at FP04 (126.96.36.199) or it will not automatically start the TririgiaETLDispatch.xml assembly line which will result in ETL job items failing to run successfully.
- Edit TRIRIGAWEB.properties file to enable TRIRIGA to manage TDI server. Set the following properties…
- Install a JDBC driver library so that Tivoli Directory Integrator can use it to access TRIRIGA database…
- Edit TDI global.properties file to allow TRIRIGA to check and stop the TDI server from localhost without requiring authentication and authorization certificates. Set the api.remote.ssl.on property to false to tell TDI to trust requests from localhost…
- Start Tivoli Directory Integrator Agent from TRIRIGA Admin Console and verify that it starts successfully…
[Admin: This post is related to the 08.03.16 post about installing, upgrading, or uninstalling TRIRIGA TDI, and the 05.01.16 post about documentation on developing TDI with TRIRIGA. To see other related posts, use the TDI tag.]
Moving forward, we resolved an issue where malicious files can be uploaded via document upload by bypassing the client side validation.
[Admin: This post is related to the 01.25.16 post and 07.18.15 post about restricting the upload of certain file types. To see other related posts, use the Vulnerability tag or CVE tag.]
I would like to know if it is possible to use a UX login template, created as a UX view and accessed with the WebViewSync.jar, as the ALTERNATE_INDEX_HTML. Currently, I have this configuration in the TRIRIGAWEB.properties:
- ALTERNATE_UX_LOGIN_VIEW: cstMeetingRoomsManagerViewAutoLogin
I would like to use the same login page in both places, accessing classic TRIRIGA normally, and also accessing a UX application. Can I set something like this?
- ALTERNATE_INDEX_HTML: cst-meeting-rooms-manager-autologin.html
- ALTERNATE_RESOURCE_DIRECTORY: /root/tririga/p/web
Currently, TRIRIGA does not support using a UX login view as the ALTERNATE_INDEX_HTML. That’s because of the dependency from UX views to Polymer libraries and UX components.
[Admin: To see other related posts, use the Alternate tag.]
When a report is executed from “My Reports”, the title is shown as the header, even though we have changed the REPORT_HEADER_COLUMN property to “Name” in the TRIRIGAWEB.properties.
We needed to remove the REPORT_HEADER_COLUMN property since it is no longer being used. It was used in the out-of-support TRIRIGA 2.7.x platforms and older. Moving forward, the deprecated REPORT_HEADER_COLUMN property has been removed from the TRIRIGAWEB.properties file since it has not been used since the TRIRIGA 2.7.x platform releases.
[Admin: To see other related posts, use the TRIRIGAWEB.properties tag.]
This is a common question from many TRIRIGA administrators. We have parameters to limit the file extensions for a while now, but limiting the file size was a missing capability, until…
In TRIRIGA 3.5.2, we introduced a new property in the TRIRIGAWEB.properties file called MAXIMUM_UPLOAD_FILE_SIZE_BYTES that allows administrators to configure the maximum permissible size for file uploads. If no value is set, the default is 20 megabytes. We hope you make good use of this feature after you upgrade to 3.5.2 or higher versions of the platform. I’m sure your storage specialist will owe you one!