Enable NX translators

NxClone service Calls the ug_clone.exe utility to clone NX parts. NX must be installed with the UGManager module to use this service. NxNastran service Used to launch NX Nastran remotely using Simulation Process and Data Management. Prerequisites: The clients and Dispatcher Server should point to the common staging directory and both should have read/write permissions to that directory. To launch a service remotely, ensure that the service name in the translator.xml file matches the process name in the Simulation Tools Configuration window in CAE Manager. NxTransDirect service Translates NX files (.prt) to JT (.jt) and directly stores the JT files in Teamcenter. The system creates the JT file synchronously when you save a part. Prerequisites: The NX_ETS_NXTRANSDIRECT_ENABLED Teamcenter preference must set to True. The Save JT Data option must be selected in the NX session while performing the save. You can create a customer default that allows you to create the JT file synchronously when you save a part. It is applicable only when the Save JT Data option is also selected. If this customer default is not selected, JT file creation occurs as a batch translation in the background, which reduces the overall save time. 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. (Only for NxTransDirect service) To specify user credentials explicitly for translation process, comment out the following properties from the translator.xml file. It is not recommended to add the password as plain text to the translator.xml file or translator_name.bat (Windows) or translator_name.sh (Linux) file. Instead, generate an encrypted password file using the -encryptpwf argument with the Teamcenter install utility. For more information, see the step that follows. Example: Copy

(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: "%UGII_BASE_DIR%\ugmanager\run_nxtrans.bat" -u=Dispatcher-client-proxy-user -pf=pf_filepath_filename -changeOwnerToCad=false "-pim=yes" %* Example: -pf=C:\Users\user_name\AppData\encrptPass.pwf For more information, see Manage password files and install utility. 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. 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