Page tree

Skip to end of metadata
Go to start of metadata

You can delete a folder, group, smart group, or system object.

You have the option of making it impossible to delete a folder or group unless that folder or group is empty. To perform this procedure, use the Application Server Administration console (that is, the blasadmin utility), as described in Deleting groups in the BMC Server Automation Console. This procedure has no effect on smart groups, which you can always delete.

Note

You cannot delete or remove objects from smart groups.

If other objects depend on the object you plan to delete, you can delete the other objects and the object you choose to delete. Alternatively, if you are deleting an object and a component template, Deploy Job, or Batch Job depends on that object, you can choose to delete only the original object and break all dependencies those component templates, Deploy Jobs, or Batch Jobs might have on the deleted object. If you choose to break dependencies, the component templates, Deploy Jobs, or Batch Jobs with broken dependencies appear in the content editor with a red X in one corner.

Note

To break a dependency with a component template, you must have, at minimum, the ComponentTemplate.Break authorization. To break a dependency with a Deploy Job, you must have, at minimum a DeployJob.Break authorization. To break a dependency with a Batch Job, you must have, at minimum, a BatchJob.Break authorization.

You can use a smart group to locate system objects with broken dependencies. For details, see Finding system objects with broken dependencies.

To delete a folder, group, smart group, or system object

  1. Open any folder and navigate to the folder, group, or system object you want to delete.
    Use Control-click or Shift-click to select multiple folders, groups, or objects.
  2. Right-click and select Delete from the pop-up menu. If you are removing servers from a folder in the Servers folder, select Remove from Group.
    The Delete dialog box shows the objects you have selected for deletion.
  3. If you do not want to view any dependencies on the object being deleted, select Skip dependency view and directly delete object and dependencies.
    Selecting this option instructs the system to delete the object and any other objects that have a dependency on it. You cannot view or break dependencies, as described in step 4.
  4. Click OK.
    If no folders, groups, or system objects have dependencies on other objects or you selected the Skip dependency view... option in the previous step, the Delete dialog box shows the results of your actions. A green check indicates an object was successfully deleted. Proceed to step 7.
    If any of the folders, groups, or system objects being deleted have dependencies on other objects, the Found Dependencies dialog box lists the other items affected by the deletion of the first object in the Delete dialog box. For example, if you have chosen to delete a BLPackage, the Found Dependencies dialog box might show that a Deploy Job and a Batch Job have dependencies on that BLPackage.
  5. Review the contents of the Found Dependencies dialog box and click one of the following:
    • OK — Deletes the folder, group, or object listed in the dialog box along with all of its dependent objects.
    • Ignore — Does not delete the folder, group, or object listed in the dialog box.
    • Break — Deletes the object listed at the top of the dialog box and breaks any dependencies with component templates, Deploy Jobs, or Batch Jobs.
      If the Delete dialog box in the previous step shows multiple objects being deleted, the Found Dependencies dialog box displays dependencies for the next item listed in the Delete dialog box.
  6. Continue to repeat step 4 until the Delete dialog box shows the results of your actions.
  7. To close the Delete dialog box, click Close.