What is the “Integration” check box for in the workflow Start task?
Assuming you are referring to the Start task of an asynchronous workflow, when this property is selected, the workflow is used to migrate data from staging tables in IBM TRIRIGA records. This type of workflow is used extensively in IBM TRIRIGA DataConnect.
Check out this IBM Knowledge Center topic about DataConnect that describes the “Integration” check box: Workflow task settings.
[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Staging tag or DataConnect tag.]
There are many installation scenarios that can cause TRIRIGA reports, especially BIRT reports, to fail to export due to timeout. Microsoft Excel exports are often the ones that you can observe because all of the file formatting happens during export.
Let’s focus on WebSphere Liberty installations, but this recommendation can be used for other web servers with some tweaks. Mostly, this is related to timeout settings, especially for HTTPS (SSL/TLS) connections. A good troubleshooting test is to perform the same action in a non-HTTPS (HTTP) connection. Does the report export? If so, take note of the time needed to export it and plan to extend the timeout in the HTTPS connection to at least double the time.
Refer to the IBM Knowledge Center > WebSphere Liberty > HTTP Endpoint topic. Look for the “sslOptions”, and also double-check the “httpOptions”, for timeouts.
[Admin: This post is related to the 04.20.17 post about setting the TRIRIGA session expiration warning in the portal. To see other related posts, use the Timeout tag.]
How do I address the cause of currency conversion exceptions that are appearing in my TRIRIGA server.log file so they stop being logged? The exception can occur as a result of currency conversion being done when a user profile has a different currency than the base currency. Here are some examples of the exception seen in the log:
Error in Conversion from >CHINESE YUAN RENMINBI< to >US Dollars< . Using conversion rate of 1.
Error in Conversion from >NIGERIAN NAIRA< to >US Dollars< . Using conversion rate of 1.
There are generally two ways to resolve this:
- 1. Add currency conversion values to allow the currency conversion to take place. The documentation can be found in the IBM Knowledge Center: Currency.
- 2. Confirm every user profile has the same currency as the base currency. The base currency is defined in the TRIRIGAWEB.properties file.
Also, check for duplicate UOM values for currency. This could explain the exception if the first two options fail to resolve the problem…
Starting with the TRIRIGA 3.5.0 platform release, the Object Migration tool’s “Full Package” create mode was removed from the Object Migration tool. But with TRIRIGA 3.5.2, the new “Full Metadata Package” was added in its place.
From the 3.5.2 Release Notes
- Release Notes > Object Migration: The Create Mode field in Object Migration now contains a Full Metadata Package option. With this option, the export package contains all objects from the entire TRIRIGA system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included. This option replaces the Full Package option available in earlier releases.
From the 3.5.2 Knowledge Center
- New features > Create Full Metadata Package export option: You can create an export package that contains all objects from the entire system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included. This menu replaces the Full Package option of earlier versions.
- Creating an export package: To create a package that contains all objects, select Full Metadata Package. The package will contain all objects from the entire system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included.
Where is the information regarding IBM TRIRIGA Application Platform 3.5.2 and IBM TRIRIGA 10.5.2 features, installation, and more?
[Admin: This post is related to the 06.13.16 post about finding 3.5.1 and 10.5.1 information, the 12.11.15 post about finding 3.5.0 and 10.5.0 information, and the 10.01.15 post about finding 3.4.2 and 10.4.2 information. To see other related posts, search “where is the latest“ or “where can you find“.]
The IBM TRIRIGA Connector for Business Applications (CBA) is a SOAP API for the TRIRIGA platform. The technical specification and documentation for this API can be found here: IBM TRIRIGA Application Platform 3 Connector for Business Applications Technical Specification.
Document Upload Java Client Example
The following is sample Java client code demonstrating a document upload via CBA on 3.5 platform with MTOM enabled, using Apache CXF and JAXB. This code utilizes stubs generated from the CXF WSDL to Java utility (classes such as TririgaWS and TririgaWSPortType are generated from this). Note that this is just an example for demonstrative purposes, it is not code officially supported by IBM. Please review the Connector for Business Applications Technical Specification guide for more information on working with CBA…
Maintaining a Java Client Session Example
The following is sample Java code demonstrating usage of the Apache CXF BindingProvider to maintain a single client session for multiple CBA requests with 3.5 platform. This code utilizes stubs generated from the CXF WSDL to Java utility (classes such as TririgaWS and TririgaWSPortType are generated from this). Note that this is just an example for demonstrative purposes, it is not code officially supported by IBM. Please review the Connector for Business Applications Technical Specification guide for more information on working with CBA…
Why are your retired integration workflows being republished after restarting your server?
This is working as designed. The integration object is controlled by the platform, so any changes it finds will be added back upon an application server restart. You can find more information in the IBM Knowledge Center topic: Object upgrades. Note that if you add an integration object record called IGNORE_UPGRADE, then no updates will be made to the integration object and it will not apply fixes in the future that are added to the package.