To specify the information
that the transformation uses to generate the output that you expect,
you use the New Transformation
Configuration wizard and the transformation configuration
editor, which guide you through the configuration.
About this task
A transformation configuration
has .tc as a file name extension, and contains the information that
the transformation uses to generate the output that you expect. A
transformation configuration also contains information that is specific
to a particular type of transformation. To edit an existing transformation
configuration, in a view that shows the workspace resources, double-click
a transformation configuration file, which opens the transformation configuration
editor.
To simplify
working with the transformation configuration file, save the configuration
file in the project that contains the elements to transform.
Procedure
- Depending on the view that you are working
in, complete one of the following steps:
- In the Pattern Explorer view, right-click
a transformation; then click New Configuration.
- In other views, click . If Transformation Configuration is not a menu item, click .
- Specify the details
of the configuration. In the New Transformation
Configuration wizard, on the Specify a Configuration
Name and Transformation page, complete the following steps:
- In the Name field, specify a name for the configuration.
- In the Configuration file destination field, specify the destination for the transformation
configuration file. The destination is a relative path in your current
workspace. You can specify a fully qualified project name or folder
name. If you specify a folder in a project, you must prefix the folder
name with a forward slash (/).
- From the Transformation list, select a transformation.
Note: To display the transformations that are
installed, but not enabled, click Show all transformations. A transformation must be bound to a capability
to be displayed in this list.
- Click Next.
- Specify the source and target elements
for the transformation. For a list of valid source and target elements,
see the related concept topic for this transformation. On the Source and Target page, complete the following steps:
- In the Selected source pane, select the source element for the transformation
to transform.
- In the Selected target pane, select the destination of the transformation output.
To create a new destination for the output, click Create Target Container.
- Click Finish. The transformation configuration
editor opens, and the contents of the configuration are displayed.
- Optional: To generate
debugging information, on the Main page, select the Generate a debug log check box. The
next time that you run the transformation, the log file is generated
as an XML file in the folder that you specify in the transformation
preferences. If you do not specify a location for the log files, the
transformation generates the log file in the .metadata folder in your workspace.
Tip: To set preferences for transformations,
click ; then expand Modeling and click Transformations.
The log file
provides information about the source elements, the target elements,
and the rules that the transformation applies to transform the source
elements. If the transformation transforms many elements, you might
experience decreased performance while the transformation generates
the log file; therefore, you should only generate a log file for debugging
purposes.
- Optional: Specify documentation
about the transformation configuration. This field is useful for communicating
information about a configuration that multiple users share. On the Main page, in the Documentation field, specify additional information about
the transformation configuration.
- Optional: Specify a file name for the UML service
model that the Business-Process-to-Service-Model transformation
generates. On the Business Process to Service Model Transformation
page, in the Target model file name field,
specify a value for the UML model that the transformation generates.
Specifying a file name for the service model enables you
to create multiple service models in the same target project that
you specify in the transformation configuration. The transformation
generates a UML model in the target project or folder that you specify
in the transformation configuration. The generated model has .emx
as a file name extension.
- Optional: Specify how the transformation applies
transformation extensions to the elements in the source model. On
the Business Process to Service Model Transformation page, complete
one of the following steps:
- To apply the same transformation extension to all business
processes in the source model, click Apply to all;
then select a transformation extension from the list.
- To apply a different transformation extension to each business
process in the source model, click Configure each.
For each row in the table below this button, click the Transformation column
and select a transformation extension.
From the list of transformation extensions, complete one of
the following steps: - To generate a UML model that is not domain-specific, select the Default
Implementation extension.
- To generate a UML model that is SCDL-specific, select Skeleton
only.
- To prevent the transformation from transforming the selected element,
select Do not transform.
- Optional: Specify the
profile that the transformation applies to the generated service model.
On the Properties page, from the Target profile list, select a profile.
The
transformation applies the stereotypes in the profile to the corresponding
elements in the generated service model.
Important: The Software Services profile is deprecated and a profile called the Services Modeling (SoaML) profile is available for modeling services. For information
about migrating from the Software Services profile to the Services Modeling (SoaML) profile, see the related link at the end of this topic.
For information about how stereotypes in the Software Services profile map to stereotypes in the Services Modeling (SoaML) profile, see the related link at the end of this topic.
- Click .
Results
The options are applied the next time that
you run the transformation.