Application Configuration Management in Kemp 360 Central is based around application profiles that define how an application is load balanced. Application profiles include definitions on the scheduling and persistence to be used in addition to how connections are secured. Application profiles are re-usable, with deployment-specific elements such as server pools and SSL certificates being specified at deployment time.

Application profiles define the Virtual Services (VS) and SubVS required to load balance the application and contain application-specific configuration of parameters such as timeout values and scheduling methods. Application profiles can also link to pre-defined SSL policies and traffic modification rules to enable centralized management of these elements across multiple profiles. Deployment-specific configurations such as SSL certificate, server pools, and IP addresses are specified when deploying an application profile.

The Deployment History lists each application profile deployment and can be expanded to view details such as the certificate used. To enable rollback of deployments to a known good version or state, any deployment can be redeployed to replace the most recent deployment.

Server pools group application servers to allow for easy re-use and maintenance. They exist independently of application profiles and changes can be applied across all application profiles that reference the server pool.

SSL certificates and private keys are maintained in the certificate repository. Server certificates, certificate chains, and private keys may be uploaded to the system and selected when deploying an application profile. The certificate repository also provides insight on expiring certificates with filtering on 30-day and 90-day expiry timeframes. Use of the certificate repository is optional and certificates and keys may be uploaded for single use at deployment time.

All private keys uploaded to the certificate repository are stored as password protected PEM files. If you do not want to store private keys in Kemp 360 Central, certificates and keys can be specified at deployment and not stored.