Exporting Repository Content to a Zip File

You may wish to extract the repository items that belong to one or more ExtrinsicObject objects in the registry. For example, if the objects were originally created by uploading a zip file containing WSDL files (and optionally XSD files), you may want to re-create that zip file. The Web Console allows you to do this in two ways:

• You can use a search operation to export content to a zip file, as described in this section. Use this mechanism if you are confident that your search will return the objects you want.

• After completing a search operation, you can select some of the objects and export their content to a zip file, as described in To Use the Export Button in the Registry Objects Area.

The Export Repository Content as Zip File subpanel of the Search panel allows you to export the repository items associated with any found ExtrinsicObject objects to a zip file. If any of the found objects depend on each other, you can specify the depth of dependency. For example, if one WSDL file imports another WSDL file, which imports a third WSDL file, the dependency is two levels deep.

Both the default dependency depth and the maximum number of depth levels are configurable. See Configuring the Dependency Resolution Depth for the Export Feature in Service Registry 3.1 Update 1 Administration Guide for details.

The Export feature does not remove any items from the repository; it exports a copy of each file.

To Export Content to a Zip File

1. Specify a search that will return one or more ExtrinsicObject objects.

   For example, a search by object type could specify the ExtrinsicObject type or one of its subtypes. A search by name could return some objects of type ExtrinsicObject. A WSDL Discovery Query could return one or more WSDL objects (a subtype of ExtrinsicObject).

2. Select the Export Repository Content to Zip File checkbox and specify a Dependency Resolution Depth.

   You can specify a depth of 0 (the default), 1, 2, 3, or All Levels to specify how imported files should be returned.

   For example, if you did a search by name to specify a particular WSDL file that imports one or more files, and then specify a depth of All Levels, the search will return that file and all the files that it depends on.

3. Click the Search button.

   If the search returns one or more ExtrinsicObject objects, an Export Objects panel appears in the content area with the message Click this link to download compressed content: and a Download link.

   If the search does not return any ExtrinsicObject objects, the following message appears in the content area:

   No ExtrinsicObjects were found to compress. Please refine your query.

4. Click the Download link.

5. In the browser dialog that appears, choose the option to save the file to disk.

6. In the file chooser that appears, choose a location to save the file.

   The default name of the file is exportedContent.zip. Rename the file if you wish.

   In the zip file, each repository item has a name that is based on the Unique Identifier of the ExtrinsicObject to which it belongs. This ensures that there is no duplication of file names. The name is similar to that of the Unique Identifier except that colons are replaced with hyphens.

   If the ExtrinsicObject is part of a RegistryPackage, the name of the repository item includes the directory path.

Example 2–1 File Naming Conventions for Exported Content

For example, if you export an ExtrinsicObject with the name file1.xsd and the Unique Identifier urn:com:acme:files:file1, and the ExtrinsicObject is a member of a RegistryPackage named myFiles, the zip file will contain an entry similar to the following:

  Length     Date   Time    Name
 --------    ----   ----    ----
    42795  05-22-07 06:27   myFiles/urn-com-acme-files-file1