Add custom translators to Dispatcher > Extract data and load data required for translation
What is the extract-transform-load (ETL) model?
The dispatcher client employs the ETL model (Extract-Transform-Load) for data translation. It provides a framework that supports extraction of data for translation, translation, and loading of translation results. The dispatcher client is implemented as a standalone SOA application. Extraction provides a collection of input data to be submitted as a translation task to the Dispatcher Server. The nature of the extracted data is dependent upon the input required by the desired translation. After extraction, the dispatcher client submits a translation task to the Dispatcher Server. The Dispatcher Server then processes the translation tasks. After the translation is complete, the dispatcher client loads the translated data in the appropriate Teamcenter target data model. The nature of the translation results is dependent on the output generated by the desired translation. Storage of the results is also dependent on the target data model. The dispatcher client provides support for translator integrations and related data models with two Java classes: one for preparation of translator input (TaskPrep class) and one for storage of translator output (DatabaseOperation class). These two classes provide a structure for translator- and data model-specific logic implementation. The dispatcher client configuration properties define the mapping between translators and supporting classes. These classes provide a structure for translator-specific and data model–specific logic implementation. The dispatcher client configuration properties define the mapping between translators and supporting classes.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/plm00565/eco1737253046255/eia1737253046598/xid1675534.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)