Enable QSEARCH_process_queue, QueryScos, and RenderMgtTranslator translators

QSEARCH_process_queue service generates spatial index boxes. Prerequisites: Teamcenter and the qsearchprocessqueue utility should 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. QueryScos translator Generates a list of structure context objects (SCOs) for a given saved query or folder containing the SCOs. The generated SCOs are used by the RdvContextDBDownload or RdvContextNONDBDownload translators. Prerequisites: Start the start_sco_dispatcher utility to invoke the query_scos translator. Install the RdvContextDBDownload or RdvContextNONDBDownload translator. RenderMgtTranslator service translates files from one input file format to another output file format and stores the output files in Teamcenter. This service is supported on Windows only. Prerequisites: Requires PreviewService. Use TEM or Deployment Center to install and configure PreviewService. Teamcenter Visualization Convert is a prerequisite for PreviewService. Note Verify whether Teamcenter Visualization Convert is installed correctly by performing a test conversion using the prepare command line utility. You can run this utility from the VIS_version/VVCP directory. You can use any other translator if the translator is defined as a dispatcher service configuration in Business Modeler IDE and the ServiceToExeMap attributes in the Dispatcher_Root\Module\conf\translator.xml file are set to the location of the translator .bat (Windows) or .sh (Linux) files. Note You can use the rendermgt_previewservice.bat or rendermgt_previewservice.sh file in the Dispatcher_Root\Module\Translators\previewservice directory as a template for creating the .bat or .sh file for your custom translator. 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.