Hi Richard - sorry for my delay in response on this one. The info Paul provided is correct. Jasper is resource heavy (as any reporting system usually is) and thus we recommend putting it on its own server. Additionally, as a side note, there is no real "migration path" from BOXI to Jasper. By that, we mean that there is no mechanism of exporting BOXI reports and importing them into Jasper. Unfortunately if you have customized reports in BOXI, you will need to rebuild those from scratch in Jasper using Jasper Studio. What most customers have done is run BOXI and Jasper side by side in parallel as they rebuild the custom reports in Jasper, and then they disable the reports in BOXI once that same report is published in Jasper. Out of the box we do provide quite a few reports to give you the basics. Lastly, the only other thing I wanted to mention is that in order to use Jasper, it is a requirement to be at 14.1.03 (CP3 patch level for 14.1) otherwise Jasper cannot connect to SDM to run reports.
With that, here are some links to help you out a bit with Jasper:
CA Business Intelligence - Home - CA Business Intelligence JasperReports® Server - 6.2.0 - CA Technologies Documentation
Documentation | Jaspersoft Community
Getting Started with CABI JasperReports Server r6.2.0 - CA Service Management - 14.1 - CA Technologies Documentation
Hope this helps a bit.
Thanks,
Jon I.