Integration Composer file structure

During Integration Composer installation, if the default installation path is accepted, the installation program installs the application in a predetermined file structure.

The following table lists the default installation paths:
Operating System File Path
ngunix.gif /opt/IntegrationComposer
The installation program creates the following file structure for Integration Composer on Windows operating systems (UNIX is similar):
Figure 1. Integration Composer file structure
Integration Composer

If you select a different target directory for installing Integration Composer, the installation program creates the same file structure in the directory that you specify.

The following table describes the content in the Integration Composer subdirectories:
Subdirectory Description
bin Stores the following batch files:
  • createMapping.bat (Windows) or (UNIX)—file that creates a new mapping for the data you want to transform, and imports the appropriate mapping (.fsn) file into the mapping.
  • defineDataSource.bat (Windows) or (UNIX)—file that defines the data source connections used to link Integration Composer to data sources.
  • deleteDataSource.bat (Windows) or (UNIX)—file that deletes a data source definition that links Integration Composer to the data source.
  • deleteMapping.bat (Windows) or (UNIX)—file that deletes a mapping permanently.
  • encryptExecuteMappingProperties.bat (Windows) or (UNIX)—file that encrypts the properties in the file.
  • executeMapping.bat (Windows) or (UNIX)—file that executes an Integration Composer mapping.
  •—file that contains the properties for executing a mapping, including properties for the repository password, data source password, and data target password.
  • init.bat (Windows) or (UNIX)—file used to define and initialize the Integration Composer environment.
  • startFusion.bat (Windows) or (UNIX)—file that launches the Integration Composer user interface.
data Stores mapping (.fsn) files plus the following subdirectories:
  • dataschema—stores data schemas that users export from Integration Composer or that users copy to this folder from other sources.

    Also stores a script in the data\dataschema\centennial2006_2007 subdirectory that Centennial Discovery 2006 and Centennial Discovery 2007 adapter users run to create Maximo® views on their Centennial Discovery database.

  • mappings—stores mappings that come with Integration Composer and is the default directory for importing and exporting mappings from the Integration Composer user interface.
  • properties—stores specialized application properties files.
    The data\properties subdirectory includes the following properties files:
    Properties needed for Asset Initialization adapter
    Default properties used by all deployed assets adapters
    Integration Composer properties file
    Connection information properties
    Logging properties
    Labels or messages needed by Integration Composer before database access

    The data\properties\nrs subdirectory includes specialized application properties files for Data Integration Services logging properties. The data\properties\provider subdirectory includes properties files needed for Maximo IT and Maximo Assets adapters.

etc Stores files used by the Tivoli® Application Dependency Discovery Manager Software Development Kit. Do not modify any files in this subdirectory.
genrules Stores Java™ source files that Integration Composer creates when you run a mapping. Do not modify any files in this subdirectory.
help Stores the Integration Composer online help and image files. Do not modify any files in this subdirectory.
lib Stores application program interfaces (APIs) and JDBC drivers that Integration Composer uses. Do not modify any files in this subdirectory.
log Stores Integration Composer log files.
Uninstall_Integration _Composer Stores the files that remove Integration Composer from your computer. Do not modify any files in this subdirectory.