TIER Reference Implementations are designed to enable rapid evaluation of a component or set of interconnected components and provide a starting point for a full campus deployment. Reference Implementations are developed for Docker Swarm but dependencies are minimized within the containers in order to facilitate the use of other container orchestration mechanisms.
Evolveum midPoint is a registry/provisioning tool selected as one of components of the TIER architecture. This document highlights packaging requirements for the component in the context of a Reference Implementation for production campus deployment. This approach simplifies the work needed by campus deployers, providing a fully functional service that can either be used as-is with additional campus support work or as
A production deployment of midPoint designed to support a large-scale campus typically consists of (a) a server to operate the application itself, (b) the application's database, (c) LDAP infrastructure, and (d) Rabbit MQ. Many other environments are possible. Of these elements, LDAP is typically the only component operated in high availability mode. midPoint itself is operated in standard availability mode. The midPoint database needs provisions for backups but not for high availability.
Like other primary TIER components, the Large Production TIER midPoint Reference Deployment utilizes Docker SWARM. Confidential configuration information (keys, passwords, etc.) will be managed with Swarm secrets.
Availability of midPoint demo users in ldap
Yes - see above - Demo RabbitMQ subscriber that writes to a log file