When the configuration of an Intermediary, contained in AureaMonitorIntermediary.xml, is used in a new installation, all the service groups are restored and displayed in the web interface but after a few seconds of starting the launcher, the configuration goes away.
This also happens after an immediate restart of the AI via the AMS provisioning screen. This affects the 12.x version.
Version 12.x and higher have a strict source/target concept for Intermediary. It is highly recommended therefore to have a source and a target launcher profile. The source AI is the instance where the configuration (eg., a new service group) is created. Then this configuration is uploaded to the AMS via an Export Profile.
On AMS this export profile is assigned to the target AI launcher profile. On the next provisioning, the target AI(s) receive the new configuration. Any local configuration will be wiped out (= deleted).
If you do not use source and target AI profiles, then it can be very confusing for users to know where to make configuration changes. Since we do not recommend such a setup(no source and target profiles) and neither do we test it, it is encouraged that you use two dedicated launcher profiles. The only exception is if you have only a target launcher profile and the AMS acts as the source (i.e. import from a lower environment than production, eg., staging or testing).
If an Intermediary is started with a source launcher profile with no Export Profiles assigned, but with the configuration (as found in AureaMonitorIntermediary.xml) from a previous target Intermediary, then the configuration will be deleted. There are two reasons for this:
- First reason is that the AI configuration is internally marked as "came from AMS" and will therefore be removed on the next provisioning.
- The second reason is that there is no local Export Profile defined.