thanks a lot for this clarification!

When each IBM® Lotus® Connections application starts up it reads/validates all of the Lotus Connections configuration XML files, which are stored with the IBM® WebSphere® Application Server configuration files. An important point is that configuration in a file is NOT identified by the file name as one would expect – it is identified by the ‘id=’ attribute of the config element (which is one of the standard ways to identify configuration data). Thus, if a Lotus Connections configuration file is saved by renaming it from LotusConnections-config.xml to LotusConnections.SAVE.xml, for example, both files are XML files and contain the same set of configuration as far as Lotus Connections is concerned.

In earlier releases, Lotus Connections would read both files and use whichever version it read second. Thus, configuration changes might be mysteriously ignored. In release 2.5, the duplicate configuration is noticed and the following error message is logged: CLFRO0130E: Error, multiple configurations found for configuration identifier . (In addition, the full filename for each file is given). This, I would argue, is better/safer than using whichever configuration is read second.

Unfortunately, the message can get “lost” in the lengthy log as Connections continues to initialize. This will most likely be dealt with in the next release/fix-pack.