2.4 Integration & Data Migration Options

Owned by CDS Administrator (Deactivated)
Last updated: Oct 07, 2022 by Ashley Tate
3 min read

Integration and Data Migration Options - IBM TRIRIGA SaaS Standard and Flex

IBM TRIRIGA on Cloud Standard and Flex services support integration to / from external systems. TRIRIGA on Cloud supports a number of options as required to secure integration connections such as SSL, VPN, and SFTP. SFTP is available for integrations that require file based transfers. An IPSec Site to Site VPN tunnel can be established between the client network and the IBM cloud environment using IBM's firewall in order to support other integration transport methods. Integration tables can also be created (in separate schemas from the TRIRIGA database) for customer read/write access after environments are provisioned. If you have an existing integration to / from TRIRIGA, it is highly likely IBM can configure and support it in the cloud. 

TRIRIGA Integration Solution

          Details

Connector for Business Applications (CBA) SOAP
(Business Connect)
 

  • Application Programming Interface (API)

  • Industry standards – WS-I 1.1; WS-Security, SOAP 1.1, WSDL 1.2

  • Part of TRIRIGA licensed product (TRIRIGA CBA License)

Open Services for Life Cycle Collaboration (OSLC)

  • Provides integration between applications using Uniform Resource Identifiers (URI). Several are included in the base product.

  • Utilized by TRIRIGA Anywhere (Mobile), BIM Connector and UX Apps

  • REST API

  • Inbound and Outbound

  • Use of HTTP protocol along with JSON

  • Best used for process integration – mobile or otherwise, outbound data integrations

DataConnect

  • DataConnect is part of the TRIRIGA Application Platform

  • Shifts the Integration skill set to the TRIRIGA Application and Platform

  • Best used for Inbound Integrations or Data Migrations

  • TRIRIGA on Cloud utilizes an Integration database instance

  • Inbound Data Only at this time

  • Staging table based, use with standard ETL tools

Integration Objects

  • Create Integration points through TRIRIGA configuration

  • Uses TRIRIGA User Interface

  • Predefined Integration types (Inbound, Outbound, File, Database, http)

  • Incident Reporting and Notification are built in

  • Meta-data for how an integration between TRIRIGA and external systems behave (i.e. integrations configured by TRIRIGA business objects)

  • Can be used as precursor process to DataConnect (File to Db to TRIRIGA)

  • For outbound integrations, you can export file formats that include standardised delimited flat files and .json, .xml, or .xslt files

Offline

  • Data integration between the application and Microsoft Excel

  • Inbound (Check In) or Outbound (Check Out) Data can be sent via Offline

  • Offline compatible with email with minor configurations

  • Best used to extend TRIRIGA content in a disconnected mode

Data Integrator

  • Inbound Data is loaded by tab delimited .txt files

  • Best used for simple one-time set-up of data less than 10,000 records

  • Data load only supported for English language data (no special characters)

Data Load Manager

  • Advanced spreadsheet based data load utility

  • Leverages DataConnect and Integration Objects functionality

For more information on IBM TRIRIGA Application Integration and options, please refer to the IBM documentation links below.

Integrating Data with External Applications:
https://www.ibm.com/docs/en/tap/3.8?topic=integrating-data-external-applications
Integrating Data by using the OSLC REST API:
https://www.ibm.com/docs/en/tap/3.8?topic=applications-integrating-data-by-using-oslc-rest-api

Note: Customers who have chosen to provide their own integration certificates (in lieu of IBM SRE ownership/management) are responsible for providing renewed certificates to IBM prior to expiration. CDS does not track expiration dates of customer provided integration certificates.

Diagram showing IBM TRIRIGA on Cloud Integration support options: HTTPS, sFTP and IPsec VPN

 

 

Data Encryption in Transit

All IBM SRE TRIRIGA SaaS customers use HTTPS (SSL) encryption (256 bit) at the browser/REST API level to access IBM hosted applications. Connections are SHA-2 and TLS v1.2 compatible

 

Data Encryption at Rest

All IBM Cloud TRIRIGA SaaS databases are located on IBM's internal network and are AES-256 Encrypted at rest. Only IBM Cloud Delivery Services staff who have been granted the DBA role are allowed access.

 

Encrypted Backend Interfaces

All IBM SRE TRIRIGA SaaS customers use HTTPS (SSL) encryption (256 bit) at the browser/REST API level to access IBM hosted applications.

If VPNs are required, we support both IPSec and OpenVPN connectivity, both using modern encryption protocols.

Disclaimer: Information provided in this wiki is for informational purposes only. Content is not to be considered part of any existing IBM®️ Maximo or TRIRIGA customer subscription, agreement, license or contract. From time to time, this site may contain technical inaccuracies or typographical errors, and IBM do not warrant the accuracy of any posted information. The information contained in this wiki is subject to change without notice. By visiting this wiki, you consent to use of cookies and other tracking technologies by IBM’s subcontractor, Atlassian, in accordance with the Atlassian Cookies & Tracking Notice found at https://www.atlassian.com/legal/cookies. If you do not consent to the collection of your data by Atlassian at any time, please leave the wiki and delete the cookies and other web-tracking technologies through your browser.