Exporting and importing views

With this feature, you can complete the following use cases:

• Create a copy of a view: Export an out-of-the-box view, import it with a new name, modify its configuration, and save it as a new view. 
• Migrate a view: Create a custom view in the development or test environment and after confirming that the results are accurate, import it in the production environment.
• Share a view: Import a custom view that is created in one environment into a different destination environment.

For details, see the following sections:

• • To export a view
  • To import a view
  • Data mart considerations

To export a view

1. In the TrueSight console, navigate to Administration > Capacity Views. By default, the View tab is displayed. 
2. From the action menu that is located next to the view you want to export, click Export view. 
   The view is exported and you can select the location to save the exported view. The view is exported as the <View_Name>_<timestamp>.viewpkg file. 

To import a view

1. If you are importing an out-of-the-box view, first install the view.  
2. In the TrueSight console, navigate to Administration > Capacity Views. The View tab is displayed.
3. Click Import view. The Import view dialog box is displayed. 
4. Click Browse to select the view package file (.viewpkg) that you want to import. 
5. Click Apply. 
   A message indicating the data mart creation or update is displayed. You can choose to Proceed or Cancel the import. If the destination environment already contains the view with the same name, a backup of the existing view is created. 
   The view is imported and listed in the Views table. 

Data mart considerations

When you export and import the custom view, if the view is using a data mart, that data mart is also exported and then imported. If this data mart is using any data marts or being used in other data marts, all these data marts, that is, the entire hierarchy tree gets exported and and then imported in the destination environment. 

If your destination environment does not contain data marts that are being exported as part of the view package, they will be created. If the destination environment already contains the same data marts, they be updated based on the following scenarios:

• When importing from the TrueSight Capacity Optimization version 11.5.01.
  If your destination environment includes any data marts with the same identifier as one of the data marts being imported, the existing data marts are updated by the imported data marts.
  
  

  Example that shows the export/import flow

  Consider that you have exported the VMware view that contains the VMware systems data mart with identifier as ER_V_VMWARE_SYS. This data mart has a related data mart as VMware hosts.

  The destination environment contains the VMware VMs data mart with the identifier as ER_V_VMWARE_SYS.

  After you import, the the VMware systems data mart overwrites the VMware VMs data mart as both have same identifiers. The related data mart, VMware hosts is linked to the VMware systems data mart.

  In the following diagram, red text indicates data mart names and blue text indicates identifiers. 

  

• When importing from the TrueSight Capacity Optimization versions 11.5 and earlier.
  If the destination environment includes any data mart with the same name as the data mart being imported or its related data marts, the existing data mart is overwritten by the imported data mart. If there are multiple data marts with the same name, the new copy for the imported data mart is created.
  • The name of the data mart is considered as the identifier. Therefore, if the destination environment includes any data mart with the same name as one of the data marts being imported, the existing data mart will be overwritten by the imported data mart unless there are multiple data marts with the same name. In this case, the new copy for the imported data mart will be created. The message is displayed indicating these changes. 
  • the system tries to use the name of the data mart as identifier, if there is another data mart with same name, the system will try to update it. unless the system finds more data marts with the same name, then copy 
  • the user is notified about any change that system wants to apply. if u dont agree with update, cancel the operation, rename the existing data mart and redo the operation.