Step 2: Creating a mapping

Options:

Parameters:

mappingName

The name of the mapping; for example, TADDM72ToDPA75. Mapping names have maximum length of 255 characters. Mapping names are also case sensitive; for example, TADDM72ToDPA75 is not the same as taddm72toDPA75.

pathToMappingFile

The fully qualified mapping file name; for example: "C:\Integration Composer\data\mappings\TADDM72ToDPA75.fsn”. (The .fsn extension identifies Integration Composer mapping files. The path in the example includes spaces and therefore must be enclosed in quotation marks.)

repositoryPwd

The login password for the Integration Composer repository; for example, maximopwd.

sourceName

The name for the data source for the discovered data; for example, TADDM72, representing the source Tivoli® Application Dependency Discovery Manager 7.2. (The name is case sensitive.)

sourcePwd

The login password for the data source of the discovered source data; for example, taddm72pwd. (Database users enter a database password.)

targetName

The name for the target data source (the Maximo database); for example, DPA75 representing Deployed Assets 7.6.

targetPwd

The login password for the target data source (the Maximo database); for example, sys1admin1pwd.

Usage:

• Close Integration Composer before issuing the command.
• Windows conventions are followed for specifying directory names and directory paths. UNIX users should replace each backslash (\) with a forward slash (/) in any Windows directory paths that include backward slashes.
• UNIX users must specify ./createMapping.sh as the command name; Windows users specify createMapping.
• Issue the command from the bin subdirectory in your Integration Composer installation directory, installation_dir\bin.
• Always type the parameter values for your command in the same order as they appear in the command syntax.
• Parameter values with one or more spaces must be enclosed in quotation marks (").
• If you enter an incorrect user ID or password, the database driver returns an authentication error; for example, the DB2® driver returns: Connection authorization failure occurred. Reason: User ID or Password invalid.
• If the property mxe.db.user in the fusion.properties file is commented out or missing, the following error is displayed: The mxe.db.user property is not set in the fusion.properties file. Make sure the properties file is configured correctly.
• If the data source name that you enter for either the source or the target is not valid, the following error is displayed: The data source dataSource does not exist.
• If you try to create a mapping using a mapping name that already exists in the database, the following message is displayed: The specified mapping name already exists.
• If all required arguments are not entered, the command syntax is displayed.
• If the path to the mapping file is entered incorrectly, the following message is displayed on Windows operating systems (UNIX is similar): C:\Integration Composer\data\mappings\MappingFile.fsn does not exist.
• If you enter an incorrect data source, the following message is displayed: Error connecting to source/target data source.
• If the specified target data source is not actually a target, the following message is displayed: Specified data source targetName is not a target data source.
• If the mapping has errors, the errors are displayed to the console. The errors are separated into source and target errors:
  Source Error Example:

  Parent: Deployed Asset
  Class: Computer
  Property: Ramsize
  Case Number: 0
  Expression: Math.round('Memory.TotalPhysicalMemorya'/(float)1024.0)
  Error: Parse Error:Property 'TotalPhysicalMemorya' not found in 
    class 'Memory', dataSource 'SCCM2007'
  Last token read:'Memory.TotalPhysicalMemorya'

  Target Error Example:

  Target Computer:Ramsizea does not exist.