2.5.2 Work With Transformation Maps
You can create and maintain as many Transformation Maps as your applications need.
To work with Transformation Maps, expand in the and select . To find out how to locate and select Transformation Maps to work with, refer to:
Locating and selecting items in the Instance Lists
For information on common tasks associated with Transformation Maps (such as creating, copying, deleting and printing definitions) refer to:
For information on tasks associated specifically with Transformation Maps, refer to the following headings:
2.5.5 Edit And Prepare Transformation Map
Review Transformation Map Parameters
Display Catalogued Transformation map Information
Work with Transformation Map Version History
Display the Run History of a Transformation Map
2.5.3 Transformation Map Details
2.5.4 Transformation Map Data Interchange Attributes
You can run an existing Transformation Map directly, without having to first create a Processing Sequence containing the Transformation Map.
To do so, select the required item in the Transformation Maps list. Details of the selected Transformation Map will be displayed. Click the button to run the Transformation Map. LANSA Composer will display a window like the window in which you can enter the input parameter values for the Transformation Map.
Refer to Run a Processing Sequence from LANSA Composer.for further information on using the window.
Running a Transformation Map in this way is very much like running a Processing Sequence containing just that Transformation Map. LANSA Composer will automatically log the input and output parameter values in the Processing Sequence log (subject to the logging level currently in effect).
Review Transformation Map Parameters
To review the parameters for an existing Transformation Map, select the required item in the Transformation Maps list and select the tab. A list of the parameters expected for the transformation map will be displayed.
The parameter information is derived from the map definition once you have fully prepared the Transformation Map. It is provided for information and can only be altered by editing the map. When you include the Transformation Map in a processing sequence, you will need to provide values for each Transformation Map parameter.
Parameters provide the variable information necessary for the Transformation Map to complete its work. They also provide the communication between activities and transformations that are orchestrated together in a single processing sequence. Thus, the output (outbound parameters) from an activity might provide the input (inbound parameters) for a Transformation Map.
LANSA Composer derives the parameter information from the generated source code for the map. Consequently the parameter names and parameter descriptions shown may not be very meaningful. It is a good idea to define notes for the Transformation Map to clearly describe the expected input parameters, and to do this immediately after defining the Transformation Map, while its definition is fresh in your mind.
Display Catalogued Transformation map Information
When a Transformation Map is prepared, LANSA Composer collects and catalogues a selection of information about the map. This includes:
- The date and time and user name when the map was prepared;
- LANSA Composer, Java and Altova MapForce version information relating to the Prepared map;
- File size and checksum information pertaining to the map definition file(s) and the generated Java executable file;
- The map definition file(s) and the generated Java executable file at Prepare time are saved in the LANSA Composer database (and can be restored if required);
- Selected mapping information collected from the Altova MapForce map definition, including the components used and the database table selections for database components.
To review the information catalogued for an existing Transformation Map, select the required item in the Transformation Maps list and select the tab.
You can press to compare the file sizes and checksums of the current Transformation Map definition and executable files against those catalogued when the map was last prepared.
Work with Transformation Map Version History
LANSA Composer can store multiple versions of the definition of a Transformation Map. This permits the flexibility to restore and run an earlier version of the Transformation Map if required.
When a Transformation Map is successfully prepared, the prior (prepared) version is archived (subject to the corresponding system setting). The archived version contains the complete definition and executable form of the Transformation Map, but does not include the attachments or notes.
To review the the available prior versions for an existing Transformation Map, select the required item in the Transformation Maps list and select the tab. You can delete or restore the archived versions using the buttons provided.
Display the Run History of a Transformation Map
To display available Run History for a Transformation Map, select the required item in the Transformation Maps list and select the tab. A list of processing sequence runs (including direct runs of the Transformation Map) that used the selected Transformation Map will be displayed. You can double-click an item in the list to view the Processing Sequence Log.
Select an item and click the button to display the Processing Sequence log or the button to print the Processing Sequence log for the run.
If a prior Processing Sequence run has ended in error, you may be able to use the button to restart it from the point of failure. Refer to Restart a Processing Sequence Run for more information.
Note: The completeness of the Run History is subject to the logging level that was in force for each run. Only at more detailed levels of logging is the log information sufficient to identify each and every Activity run. In addition, Processing Sequence run history can be purged using the Database Housekeeping function. The run history for Processing Sequence runs that have been purged is no longer available.