Step 4: Running a mapping

When you create a mapping, you define a set of expressions that specify how to transform data from a source to a target. To transform the source data and import it from the source database into the target (Maximo®) database, you must run the mapping.

Mappings must be run from the Integration Composer command line interface. Running a mapping processes either a batch or shell script, and optionally, a properties file.

There are three ways to run a mapping from the command line:

If you do frequent data imports, most likely you will want to run a script that is prefilled with all the values, so you do not have to type all the parameter values on the command line each time. You can run the script as often as needed, or use a scheduler and batch processing to run the script automatically. If you have more than one mapping to run, you can create separate prefilled script files for running each mapping.

There are several parameters to consider when running a mapping:
Delete last scan history option
Setting this parameter is optional. By default, when importing data, Integration Composer processes only the data that has changed since the last scan date. However, if you modify a mapping and you want to implement the change, you might want all data processed. To accomplish this, you must delete the last scan history. Use the -delete option only if you want all data processed when you run the mapping.
Identification parameters
Provide values for some identification parameters that specify mapping name, repository user name and password, source user name and password, and target user name and password for mapping execution.

The procedures that follow are described for Windows operating systems (procedures for UNIX-based operating systems are similar but use the installation_dir/bin/executeMapping.sh file instead).



Feedback