Where can you find information about the IBM TRIRIGA Connector for Watson Analytics (CWA)?


You can use the IBM Watson Analytics service to discover patterns and meanings in your data. Watson Analytics guides data discovery and predictive analytics by using automatic visualizations and enables dashboard creation so that you can get insights and make informed decisions.

By using Watson Analytics, you can add and tune data, discover insights to help solve your business problems, and display your findings. You pair Watson Analytics with data from IBM TRIRIGA to explore your integrated workplace management processes and obtain new insights on your day to day operations. You use TRIRIGA Connector for Watson Analytics to export TRIRIGA data of your choice into Watson Analytics.

[Admin: This post is related to the 11.15.16 post about the overview and demo.]

Continue reading

When will TRIRIGA integrate with other CMIS or ECM solutions?


I know that the TRIRIGA Document Management tool was not developed nor intended to be a full-fledged document management system. However, some clients have a need for a more robust document management system for controlling their CAD drawings. Are there any efforts to integrate TRIRIGA with other document management tools? Or are changes being made to implement a third-party document management tool within TRIRIGA? If so, has a timeline been established as to when that would occur?

IBM has announced that the upcoming release of the IBM TRIRIGA Application Platform, version 3.5.2, includes support for Content Management Interoperability Services (CMIS), providing integration between the IBM TRIRIGA document manager and enterprise content management implementations that support CMIS, such as IBM FileNet®. The planned availability date for electronic download is December 16, 2016.

To add to this, the initial release is a first phase of CMIS support which is primarily focused on starting to get binary content out of the TRIRIGA database schema. To keep it simple, once you establish a link between TRIRIGA and an ECM solution, and users begin uploading new documents, the binary content for those documents will be routed to the ECM while still retaining a document record in TRIRIGA. More details on this will be in the release notes.

Also note that customers have been integrating TRIRIGA with other document management tools for many years. It does not require the aforementioned CMIS enhancement. Our APIs (CBA, OSLC) offer access to upload and download binary content, and you can create dynamic links to any ECM solution from our records.

Continue reading

Where can you find information about the IBM TRIRIGA Connector for Business Applications (CBA)?


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.

Continue reading

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…

Continue reading

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…

Continue reading

RFE: Are AEC objects supported in CAD Integrator for AutoCAD?


I have created the following request for enhancement (RFE) to address adding the functionality to directly support AEC Objects in CAD Integrator. The Architectural version of AutoCAD does support exporting these AEC Objects as blocks into a DXF format. If AutoCAD provides an API that performs the same export function as their DXFOUT command in the Architectural version of AutoCAD, then vote for this RFE so that the TRIRIGA development team can consider using that API in a later release of CAD Integrator.

Support of AEC Objects in CI for AutoCAD (RFE ID 94102).

Continue reading

How do you call a nested resource using TRIRIGA OSLC API?


I am doing an interface proof-of-concept using TRIRIGA OSLC API and getting an error from calling a nested resource. I’m creating a new work task using the out-of-the-box Work Management Service Provider, but creating and assigning a person resource to the new work task fails with the error: “The nested resources are requested on property {0}, which is not linked to any resources.” This is how it’s being called using the Advanced REST Client…

Continue reading

How do you build a servlet proxy that accepts file uploads?


I’m trying to build a simple servlet proxy which takes a file input and uploads it to TRIRIGA. When I test it with the correct parameters, I receive this WebSphere error:

SRVE8020E: Servlet does not accept multipart requests

I plan on using the upload method. Currently, I’m stuck on getting the request to include the data. Here is a snippet of my code taking the parameters:

Part filePart = request.getPart("file");
Long recordId = Long.parseLong(request.getParameter("RecordID"));
String fieldName = request.getParameter("fieldName");
InputStream fileContent = filePart.getInputStream();

The upload to TRIRIGA is easy, but getting these parameters from the request is where I’m experiencing the issue… I’ve created a few classes before that are called using GET with parameters in the URL and everything worked fine. I’m just not sure if it supports POST with the multipart request… I will be triggering this from a UX application. Since it doesn’t support file/image uploads, I’m looking into building a custom solution using servlet proxies.

For that use case, another option in lieu of a servlet proxy is posting the file with an OSLC API. I know there are others that have done this. The following pull request on the vaadin-upload component was actually done to help facilitate this: Upload Mode with option RAW added. So essentially, it’s a direct post to the REST endpoint rather than a form post. Also, it’s worth mentioning that we do tentatively plan to add a TRIRIGA component for file upload in our next release, but hopefully this helps in the meantime.

Continue reading

UX: How do you lazy-load triplat-route pages for performance?


In most cases, your UX application will consist of several pages that a user can navigate into and these pages may not necessarily be shown to the screen when the user initially accesses your application. If you are using the <link rel=”import”> tag to import your routing pages, the resources of these pages will be requested and loaded as the page containing these links is being accessed or loaded. If you have a complex application that consists of layers and layers of routing pages, it may not be good to load all your resources at once by using the <link> tag declaration.

In this article, we will show you how to lazy-load your pages to improve the performance of your application, if you are using a <triplat-route> component when handling their routing behavior. Here are the basic steps you need to do to lazy-load your pages:

  1. Do not use <link rel=”import”> when loading your routing page.
  2. Add the on-route-active event handler to your triplat-route declaration.
  3. Add the id attribute to your routing page declaration.
  4. Lazy-load your page using Polymer importHref API.

Let’s take a closer look at each step…

Continue reading