multiple_svr_variant_configurator

Assists in creating configured structure representations using saved variant rules (SVRs) from unconfigured structure representations. Use the bomwriter utility to generate an unconfigured PLM XML file containing product structure information, including the variant conditions for child lines. Use the multiple_svr_variant_configurator utility to read the unconfigured PLM XML file and the specified SVRs. The utility generates multiple pruned PLM XML files, corresponding to each SVR. Optionally, import pruned PLM XML files back into Teamcenter as DirectModelAssembly datasets using the import_file utility. Open the configured PLM XML files or datasets in Lifecycle Visualization. Note Before running this utility, there must be a DirectModelAssembly dataset with a TCEng_rdv_plmxml_unconfigured relation placed under the product revision containing the unconfigured PLM XML file. Import the dataset using the import_file utility, ensuring that the variant XML preexists as a named reference of the unconfigured dataset. Syntax multiple_svr_variant_configurator [-u=user-id -p=password | -pf=password-file -g=group] -product_id=product-item-ID -product_rev=product-revision-ID -dataset_name=unconfigured-dataset [-log_file=file-name] -directory_name=directory-name {-svr_input_file=file-name | -process_all_svrs=Y} [-is_import_required=Y] [-import_utility=path-to-utility] [-import_utility_parameters=utility-parameters] [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges. Note If Security Services single sign-on (SSO) is enabled for your server, the -u and -p arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -product_id Specifies the product item ID. Specify the top level of the assembly for which you want to generated configured PLM XML files. -product_rev Specifies the product revision ID. Specify the top level of the assembly containing the SVRs. -dataset_name Specifies the name of the dataset under the product revision containing the unconfigured files. This must be a DirectModelAssembly dataset with a TCEng_rdv_plmxml_unconfigured relation placed under the product revision containing the unconfigured PLM XML file. -log_file Specifies the full path to the log file in which activity if recorded. Use this argument only when importing the pruned PLM XML files. -directory_name Specifies the full path to the directory in which the pruned PLM XML files are stored. The user running the utility must have write access to this directory. -svr_input_file Specifies the full path to the file containing the SVRs with which to configure the assembly. You must specify either the -svr_input_file or the-process_all_svrs argument for the utility to run. If both are specified, -svr_input_file takes precedence. -process_all_svrs Specifies that all SVRs are processed. The valid value is Y. You must specify either the -svr_input_file or the-process_all_svrs argument for the utility to run. If both are specified, -svr_input_file takes precedence. -is_import_required Specifies whether the pruned files are imported. Valid values are Y and N. The default setting is N. If you set this argument to Y, you must set the -import_utility and -import_utility_parameters arguments. -import_utility Specifies the full path to the import_file utility, used to import the pruned files. If you set this argument, you must set the -import_utility_parameters argument. -import_utility_parameters Sets the required parameters of the import_file utility. Specify parameters in a single string. Separate each parameter with a hash sign (#). For example: Copy -import_utility_parameters=#-u=userID#-p=password#-g=group> #-d=ConfiguredAll#-ref=ConfiguredAssembly#-type=DirectModelAssembly #-relation=TCEng_rdv_plmxml_configured#-desc=ConfiguredAll #-use_existing=no#-f=#-item=ABC00004#-revision=001# -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 Before running this utility, there must be a DirectModelAssembly dataset with a TCEng_rdv_plmxml_unconfigured relation placed under the product revision containing the unconfigured PLM XML file. Import the dataset using the import_file utility, ensuring that the variant XML preexists as a named reference of the unconfigured dataset. Examples In the following example, all SVRs listed in the input_svr.txt file are used to generate multiple pruned PLM XML files, one file for each SVR. The files are not imported. The pruned PLM XML files are generated from the multi_svr directory. Copy multiple_svr_variant_configurator -u=userID -p=password -g=admin -product_id=ABC004 -product_rev=001 -dataset_name=ABC00004Unconfigured2-directory_name= c:\temp\multi_svr -svr_input_file=c:\temp\multi_svr\input_svr.txt In the following example, all SVRs under the ABC004/001 product revision are used to generate multiple pruned PLM XML files, one file for each SVR. The files are not imported. The pruned PLM XML files are generated from the multi_svr directory. Copy multiple_svr_variant_configurator -u=userID -p=password -g=admin -product_id=ABC004 -product_rev=001 -dataset_name=ABC00004Unconfigured2 -directory_name=c:\temp\multi_svr -process_all_svrs=y In the following example, all SVRs under the ABC004/001 product revision are used to generate multiple pruned PLM XML files, one file for each SVR. The files are then imported back into the Teamcenter database. Copy multiple_svr_variant_configurator -u=userID -p=password -g=admin -product_id=ABC004 product_rev=001 -dataset_name=ABC00004Unconfigured2 -directory_name=c:\temp\multi_svr -process_all_svrs=y -is_import_required=Y -log_file=c:\temp\multi_svr\log_file.txt -import_utility={TC_ROOT}\bin\import_file -import_utility_parameters=#-u=userID#-p=password#-g=admin #-d=ConfiguredAll#-ref=ConfiguredAssembly #-type=DirectModelAssembly#-relation=TCEng_rdv_plmxml_configured #-desc=ConfiguredAll#-use_existing=no#-f=#-item=ABC00004 #-revision=001# The parameters for the import_file utility are set in a single string, each parameter separated by a hash mark (#). The -d parameter specifies the prefix to the dataset names created upon import, followed by an underscore. For example: Copy ConfiguredAll_ You must include the -f parameter in the parameter string for the import_file utility. Do not assign it a value. The import utility automatically supplies the pruned PLM XML files. Related Topics Structure Management on Rich Client ─ Usage