Dispatcher Services (Engineering Translation Service) is included with Teamcenter and can be used, instead of the catia2jt script, to translate files into JT. It is a complete translation service.
Dispatcher Services software must be installed on a dedicated translation server and is responsible for CATIA files translation. Please refer to the Teamcenter Installation Guide for assistance on configuring Dispatcher Services for your environment. It is not part of the Integration.
It is not necessary to modify the catia2jt script while using this method.
Teamcenter Integration for CATIA supports Dispatcher Services translations.
When Dispatcher Services is installed, and preferences are set correctly, CATIA files are sent to the Dispatcher Services Translation Server when the Create JT option on the Save Manager form or Convert to JT option within the CATIAV5 Teamcenter menu is selected.
A dialog displays when Dispatcher Services is active.
The JT Conversion Process dialog box only displays when CATIA_ETS_catiav5tojtdirect_available
or CATIA_ETS_catiav4tojtdirect_available is
set to FALSE and translation requests
have still been submitted to the defined Dispatcher Services.
The JT Conversion Process window does not display during the conversion process when Dispatcher Services is used. During the Dispatcher Services translation process, it is possible to continue working on the CATIA side while translation of files occur on the server.
To view a file's Dispatcher Services translation status, pick Translate CAD >> to JT Administration from the Teamcenter toolbar to view files currently in queue for translation. Refer to the Teamcenter documentation for detailed information on using the Dispatcher Services interface through the Portal client.
The following prerequisites provide the ability to convert V4 and V5 files using Dispatcher Services, one using Dispatcher Services and one using the catia2jt script, or both V4 and V5 files using the catia2jt script.
1. The Dispatcher Services solution must be installed (the ETS_available Teamcenter Preference will be set to TRUE or Yes)
2. The catiav5tojtdirect translation solution must be installed
3. The CATIA_ETS_catiav5tojtdirect_available preference set to TRUE.
If either ETS_available or CATIA_ETS_catiav5tojtdirect_available is set to false, the catia2jt script is used to translation V5 files into JTs, by default.
1. The Dispatcher Services solution must be installed (the ETS_available Teamcenter Preference is set to TRUE or Yes).
2. The catiav4tojtdirect translation solution must be installed
3. The CATIA_ETS_catiav4tojtdirect_available preference set to TRUE.
If either ETS_available or CATIA_ETS_catiav4tojtdirect_available is set to false, the catia2jt script is used to translation V5 files into JTs, by default.
By default, the catia2jt script is used unless Dispatcher Services options (ETS_available and CATIA_ETS_catiav5tojtdirect_available) within Teamcenter Preferences are set to TRUE.
Settings such as Dataset Types or Named References supported by Dispatcher Services are part of the Dispatcher Services configuration. Please advise an Dispatcher Services administrator prior to changing them.
The service name for the CATIA V5 translation service is CATIA_translation_service_name. Set the Teamcenter multiple string values preference, CATIA_ETS_translation_services, with the CATIA_translation_service_name value and set the CATIA_translation_service_name to SIEMENS.catiav5tojtdirect, to use the CATIA V5 translation service.
To convert CATIA V5 files into JT files using Dispatcher Services, set the CATIA_ETS_translation_services to the CATIA_translation_service_name and set the CATIA_translation_services name to SIEMENS.catiav5tojtdirect. After setting this preference, the Integration submits the datasets that are supported by the designated services.
By default, CATIA_translation_service_name is configured to manage CATPart and CATProduct dataset types. View the dataset type definition list of the CATIA_translation_service_name located in the COMMONcatiatojt_ets_ds_types Teamcenter Preference.
It may be necessary to delete the CATProduct entry within the COMMONcatiatojt_ets_ds_types Teamcenter Preference. The value is set by default during Dispatcher Services installation, and may lead to latency of the translation server.
The service name for the CATIA V4 translation service is defined by CATIA_V4_translation_service_name. Set the Teamcenter multiple string values preference, CATIA_ETS_translation_services, with the CATIA_V4_translation_service_name value, and set the CATIA_V4_translation_service_name to SIEMENS.catiav4tojtdirect to use the CATIA V4 translation service.
To convert CATIA V4 files into JT files using Dispatcher Services, set the CATIA_ETS_translation_services to the CATIA_V4_translation_service_name and set the CATIA_translation_services name to SIEMENS.catiav4tojtdirect.
By default, CATIA_V4_translation_service_name is configured to manage catia (.model) dataset type. View the dataset type definition list of the CATIA_V4_translation_service_name located in the COMMONcatiatojtV4_ets_ds_types Teamcenter Preference.
It is possible to call other Dispatcher services during the JT conversion process (script and/or Dispatcher Services).
A dialog box which appears during the JT conversion process is the result of using catiav5tojtdirect and catiav4tojtdirect. Pick Translation >> Administrator Console - All to verify the status of a translation task using other services.
When Dispatcher Services is installed, the ETS_available Teamcenter preference is set to true or yes. It must also be true or yes to call other Dispatcher Services.
To call other services:
Define the service to use in the CATIA_IdService _translation_service_name preference, where IdService is an identifier related to the service, myService.
CATIA_IdService_translation_service_name =
PROVIDER.myService
Add CATIA_IdService _translation_service_name to the CATIA_ETS_translation_services preference values list, to use this service. The Dispatcher Translation Services method calls all services defined in CATIA_ETS_translation_services.
Add the list of dataset types which can be sent to the service to the COMMONcatiatojtIdService _ ets_ds_types preference. After setting this preference, the Integration submits the datasets that are supported by the designated services.
Add the CATIA Named References required to translate the correspondng dataset types (listed in the COMMONcatiatojtIdService _ets_ds_types preference) to the COMMONcatiatojt_<dataset_type>_ets_nr_types preference.
To send CATPart and CATProduct files to the Dispatcher Service called
myService, define the identifier related to that service, i.e.,
IdService and set the following preferences:
1. CATIA_ETS_translation_services
=
CATIA_translation_service_name
CATIA_IdService_translation_service_name.
2. CATIA_
IdService_translation_service_name =
PROVIDER.myService
ETS_available = TRUE
3. COMMONcatiatojt
IdService_ets_ds_types =
CATPart
CATProduct
4. COMMONcatiatojt_CATPart_ets_nr_types
=
Catpart
5. COMMONcatiatojt_CATProduct_ets_nr_types=
Catproduct
A Translation Service can also be called from a workflow process or by using the Translation >> Translate menu in Teamcenter.
First, select a dataset with defined preferences then pick Translation >>Translate. The translator(s) defined for the dataset display. Select a cell containing a translator service to display translator values.
A list displays when more than one translator has been defined.
The Integration submits the item revisions that are supported by the designated services.
For example:
1. The
following structure is created in CATIA.
A1
|_ P1 with a CATShape Shape Representation and a V4 Shape Representation
2. The assembly is saved to Teamcenter without JT translation activated.
3. After selecting P1 CATPart and the CATShape datasets in MyTeamcenter, Translation >> Translate menu in Teamcenter is used and catiav5tojtdirect service is selected.
Result:
Two ETS requests are sent after translation:
A DirectModel dataset is created, attached to item revision and CATPart dataset
A DirectModel dataset is created and attached to the CATShape dataset only.
JT files are imported into DirectModel datasets. DirectModel dataset versions have the same version number as their source datasets.