Integration Composer components

Integration Composer consists of a user interface, a command line interface, an engine for processing mapping expressions, connection drivers, and a repository that is a subset of the Maximo® database where your information technology data is imported.

A short description of the Integration Composer components follows:

Integration Composer user interface	The Integration Composer user interface lets you define data sources, browse the source data, define data schemas, and create mappings to transform and import data.
Integration Composer command line interface	The Integration Composer command line interface lets you start the Integration Composer user interface and invoke the Integration Composer engine to run mappings that transform your source data and import it from the source to the target Maximo database.
Integration Composer engine	The Integration Composer engine processes mapping expressions that transform data from the source data and integrate it into a target database.
Connection methods	Integration Composer uses a JDBC driver or an application programming interface (API) to establish connections to the source data location and target database. Integration Composer includes the following JDBC drivers: Oracle JDBC Thin driver. This driver supports Oracle 11g and earlier versions. Microsoft SQL JDBC driver. This driver supports Microsoft SQL Server 2008 R2, SQL Server 2008, SQL Server 2005, and SQL Server 2000. [Not included but supported.] i-net OPTA JDBC Driver for Microsoft SQL Server. This driver supports Microsoft SQL Server 6.5 through SQL Server 2008. Note: Users upgrading from a previous release and who already have this (deprecated) driver can use it for Microsoft SQL Server support. IBM® DB2® JDBC Driver. Generic JDBC Driver. Integration Composer includes the IBM Configuration Discovery and Tracking API, which is used only by the Integration Adapter for IBM Tivoli® Application Dependency Discovery Manager (TADDM) that is provided with IBM Tivoli Change and Configuration Management Database. Integration Composer also includes the IBM Tivoli Monitoring API, which is used only by the Integration Adapter for IBM Tivoli Monitoring that is provided for licensees of the Maximo for Energy Optimization product.
Integration Composer repository	The Integration Composer repository in the Maximo database contains the following Integration Composer data: Metadata for data schemas delivered with Integration Composer. This metadata defines the structure of the data. Metadata for data schemas that you create in Integration Composer. Data source definitions that provide data connection parameters. Mappings that define how to transform data instances and move them from a source to a target. The time stamp of the most recent scan for top-level objects in the source data of the Integration Composer repository, if such a last-scan time stamp exists.

Feedback