IBM E02HMLL-I Implementation Guide - Page 127

Working with duplicate components during deployment Commonly there will be components with the same name in the package file as there are in the repository. In this case you must decide whether or not you want to replace the components in the repository with those in the package file. The -ai option specifies that duplicate components should not be loaded into the repository: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iCustomer.jar -ai If you want to replace all the duplicate components in the repository, use the -ar option as in the following example: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iCustomerSyncInterface.jar -ar You can use the -arp option to interactively replace duplicate components in the repository. This lets you decide for each individual duplicate component whether it should be replaced or not. C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iCustomerSyncInterface.jar -arp Compiling and creating schemas For maps and collaboration to execute at runtime, the maps and collaboration templates defined in the repository must be compiled. For relationships to function properly at runtime, their schemas must be created. When you deploy components to a server running in production mode, all templates are automatically compiled and all relationship schemas are created. For the deployment to succeed, then, the code of the map and collaboration templates must be valid and InterChange Server Express must be able to communicate with the databases specified in the settings of the relationship definitions. When you deploy components to a server running in design mode, the templates are not automatically compiled; relationship schemas are automatically created. There are options you can use to compile the templates, however, and there are options to not create relationship schemas. The following example uses the -xCompilePackage option and does not use any form of the -r option. The result is that when the package specified by the -i option is deployed, the maps and collaboration templates are compiled and schemas are created for the relationships: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iWebSphereICSServer.jar -xCompilePackage You may not want relationship schemas created when you do a deployment. For instance, if you are deploying a package from one environment to another and did not change the properties of the relationships to use the database resources in the new environment then you will not want the schemas created until after you have changed the relevant properties. The following example uses the -r* option to not create schemas for all of the relationships in the package being deployed: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iWebSphereICSServer.jar -xCompilePackage -r* Note: You can use the -r option without the asterisk to specify the names of individual relationships whose schemas should not be created. For instance, Chapter 6. Using repos_copy 115