Exporting and importing
You can export customized configuration data from an existing Dashboard Application Services Hub installation to another by exporting the data and subsequently importing the exported data.
Exporting and importing customized settings can be done at the command line through the consolecli.sh|bat Export and consolecli.sh|bat Import commands.
Restriction: When running consolecli.sh|bat commands
in Tivoli® Integrated
Portal environments,
you must use tipcli.sh/bat instead. That is, the consolecli.sh|bat commands
replaced the tipcli.sh/bat commands with the release
of Dashboard Application Services Hub.
Note: The consolecli.sh|bat Export and consolecli.bat|sh
Import commands are case sensitive. Also, if you make a typing
error, that is, if you type a parameter incorrectly, or use the incorrect
case, then the commands runs as if no parameters were specified and
no warning message is displayed.
You can export and import the following elements:
- Custom dashboards and customized system page elements, with the
exception of core and system pages, including:
- Dashboard name and layout.
- Widget entities.Note: Copies of a widget entity are not exported; either through the console Export Wizard or through the consolecli.bat|.sh Export command.
- View profiles.
- Events and wires.
- Access permissions.
- Navigation structure.
- Custom views (or customized system views).Note: You can also export dashboards associated with a view if the exportpageinview parameter is set to true.
- Custom roles, including:
- Role name, creation date, and update date.
- Role mapping information in relation to users and groups.
- Associated role preference, that is, the relevant console preference profile.
- Console properties and customization properties, including:
- Transformations.
- Themes and images.
- Bundles.
In a load balanced environment the import operation migrates imported elements across all the computers in the pool, with following conditions:
- All the required applications (WAR files) must be deployed on all computers in the pool.
- The load balanced pool configuration must be locked during the import operation.
- The import operation must be ran on one of the nodes in the pool.Restriction: In a load balanced environment that includes charting, the ListRestore command only runs successfully on the node that is used for the import operation because backup files are stored locally on that node and are not synchronized across other nodes in the cluster.
- You must provide the load balancing manager an updated file list to update the load balancing scope. The migration tool plugin provides the file list.
- The load balanced pool configuration, can then be unlocked.
The import of transformations in a load balanced environment is not supported. Transformations must be imported to each node independently.
The haSupport command controls this aspect of the import operation:- If it is set to True, then only load balancing information is imported, that is, no transformation data.
- If it is set to False, then only transformation data is imported, that is, no load balancing data.
- If it is set to Both, then transformation data and load balancing data is imported.