TeamcenterKnowledge

Enable default translators > Enable the default translators

Enable FMSTransfer, ImportObjects, JtToBBoxAndTso, and mmvindexgen translators

FMSTransfer service Used to forward a file from a temporary store and forward volume to its destination volume. Prerequisites: TC_ENABLE_STOREANDFORWARD site preference must be set to true. Uploaded files are transferred to their destination according to the set rules and the configured schedule. The user must have appropriate permissions to upload files. ImportObjects service Executes data_share -f=remote_import for a given items list. Prerequisites: Teamcenter and the Classic-Multisite feature must be installed to use this translator. JtToBBoxAndTso service Generates bounding box and TSO files from JT files in Teamcenter. Prerequisites: Teamcenter and the jttobboxandtso utility must be installed to use this service. This translator requires the Teamcenter password. To encrypt a password file, you set a temporary environment variable to the password you want to encrypt, and then generate an encrypted password file using the -encryptpwf argument for the install utility. mmvindexgen translator An MMV dataset consists of a spatial hierarchy of a model, which is harvested from JT data using the Teamcenter Dispatcher mmvindexgen translator. You can use the My Teamcenter Translation menu to automate the generation of the spatial index on a recurring basis, in order to capture design changes over the course of the product lifecycle. Prerequisites: When MMV index production is performed on an assembly under which a Spatial Hierarchy dataset already exists for one or more item revisions, the existing Spatial Hierarchy dataset is overwritten. To avoid an accidental overwrite of the Spatial Hierarchy dataset, Siemens Digital Industries Software recommends that you restrict the authorization of performing Spatial Hierarchy production to select user accounts. The VIS_mmvindexgen_admin_group site preference is used to give the user group the authority to run the mmvindexgen translator from the Teamcenter Translation menu. This translator requires Perl version 5.0.3 or later. (Optional) To define one or more revision rules to generate the Spatial Hierarchy dataset, open the mmvindexgen.config file from the Dispatcher_Root\Module\Translators\mmvindexgen directory and edit the revision_rules option. By default, this option does not have any revision rule and generates Spatial Hierarchy in the unconfigured mode. Enable the translators You can use TEM or Deployment Center to install the translator or manually edit the translator.xml file to enable the translator. The following is an example of how to edit the translator.xml file to enable the translator. Procedure Open the translator.xml file from the Dispatcher_Root\Module\conf directory. Set the isactive attribute to true to activate this translator. Note By default, this attribute is set to false. Open the translator.bat (Windows) or translator.sh (Linux) file from the Dispatcher_Root\Module\Translators\translator_name directory and edit the CHANGE_ME tags. For more information about CHANGE_ME tags, see the .bat file for the translator. Run the translator in standalone mode from the command prompt to verify whether it is working properly. For more information about running the translator in standalone mode, from a command prompt, change to the Dispatcher\Translators\translator_name directory and run the appropriate command for your platform: Note For more information, see the Readme file in the Translators\translator_name directory. Windows: translator_name.bat -help Linux: translator_name.sh -help (Optional) To set up Dispatcher-client-proxy-user as the owner of the translated files, make the following change to the translator_name.bat (Windows) or translator_name.sh (Linux) file. NxTransDirect translator example: Copy "%UGII_BASE_DIR%\ugmanager\run_nxtrans.bat" -u=Dispatcher-client-proxy-user -p=password -changeOwnerToCad=false "-pim=yes" %* If you set up Dispatcher-client-proxy-user as the owner of the translated files, you must create a dispatcher client access rule. After installation, you must add a rule to the access rule tree permitting the translation service proxy user to update attributes of a DispatcherRequest object. If this access rule is not created correctly, the dispatcher client reports errors.

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