To specify the information that the transformation uses
to generate Web Services Description Language (WSDL) output that you
expect, use the New Transformation Configuration wizard and 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.
To
configure a UML-to-WSDL transformation:
Procedure
- 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 appear in this list.
- In the Protocol section,
specify the modeling protocol, which is also called the design contract
management protocol (DCMP). The value that you select determines whether
to synchronize the source and target of the transformation.
- If the source model is the primary
engineering artifact, select Conceptual.
Any changes to the source model are propagated to the target model.
- If the target model is the primary engineering
artifact, click Mixed.
The transformation converts the source artifacts to visual representations
that are directly connected to the target artifact. Select this option
to work in the target domain instead of with the source model, or
to retain the artifacts for analysis. The transformation output becomes
the primary engineering artifact.
- If the architecture that the source
artifacts represent evolves independently from the target, select Reconciled.
Selecting this option enables the reverse transformation, which you
can use to compare the source and target, and to reconcile changes.
You might also select this option if different teams implement, develop,
or maintain the architecture.
Note: When you select
this option, additional properties become available in the "Reverse
transformation" section of the
Main page.
For some transformations, additional pages become available in the
transformation configuration
editor.
For information about configuring the reverse transformation, see
the related link below.
- 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 specify whether the output that
a transformation generates replaces or merges with a saved model,
in the Merge options section, select from the
following merge options:
| Option |
Description |
| Visual merge |
Displays user prompts and warning dialog boxes when models
merge. |
| Silent merge |
Suppresses prompts and dialog boxes when models merge. |
| Do not merge: Overwrite files without a warning |
Overwrites all conflicting files automatically. |
| Do not merge: Warn before overwriting any files |
Prompts you for confirmation before conflicting files are
overwritten. |
| Automatically add new elements to the target model |
Adds new elements without prompting you for confirmation.
Selecting Visual merge enables this option. |
| Save changes before validating files |
Requires that you to save merged models before allowing file
validation. Selecting Visual merge enables
this option. |
| Automatically validate saved changes |
Opens the Validate Merged Result Session window after a merged
model is saved. Selecting Visual merge enables
this option. |
- 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: To
display the errors that occurred when the transformation ran, on the Main page,
select the Open the Report dialog box when the transformation
is complete check
box. Selecting this check box displays only the generated errors.
The same information is also written to the error log, which you can
view by clicking .
To display the warnings that occurred when the transformation
ran, select the Show warnings in the Report dialog
box check
box.
- 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: Click the WSDL Options tab
to specify the default or custom WSDL binding that the UML-to-WSDL
transformation uses.
- Optional: Click the Output Options tab
to specify the transformation configuration output options.
- To create a separate file for each interface and data type
that the transformation generates, select Create a separate
file for each interface and data type. The transformation
also uses the Wrapped Document Literal binding.
- To process UML elements that do not have a stereotype applied,
select Process UML elements that do not have stereotype.
If
you clear this check box, and the
Services Modeling (SoaML) profile
is applied to the model, the transformation processes only the following
elements:
- Components that have the «Participant» stereotype applied
- Interfaces that have the «ServiceInterface» stereotype applied
If you clear this check box, and the deprecated Software Services profile
is applied to the model, the transformation processes only elements
in a package or component that have a stereotype applied.
For
more information about the output that the transformation generates,
see the related reference topic below.
- In order for WSDL document output to be compatible with IBM® WebSphere® Integration Developer,
select Generate additional complex types (applies to the
WRAPPED-DOCUMENT-LITERAL binding only) for the transformation
to generate additional complex types for UML interfaces containing
operations without input parameters.
The transformation generates
an XSD element, gives it a name from the interface operation, and
adds a WSDL part to the WSDL request message that references the new
element.
- To specify how the transformation processes referenced and
derived data types, select a setting from the Data type
processing list.
- To specify the addition of prefixes and suffixes for the target
namespaces of resources, select a resource in the table; then click Edit
Namespace.
- To specify the path of the output schema file, click Edit
Output Location.
The location for the schema file can
be any folder under the target container. The target container is
specified on the Source and Target page. You can also specify a path
under the target container to which to add new folders. New folders
are created when the transformation completes.
- To specify prefixes and suffixes to add to the file names
of resources, select a resource in the table; then click Edit
File Name.
- Optional: Click the Properties tab
to specify values for the properties of the UML-to-WSDL transformation
by selecting a property in the Value column.
| Option |
Description |
| Perform extensive context validation |
Specifies whether the transformation performs extensive context
validation every time the transformation configuration is saved. Setting
this value to false can improve performance, and
is a requirement if you want to generate Parlay X specification-conformant
WSDL. The context validation is still performed whenever the transformation
is run.
|
| Reverse the first segment of the namespace |
If set to true, the transformation generates
a schema in a folder with the top-level UML package name, a namespace
resembling a real URL, and a conventional name for the Java package.
For example, if the top-level package name is com.xyz.test, the schema
would be generated in a folder, com/xyz/test, with the namespace of
http://test.xyz.com/ and a Java package name of com.xyz.test. |
| Validate the transformation source for cyclic
references |
Specifies whether to check source for cyclic references or
not. XSD can use cyclic references; however, some tools used to generate
code from WSDL documents generate errors. |
- Optional: Specify
the transformation extensions to enable or disable.
- Optional: This content applies to version 7.5.4 or later. If
you have installed the feature for IBM Rational® Modeling for Communications Applications and
you want to generate Parlay X specification-conformant WSDL, you must
enable the associated transformation extension and turn off context
validation. To generate Parlay X WSDL, perform the following steps:
- Click the Extensions tab; under UML
to WSDL extensions, in the ID column, click the check
box for the extension named ParlayX extension Transformation
extension.
- Click the Properties tab; then
set Perform extensive context validation to false.
- Click .
Results
The options are applied the next time that
you run the transformation.