Why is this process needed?
Company Alpha has a number of applications Deployed in WebSphere. They manage their WebSphere configuration as code using IBM UrbanCode Deploy (UCD). This allows Company Alpha to version their WebSphere configuration and deploy it to multiple environments, ensuring the configuration always matches their expectations.
But what if someone alters the WebSphere configuration not from IBM UrbanCode Deploy, but from WebSphere directly? For example, let’s say version 2.0 of the WebSphere configuration has been deployed to production. In the middle of the night, a defect is discovered, causing an application to become inaccessible. Ideally, the defect would be fixed in version 3.0 of the WebSphere configuration and applied by UCD. Instead, let’s say that, in an effort to fix the problem as quickly as possible, a WebSphere admin logs in to the WAS admin console and changes some settings to get things working again. Now, WebSphere configuration in UCD thinks version 2.0 is deployed but that’s not the case because of the manual intervention. Such situations can be avoided by running a live comparison process to detect differences between the WebSphere configuration in UCD and the actual WebSphere configuration. Additionally, this comparison process may be scheduled to run on a regular basis. Notifications, such as an email message, may be sent to interested parties if configuration drift has been detected.
For more information on the live compare feature, visit Comparing configurations with live WebSphere Application Server instances and Automating live comparisons.
This video walks users through the steps of creating component and application process to run WebSphere Configuration discovery and compare it to the configuration saved in UCD. After comparing configurations, it notifies designated users of the finding.
Users are familiar with WebSphere configuration discovery by UCD. A number of example processes are available to help users learn about WebSphere Configuration Discovery.
Areas/Features of Product Used
- Components (versions and processes)
- Applications (processes and environments)
- Resources and Resource Group
- Teams and User Roles
- Event/Deployment Scheduler
Though a number of UCD features are used, the critical role is played by “WebSphere Configuration Compare” and “WebSphere Get Compare Result” steps.
Here are a few screen shots to show what to expect from the video. The video shows that an application process is run at a scheduled time which calls on a component process to run live comparison and get comparison result as shown in Figure 1. UCD then sends an email showing the status and a link back to the UCD server shown in Figure 2.
Figure 1. WebSphere Configuration Compare and Get Result steps
Figure 2. Email content with the executed process result link
Figure 3. Execution Log
Figure 4. Difference table showing the differing resources elements
Figure 5. Changed parameters with values