Overview Business Service Management Value Propositions Feature Summary Platforms Management Console Alarm Manager Virtual Appliance Cloud Ready Monitoring MSP Ready Monitoring

eG Monitors

Single Agent Agentless Monitor Network Monitor Integration Console

eG Virtualization Monitors

eG Monitor for VMware^® Infrastructures eG VDI Monitor Citrix XenServer Monitor Citrix XenApp Monitor Citrix XenDesktop Monitor Solaris LDoms Server Monitor

eG Application Monitors

Citrix XenApp Monitor Terminal Server Monitor Oracle Monitor Java Monitor WebLogic Monitor SAP Monitor Sun Java Enterprise System Monitor Microsoft Exchange Monitor Microsoft SQL Monitor Corillian Voyager Monitor Micros Opera Monitor

eG Web Monitors

Web Server Monitor Microsoft IIS Monitor Apache Web Monitor

eG Server Monitors

Server Hardware Monitor System Monitor Microsoft Windows Monitor AIX Monitor Solaris Monitor Linux Monitor Unix Monitor

eG Reporter eG Extensions

Client Emulator Redundant Manager SMS Manager Integration Console

Services

Support

FAQ White Papers

Partners

Technology Partners Strategic Partners Partner Benefits Partner Login

Company

Management Team Investors Customers Locations

News

Press Releases Success Stories Reviews Presentations Events Newsletter

Blog

Careers

Sales Technical

Contacts

Locations

eG WebLogic Performance Monitoring

Get Your Free Trial

For More Information

Monitoring Multi-Tier WebLogic Environments

To achieve scalability and performance, most Internet application deployments have evolved into multi-tier infrastructures where the web server tier serves as the web front-end, the business logic is executed on middleware application servers, and the backend storage and access is provided via database servers. While multi-tier infrastructures offer a variety of scalability and extensibility benefits, they are also more difficult to operate and manage. When a problem occurs (e.g., a slowdown), an administrator often has difficulty in figuring out which application(s) in the multi-tier infrastructure could be the cause of the problem - i.e., is it the network? Or the database? Or the WebLogic server? Or the middleware? Or the web server? Comprehensive, routine monitoring of every infrastructure application and network device is essential to be able to troubleshoot effectively when problems occur.

The application server middleware that hosts and supports the business logic components is often the most complex of the multi-tier infrastructure. To offer peak performance, an application server provides a host of complex functions and features including database connection pooling, thread pooling, database result caching, session management, bean caching and management etc. To ensure that the application server is functioning effectively at all times, all of these functions have to be monitored and tracked proactively and constantly.

The eG WebLogic Monitor

eG Enterprise's WebLogic model

WebLogic monitoring end-to-end: The topology of a
WebLogic service

The eG WebLogic Monitor offers comprehensive monitoring for the BEA WebLogic application server. Over a hundred critical metrics relating to a WebLogic server instance can be monitored in real-time and alerts can be generated based on user-defined thresholds or auto-computed baselines. Through these metrics, administrators can track the functioning of the WebLogic server's database connection pools, thread pools, session management, bean container, cluster manager, etc. eG Enterprise's customized layer model for WebLogic allows correlation of the WebLogic application server performance with other network and operating system metrics.

In conjunction with eG Enterprise's web server and database server monitors and it's built-in single click root-cause diagnosis capability, the eG WebLogic performance monitor allows administrators to quickly pin-point which of the infrastructure applications could be the cause of a bottleneck in a multi-tier infrastructure.

Versions Supported
Support for WebLogic Version 5.1 onwards is available as part of the eG Enterprise suite with SNMP and the Java Management Extensions (JMX), being used as mechanisms through which the eG agent interfaces with a WebLogic server instance.

A single eG agent is capable of monitoring all of the WebLogic application server instances executed on a system. The eG Reporter includes pre-canned reports highlighting the availability, performance, and usage of a WebLogic server instance.

What the eG WebLogic Monitor Reveals

Server monitoring	Is the WebLogic process running? Is the memory usage of the server increasing over time? Is the server's request processing rate unusually high?
JVM monitoring	Is the JVM heap size adequate? Is the garbage collection tuned well or is the JVM spending too much time in garbage collection? What is the average CPU utilization of the JVM? Which threads are responsible for the CPU usage and what lines of code is each thread executing? Are there any deadlocks happening in the JVM? Which threads are responsible for a deadlock and which lines of code (which modules, classes, files) were they executing prior to the deadlock? Are there any blocked threads? Which threads are blocking them and which lines of code are responsible for this?
Thread monitoring	Are the WebLogic server's execute queues adequately sized? Are there too many threads waiting to be serviced, thereby causing slow response time?
Security monitoring	How many invalid login attempts have been made to the WebLogic server? Are these attempts recurring?
JMS monitoring	Are there many pending messages in the messaging server? Is the message traffic unusually high?
Connector monitoring	What is the usage pattern of connections in a connector pool?
Cluster monitoring	Are all the WebLogic servers in the cluster currently available? Is the load being balanced across the cluster?
Transaction monitoring	How many user transactions are happening? Are there too many rollbacks occurring?
Servlet monitoring	Which servlet(s) are being extensively accessed? What is the average invocation time for each servlet?
EJB Pool monitoring	Are there adequate numbers of beans in a bean pool? How many beans are in use? Are there any clients waiting for a bean?
EJB Cache monitoring	Is the cache adequately sized or are there too many cache misses? What is the rate of EJB activations and passivations?
EJB Lock monitoring	Is there contention for locks? How many beans are locked? How many attempts have been made to acquire a lock for each bean?
JDBC Connection monitoring	Are all the JDBC pools available? Is each pool adequately sized? What are the peak usage times and values? How many connection leaks have occurred?
JDBC call monitoring	How many JDBC calls have been made? What was average response time of those calls? What are the queries that take a long time to execute?

Benefits of WebLogic Monitoring using eG Enterprise

In-depth real-time analysis of a WebLogic server's performance including analysis of various sub-components such as the Virtual Machine (JVM), Database Access (JDBC), Java Beans (EJB), Connectors, Clusters, etc

Automatic baselining of WebLogic performance and intelligent time-based alerting when any unusual high activity is detected

Automatic Correlation of WebLogic's performance with Web server and database performance to pin-point the root-cause of problems

A 100% web-based monitoring solution that allows anytime, anywhere Weblogic performance monitoring & performance tuning.

eG Agentless Monitor

eG Java Monitor

Live Demonstration