mValent Integrity™ enables IT organizations to achieve dramatic improvements in ITIL®-based configuration, change and release management processes, thereby delivering improved productivity, reduced costs and improved IT service levels through a best practices approach to managing the application infrastructure.
mValent Integrity provides a ready-made solution to drive ITIL best practices for gathering configuration knowledge, implementing change control and release management for the thousands of configuration parameters that support large, distributed application infrastructures.
mValent Integrity drives dramatic improvements for these ITIL processes:
- Configuration Management – mValent Integrity uses a “deep dive,” agent-less technique that catalogs the interdependencies among thousands of configuration settings (CIs) across all phases of the application lifecycle in a single repository that can easily feed a federated configuration management database (CMDB). Learn more
- Change Management – mValent Integrity delivers dynamic Compare and Version Control (Configuration Baseline in ITIL language) so that IT teams can isolate root causes quickly and roll-back immediately to a “known good” version of configuration settings—either for a particular component or for the entire set of components that comprise a J2EE application environment. Learn more
- Release Management - mValent Integrity leverages the value of the comprehensive configuration data (or CIs) through a dynamic model that demonstrates change impact before implementation. This forward-looking view of proposed changes ensures that service levels remain high and unexpected outages are minimized. mValent also automates change provisioning, change validation and change ‘capture’ which allows IT to immediately back out any changes that have an undesirable impact. Taken together, these heighten IT’s confidence that changes are being made correctly and comprehensively. Learn more
Here are a few more examples of ITIL processes inherent in mValent Integrity:
- Configuration Baseline – Both “Point-in-Time” views and “Versions” provide baselines to recover from configuration-related problems.
- CMDB – The comprehensive configuration data stored in mValent provides complete input on application configuration data to a federated CMDB.
- Full Release – Release management tools in mValent Integrity ensure that all components of the application infrastructure can be built, tested, distributed and implemented together.
- Change History – mValent delivers fully on ITIL’s mandate to maintain “auditable information that records, for example, what was done, when it was done, by whom and why.”
Learn more about how you can adopt ITIL best practices. |
