BI Publisher clustering support enables you to add server instances on demand to handle processing and delivery load; the JMS queues for scheduling and JMS topic for publishing diagnostic information are shared across the server by registering JMS queues and topics through JNDI services. In each managed server instance all the processes (Job Processor, Report Processor, E-mail Processor, FTP Processor, Fax Processor, File Processor, Print Processor, and Web Dav Processor) are configured. Therefore the moment a server instance pointing to the same repository is deployed, it is added to the cluster and all the processors in this instance are ready to run. BI Publisher provides a robust failover mechanism; by enabling the Job Processor in two nodes, if one node fails, then the second node can process the jobs.
After you install BI Publisher using the BI Platform Installer and start the servers, the BI Publisher scheduler is running; and JMS is configured in your server for BI Publisher. You can see this configuration in the Scheduler Configuration page: From the Administration page, under System Maintenance, click Scheduler Configuration. Figure below shows the JMS Configuration regions of the Scheduler Configuration page. For each cluster instance that you have configured, a processor configuration table is displayed. Use the tables to enable and disable processors and specify threads for each processor. The default number of threads for each processor is set by the Threads per JMS Processor property under JMS Configuration, as shown in the figure; edit the threads for a specific processor in the Cluster Instances region by updating the Number Threads setting.
NOTE: Processors that use the default setting show no entry in the table (default is 5, for BIP Job Q).
Enter a Number Threads value only to set a thread count for a particular processor to differ from the default (Change it to 3, to reduce traffic). This will allow only 3 threads per JMS queue to be processed at a time. Bounce is required to have this change effect. These changes are required in circumstances when you don’t have enough memory to support parallel jobs. You need to either increase the Heap Size OR reduce the number of parallel jobs.
For bursting job, one job after bursting will parallel call BIP core engine to generate report.If you don't have enough memory, you need to reduce the number of parallel processes by change the # of threads per processor: go to scheduler Administration page-> Scheduler configuration -> JMS configuration to change the default processor to say 2 (or any lower value than default).
NOTE: After this changes, clean-up the XDO temp directory, before you start the BI.
Navigation
Login to: BI -> Administration -> Scheduler Configuration (Under “System Maintenance”), change all the JMS Processor (Number Threads) = 3.
