Create a translator to define the commands to run on all
the buildable files for a language definition.
Before you begin
Before you begin this task, you must create a project area.Restriction: Before you can create, modify, or delete a translator,
you must have permission to modify the translator. You can manage
these permissions from the Project Configuration node on the Process
Configuration tab in the Project Area editor.
Note: If
you created a translator with the Rational Team Concert version
3.0.1.x client, you must update to version 4.0 or later and change
that translator. The client preserves your version 3.0.1.x translator
output name.
About this task
You can create a translator one of two ways:
- Expand these nodes in the Team Artifacts navigator: .
- From the main menu, select .
The following task describes how to create a translator from
the Translators node in the Team Artifacts navigator.
Procedure
- From the Team Artifacts view, select your repository connection
and log in to your project area.
- Expand your project area node, and then expand .
- Right-click the Translators node and click New
Translator.
The Translator editor
opens with two tabs: General and History.
- In the Name field of the Translator editor,
provide a name for the translator.
- On the General tab, specify the
following attributes:
- Optional: On the General tab, in the Description field,
provide a brief description of your new translator.
- If you select the Inspect built object and
update build map option, Link-Edit support is enabled
for the translator.
- If you made changes to this translator that do not require
a full analysis of buildable files, click the Ignore changes
to this system definition for dependency builds check
box.
- To use a search path other than the default search path
in the build definition, select Override build definition
search path in the Search path section
and complete these steps:
- Click Browse to select a specific search
path or a search path build property.
- In the Select Search Path pane, select either Search
path or Build property. To select
a search path, click Browse and choose the
search path that you want to use for this translator. If you select Build
property, enter a search path build property that is defined
in the build definition. Specify the property name in the form of
${my.build.property}.
- In the Output Object section,
specify a name and type of target output object. In the Deployment
type or variable field, you can enter either a deployment
type, or a variable that exists in the translator you are editing.
Optionally, select the Rename output object check
box to modify the translator output name by using a pattern or variable.
For details about translator output pattern rules, see Translator output pattern rules.
- In the Variables section, click Add to
create variables and values for the translator to use. You can also
edit or remove existing variables.
- In the Commands section, enter
the commands that you want the translator to run, depending on whether
the output object exists.
- On the History tab, you can see
all changes made over time by different users to the translator. You
can review the state of the translator at any point in time, which
is useful for debugging and fixing dependency build problems.
- To save your new translator, click Save .
What to do next
You can also duplicate any translator. To duplicate a translator,
complete the following steps:
- Open the Team Artifacts view.
- Expand the Translators node.
- Right-click the translator to duplicate and click Duplicate.
- In the Duplicate system definition window, in the Name field,
provide a name for the duplicate translator.
- To duplicate the translator, click OK.
The new duplicate translator is displayed under the Translators node.
If it is not, refresh the view.