Deleting a mapping

Sometimes you no longer need to retain a mapping. Perform this task to delete a mapping permanently. If you delete a mapping, Integration Composer also deletes the mapping's last scan history, if any.

Before you begin

You delete a mapping by running either the deleteMapping.bat command (on Microsoft Windows operating systems), or the deleteMapping.sh command (on UNIX-based operating systems). You run the command from the bin subdirectory in your Integration Composer installation directory.

Before you run the command, review the following command syntax, option and parameter definitions, and usage:

Syntax:  
     
  deleteMapping  
    help

    listMappings repositoryPwd

    repositoryPwd mappingName

     

Options:

 
 
help
Displays the command syntax.
listMappings
Displays existing mappings and their corresponding data sources. The display format is:
Mapping Name: mappingName Source: sourceName Target: targetName
     

Parameters:

 
 
mappingName
The name of the mapping; for example, TADDM72ToDPA75. Note that mapping names are case sensitive; for example, TADDM72ToDPA75 is not the same as taddm72toDPA75.
repositoryPwd
The login password for the Integration Composer repository; for example, maximopwd.
     

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 ./deleteMapping.sh as the command name; Windows users specify deleteMapping.
  • 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 you try to delete a mapping using a mapping name that does not already exist in the database, the following message is displayed: The specified mapping does not exist in the Integration Composer repository.
  • If all required arguments are not entered, the command syntax is displayed.
  • When you run the command, you will receive a message asking to confirm the deletion: This action will delete mapping mappingName. If you do not want to delete this mapping, press CTRL-C. Press Enter to continue.

About this task

Deleting a mapping deletes the mapping information from the Integration Composer repository (not the .fsn file).

After you delete a mapping from the repository, you must recreate it if you subsequently want to use it.

The steps for deleting a mapping follow.

Procedure

  1. If Integration Composer is open, close the application.
  2. Open a command prompt.
  3. Navigate to the bin subdirectory in your Integration Composer installation directory, installation_dir\bin.
  4. On the command line, type one of the following commands and add the command options, parameters, and values you want:
      Windows: deleteMapping
      UNIX: ./deleteMapping.sh
  5. Press Enter to run the command. If you receive a confirmation message, press Enter to continue (or press CTRL-C to cancel the command).

Example

The following command example (for Windows operating systems) shows a command that deletes a mapping named TADDM72ToDPA75 that maps data from the source, Tivoli® Application Dependency Discovery Manager 7.2, to the target, Deployed Assets 7.6 (the Maximo® database):

deleteMapping maximopwd TADDM72ToDPA75

On UNIX-based operating systems, specify ./deleteMapping.sh instead of deleteMapping as the command name, specify /home/user/Integration_Composer as the default installation path, and use forward slashes (/) instead of backward slashes (\) in the file path.

Successful command processing yields the following message:

Mapping TADDM72ToDPA75 deleted successfully.



Feedback