Application Configuration Management (CM) in Kemp 360 Central can address many use cases, all of which enable rapid and consistent configuration of application delivery resources.

DevOPS and Continuous Delivery

With CM, the load balancer configuration can be defined and tested as part of the development process before being made available for production use. Application profile versioning uses the minor version number of a profile to identify if a profile is in 'development' or production ready. If the minor version is zero (for example, 5.0), the application profile is considered production ready and may be deployed by the system or manually. If the minor version is non-zero, the application profile is considered to be in development and can only be manually deployed.

Configuration management enables the rapid creation of disposable environments for development, QA, and staging. This reduces the effort and cost of maintaining and hosting parallel systems.

Multi-Cloud Deployment

In a multi or hybrid cloud environment, configuration management enables consistency across platforms and provides a single point of control. For example, a single application profile can be defined to optimize and secure delivery of services based on the Apache web server. This profile can then be applied across the complete estate of Apache services reducing the configuration and maintenance effort and ensuring consistent deployment.

Hosting Service Provider

Service providers that offer customer-specific application instances can simplify life-cycle management of application resources through the use of pre-defined profiles for the workloads being delivered to users. The use of profiles ensures consistency and accelerates deployment and provides a single point to manage change across all customer instances.