Though the WorldServer user interface (UI) displays a great deal of information as it is processing or scheduling operations, you might want to make this information available outside of WorldServer. For example, you might want to share, or put on file, information about active projects and tasks, translation costs, translation status, vendor task completion summaries, and so on. This information is stored in the archive and active schema tables and can be extracted and formatted into reports.
WorldServer is bundled with a reporting engine called JasperReports. This is an easy solution to get started with because it is included with WorldServer, a number of useful reports for JasperReports come out of the box, and the integration work for single sign-on between WorldServer and JasperReports has already been done.
However, WorldServer stores its data in an Oracle or MS SQL Server database, so any reporting tool that can query these data sources can be used to build reports on WorldServer. If the reporting tool you want to use has a web interface for managing reports, you can configure WorldServer to bring up this management web page when users select Tools > Report Center. To configure another reporting engine, open the general.properties file (in your WorldServer application server area) in a text editor and find the report_center_url option. The default value is for use with JasperReports.
Report Center, as shipped, is configured to use Jaspersoft's JasperReports Server. To use a different reporting engine, set this value to the URL of the reporting application you want to open. WorldServer will pass the active WorldServer token as a URL parameter in case this application can use the token to implement a single sign-on.
More information can be found in our RWS Documentation Center and in this article: Where can I find information about the purpose of each out-of-the-box Report in the WorldServer Report Center?
