Setting up a dedicated TIBCO JasperReports® Server Job Server

Introduction

In this article, we take a look at how to set up a dedicated TIBCO JasperReports^® Server job server, and the advantages of doing that.

Advantages

• Customer-facing TIBCO JasperReports Server instances dedicated to the on-demand experience are not burdened with scheduled job execution duties
• Can use existing version of TIBCO JasperReports Server you’re on, no need to upgrade
• If you’re already used to working with load balancers and spinning up new instances, this isn’t going to be much more difficult
• In terms of TIBCO JasperReports Server, there are only configuration file changes to make

Procedure for setting up a Dedicated Job Server

• Add new TIBCO JasperReports Server instance to cluster
• Don’t add the new instance to the load balancer rules
• Disable the LB-facing TIBCO JasperReports Server instances from executing scheduled jobs

Configuration Change to Disable the Job Scheduler

• Comment out the quartzSchedulerControl bean in the Spring configuration files
• Find the applicationContext-report-scheduling.xml file in the ../jasperserver-pro/WEB-INF directory
• Comment out the quartzSchedulerControl bean completely so it looks like this:

– <!--bean id="quartzSchedulerControl"
           class="com.jaspersoft.jasperserver.api.engine.scheduling.quartz.QuartzSchedulerControl"
           depends-on="reportSchedulingService"
           init-method="start">
      <property name="scheduler" ref="quartzScheduler"/>
  </bean-->

You can further tune the Quartz properties

• Configure the number of threads available for job execution via the org.quartz.threadPool.threadCount property
• Configured to 2 concurrent threads by default, can be set much higher
• Quartz resource: http://quartz-scheduler.org/documentation/quartz-1.x/configuration/ConfigThreadPool