TeamcenterKnowledge

Enable default translators > Planning for enabling translators > Editing the translator.xml file

Editing the translator.xml file

Each translator is associated with a translator module by specifying the required information in the translator.xml file in the Dispatcher_Root\Module\conf directory. Similar to any XML file, it consists of elements and attributes. Each translator is defined within a unique element Each supported translator is defined in its own element (for example, ToZipfile), all nested within a element. Nested within each translator element are elements that define the location of the translator and any required software, supported file name extensions, class path definitions, or any other required data. Modifying the isactive attribute to activate a translator To activate a translator, modify the isactive attribute to true. Retain it as false to keep the translator turned off. Note By default, the isactive value is set to false for all translators in the translator.xml file. Wrapper class attribute for defining a wrapper Most translators have a wrapper class attribute used to define a wrapper. Wrappers are used for managing translations including threading, process control (start and stop), status checking, error handling, and completion status. Example: Copy Note You need not modify the wrapperclass attribute unless you write a custom wrapper to manage your translator. Modifying attributes to associate a translator To associate a translator with the translator module, modify the attributes that point to various executable files or the class path. In some cases, you must define additional elements to accommodate additional file extensions. Modifying input and output extensions The InputExtensions and OutputExtension elements define valid input and output file extensions for each translator. Note If your site uses nonstandard file extensions (extensions that are not specified in the translator.xml file) for certain file types, you can add that file extension to the list of supported extensions. Example: Copy As shown in the example above, you must change the nitem attribute based on the number of input or output file extensions for each translator. Editing the maxlimit, NoOfTries, and OutputNeeded properties. maxlimit defines the maximum number of translation that can run simultaneously. The default value is 1. NoOfTries defines the number of tries to make in case the translation fails. The default value is 1, that is, no retry. OutputNeeded defines whether a result file is expected from the translation. The default value is true.

Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/plm00565/kbg1737253043026/vdg1737253043125/whh1737253043229/edit_translator_xml.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)