IBM E02HMLL-I Implementation Guide - Page 130

C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -doBusObj:Customer -deep This option, unlike the -dfo option, is supported with servers running in production mode because the deletion of the referents along with the component guarantees that the repository remains valid. Keep in mind, however, that it can result in many components being deleted; you should be aware of the implications of this action prior to taking it. Exporting components to a package The -o option allows you to export components from the repository to a package. You must specify the name of the package file. When the -o option is used alone the entire repository is exported to a file, as in the following example: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -oWebSphereICSServer.jar You can specify individual components to be exported by using the -e option. You must use the -e option with the appropriate EntityType keyword listed in Table 12 on page 113, and must follow the keyword with the name of the component. You can specify multiple components by concatenating them with the plus (+) sign. In the following example, the Customer business object and CustomerSync collaboration template are exported to a package named CustomerSyncInterface.jar. C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -eBusObj:Customer+CollabTemplate:CustomerSync -oCustomerSyncInterface.jar You can use the -deep option to export the dependencies of a component as well. In the previous example, the Customer business object was exported, but none of its child business objects were. The following example uses the -deep option to export the CustomerSync_ClarifyToSAP collaboration object and all of its dependencies. C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -eCollaboration:CustomerSync_ClarifyToSAP -oCustomerSyncInterface.jar -deep If you want to export specific components, but do not want to have to enter the entity type keyword and component names, you can store them in a text file and use the -f option. This is very convenient when you want to frequently export the same components. The following example uses the -f option to load the components listed in a text file named Components.txt : C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -fComponents.txt -oCustomerSyncInterface.jar -deep The contents of the file Components.txt are shown below; a paragraph return follows each entity type keyword and name combination: BusObj:Customer Relationship:Customer CollabTemplate:CustomerSync Note: Repos_copy and System Manager are unfortunately inconsistent with respect to what they identify as "dependencies". If you attempt to delete a component using repos_copy but there are components that depend upon it then repos_copy lists those referring components as dependencies. However, if you right-click the component in System Manager and select Show Dependencies from the context menu the tool lists the components that the selected component depends on. 118 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide