Importing a Resource
You import CAR files to replicate TDV resources and resource configurations. CAR files are created by exporting TDV resources, and they usually contain many object resources—possibly even a full server backup. For details on creating a CAR
file, see
Exporting Resources and
Using Studio for a Full Server Backup.
During the import process, you can choose to import or not import caching information, privileges, custom adapter JARS, and data source connections. You can also override locks, overwrite resources, merge folders, and create caching tables.
Resources imported from an archive using Studio are placed in the selected folder in Studio’s resource tree. Import performs a path relocation on all folder path roots in the archive. See
Rules for Importing Resources for details about the rights and privileges related to importing resources.
Prior to performing the import, you can view information about the archive file to make sure it is the one you want. You can also preview the messages generated during the import without actually performing the import.
To import a resource
1. Right-click the container into which you want to import a resource, and select Import; or select the resource and then the option File > Import Into <container>.
The Import into window opens.
2. Use the Browse button to locate and upload the CAR file, or type the full path to the import file in the File field.
3. Optionally, type a password. If the CAR was created using a password, you must type that password here. If the CAR was created without using a password, you can leave this field blank.
4. Optionally, check the Ignore Encryption Errors check box to ignore any encryption errors.
Note: If this option is used, then all backup data will be imported regardless of whether a valid encryption key was provided. This means that the import will not fail. This option can be used to allow partially importing any backed up data. However, the import process will only import data that is not encrypted or can be decrypted using the provided encryption key. All encrypted portions of the backup data that cannot be decrypted will be imported as empty values and the import will otherwise succeed.
This affects all encrypted values in the backup data, which includes, but is not limited to data source and LDAP domain connection passwords.
5. Clear items in the Include Resource Information section that you do not want to import.
Note: A resource information box is checked only if that resource is present in the CAR file and you have appropriate user rights. For example, the Privileges check box is enabled only for users with the Read All Users right.
Option | Description |
Caching | Includes or excludes resource caching configurations, including storage type, location, scheduling information, and materialized view data. |
Privileges | Includes or excludes resource group and user privilege information. User privilege information is imported into the target TDV installation only if matching username, group, and domains exist on the target and the user performing the import has the Modify All Users right or the Modify All Resources right. |
Override Locks | Clears existing resources from the target and sets the TDV Server to the resource definitions present in the full server backup CAR file. The importing user must have the Unlock Resources right to use Override Locks. |
Create Caching Tables | If selected, the cache status, tracking and target tables required by cached resources are created, if not already present in the database for your data source. |
Overwrite | Overwrites or stops import of resources that have identical names and folder paths. Owner and user privileges are not overwritten unless they are explicitly changed to new privilege setting. Use this option to guarantee that the new TDV workspace matches the folders and content present in the CAR file. This option clears target folders before copying the CAR file contents to them. |
Custom Jars | Includes or excludes any custom JAR created to support a new data source. |
Merge Users Folder | Imports all users present in the CAR file who are not already present in the server target. This option takes precedence over the Include Users Folder option. This option’s behavior might be altered by the Overwrite option. |
Data Source Connections | Includes or excludes resource-specific connection profiles and configurations, including host, port, sign-in, and password. This option requires the Read All Resources right. |
Include Users Folder | Includes or excludes resource owners who might be present in the CAR file. Imports all users present in the exported CAR file unless Merge Users Folder is specified. By default, domain, group, and user information are not included in export or import packages. When users are not included, the importing user becomes the owner of the resource. |
Include Policies | Includes or excludes policies (CBS, RBS, Cache and Security policies) that might be present in the CAR file. If your CAR file includes these policies, import the CAR from the Studio Desktop directory level. Policies must be saved and used from the /policy Studio directory. |
Discovery Files | Check this option to include Discovery files (such as indexes and relationship files) in the import. |
Different combinations of Overwrite, Include Users Folder, and Merge Users import options can alter the user definitions, resource ownership, and usage privileges defined on the TDV target after the CAR-file import is complete.
This table shows all possible combinations of these options. Check marks on the left side of the table show the import options used, and check marks on the right side show the results on the TDV target after the import.
Note: If Overwrite and Include Users Folder are both checked, all existing user definitions are removed and replaced with the users present in the import CAR file. The user performing the import must have Read and Modify All Users rights to use this combination.
Choosing check box options in this section is equivalent to enabling options in the pkg_import command-line utility. See the TDV Administration Guide for more information.
6. If you edit the entry in the File field, click Refresh to view the following information about the import file:
— File Type—archive type (whether partial or the entire server)
— Date—day, date, and time when the resource was exported
— User—name of the user who exported the resource
— Server—host machine and port from which the resource was exported
7. Select the
Show Rebinding Options box to bind a resource to an underlying source for the first time. (For details about resource binding, see
Marking Rebindables.)
8. Optionally, click Preview to view a list of the contents of the import file without actually performing any imports.
The Preview button works like the -messagesonly option to the pkg_import command-line utility. This option displays the messages generated in a package import without actually performing the import.
9. Optionally, type search criteria in Find, and click Search. Use the up or down arrow key to jump to the next instance of the search text. The text that you are searching for is highlighted in yellow.
10. Click Import to import the resources.
11. Click Done to complete the importing process.
