JasperReports Server installation notes
The WorldServer installation procedure for JasperReports Server (JRS) adapts the standard instructions to specific WorldServer features.
If you want to install JasperReports Server by using the installer (Windows only), you can find the WSReportsSetup.msi installer in the Installers folder of the WorldServer distribution kit. If you want to install JasperReports Server manually, use the package located in the \integrations\JasperSoft_<version> folder of the WorldServer distribution kit.
Prerequisites
Before you install JasperReports Server, make sure you meet the following requirements:
- Know where your WorldServer application server is installed, how to configure it, and how to deploy new web applications. You also need WRITE permissions for various folders and locations on your application server, as well as for the WorldServer configuration files.
- Know the location and login credentials of the WorldServer database server.
- Make sure the JAVA_HOME and CATALINA_HOME environment variables are configured correctly. You usually configure them as properties when you deploy WorldServer.
Installation overview
The installation of JasperReports Server for WorldServer is slightly different from the standard procedures described in the JRS documentation. Note the following about a WorldServer-specific installation of JasperReports Server:
- WorldServer does not support bundled MySQL (or PostgreSQL) servers to store the JRS repository.
- When you run the js-install.bat or js-install.sh script manually, you can usually install only the minimal configuration. This avoids installing sample data that does not apply to WorldServer. For example, on Windows, the command would be: js-install.bat minimal
- The JasperReports Server documentation refers to changing JVM parameters to run JRS (section 6.2.1 of the JRS installation guide). Though the installation guide states that "this is required", existing Tomcat deployments may already have specific settings that you should not change.
- JRS is licensed software. A license is included with the installation.
Notes for manual JRS installations on Linux
| Folder name | Observations |
|---|---|
| buildomatic | If necessary, run: chmod u+x <js-install>/buildomatic/* |
| buildomatic/bin | If necessary, run: chmod u+x <js-install>/buildomatic/bin/* |
| apache-ant/bin | If necessary, run: chmod u+x <js-install>/apache-ant/bin/* |
Notes for manual JRS installations on Windows or Windows Server
- You need to start a command shell as an administrator.
- If you edit configuration files in C:\Program Files (x86) or C:\Program Files, you also need to run your text editor as an administrator. Otherwise, any changes you make might not be displayed in the actual file.
- Run the <js-install>\buildomatic\js-install-service.bat command to install JRS as the new WorldServer Reports service. To edit the service, run c:\Program Files\Idiom\Reports\tomcat\bin\WorldServerReportsw.exe.
Notes when installing JRS on a Microsoft SQL Server database
- The database user you choose for installing the JRS repository must have appropriate permissions for creating databases (dbcreator might be enough). You may want to revoke sysadmin permissions after installation.
- You cannot store JRS data in the same database that WorldServer is using. If necessary, on low-usage environments, they can use the same database server, but they cannot share the same schema.
Notes when installing JRS on an Oracle database
Note the following about Chapter 5 of the JasperReports Server Install Guide for Oracle:
- There is no mention of the Oracle SID parameter in the JRS installation guide, but the
sidproperty is in the oracle_master.properties file. If you are using a non-default SID on your target Oracle database (the default isorcl), configure thesidproperty accordingly. - The JRS installation creates a jasperserver schema instance by default; its password is password.