Importing a Bundle Jar

A bundle jar can be imported by selecting it from the local filesystem. If the operation is successful, its entities are added to the destination master server in the order specified in the bundle descriptor file.

Ensure that all entities satisfy the usual requirements of the provisioning system, and that any plugins on which they depend are already imported.

Use the bdb.b.imp command to import a bundle jar from the local file system. This command takes the following arguments:

• path: The path to the file system from which to import the bundle jar.

• owner: The group destined to be owner of folders created through the import operation. Use this to specify the owner group of all folders to be created by the bundle jar. When a new leaf or interior folder is created, ownership is by the same group.

• v: Default value is false. Set this to true if you want to validate the import, but do not want to actually execute the import operation. Setting the value to true simulates the import, and returns any possible errors. If no errors would occur, this returns the number of entities that would be imported. Setting this value to true means that the actual import operation does not take place.

For full usage of this command, see Appendix A, Appendix — New Commands.

On each master server, you can only import one bundle jar at any time.

After the import operation, the newly imported objects are visible, but are not categorized. Any previous versions of these objects are implicitly hidden.

Entities added or updated by the import operation have no record that they were checked in by a bundle jar.

If plans or components owned by a plugin and that depend on elements in the plugin, are included in a bundle jar, the plans or components might not function after the import operation, unless all elements on which they depend are also imported. By default, therefore, search criteria in bundle templates exclude entities that are contained in plugins.

Folder paths for plans or components in the bundle jar cannot be owned by a plugin that is already imported on the master server. Best practice is not to include versions when referring to subplans, subcomponents and targeters, because subplans, subcomponents and targeters may not work reliably after import in different environments.

Only one import operation is permitted for a master server at any time.

Example 5–8 Using the bdb.b.imp Command to Validate the Import of a Bundle Jar

This example shows how to use the bdb.b.imp command with the -v option to test if the import of a bundle jar would be successful. The jar path is input as /bb/bb/bundle.jar

bdb.b.imp -v true -owner NM:myGroup -path "/bb/bb/bundle.jar"

The result is as follows.

Processed:Folder=1, Plan=1

The output shows that the operation would be successful.

Example 5–9 Using the bdb.b.imp Command to Import a Bundle Jar

This example shows how to use the bdb.b.imp command to import a bundle jar. The jar path is input as /bb/bb/bundle.jar

bdb.b.imp -v false -owner NM:myGroup -path "/bb/bb/bundle.jar"

The result is as follows.

Processed:Folder=1, Plan=1

The output shows that the import operation was successful.