IBM E02HMLL-I Implementation Guide - Page 129

Deleting components from the repository There are several options provided by repos_copy for deleting components in the repository. You can delete the entire repository, individual components, and individual components as well as any components that reference them. Note: Components must be inactive for you to delete them. If you delete a single component then you must deactivate it first or the delete operation will fail. If you want to delete a component and all the components that reference it, you must deactivate not only the single component, but all those that reference it as well. You can delete the entire repository while the components are in an active state. Use System Monitor or web-based System Monitor to manage the states of components. System Monitor and web-based System Monitor are described in the System Administration Guide. Deleting the entire repository Use the -d option to delete all of the components in the repository. The following example shows the syntax: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -d Repos_copy presents a prompt asking if you want to delete the entire repository or not. Deleting components without referents If a component does not have any referents-other components that reference it and require it to exist in order to perform their function in the system-then you can delete the individual component. Use the -do option followed by the entity type, a colon, and the name of the component. The entity types are listed in Table 12 on page 113. The following example deletes the relationship named Customer: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -doRelationship:Customer Deleting components with referents If a component does have referents-other components that reference it and require it to exist in order to perform their function in the system-then you can only delete the component if the server is running in design-mode, and by using certain options. Forcing a delete in spite of references: If a component has referents, repos_copy will not let you delete it with the -do option. You must use the -dfo option to force deletion of a component with referents. Forcing deletion of a component that has referents will leave the repository in an inconsistent state, and a server running in production mode does not permit that, so this option only works with a design-mode server. The following example shows the use of the -dfo option to delete the Order business object in spite of the fact that other components in the system (such as maps and relationships) have references to it: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -dfoBusObj:Order Deleting the referents as well: Another way you can delete a component that has referents is to use the -deep option to delete the referents as well. This deletes the component and all of the components that have references to it. The following example shows the use of the -deep option when using the -do option to delete the Customer business object: Chapter 6. Using repos_copy 117