upgrade_variant_rule_data

Migrates the variant rule objects to the new expression data model that allows to persist the session information. The perspective parameters and solver profile parameters together constitute the configurator session information for Product Configurator. This utility is by default run during Teamcenter upgrade process. However, if needed this utility can be run independently. Syntax upgrade_variant_rule_data [-u=user-id {-p=password | -pf=password-file} -g=group] [-batchSize=batch_size] [-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 user and password 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. -batchSize Specifies the number of variant rule objects migrated to the new expression data model in each batch. The default batch size is 1000. -h Displays help for this utility. Note While performing the upgrade in the replica site, the variant rule object is not upgraded to the new expression data model. This is done to ensure that site ownership is not changed for the variant rule object. You should run the data_sync utility before using the variant rule object in the replica site. It upgrades the variant rule to the new expression data model. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None. Examples Example 1 In this example, all variant rules that are referring to the old expression data model is migrated to the new expression data model in multiple batches with the default batch size of 1000. upgrade_variant_rule_data -u=Tc_admin -p=password Example 2 In this example, all variant rules that are referring to the old expression data model is migrated to the new expression data model in multiple batches with the default batch size of 2000. upgrade_variant_rule_data -u=Tc_admin -p=password -batchSize=2000