How do you handle Report Repository setup when using a load balancer?
Hi Team,
Our environment architect includes a load balancer distributing incoming traffic to 2 PeopleSoft webservers. Setting the Report Repository Path to a local drive on each of the web servers results in a situation where report files cannot be retrieved when accessing to the system via a web server other than the original server where report process was run and outputs were assigned to the Report Repository Path of that server. Looks like a practical solution to this dilemma is to specify a common Report Repository Path of the web profile.
Does anyone use a different solution? If you use the approach of using Report Repository Path of the web profile, do you use a separate server other than one of the web servers for the Report Repository Path?