Exporting Resources
You can export selected nodes and resources in the Studio resource tree to a CAR file that contains the relevant resource definition metadata. Resources selected are exported with all of their child objects.
Exported CAR files can include caching configurations and the cached data, data source connections, access privileges, custom JAR files, dependencies, cardinality statistics, Discovery files, and the owners of the exported resources (called “required users”).
To export resources using Studio
1. Select one or more resources in the Studio resource tree.
To select multiple resources for exporting, hold down Ctrl while selecting the resources one by one, or hold down Shift while selecting a set of adjacent resources.
2. Right-click and select Export, or choose File > Export <resource>.
Studio displays the Export dialog.
3. For Name, type a name for the CAR file, or use the Browse button to locate a file in which to store the exported resources.
4. In the Include Resource Information section of the Export <resource> dialog box, select and uncheck export options as required.
Each export option is enabled only if the user has the appropriate rights for it.
Export Option | Description |
Caching | Resource caching configurations: storage type and location, scheduling information, materialized view data. |
Privileges | Resource group and user privilege information. User privilege information for exported resources is imported into the target TDV installation only for matching user, group, and domains on the target, and only if the user performing the import has the Modify All Users right or the Modify All Resources right. |
Dependencies | Any dependency resources in the exported CAR file. To view dependencies that have been exported, open the resource and select the dependency panel. |
Required Users | Owners of the exported resources. |
Data Source Connections | Resource-specific connection profiles and configurations, including host, port, sign-in, and password. This option requires the Read All Resources right. |
Custom Jars | JAR files created to support new data sources. JAR drivers in the conf\adapters\system folder are exported, but JAR files in the apps\dlm\<DATASOURCE>\lib folder are not exported, regardless of this setting. Custom JAR settings overwrite system JAR settings, which in turn overwrite DLM JAR settings. |
Cardinality Statistics | Includes data source statistics, and configurations such as refresh mode, refresh timeframe, manual cardinality overwrites, and specific column settings. |
Discovery Files | Be sure to include Discovery files, such as indexes and relationship files. |
Parent Resources | Check this option to include the parent resources while exporting the datasource metadata. |
Choosing check-box options in this section is equivalent to enabling options using the command line in the pkg_export utility. For more information on the pkg_export utility, see the TDV Administration Guide.
5. Type a password to encrypt the CAR file. Type the same password to confirm it.
A password is required to export resource data.
6. Optionally enter a description of the export file in the Description box.
7. Click OK.