Hi all
I know vCAC 5.2 is the previous version now with vCAC 6.0 being released. However there are still a large number of vCAC 5.2 projects running. Including the one I am working on at the moment.
I had a problem where the initial install was done by some colleagues and I continued with the installation building out the vCAC web layer to a 2 node load balanced construct. The install completed by my colleagues was following my design. I had placed the vCAC Manager Server role and the vCAC Model Manager Web services role on separate machines. My reasoning around this was based on the security requirements of the customer.
The installation was functioning well until we came to build the second web server. We had some major problems with all the portals. We lost both the vCAC admin portal and the vCAC Self Service Portal and got REPO404 errors when trying to access them.
I looked over the logs of the vCAC web servers and could see loads of SSL errors. So I check the certificates on all the servers and all of them were correct.
After some discussions internally I decided to place the Model manager web service on the web servers with the other website components. We installed vCAC from the start and found this removed the error.
I think the problem was a combination of the SSL and communication URL that the model manager was using was being replaced with a new one when the second Admin portal service was installed. This then conflicted with URLs and certs in the Manager service and maybe in the repository. We could have over come this with a load balancer, but at the time we didn't have this available.
Hope this helps if you see the REPO 404 error as there isn't much documented about it.
No comments:
Post a Comment