Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

Chapter 13. Monitoring Your System with the JON for SOA Web Console

13.1. JBoss Operations Network (JON)

The JBoss Operations Network (JON) program is a tool that you can use to administer your JBoss Enterprise SOA Platform server.
It enables you to perform inventorying, monitoring, deployment and software update administrative tasks. JON utilizes a customizable web-portal interface and it provides a central place where you can manage your system.

13.2. JON for SOA

JON for SOA is a specially-packaged version of JON that includes functionality designed specifically for the JBoss Enterprise SOA Platform.

13.3. Analyse JBoss Enterprise SOA Platform Enterprise Service Bus Statistics

Procedure 13.1. Task

  1. Click on JBoss ESB Statistics (above the Resources menu) to "drill down" through various levels of statistics.
    On the first level, the figures displayed are a summary for the overall ESB instance.
  2. Click on the JBoss ESB Deployment item to view a list of all of the Enterprise Service Bus packages deployed on the server. One will not see any statistics at this level but, from here, one can select a deployment and drill down into it to view them.
  3. Drill down further still to view details for that deployment's constituent services and actions.

13.4. Metrics Available Through JON for SOA

Different metrics are displayed depending on the level selected. The following lists summarises everyone that is available:

Statistics Available at the ESB Level:

  • Message Count (Successful)
  • Message Count (Total)
  • Message Counts (Failed)
  • Processed Bytes
  • Last Failed Message Date
  • Last Successful Message Date

Statistics Available at the Service Level:

  • Message Count
  • Message Count (avg) per Minute
  • Overall Bytes
  • Overall Bytes Failed
  • Overall Bytes Processed
  • Overall Service Time Processed

Statistics Available at the Action Level:

  • Message Count
  • Message Count (avg) per Minute
  • Messages Failed
  • Messages Failed (avg) per Minute
  • Messages Successfully Processed
  • Messages Successfully Processed (avg) per Minute
  • Overall Bytes
  • Overall Bytes Failed
  • Overall Bytes Processed
  • Processing Time

Statistics Available at the Listener Level:

  • Life-cycle State
  • Maximum number of threads
  • MEP
  • Service Category
  • Service Description
  • Service Name
  • Start Date
Use these statistics to configure any standard JBoss Operations Network function, (such as alerts), for any JBoss Enterprise SOA Platform deployment, service or action.

13.5. Use JON for SOA to Deploy an Archive

Procedure 13.2. Task

  1. Open a web browser and log into the JON for SOA Console.
  2. Go to the JBoss ESB Statistics screen.
  3. Click on the INVENTORY tab
  4. Go to Child Resources.

    Note

    You can view historical deploy requests here as well.
  5. Go to the Create New menu and select JBoss ESB Deployment.
  6. On the Create New Resource page, choose the archive to deploy and select where it should be sent (which, under normal circumstance, will be your deploy directory).

    Note

    Remember that only compressed files can be uploaded: use the Deploy Zipped option to determine whether it should be deployed as a compressed or an exploded archive.

13.6. Use JON for SOA to Delete an Archive

Procedure 13.3. Task

  1. Open a web browser and log into the JON for SOA Console.
  2. Go to the JBoss ESB Statistics screen.
  3. Click on the INVENTORY tab
  4. Go to Child Resources list.
  5. Tick the entry to be deleted.
  6. Click DELETE

    Note

    You can view historical delete requests here as well.
Result

The archive is deleted.

13.7. Automatic Service Discovery

The JON agent can automatically detect ESB archives deployed or deleted independently of JON. This is known as the Automatic Service Discovery feature. The JON agent performs this check once every twenty-four hours.

13.8. Change the Automatic Service Discovery Feature's Polling Rate

Procedure 13.4. Task

  1. Open the configuration file installed with the JON Agent in a text editor: vi rhq-agent/conf/agent-configuration.xml
    Edit the file as per this example code:
    <entry key="rhq.agent.plugins.service-discovery.period-secs" value="86400"/>
    
  2. Save the file and exit.
  3. Restart the JBoss Enterprise SOA Platform.
    In contrast to the JBoss Enterprise SOA Platform consoles, there is no way to force the JON web console to collect new data on demand. Clicking on buttons such as Get Current Values (found under the Metric Data tab) only updates the display to reflect the most recently collected data. If you want an an update immediately, reset the collection period to a very low value, such as thirty seconds. (Remember to set the interval back to the previous figure afterwards.)

    Important

    If you set the value to too low a figure, performance will suffer.

13.9. Change the Automatic Service Discovery Feature's Polling Rate (Alternative Method)

Procedure 13.5. Task

  1. Open a web browser and log into the JON for SOA console.
  2. Add a JON agent to the server's inventory of resources.
  3. Click on CONFIGURE.
  4. Change the value for Service Discovery Period.

    Note

    You do not need to restart the agent for the change to take effect.