Tutorial: Basic Monitoring for Oracle SOA Suite 11g
Matt Brasier and Nick Wright, authors of Oracle SOA Suite 11g Performance Tuning Cookbook, show us how to get the key aspect of monitoring right.
Having recently written the Oracle SOA Suite 11g Performance Tuning Cookbook, we felt it would be interesting to discuss one of the key topics covered. The purpose of the book is to provide a one-stop shop for information on tuning Oracle SOA Suite 11g, from optimizing the operating system to tuning composites. One of the key aspects of any performance strategy is monitoring, which not only allows you to observe and identify the cause of any performance problems that you may have, but to observe the impact that any changes you make have on performance.
A coherent monitoring strategy encompasses all aspects of the application lifecycle, with monitoring in development used to ensure that applications meet their non-functional requirements and to determine alerting levels that should be set in reference and production environments. Reference and operational systems need to be monitored to ensure they are behaving as expected, and to provide a baseline for what "known good" performance looks like. This tutorial looks at how you can monitor various aspects of your SOA Suite application.
Probably the most basic monitoring you can perform is to use the operating system level tools to view the CPU and memory usage of your application server process. Use the command: jps –v to obtain a list of all the java processes on your box, and note the process ID of the one running your application server. You can then use operating system tools such as top or the windows task manager to view the CPU and memory usage of the process with the matching ID.
Monitoring with the Administration Consolelog into the WebLogic Administration Console
Log into the WebLogic Administration Console http://admin-server-host:<admin-port>/console and under Environment -> Servers -> <SOA Server name> -> Monitoring -> JDBC we'll see a breakdown view of the JDBC connections. Click Customize this table and ensure that Prep Stmt Cache Current Size and Active Connections Current Count are added to the chosen list.
Monitoring with Oracle Fusion Middleware Enterprise Manager
If you have installed the enterprise manager components in your domain, you can use the enterprise manager to obtain some basic monitoring information. Connect to:
And log in with your domain admin credentials. Then navigate to WebLogic Domain -> <SOA domain name> -> <SOA server name>, right click and select Performance Summary.
Click the button Show Metric Palette and select metrics to monitor. Good starting candidates are JVM Heap and Memory Usage, SOA Composite Errors and Incoming Message Throughput, finally in the Server Overview folder there is a summation of the JDBC connections Open JDBC Connections.
All of the methods here are very basic, and donít really provide the necessary level of detail or control that we would recommend for a production domain. We would strongly urge anyone with an Oracle SOA Suite installation to configure this or a similar monitoring tool, and establish good performance baselines so that "normal" performance is well understood. This would include monitoring aspects such as JTA transaction volumes, datasource pool sizes, JVM memory usage, open sockets, etc. Configuring such tools is beyond the scope of this simple tutorial, but could be covered in a follow-up article.
Coming soon - an introductory tutorial to Oracle SOA Suite 11g
Author Bios: Matt Brasier and Nick Wright are the authors of Oracle SOA Suite 11g Performance Tuning Cookbook, which contains interesting, hands-on recipes, giving detailed descriptions and lots of practical walkthroughs for boosting the performance of your Oracle SOA Suite. Matt is Head of Consulting at C2B2 while Nick is Senior Middleware Consultant at C2B2 and JSR 343 (JMS 2.0) Expert Group member.