Question & Answer
How to check multiple server and resource configurations to:
- check for potential inconsistent behavior between application servers in a cluster.
- check for configuration creep.
- check for migration of configuration from version to version.
- check file systems for differences.
Important Note: The WebSphere Application Server Configuration Comparison Tool is published "as is." Please do not open a Case or PMR for tool usage issues. Best effort support can be obtained via the question and answer section of this document.
Manually configured application servers and resources are likely to have configuration differences. Finding these differences by navigating to configuration panels is error prone and time consuming. Applications servers and resources should be periodically checked for configuration differences.
The Configuration Comparison Tool (CCT) is a lightweight wsadmin script and Python report generation script which will produce HTML reports on configuration settings for the following types of resources.
- Application Servers
- Node Agents
- Global Security configuration (not Domain Security)
- Trust Association (Global and Domain)
- SSL Configurations
- Data Sources
- J2C Resource Adapters
- JDBC Drivers
- Object Cache instances
- Servlet Cache instances
- Service Integration Bus instances
- Resource Environment Providers
- Resource Environment Entries
- File system comparisons
CCT usage scenarios:
- Isolating configuration creep: Periodic configuration snapshots can be gathered and archived. These can be used to see what configuration changes that have been made over time.
- Troubleshooting inconsistent cluster member configuration: Servers and node/server specific resource configuration anomalies can causes unexpected runtime behavior from different servers within a cluster.
- Assisting in migration to a new version of WebSphere: Cross version configuration reports can help ensure a complete migration of server and resource settings.
Download tool: cct-20190822.tar.gz
Important note: For users of this tool prior to June 2018, see the "Properties file considerations" in the WAS_Configuration_Comparison_Tool.pdf presentation for important information on how loading properties has changed.
Tar File Contents:
- ConfigReport.py: Script for creating reports for Traditional profile WebSphere
- ConfigDump.py: wsadmin script for dumping configuration
- ConfigUtils.py: Utilities script
- WAuJ.py: Utilities script
- WAuJ_utilities.py: Utilities script
- ConfigReport.properties: Sample properties file for defining reports for Traditional profile WebSphere
- ConfigReportAttributes.properties: Defines attributes reported in Traditional profile WebSphere reports. It is recommended not to edit this.
- CollectFileData.sh: Collects file data from the specified file system
- ConfigReportFiles.py: Generates file system comparison reports
- WASConfigurationComparisonTool.pdf: Tool documentation
- August 22nd 2019
- More documentation updates.
- August 21st 2019
- Documentation updates.
- August 19th 2019
- Corrected report generation failure in SSL cipher reporting.
- Added support for collecting file system data for AIX.
- Added optional parameter on ConfigDump to set the cell suffix from the command line.
- Improved syntax help on ConfigReportFiles.py
- June 6th 2019
- Changed files that match in CRC and size but not date and time to be a conditional correct match.
- Corrected issue with Trust Association report generation.
- Disabled specific error messages in ConfigDump.py.
- Added more documentation for file system reports.
- Reordered documentation for better flow.
- April 3rd, 2019
- Reports on Trust Association and Trust Associatoin Interceptor configuration.
- Light weight file system comparison using date, time and chksum of files.
- December 29th, 2018
- Generate sample wsadmin scripts which will make configuration values consistent for resources identified in a given report.
- November 14, 2018
- Added application comparison reports.
- Built in "Applications" report that compares configurations by deployed module name.
- User defined reports that allow comparing any applications with each other.
- Updated documentation.
- Reordered presentation pages.
- Added page for installation instructions
- Added page detailing available resource reports
- Added page detailing built in reports.
- Added application comparison reports.
- October 31, 2018
- Corrected character truncation for generic JVM arguments as well as extraneous characters with leading and trailing arguments.
- August 3, 2018
- Resource Environment Provider reports.
- Resource Environment Entry reports.
- August 2, 2018
- Corrected issue in ConfigDump.py preventing it from running.
- Accounted for configuration anomalies with incomplete and orphaned variable substitution entries.
- Corrected path separator issue on Linux for report generation.
- June 17th, 2018
- Added ability to compare all SSL configurations, not just cell defaults.
- Enhanced Resources report to compare SSL configurations by the same name automatically.
- Added cipher report to compare which ciphers may be inconsistent between SSL configs.
- Updated ConfigDump.py to explicitly gather configuration data for all SSL configurations. Configuration dumps done with prior versions of ConfigDump.py may not pick up all SSL configurations.
- Enhanced Cell Summary report to list all SSL Configuration aliases and scopes.
- Corrected a bug which broke individual JVM argument comparisons.
- June 2nd, 2018
- New report properties file processing introduced.
- Individual report properties may be set on the command line.
- Reports may be abbreviated to attributes that have differences only.
- A node agent report was added.
- Thread Pool Manager and all thread pools are now reported.
- May 27th, 2018
- Added a report key at the top of all report documenting values in match column and cell background colors.
- Added capability to replace a string with another value or a regular expression for the purposes of matching.
- Cell, node and server names are replaced with .* by default for matching purposes.
- January 19th, 2018
- ConfigDump.py on Windows systems that do not have a Unix shell (sh) will fail. Added messages documenting a workaround.
- Updated PDF presentation with ConfigReport.py prerequisites and syntax.
- January 17th, 2018
- Initial publication
22 August 2019