Netsight Configuration data (Nodes, Measurement Jobs, Users etc) can be uploaded in bulk from a file as an alternative to creating or editing these objects individually. Netsight enforces the same permission-based restrictions on what changes a user can make through uploading data as what they can do otherwise.
These bulk data operations can be much more efficient for creating a large number of similar data items in the database than using the GUI.
Netsight folders and their contents can be exported to comma-separated value (CSV) files. This is done from the Export Database Contents page. To reach this page, choose "System Tools" from the menu-bar and "Export" under "System Objects" from the Side Menu. Alternatively, you can right-click a folder in the Netsight Explorer and choose "Export Folder Contents" from the context menu. Once on the page:
The files exported from Netsight are comma-separated value (CSV) files, with logical data sections separated into tables by the use of markup tags. These tags should be placed on lines by themeselves, as this makes the file easier to read in a CSV file editor. The logical data sections are referred to as tables. They do not exactly match the database tables, but are a close approximation. For each relevant table, a there is a structure in the CSV file as follows:
<table> <tablename> TABLENAME </tablename> <columnnames> COLUMNNAME1, COLUMNNAME2, ... </columnnames> <data> Data for Column 1 Row 1, Data for Column 2 Row 1, ... Data for Column 1 Row 2, Data for Column 2 Row 2, ... ... </data> </table>
An import is made for each such structure that exists in the file. You do not have to include the structure for tables you do not wish to import any data into.
Each table in the file has an identifier to uniquely identify each row. This may be a single attribute or more than one in some cases, the combined contents of which must be unique in the table. Netsight decides whether to create a new entity or update an old one, based on whether an object already exists in the database with the supplied identifier. You should make sure before importing a file that your identifiers are correct. Incorrect identifiers can lead to unexpected results, such as entities getting created when an update was desired, and vice versa. If you are planning to use a bulk import to update the contents of an existing folder, it is a good idea to export the folder you are planning to update first. You can the update or add contents as required, rather than trying to create the folder's contents from scratch in the file.
The identifier for each entity type is given in the Import Template.
For security, user password hashes are NOT exported to the CSV file. The column is left blank. However, when updating the user through a bulk upload, the password is not changed. There is therefore no need to fill out this column before uploading your file. Note however, that if you are going to create a user, you should specify the plain text password of the user in the appropriate column. No user can be created without a password.
System Administrators can also specify system administration data such as Job Types when editing a CSV file for upload. This is no different to the specification of any other data in the file.
Here is a template for an import. It includes a structure for importing each of the tables that data can be imported into. It also specifies which column(s) form the identifier for each table, and gives an example for uploading some Nodes to the database. Please copy and paste the relevant structures from this template to help you build your CSV file for upload.
The Bulk Import operation is very powerful, having the ability to change a lot of database records in one operation. A user cannot do anything they wouldn't normally have permission to do through this operation. However, care is needed when preparing a file for import, as there is no shortcut for undoing changes. Please check your file carefully before uploading it.
To upload a file to the database, Write Access must be enabled.
Note that the import is not undone if errors occur — as much of the file as can be imported will be. You should examine the error messages carefully to determine what action you need to take in order to correct any problems.
System Administrators have the option of downloading all configuration data in the database to a CSV file. This download includes all folders and their contents, and also the Job Type configuration data. Note that this data is not exported when you export a folder (including the root JANET(UK) folder).
To do a full database download: (System Administrators only)
You can edit this file in the way described above, and later import it back to the database.