Platform notes

The installation of the JasperReports Server (JRS) with WorldServer implies certain differences from the standard procedures described in the JRS documentation. Note the following:

  • When you run the js-install.bat or js-install.sh script, install only the minimal configuration in all cases. This avoids installing sample data that does not apply to WorldServer. For example, on Windows, the command would be js-install.bat minimal
  • The JasperSoft documentation refers to changing JVM parameters to run JRS (section 6.2.1 of the JRS installation guide). Though the installation guide states "this is required", existing Tomcat deployments may already have specific settings that should not be changed.

The following sections provide more information for various platforms.

Linux permissions

On Linux installations, after you extract the jasperreports-server-6.3.0-bin.zip archive, make sure the files in the following folders are executable:
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/*.

Windows 7 and Windows Server 2012 R2/2016

  • When you install JasperReports on Windows 7 or Windows Server 2012 R2 or 2016, start a cmd shell as an administrator, so you can perform the installation.
  • If you edit configuration files in C:\Program Files (x86) or C:\Program Files, your editor must also "run as administrator". Otherwise, any changes you make will not be displayed in the actual file and you will not see a message informing you of the problem.
  • You should run the <js-install>\buildomatic\js-install-service.bat to install JRS as the new SDL WorldServer Reports service. To edit the service, also run c:\Program Files\Idiom\Reports\tomcat\bin\SDLWorldServerReportsw.exe.

Microsoft SQL Server

  • The database user you choose for installing the JRS repository must have permission to create databases (dbcreator might be enough). You may want to revoke sysadmin permissions after installation.
  • You cannot put the JRS data into the same database WorldServer is using. They can share the same server, but they cannot share the same schema.

Oracle

Note the following about the Chapter 5 of the JasperReports Server Installation Guide instructions for Oracle:

  • There is no mention of the Oracle "SID" parameter in the JRS installation guide, but the property sid does appear in the oracle_master.properties. If you are using a non-default SID on your target Oracle database (default is orcl), adjust the sid property as required.
  • In practice we have found that you do not have to define the "sysUsername" and "sysPassword" properties in the default_master.properties file for Oracle. They can be removed completely from the file. You can also separate the creation of the Oracle database schema from the rest of the server installation. This eliminates any need to enter the SYSDBA username and password into the default_master.properties file.

The JRS installation creates a jasperserver schema instance by default, with the password password.