Hi all! We have a customer that was using eB with High Availability with two Application Servers. Most communities where upgraded from 14.6.2 to 15.4.1 and are working fine. Now they created a new community and It's working fine in App1 but they cannot link the repository in App2 the same way they did for 14.6.2. The error message says that the repository already exists. In v14.6.2 in that case the SMC used to ask if the repository should be linked to App2, you clicked "yes" and that was all. What is the correct procedure on v15.4.1? We were looking at the documentation and we found nothing. Any updated documentation about high availability scenarios? Keep in mind that in this case we are talking about two Application Servers running at the same time serving the same communities and using the same repositories, we are not talking about Storage Servers replicating remotely over an slow link. That case is well documented. And keep in mind that in v14.6.2 was an easy configuration and communities upgraded from v14.6.2 to v15.4.1 are today working fine in the same installation. Thanks a lot, Ezequiel.
↧