assign_propagation_data

The assign_propagation_data utility performs security data assignments on a list of objects and restores data conditions where security data on top-level objects exists, but the associated POR (ProjectObjectRelation) objects are missing or invalid. Syntax The syntax for the assign_propagation_data utility is as follows: Copy assign_propagation_data [-u=user-ID {-p=password | -pf=password-file} -g=group] [-mode=auto | explicit] [-attr_name=name] [-value=value] [-filePath=file path] [-bypass_lmdlmu=1] [-h] Arguments -u Specifies the user ID. This must be a user with Teamcenter administration privileges. If this argument is used without a value, the operating system username is used. 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 clear text password. This argument is mutually exclusive with the -pf argument. -pf Specifies the full path and filename to a password file. For 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. -mode Different modes for running the utility. Report is written to the syslog. Set TC_KEEP_SYSTEM_LOG to true to keep the syslog file. For more information, see Setting environment variables for logging explicit The value for the propagation-enabled attribute of interest must be provided on the command line by using the “-value=” parameter. For list-based entries, a single value or a comma-separated list of values can be provided. If project or license objects are specified, their respective project ID or license ID is required as input. auto Analyze the list of WorkspaceObject UIDs in the input file for their security values set related to the propagation-enabled attribute name specified in the attr_name parameter. -filePath An input file containing UIDs of objects which are top-level WorkspaceObject in need of propagation or re-propagation. -bypass_lmdlmu If set to 1, this bypasses the update of the last modified date and the last modified user. Else, these are updated accordingly once attribute data changes are processed and saved. -attr_name Name of the attribute we want to associate propagation data to. Custom propagation-enabled attributes are supported, except for scalar and list-based date attributes. -value In case of mode=explicit, specify the explicit value for the propagation enabled attribute defined in -attr_name. If the propagation-enabled attribute allows list-based values, specify one or many values (comma-separated), and in the case of a single value propagation-enabled attribute such as owning_project, IP or government classifications, specify one value. -h Displays help for this utility. Examples The following is a sequence of usage commands: Assign projects p1, p2, p3 to a list of top-level objects specified in the input file. Copy assign_propagation_data -u=Tc-admin-user -p=password -g=group -mode=explicit -filePath=t.txt -attr_name=project_list -value=p1,p2,p3 Perform propagation repair for objects where PORs are missing. Copy assign_propagation_data -u=Tc-admin-user -p=password -g=group -mode=auto -filePath=t.txt -attr_name=owning_project Assign value to attribute bypassing the update of last modified user and last modified date. Copy assign_propagation_data -u=Tc-admin-user -p=password -g=group -mode=auto -filePath=t.txt -attr_name=owning_project -bypass_lmdlmu=1 Additional Notes All custom propagation-enabled attributes (both scalar and list-based) are supported except scalar and list-based Date. Logical values are specified as 0 [=false] or 1 [=true]. Care must be taken when propagation-enabled attributes are updated on objects where propagation-enabled attributes in other groups exist but do not have an associated POR. In that case (and this applies to both “auto” and “explicit” operation modes), the system will also perform re-propagation and POR creation for those other propagation-enabled attributes. This cannot be de-activated. Note If there are such known data conditions, it is advised to first process auto assignment of such missing POR before explicit assignment of other Security Groups is attempted.