IBM E02HMLL-I Implementation Guide - Page 104

v Select the folder for a component type to populate the right-hand pane with a list of the components of that type in the repository and then enable the checkbox for individual components. 4. Enable the Force remove even if other objects depend on this object checkbox to delete the component even if other components reference it. For instance, a business object cannot be deleted if it contains other business objects because they depend on it, even if those dependent components are also selected for deletion, unless this option is enabled. 5. Enable the Delete dependent objects also checkbox to also delete the dependencies of the selected components. For more information about dependencies, see "Dependencies and references." Figure 29 shows the "Server Objects Delete Wizard". Figure 29. Deleting objects from the server 6. Click Finish. If the delete operation is successful then the wizard exits. If the delete operation failed, click OK to close the error prompt, then resolve the problem and try the operation again. The error information in the prompt can be very difficult to use in troubleshooting, so it is recommended that you use the server logging output to determine the cause of the failure. Dependencies and references Integration components depend upon one another to perform their roles in the business integration system. For instance, business object definitions can contain other business object definitions as children, collaboration templates have business object definitions associated with their ports, and connectors have maps associated with their supported business objects. These dependencies must be satisfied for the system to function properly, and when InterChange Server Express is started in production mode it checks to make sure that all dependencies and references are 92 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide