IBM E02HMLL-I Implementation Guide - Page 87

v Merge Property Descriptor The Merge option causes all the server names, integration components, properties, and values established in the imported file to be added to the existing file. The merge is completely hierarchical and granular. For example, if the original file contains only a Server1, and the import file contains a Server1 and Server2, the Server2 name and all the integration components, properties, and values associated with it will be added to the original file. The Server1 name already established in the original file is not removed. If an integration component exists in Server1 in the import file, but not in Server1 in the original file, that component will be added to Server1 in the original file. Likewise, if a property exists for a specific integration component in Server1 in the import file, but not in the original file, that property will be added for that specific integration component in Server1 in the import file. At the lowest level, value replacement occurs. That is, the value for a specific property of a specific integration component in a specific server name in the import file will replace the value (if one exists) for the same property of the same integration component associated with the same server name in the original file. Copying and pasting deployment configuration properties Deployment configuration properties created for one server can be copied and pasted into the configuration for another server. When you copy and paste properties, any values assigned to those properties are copied and pasted as well. When you paste properties, if the properties already exist in the configuration, they are overwritten by the paste operation. Setting deployment properties without System Manager A standalone utility, contained in the deploymentconfigutil.zip file in the product \bin directory, can allow a *.dfg file to be edited without the use of System Manager. This can be useful, for example, in a situation where a database administrator needs to have a connector password property set to a specific value for interacting with the database, but does not want to reveal that value to the implementer who is using System Manager. The implementer can use the Deployment Configurator feature of System Manager to create a *.dfg file with default values and then send that file to the database administrator. The database administrator then runs the standalone utility, which allows modification of the property values (not the addition or deletion of integration components or properties). The database administrator uses the utility to modify the password value, and then sends the file back to the implementer, who uses System Manager to import the *.dfg file into Deployment Configurator. This utility is controlled by a pre-defined password and you must contact the product support center to get one. The password is intended to prevent users without appropriate privileges from changinge the passwords or encrypted data specified in the deployment descriptor files. This standalone utility is contained in the deploymentconfigutil.zip file, which resides in the IBM\WebSphere\bin directory. The file can be extracted and used on a system that does not have either System Manager or InterChange Server Express installed. Setting the initial states of components for deployment For components with states (such as connectors, collaboration objects, maps, relationships, and database connection pools), you can set the state in which the component initializes when rebooting the server after deployment. Do the following to set the initial post-deployment state of components: Chapter 4. Using System Manager 75