Thanks for opening the documentation issue.
While we're at it - I'll disagree with your Report service observation. I'll agree that when CABI went from BOXI R2 to BOXI R3.1 the bug is that the set Service Name variable in the servicereports template (%NIKU_HOME%\.setup\templates\bin\reports\bo\servicereports.bat) was not updated from 'Central Management Server' to 'Server Intelligence Agent'. I believe I opened this as a bug back in the day but I don't recall. It's just a standard part of my upgrade process to update this template as appropriate. For Jasper I'll do the same. I'm assuming for now I'll point it at Jasper's Tomcat service - I'll update this thread when I get there, get this up, working and 'managed'.
I highly recommend CA stay the course with the report service. Not every organization has administrators with remote rights or skills to restart services. It's been easy for me to train others that, when trouble starts (and BO starts it), goto CSA, click this Reports check box, click Stop, watch it stop, then click Start. Watch it start then test.