Exporting configuration properties for comparison

You can export the configuration properties from two different V19.0.0.3 deployment environments and compare them, using your own comparison tools, to understand the difference between two IBM® Business Automation Workflow systems. You can also compare against V8.5.5 configurations, but you must take into account that the more recent version extracts more properties than the previous version.

To compare configuration properties between two deployment environments, complete the following steps:

1. Run the BPMConfig –export command to extract the configuration data from each Business Automation Workflow deployment environment.
   For example:

   • BPMConfig.sh -export -profile DmgrProfile -de DeploymentEnvironment1 -outputDir /home/user_name/DE1ConfigFolder
   • BPMConfig.bat -export -profile DmgrProfile -de DeploymentEnvironment1 -outputDir C:\DE1ConfigFolder

   If there is only one deployment environment in the WebSphere cell, you can omit the -de option.

   Important: Specify a different output directory for each deployment environment. In the case where a cell has multiple deployment environments, a unique output directory is required for each deployment environment.

   Table 1. Configuration files for each deployment environment

   Sample name	Description
   DE_name.properties	This properties file contains the configuration properties from your source environment. You use this file when you configure the target environment. For more information about the configuration properties, see the topic Configuration properties for the BPMConfig command.
   fileRegistry.xml	If you use a file-based user registry, the user registry file is copied from the source environment to be added to the target environment.
   ltpa.jceks	If you use LTPA, the LTPA key file is copied from the source environment to be added to the target environment.
   ldap_additional_properties.xml	If you use a federated repository and an unencrypted LDAP connection in the source environment, user-defined additional properties of the LDAP server are copied from the source environment to the output directory, where they are later used automatically to create the target environment. Restriction: If you extend the federated repository to use a custom login property (such as userPrincipalName) in addition to the default uid property in the source environment, LDAP is not configured for the target environment, with the following warning: CWMCB0600W: LDAP could not be configured! You may configure LDAP separately after BPMConfig has terminated successfully. If you see this warning, manually configure LDAP with the login properties you want to use after the migration is complete.
   ProcessServer_100SourceCustomMerged.xml and PDW_100SourceCustomMerged.xml	If you have XML configuration properties files, they are copied from the source environment. The exported configuration files are merged and renamed to 101CustomMigrated.xml in the target environment.
   Application-config-bpc.xml and resources-bpc.xml	If you have Business Process Choreographer configured in the source environment, the configuration files are copied from the source environment to the output directory, where they are later used automatically to create the target environment.
   Support-config-bpc.xml	If you have Business Process Choreographer Archive Manager configured on the support cluster in the source environment, the configuration is copied from the source environment to the output directory, where it is later used automatically to create the target environment.

2. Use your comparison tools to compare the differences between the extracted configuration files for each deployment environment.
   Tip: Use comparison tools for comparing these files, because most of them are not intended to be human-readable.

   • To compare XML files: If the XML files are very different, you might first want to sort all XML elements and attributes based on your needs using a tool, for example, XML Sorter. Then, using a comparison tool, for example, Pretty Diff, Altova DiffDog, or Stylus Studio XML Editor, compare the extracted XML files for each deployment environment.
   • To compare properties files: Use a comparison tool, for example, Beyond Compare, Compare Suite, or Compare++, to compare the extracted configuration files for each deployment environment.
   • The ltpa.jceks file is a binary file for LTPA keys and you cannot compare the contents.

   .