Object elements

The triIntegration module contains several business objects such as the TRIRIGA® integration object. In addition, the integration object record requires the use of several class loader elements.

The triIntegration module includes the following business objects:

triIntegration: The TRIRIGA integration object is the primary business object that defines the integration between IBM® TRIRIGA and external systems. You create integration definitions or integration object records from this TRIRIGA integration object.
triDataSource: The data source business object contains the property settings that define the connection to a database. This object is referenced as a single-record smart section in the integration object record. This referencing allows the reuse of data source definitions across multiple integration definitions.
triIntegrationInstance: The integration instance business object contains the details about a specific instance of an integration run. This object contains the counts, the time it took to run, a collection of error messages if any, and a query section with details about each record that failed. This object is associated to records that are affected by the response. This object is referenced in the Execute History section of the integration object record.
triIntegrationInstanceFailure: The integration instance failure business object contains the details about a single record that failed for an inbound integration. This object contains the error message for the failure and a simplified representation of the submitted record that can be manually edited and resubmitted.

The TRIRIGA class loader record that is named Integration is required by the integration object record. This Integration class loader record includes the following elements in its Resource Files query section:

jtds-1.2.5.jar

The Java Device Test Suite (JDTS) .jar file is the database driver for Microsoft SQL Server.

Although IBM TRIRIGA is delivered with the Oracle Java Database Connectivity (JDBC) driver for Oracle Database, IBM TRIRIGA does not include a database driver for Microsoft SQL Server. If you are connecting to Microsoft SQL Server, you must add a Microsoft SQL Server driver such as the jtds-1.2.5.jar to the Resource Files query section of the Integration class loader record.

TRIRIGAIntegration.jar

The TRIRIGA integration .jar file contains all of the Java classes that are used by the TRIRIGA integration object components. The file includes workflow-related Custom task entry points and a communication layer that is used by the TRIRIGAIntegration_Assets.zip file elements.

TRIRIGAIntegration_Assets.zip

The TRIRIGA integration assets .zip file contains all of the .html, .css, JavaScript, and image files that are used by the data map for inbound integrations. The JavaScript communicates with the Java API of IBM TRIRIGA Connector for Business Applications by using URI-based servlet proxy handles. The server-side elements are contained within the TRIRIGAIntegration.jar file.