Running a mapping using a properties file

You can run a mapping using the parameters specified in the executeMapping.properties file. Use this option if you want to encrypt your database passwords in the mapping. This is the only option that allows you to encrypt passwords. However, you can use this option without running the encryption script, if you wish.

Before you begin

Before you run the mapping, you need to enter all the necessary parameter values inside the executeMapping.properties file and run the encryption script.

About this task

Properties file parameters

The executeMapping.properties file stores user identifiers and passwords that are used to access the Integration Composer repository, plus source and target data sources, when mappings are run. The properties file, located in the bin subdirectory, can be used in order to run the executeMapping.bat or executeMapping.sh files securely.

The properties in the file are as follows:

MAPPINGNAME: Name of the mapping. Use the name that you assign to the mapping when you create it.
REPOSITORYUSER: User identifier for the Integration Composer repository.
REPOSITORYPWD: Password for the Integration Composer repository.
SOURCEUSER: User identifier for the data source for the mapping.
SOURCEPWD: Password for the data source for the mapping.
TARGETUSER: User identifier for the target for the mapping.
TARGETPWD: Password for the target for the mapping.

To enhance security when processing a mapping, administrators can run a script that encrypts the passwords in this properties file.

Running the encryption script—with validation processing

To encrypt an executeMapping.properties file, administrators specify passwords in the properties file and then run one of the following encryption scripts:

encryptExecuteMappingProperties.bat (on Microsoft Windows systems)
encryptExecuteMappingProperties.sh (on UNIX systems)

The encryption scripts are in the bin subdirectory of the Integration Composer installation directory.

When you run the encryption script, the Integration Composer encryption utility by default validates that the passwords are correct by attempting to connect to the data sources that are specified in a mapping.

To run the script, use the following syntax, where filename is the name of the executeMapping.properties file that you created for this mapping:

encryptExecuteMappingProperties.bat filename (on Microsoft Windows systems)
encryptExecuteMappingProperties.sh fully_qualified_filename (on UNIX systems)
Note: UNIX requires both a file path and file name.

After the script runs, the executeMapping.bat or executeMapping.sh file can run the mapping with the encrypted passwords.

Running the encryption script—without validation processing

To skip the step that validates your data source and target connections, and instead encrypt the file even if connections are unsuccessful, use the following syntax that includes the -s parameter (where filename is the name of the executeMapping.properties file):

encryptExecuteMappingProperties.bat -s filename (on Microsoft Windows systems)
encryptExecuteMappingProperties.sh -s fully_qualified_filename (on UNIX systems)

The encryption utility will encrypt the values specified in the executeMapping.properties file without validating the connections.

Encrypting multiple files

If you want more than one properties file to use for different mapping runs, you can create multiple properties files by copying and renaming the executeMapping.properties file.

To use the encryption script to encrypt multiple files at one time, use the following syntax:

encryptExecuteMappingProperties.bat [-s] filename_1 filename_2 ... filename_n (on Microsoft Windows systems)
encryptExecuteMappingProperties.sh [-s] fully_qualified_filename_1 fully_qualified_filename_2 ... fully_qualified_filename_n (on UNIX systems)

The -s option applies to all files. If you omit the -s, all files will be validated. If you include the -s, no files will be validated.

The steps for running a mapping using the executeMapping.properties file follow:

Procedure

If Integration Composer is open, close the application.
Create an executeMapping.properties file with the parameters required for your mapping (as described above).
Open a command prompt.
Navigate to the bin subdirectory in your Integration Composer installation directory, installation_dir\bin.
Select the appropriate option for your environment:
- For Microsoft Windows installations:
  - To delete last scan history (as described in Step 4: Running a mapping) and then run the mapping, use the following syntax:
    executeMapping.bat -delete -f filename
    
    Example
    
    executeMapping.bat -delete -f Integration Composer\bin\executeMapping1.properties
  - To run the mapping without deleting last scan history, use the following syntax:
    executeMapping.bat -f filename
    
    Example
    
    executeMapping.bat -f Integration Composer\bin\executeMapping1.properties
- For UNIX installations, select the appropriate option:
  - To delete last scan history (as described in Step 4: Running a mapping) and then run the mapping, use the following syntax:
    ./executeMapping.sh -delete -f fully_qualified_filename
    Note: UNIX requires both a file path and file name.
    
    Example
    
    ./executeMapping.sh -delete -f Integration_Composer/bin/executeMapping1.properties
  - To run the mapping without deleting last scan history, use the following syntax:
    ./executeMapping.sh -f fully_qualified_filename
    
    Example
    
    ./executeMapping.sh -f Integration_Composer/bin/executeMapping1.properties
Press Enter.
When the mapping is completed, press Enter again.

Feedback