bmide_manage_batch_lovs

Reports, extracts, and updates values for externally managed Lists of Values (LOVs). Extracted batch LOVs comprise at least two files: the list definition, and localizations of list values. When you use the bmide_manage_batch_lovs utility to update externally managed LOVs in the database, you submit the LOV list definition as a single XML file, with localizations in a lang subdirectory. A consolidated localization file can contain localizations for multiple languages and is named LOV_file-name_lang.xml. Individual locale files each contain localizations for one specific locale, and are named LOV_file-name_lang_locale.xml. For example, file-name_en_US.xml, file-name_zh_CN.xml. You can place either a single consolidated file or multiple locale-specific files in the lang folder, but not both at the same time. If you are using client cache at your site, then after updating the externally managed LOVs through this utility, to update the LOV cache stored on the server run the generate_client_meta_cache utility with the generate lovs command. For information about externally managing LOVs, see Create an externally managed (batch) list of values in BMIDE for Data Model Design. Syntax bmide_manage_batch_lovs -u=user-id {-p=password | -pf=password-file} [-g=group] -option=[update | extract | report] -lov=[all | comma-separated-list-of-lov-names] -file=file-path [-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 user's password. This argument is mutually exclusive with the -pf argument. -pf Specifies the full path and filename of 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. -option Valid values for option are: update Updates the values for all the externally managed LOVs defined in the input file. extract Extracts all the externally managed LOVs and their corresponding values into the specified file. The localizations also get extracted and are stored in the lang directory. Use with the -lov argument to specify the externally managed LOVs to be extracted. report Provides a report of all the externally managed LOVs in the Teamcenter database. Use with the -lov argument to specify the LOVs in the report. The report is generated in the HTML format. -lov Use only in conjunction with the -extract or -report arguments. Valid values for option are: all Extracts or runs a report on all externally managed LOVs. comma-separated-list-of-lov-names Extracts or runs a report only on the listed externally managed LOVs. If a list of LOV names is not specified, the all argument is assumed by default. -file Specifies the path to the file containing LOV values (when updating LOV values in the database), the path of file where the extracted LOVs are to be saved (when extracting LOV values from the database), or the file where the generated report needs to be saved (when running a report of LOV values in the database). -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 None. Examples When you install the Business Modeler IDE, sample files are installed to TC_ROOT\bmide\client\samples\externallymanagedlovs. To extract all the LOV values, sub-LOV attachments, and localizations from the database, enter a command like the following on a single line: Copy bmide_manage_batch_lovs -u=username -p=password -g=dba -option=extract -file=BatchLOV_LOV1_extracted.xml Do this when you want to check the current values on any of the LOVs or to use the extracted file as the basis for the next set of changes if the original source input file is no longer available. To extract LOV values, sub-LOV attachments, and localizations for specific LOVs in the database, enter a command like the following on a single line: Copy bmide_manage_batch_lovs -u=username -p=password -g=dba -option=extract -lov=BatchLOV_LOV1,BatchLOV_LOV2 -file=BatchLOV_extracted.xml To update the LOV values and localizations from an external file to the database, enter a command like the following on a single line: Copy bmide_manage_batch_lovs.bat -u=username -p=password -g=dba -option=update -file=BatchLOV_LOV1.xml Following is the BatchLOV_LOV1.xml file used in the example: Copy

Following is the BatchLOV_LOV1_lang.xml file that supplies the localization for the LOV values in the BatchLOV_LOV1.xml file. When you create a localization file, give it the same name as the LOV values file with _lang added to the file name, and place it in a lang subdirectory. Copy Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Level 7 Level 8 Level 9 Level 10 Level 1 Desc Level 2 Desc Level 3 Desc Level 4 Desc Level 5 Desc Level 6 Desc Level 7 Desc Level 8 Desc Level 9 Desc Level 10 esc To add LOV values and sub-LOV attachments to cascading LOVs, enter a command like the following on a single line: Copy bmide_manage_batch_lovs.bat -u=username -p=password -g=dba -option=update -file=BatchLOV_ValidCascading.xml Note You can add sub-LOV attachments in this way only on externally managed LOVs. Following is the BatchLOV_ValidCascading.xml file used in the example: Copy

Related Topics BMIDE for Data Model Design