You must know about the Veritas Operations Manager Enterprise Server CSV object files if you update business views using the command line interface.
Each .csv file represents one of the object types that are defined in the .view file for this business view. These files, collectively, are called the business view assignment CSV files.
Each file should have the same base name as the name of the .view file. Business view .csv files use the following naming convention. All files that make up an individual view must use the same prefix. While the business view definition file has a '.view' extension, the CSV files have the extensions that map directly to their associated object type. For example, a "foo_Host.csv" extension defines the business view assignment for hosts.
If you used "GEOGRAPHY" as a base name, the .view and CSV files would be named as follows:
Each object type has a set of columns that uniquely identify the object. These columns are required in each object .csv assignment file. They are in addition to the required hierarchy level columns that are defined in the .view file. Records that do not have the required number of columns are rejected.
Each object type requires the following columns.
Table: Object types and their required columns
The columns in the CSV file start with all of the levels in the branch, in order, separated by commas. There must be a column for each of the levels that are defined in the business view definition file. In addition to the level columns, you must define all the columns required for the object type. The unique identifier columns for the object type follow the levels.
Each non-comment, non-blank line defines a node or object in the business view. If the view defines a tree branch but no object assignment, use empty commas as placeholders for the object columns. If a leaf node misses its parent nodes, use empty commas as place holders.
#Continent, Country, State or Province, City, Data Center, name, IP, unique id
Comment lines start with "#". Comments and blank lines are ignored. Do not place any characters before the #. For example, if you include double quotes (") before the #, then the business view import process fails because the comment lines are considered assignment rows.