We want to integrate IBM TRIRIGA with FileNet using CMIS 1.1, but we need to know what is all of the standard metadata that TRIRIGA sends to FileNet. For example, the file name, date creation, date modification, document type, document size, TRIRIGA user owner, etc. And if it is possible to send custom metadata when creating new custom fields in the Document business object? How can we do it?
The following properties are sent as part of the integration: Document Name, Document Type, Document Path. The Owner is going to be the CMIS username as defined in the TRIRIGAWEB.properties. Further custom metadata is not supported. The purpose of the CMIS integration is to have the binary content not stored in the TRIRIGA database as BLOBs.
[Admin: This post is related to the 07.26.17 post about CMIS FileNet integration issues, and the 12.02.16 post about integrating with CMIS and ECM solutions. To see other related posts, use the CMIS tag or ECM tag.]
I installed IBM TRIRIGA Application Platform 3.5.3 in Linux CentOS 7. While running the TRIRIGA installer, I selected an embedded server, that is IBM WebSphere Application Server (WAS) Liberty Profile 184.108.40.206. This server is successfully installed and up and running.
From the log, I found that the server host where IBM TRIRIGA is accessed has an URL something like this: http://some.static.ab-xyz.com:8001. This URL value was taken by default. I did not provide this value. My question is: How do I change this host name URL? Where is the setting for this?
I’m not sure what log you’re looking at and what specifically you’re seeing. What is set as your FRONT_END_SERVER value in your TRIRIGAWEB.properties file?
[Admin: To see other related posts, use the Hostname tag.]
When trying to upload a file type that should be allowed based on the contents of the INCLUDE_EXTENSIONS and EXCLUDE_EXTENSIONS lines, the user gets a message stating that uploading a file of that type is not allowed. Why?
Adding spaces in the extension list will invalidate any other defined value after the first one listed. In the TRIRIGA 3.5.2 and later releases, more variables were added to the TRIRIGAWEB.properties file, for more-precise control over what can be loaded as an attachment to a record, or added to Document Manager. These variables are documented in the TRIRIGA Release Notes, but to give the basic information, these are the two new sets of variables:
- COMPANY_FILE_UPLOAD_EXCLUDE_EXTENSIONS and COMPANY_FILE_UPLOAD_INCLUDE_EXTENSIONS
- IMPORT_CONTENT_EXCLUDE_EXTENSIONS and IMPORT_CONTENT_INCLUDE_EXTENSIONS.
Any file extensions can be added here, but the format of the list needs to be properly set. Use only comma-separated values (CSV) without spaces to build the string. If there are any spaces in the list, remove them…
[Admin: To see other related posts, use the “include_extension” search phrase.]
We are using IdP-initiated SAML, and we access TRIRIGA via a link that looks something like this: http://idpprovider/applications/Tririga. Can we pass this link in FRONT_END_SERVER in TRIRIGAWEB.properties so that users can click on the link that they get in a work task email, and they can be redirected to TRIRIGA?
SAML does not support basic authentication for non-browser clients. This is a SAML limitation. See the following APAR IV88274 link.
[Admin: For convenience, here are the meanings of the acronyms: Identity Provider (IdP), Security Assertion Markup Language (SAML).]
[Admin: This post is related to the 08.18.16 post about lack of support for non-browser clients. To see other related posts, use the SAML tag.]
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 (220.127.116.11) 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.]
We have an IBM-hosted environment that will be connected to an IBM-hosted FileNet instance as the CMIS. After configuring everything, the connection is established and the containers are created in FileNet, but the actual file is not uploaded. Has anyone been able to have this integration work in their environment? Here is a snippet of the error log when CMIS integration is active…
This was most likely due to a misconfiguration on the TRIRIGAWEB.properties or CMIS side. TRIRIGA supports the CMIS 1.1 standard. IBM TRIRIGA can be configured to store documents in Enterprise Content Management (ECM) systems that support the Content Management Interoperability Services (CMIS) ECM gateway Version 1.1 of the CMIS standard, as established by OASIS.
These gateways are specific to the vendor of your particular ECM and should be installed accordingly, if one does not already exist in your organization. See the Compatibility Matrix. IBM FileNet adheres to the CMIS 1.1 standard. So, as long as the FileNet version has support for 1.1, it is supported by TRIRIGA.
[Admin: A similar question is also posted in the triDeveloper Google group. To see other related posts, use the CMIS tag or ECM 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!