Installing the WAR File Using js-install Scripts

Follow this procedure to install JasperReports Server using the WAR file distribution. The js-install shell scripts, supported on Windows, Linux, and Mac, do most of the work for you.

Prerequisites for installing the WAR file:

If you use a custom domain with GlassFish, see GlassFish Modifications.

For an optional pre-install validation test, run js-install.bat/sh test. See js-install Script Test Mode for more information.

To install the WAR file using js-install scripts:

The scripts are intended for the bash shell.

The directory, TIB_js-jrs_7.2.0_bin, appears in the file location you choose.

For example, if your database is PostgreSQL, copy postgresql_master.properties to <js-install>/buildomatic.

appServerType=tomcat [jboss-eap-7, wildfly, glassfish, skipAppServerCheck]
appServerDir=c:\\Program Files\\Apache Software Foundation\\Tomcat 9.0
dbHost=localhost
dbUsername=postgres
dbPassword=postgres

appServerType=tomcat [jboss-eap-7, wildfly, glassfish, skipAppServerCheck]
appServerDir=c:\\Program Files\\Apache Software Foundation\\Tomcat 9.0
dbUsername=root
dbPassword=password
dbHost=localhost

appServerType=tomcat [jboss-eap-7, wildfly, glassfish, skipAppServerCheck]
appServerDir=c:\\Program Files\\Apache Software Foundation\\Tomcat 9.0
dbUsername=jasperserver
dbPassword=password
sysUsername=system
sysPassword=password		
dbHost=hostname

dbUsername=c##jasperserver		
sid=cdb1

foodmart.dbUsername=c##foodmart
sugarcrm.dbUsername=c##sugarcrm

appServerType=tomcat [jboss-eap-7, wildfly, glassfish, skipAppServerCheck]
appServerDir=c:\\Program Files\\Apache Software Foundation\\Tomcat 9.0
dbUsername=db2inst1
dbPassword=password
dbHost=localhost

appServerType=tomcat [jboss-eap-7, wildfly, glassfish, skipAppServerCheck]
appServerDir=c:\\Program Files\\Apache Software Foundation\\Tomcat 9.0
dbUsername=sa
dbPassword=sa
dbHost=localhost

Note the following: When the property appServerType is set to skipAppServerCheck, buildomatic skips any application server validation. Backslashes in paths must be doubled in properties files, for example: appServerDir=C:\\Apache Software Foundation\\Tomcat 9.0. The dbUsername must be the same as the Oracle user name. In addition, buildomatic will not work with the “sys as sysdba” syntax. For Oracle 12c without CDB/PDB, do not use the c##jasperserver dbUsername. Use the standard jasperserver dbUsername instead.

The default_master.properties file has a property setting to enable encryption of passwords that reside on the file system. This applies to all files found under the buildomatic folder, as well as the connection pooling file used by Apache Tomcat (context.xml). Currently, password encryption for connection pooling supports only the Tomcat application server.

To enable encryption on the file system, uncomment the encrypt property so it looks like this:

encrypt=true

If you encounter errors during the js-install script execution, see Error Running js-install Scripts (js-install.bat/sh).

Configuring Tomcat to Allow Groovy Scripts

When running JasperReports Server, Tomcat requires additional permission configuration for Groovy scripts in both the catalina.policy file and in the protection domain for reports.

In <apache-tomcat>/conf/catalina.policy, you need to grant Groovy scripts permission to read the JasperReports Server classpath:

In <js-webapp>/WEB-INF/applicationContext.xml, the same permissions need to be added to reportsProtectionDomainProvider. This change grants access to reports that use the Groovy language, plus reports that need to load additional classes from the JasperReports Server web application.

<bean id="reportsProtectionDomainProvider" class="com.jaspersoft.jasperserver.api.<br />  engine.jasperreports.util.PermissionsListProtectionDomainProvider">
    <property name="permissions">
      <list>
        <bean class="java.io.FilePermission">
          <constructor-arg value="${catalina.home}${file.separator}webapps<br />            ${file.separator}jasperserver-pro${file.separator}<br />            WEB-INF${file.separator}classes${file.separator}-"/>
          <constructor-arg value="read"/>
        </bean>

        <bean class="java.io.FilePermission">
          <constructor-arg value="${catalina.home}${file.separator}webapps<br />            ${file.separator}jasperserver-pro${file.separator}WEB-INF<br />            ${file.separator}lib${file.separator}*"/>
          <constructor-arg value="read"/>
        </bean>
      </list>
    </property>
</bean>

These settings are required to start any supported version of Tomcat.

Open topic with navigation