mrm_plmxml_updater

Compares two PLM XML files and their corresponding folders that contain images, and generates a script containing the differences. You can use this utility to create scripts to update the Manufacturing Resource Library's (MRL) class hierarchy according to an exported customer PLM XML file and the PLM XML file found in the MRL kit. Note Running this script can be time-consuming, depending on the number of differences found when comparing the two files. Syntax mrm_plmxml_updater -customer=customer-PLM-XML-file -master=PLM-XML-file-in-MRL-kit [-configurationfile=configuration-file] [-outputdirectory=output-directory] [-v] [-h] Arguments -customer Specifies the customer PLM XML file. This is the class hierarchy for one MRL module that is exported from the customer’s database. The folder with the class images and icons should be in the same directory. -master Specifies the master PLM XML file from the MRL kit for the same MRL module that is specified in the customer argument. The folder with the class images and icons should be in the same directory. -configurationfile Specifies the path and file name of the configuration file that configures specific processing of the utility. This parameter is optional. If not specified, the default settings are used. If this argument is not specified, a default configuration file, configurationfile.xml, is created in the directory where the utility is started. The default configuration file can subsequently be modified and used as the input configuration file for the next comparison. -outputdirectory Specifies the path to the directory where all output files are stored. This parameter is optional. If not specified, the output files are stored in a directory entitled UPDATE located in the directory where the utility is started. If the directory does not exist, the utility creates it automatically. -v Provides more output on the currently running operation. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions Empty spaces in a path or file name must be surrounded by quotation marks. Examples Copy mrm_plmxml_updater -customer=D:\customer\mrl_tools_hierarchy_en.xml -master=D:\advanced_installations
resource_management\MRL\ImportFiles\tools\mrl_tools_hierarchy_en.xml -outputdirectory=D:\OUT\tools With verbose and configuration file set: Copy mrm_plmxml_updater -v -customer=D:\customer\mrl_tools_hierarchy_en.xml -master=D:\advanced_installations
resource_management\MRL\ImportFiles\tools\mrl_tools_hierarchy_en.xml -outputdirectory=D:\OUT\tools -configurationfile=D:\conf\configurationfile.xml The following update script files are created by the utility: Update script Contains 1_KEYLOV_PLMXMLIMPORT.bat The plmxml_import commands that import the new and updates KeyLOVs 2_ATTRIBUTE_PLMXMLIMPORT.bat The plmxml_import commands that import the new attributes 3_ATTRIBUTE_UPDATE.bat The smlutility commands that update the attributes 4_CLASS_PLMXMLIMPORT.bat The plmxml_import commands that import the new classes 5_CLASS_UPDATE.bat The smlutility commands that update the classes 6_VIEW_PLMXMLIMPORT.bat The plmxml_import commands that import the new views 7_VIEW_UPDATE.bat The smlutility commands that update the views The numbers of the files indicate the order in which they must be run to update the MRL hierarchy. In addition to the update scripts, the following directories are generated. Directory Contains ATTRIBUTES_XML The PLMXML files for the new attributes CLASSES_XML The PLMXML files for the new classes KEYLOVS_XML The PLMXML files for the new/updated KeyLOVs VIEWS_XML The PLMXML files for the new views INFO_FILES Information text files with the comparison For each of the following directory types, six information files are generated in the INFO_FILES directory: Key-LOVs Attributes Classes Views For example, for key-LOVs: File The file KEYLOV_LIST_ALL_CUSTOMER.txt Lists all key-LOVs from the customer PLM XML KEYLOV_LIST_ALL_MASTER.txt Lists all key-LOVs from the master PLM XML KEYLOV_LIST_CUSTOMER.txt Lists all key-LOVs that are in the customer PLM XML, but not in the master (= customer key-LOVs). KEYLOV_LIST_NEW.txt Lists all key-LOVs that are in the master PLM XML but not in the customer (that is, new key-LOVs) KEYLOV_LIST_MODIFIED.txt Lists all key-LOVs to be modified during the update KEYLOV_LIST_INFO.txt Describes exactly how each key-LOV is modified during the update. An example of the MRL update configuration file is listed in Configuring the update.