Overview of the Import-Export Feature

Service Provisioning System objects such as components, plans and host sets can now easily be copied from one master server into a single file and on to another master server. This is done as follows:

1. On the source master server, create a bundle template.

   A bundle template contains an ordered list of search criteria that add your selection of service provisioning system objects such as the following:

   • Component Types

   • System Services

   • Host Types

   • Host Sets

   • Host Searches

   • Folders

   • Components

   • Plans

   The ordering of these objects is important, because you export these objects in to the bundle template, using search criteria, in the order of the objects' mutual dependencies: matched objects are exported into the bundle template in the order of the search criteria that they match. See Declaring Search Criteria for a Bundle Template for details. If the objects are not exported in the correct order, the export succeeds but the subsequent import operation can fail.

2. When you have created and saved the bundle template, export the bundle template in to a bundle jar. See Exporting a Bundle Template to a Bundle Jar for details.

   You can manually create a bundle jar, or modify it after it has been automatically created by the system. This is on the condition that the jar contents are always consistent with the bundle descriptor file. See Contents of a Bundle Jar for details.

3. On the destination master server, test to see if the import of the bundle jar would work, using the validate feature. See Example 5–8 for details.

4. If the validation succeeds, import the bundle jar. See Example 5–9 for details.

All users can use the import-export feature.