Can a Reports Server leverage OPMN and the auto-rerouting of requests?
Since the in-process reports server just runs within the OC4J process, OPMN effectively restarts it by restarting OC4J on failure. OPMN does not manage out of process Reports Server. However, after certain amount of requests Reports Engine is restarted, thus reducing the failure possibility. Since there can be only one in-process reports server per machine, a glitch in the reports server on a machine is end-user visible until OPMN restarts that OC4J instance. Multiple machines can however be running the in-process reports server that can then be load balanced via Web Cache or an external load balancer.