Introducing the TRIRIGA integration options


TRIRIGA provides multiple options for data exchange and the options range from very simple data dump using text file to a sophisticated real-time REST API… Although there are additional options for data exchange, we will focus mostly on the OSLC (REST API) and Integration Objects. A lot has already been talked about CBA (SOAP API) (erstwhile known as BusinessConnect)…

  • The TRIRIGA Applications layer consists of configuration related to OSLC Manager and Resources. It also consist of configuration related to the Integration Object, although Integration Object in essence is really an extension to the platform.
  • The TRIRIGA Application Platform layer consists of the underlying code base which enables interaction with the TRIRIGA applications.
  • The Systems Integration Layer consists of code base which provides inter-connectivity options for the data exchange.

Let’s have a quick introduction to these technologies starting with CBA.

  • Connector for Business Applications (CBA): CBA is essentially an extension to the underlying TRIRIGA application platform and you can programmatically perform nearly any action using CBA which you could perform using the application itself. Catch is, to use CBA, you potentially need to be a Java rock star. You need to understand Java in depth to a level where you can create a client tool or code to consume the Web Services utilising SOAP construct and be able to write Java code to handle the request and response from CBA…
  • Integration Objects: Integration Object is a great initiative in trying to bridge the gap between the old and complex data exchange technology and the emerging requirements from customers who are looking for more simpler methods to exchange data. Integration Object is built utilising the platform tools and a set of custom Java code. It has a user-friendly field mapping tool and overall fairly easy to grasp. It allows you to look at the failures through the UI and potentially resubmit the transactions…
  • Open Services for Lifecycle Collaboration (OSLC): OSLC is essentially a set of specifications which were developed (and being improved) to promote integration of software development life-cycle and to allow seamless integration between different software. The OSLC specifications builds on various standard like REST and supports HTTP verbs through CRUD (Create, Read, Update, Delete) options and is essentially a step towards building a hypermedia (extended hypertext) system to enable machine to machine interaction (read IoT)…

[Admin: This post is related to the 01.12.16 post about API documentation.]

Continue reading

4 thoughts on “Introducing the TRIRIGA integration options

  1. Pingback: Extending TRIRIGA with the CREF digital enterprise framework | TRIRIGAFEEDIA

  2. Pingback: Where can you find the IBM TRIRIGA API documentation? | TRIRIGAFEEDIA

  3. Pingback: Top Ten TRIRIGAFEEDIA posts of September 2016 | TRIRIGAFEEDIA

  4. Pingback: Top Ten TRIRIGAFEEDIA posts of November 2016 | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s