5.8.2  Importing Assets

Assets can be selectively imported into the data space by using the 'Repository' > 'Import Asset' node under the Server tab, which opens the 'Import Asset' page. This allows an administrator to incrementally deploy assets to an existing environment without overwriting all the assets in that environment. The assets to import must reside in an archive file generated by the 'Export Asset' feature described in Exporting Assets.

You cannot import a user-scope asset into an environment which has security disabled, or which has no defi­nition for the particu­lar user.

To import a set of assets from an archive file:

1. On the 'Import Asset' page, enter the file name of the archive con­taining the assets to import, and click OK.

2. The 'JAR Information' page opens and displays the asset contents of the specified JAR file.

The items listed in the 'Selected Entities' panel will all be imported. The items listed in the 'Included Dependent Assets' table are required by items in the 'Selected Entities' panel, and will be imported by default. However, if one or more of these items already exist in the current server environment, you can choose not to import those items.

3. Click the 'Include' box next to assets in the 'Included Dependent Assets' table that you wish to import.

4. Select 'Overwrite existing files' if the assets in the archive should overwrite existing assets of the same name upon import. The default setting of the 'Overwrite existing files' checkbox is speci­fied by the export settings under which the archive was saved. See the Exporting Assets section above.

5. Click OK to import these assets into the current environment.

Figure 27. The Import Asset node.

 

Figure 28. The Import Asset page.

 

See Also

Ant Task for Import/Export of Assets, to programmatically control deployment.

<< 5.8.1 Exporting Assets © 1996-2013 InetSoft Technology Corporation (v11.5) 5.8.3 Ant Task for Import/Export of Assets >>