Installation Types

As of version 8.0, JasperReports Server supports the following installations:

• Compact installation: The Repository, Audit, Access, and Monitoring tables are created in a single repository database. This is the same configuration as previous versions.
• Split installation: Only the Repository tables are created in the repository database. The Audit, Access, and Monitoring tables are created in a separate audit database. For servers with high loads or performance needs, this speeds up repository access by storing diagnostic logs separately.

The default installation is the Compact installation.

The Access and Audit events are now processed asynchronously using a thread pool. The default number of threads is 15 and is configurable in the applicationContext-events-logging.xml file. If you want to switch back to the synchronous mode, comment out the following section:

<bean id="loggingEventsService" class="com.jaspersoft.jasperserver.api.logging.service.impl.LoggingFacade">
<property name="asyncExecutor" ref="asyncEventsExecutor"/>
</bean>

 

The binary installer does not support split installation. For split installation, use the stand-alone WAR file distribution, which is the official TIBCO JasperReports Server installer.

Additional Buildomatic Configuration for Split Installation Upgrade

The default_master.properties file handles the configuration for the Split installation upgrade.

To configure the default_master.properties file for the Split installation upgrade:

• Edit the default_master.properties file to configure settings specific to your database and application server.

Look for the line Uncomment below settings ONLY for split installation and uncomment the settings listed in “Sample Values for the default_master.properties File”.

For example: To uncomment # installType=split, change it to installType=split.

“Sample Values for the default_master.properties File” lists the settings you need to uncomment with sample values for each supported database.

Sample Values for the default_master.properties File

Database

Sample Property Values

PostgreSQL

 
# installType=split
# audit.dbHost=localhost
# audit.dbUsername=postgres
# audit.dbPassword=postgres
# audit.dbPort=5432
# audit.dbName=jsaudit

MySQL

 
# installType=split
# audit.dbHost=localhost
# audit.dbUsername=root
# audit.dbPassword=password
# audit.dbPort=3306
# audit.dbName=jsaudit

Oracle

 
# installType=split
# audit.dbHost=localhost
# audit.dbUsername=jsaudit
# audit.dbPassword=password
# audit.dbPort=1521
# audit.dbName=jsaudit
# audit.sysUsername=system
# audit.sysPassword=password

# audit.sid=ORCL

If you're using an Oracle service name instead of an SID:

# audit.serviceName=: uncomment and add your service name.

# audit.AdditionalAdminProperties=;SysLoginRole=SYSDBA;User=sys;Password=password

DB2

# installType=split 

# audit.dbHost=localhost
# audit.dbUsername=db2admin
# audit.dbPassword=password
# audit.dbPort=50000
# audit.dbName=JSAUDIT

For DB2, the audit.dbName value must be in uppercase.

SQL Server

# installType=split 

# audit.dbHost=localhost
# audit.dbUsername=sa
# audit.dbPassword=sa
# audit.dbPort=1433
# audit.dbName=jsaudit

Note the following:

If the installType=split property is not configured, the installation upgrade will be compact.

The audit.dbPort property is specific to the database. You can change the values for other properties as required.

Each sample_conf/<dbType>_master.properties file contains the properties and appropriate sample values.