To create a mapping model, the transformation that you configure must support mapping. If a default transformation in the Rational® modeling products supports mapping, the transformation configuration editor displays a Mapping page. To enable mapping functionality for custom transformations, a transformation author must set the supports Mapping property equal to true. The transformation manifest file contains this property.
A transformation assigns default file names to the files and folders that it generates. You can specify alternate file names for any of the files and folders that a transformation generates by creating a mapping model. Specifying alternate names in a mapping model does not modify the source model. You must create a mapping model in the same workspace as the selected model elements.
To create a mapping model, you must select the source model elements on which to run a transformation. The source model elements can exist in different models or different projects. When you generate a mapping model, a separate model is created that contains an artifact for each element that you select in the source model. A manifestation relationship exists between each created artifact and its corresponding element in the source model.
Except for components, you can only rename UML elements with simple identifiers. You can rename UML components with either a simple identifier or with a partial path name that is relative to the target container that contains the IDL file that the transformation generates. The path name of the file can end with the name of the IDL file. For example, if you rename ComponentA as dirA\A, the transformation generates A.idl in the directory named dirA, instead of in the top level of the target container.
The next time that you run a transformation using a
mapping model, the alternate file names that you specify in the mapping model
are applied to the elements that the transformation generates.