To migrate views between instances of TrueSight Capacity Optimization console
When you migrate a view from one TrueSight Capacity Optimization instance (environment) to another (for example, from a test environment to production), you may be required to perform additional steps to enable same views from different environments to display the same content, other than exporting a view from one instance and uploading it to another.
Migrating each type of view (portlet) exhibits a specific type of behavior. For more information, refer to the following sections that describe the behavior for each type of portlet, and other best practices:
Table/Summary View/ERTA Analysis portlets
When you migrate Table, Summary Views or ERTA Analysis portlets from one TrueSight Capacity Optimization instance (environment) to the other, the overall configuration is preserved, and the underlying data mart is also migrated to the target environment except if the:
- Underlying SQL data mart is based on another SQL. For example: If a query of type
Select * from sql_datamart_2is used in the source portlet.
- In this case only the 'first level' data mart is created, while you are required to create other other data marts manually.
- Since IDs of the nested data marts created in the target environment will be different from the source, you are required to modify the 'first level' data mart to correctly point to them.
- Table is using an OOTB data mart (not recommended). In this case, the general assumption is that the same data mart is already present in the source environment.
System and Business Driver Analysis portlets
When you migrate System and Business Driver Analysis portlets from one TrueSight Capacity Optimization instance (environment) to the other, the underlying analysis is recreated on the target environment except if it is based on a custom template that is not present on the target environment. In this case, you are required to manually recreate the custom analysis template before importing the View.
When you migrate Filter portlets from one TrueSight Capacity Optimization instance (environment) to the other, no manual steps are required if best-practices have been followed.
Model/Analysis Viewer portlets
When you migrate Model and Analysis Viewer portlets from one TrueSight Capacity Optimization instance (environment) to the other, you are required to manually recreate their content in the target environment after you import the Views, and are then to reconfigure portlets to use them.
The following table lists the steps required to migrate Model and Analysis Viewer portlets from one TrueSight Capacity Optimization instance (environment) to the other.
Migrating Model Viewer portlets
Migrating Analysis Viewer portlets
Refer to the source environment and check (ideally make a note of) all options that are selected, and then perform the following task:
Refer to the source environment and check (ideally make a note of) all options that are selected. Create an analysis under the target environment Workspace which is the same as that present in the source, and then perform the following task:
Best practices to allow for easy migration of views
When you create a custom view, best practices to follow for easy migration are:
- Avoid specifying system or domain parameters directly into portlet preferences. Doing this will require you to manually specify them after importing the view to the target environment. To avoid this situation, put filter portlets into the page.
- Avoid specifying time filters directly into portlet preferences, especially if they aren't restricted.
- Avoid using OOTB SQL data marts, since their structure can change across different versions and also because they are not created on importing a View.
- Keep track of any custom elements used in the source environment so as to be able to reproduce them on the target environment.