Review Scheduler Diagnostics

The Scheduler diagnostics page provides the runtime status of the scheduler.

The Diagnostics page provides status of its JMS configuration, JMS queues, Cluster instance status, Scheduler Database status, Toplink status, and Scheduler (Quartz) status.

The Diagnostics page displays how many scheduled report requests have been received by the JMS queues, how many of them have failed and how many are still running. The JMS status can be viewed at the cluster-instance level enabling you to decide whether to add more instances to scale up by one or more of these JMS processors.

For example, if there're too many requests queued up for the e-mail processor in one instance, you can consider adding another instance and enabling it to handle e-mail processing. Similarly, if there're very large reports being processed and showing in the Report Process queue in running status, then you can add another instance to scale up the Report Process capability.

Also, the Scheduler Diagnostics page reflects the status of each component to show if any component is down. You can see the connection string or JNDI name to the database, which cluster instance associates to which managed server instance, Toplink connection pool configuration, and so on.

If an instance shows a failed status, then you can recover the instance and with the failover mechanism of the JMS set up in the cluster, no jobs submitted are lost. When the server instance is brought back, it is immediately available in the cluster for service. The instance removal and addition reflects dynamically on the diagnostic page.

When an instance is added to the cluster, the Scheduler Diagnostics page immediately recognizes the new instance and displays the status of the new instances and all the threads running on that instance. This provides a powerful monitoring capability to the administrator to trace and resolve issues in any instance or any component of the scheduler.

The Scheduler Diagnostics page provides information on the following components:

• JMS

• Cluster

• Database

• Scheduler Engine

The JMS section provides information on the following:

• JMS Cluster Config: This section provides configuration information for JMS setup:

  • Provider type (Weblogic / ActiveMQ)

  • WebLogic version

  • WebLogic JNDI Factory

  • JNDI URL for JMS

  • Queue names

  • Temporary directory

• JMS Runtime: This provides runtime status of all JMS queues and topics.

  
  

  
  Description of the illustration xdo11g_sched_jms_rt.gif

  
  

The Cluster section provides details on the cluster instance. Use this information to understand the load on each processor.

Description of the illustration xdo11g_sched_cluster_diag.gif

• JMS instance config

• JMS Wrapper

• JMS Client - System — Provides status of the BIP System topic. The scheduler diagnostic page is a subscriber to this topic.

• JMS Client_producer — Not used.

• JMS Client_schedule — Provides status of the job processor and report processor, each processor showing number of active threads, number of messages received, number of messages failed, and number of messages running.

• JMS Client_delivery — Provides status of different delivery processors as listeners, each delivery processor showing number of active threads, number of messages received, number of messages failed, and number of messages running.

The Database section provides information on these components.

• Database Config — Connection type, JNDI Name, or connection string

• Toplink Config — Connection pooling, logging level

• Database Schema

Description of the illustration xdo11g_sched_data.gif

The Quartz section provides information on these components, as shown in the figure below.

• Quartz Configuration

• Quartz Initialization

Description of the illustration xdo11g_sched_q.gif