This feature is available in midPoint 3.6 or later.
MidPoint is often deployed in several environments: development environment, testing environment, production environment. These environments have almost the same configuration. The difference is often just host names and port numbers. However, these configuration properties may be spread across many places: resource configuration, outbound mappings, object templates and so on. It might be quite hard to maintain all these properties up to date, especially when moving configuration updates from development environment to testing and from testing to production.
Therefore midPoint 3.6 has a new mechanism for that: constants. The constants can be defined in a single place in the system and then easily used in midPoint expressions. The constant definition can be bound to a specific environment and defined locally. Then the midPoint configuration object do not contain any environment-specific data and the configuration can be easily transferred from environment to environment.
Configuration and Use
See Configuration and Use of Constants for more details.