Accelerate Your Path to Full-Stack Monitoring and Alerting
Register for this live webinar featuring Zenoss and VictorOps today!
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
The ZenPacks.zenoss.WebLogicMonitor ZenPack monitors Oracle WebLogic Server services.
This ZenPack uses the JMX Remote API and and accesses MBeans deployed within WebLogic that contain performance information about the components that are being managed. This performance information includes pool sizes for data sources (JDBC), threads, connections (JCA), queues (JMS), servlets, JSPs, Enterprise Java Beans (EJB), timer queues.
Throughput is also monitored when it is available. This metric is computed by WebLogic and is based on the number of messages moving through a queue at any given time. The throughput metric gives a good picture of the health of the messaging subsystem, which is commonly used throughout many enterprise applications. Stateless, Stateful, and Entity EJB performance metrics are monitored, as are message driven bean performance.
Security realms are also monitored for potential denial of service attacks. This includes recording of authentication failures, broken out by valid accounts, invalid accounts, and accounts that are currently locked out. Application specific realms can be monitored by customizing the built in WebLogic default realm.
WebLogic 10.0 or higher is required.
To enable remote JMX access set the following variables in "startWebLogic.sh" (Linux) or "startWebLogic.cmd" (Windows):
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12347 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
This file normally located in "bin" directory under your domain. For example on Windows with domain "base_domain" this may be "C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd"
Open it with text editor and search for "echo WLS Start Mode=%WLS_DISPLAY_MODE%" line. Put JAVA options above after this line. Then save file and restart WebLogic. Now you have your 12347 port binded to JMX queries from Zenoss (zJmxManagementPort property). This port number may be changed due to your needs.
Depending on your OS security, it may be required to add appropriate rule to firewall.
All WebLogic services must have a device entry under the /Devices/Server/WebLogic device class.
Note: The zenjmx daemon must be configured and running. See ZenPack:Java_2_Platform_Standard_Edition_(J2E) for more information about configuring the zenjmx daemon with the Sun JRE tools.
Tip: The out-of-the-box WebLogic data source configuration has been defined at the macro level, but can be configured to operate on a more granular basis. For example, the Servlet Reload Count applies to all servlets in all web applications but it could be narrowed to be Servlet /submitOrder in web application "production server".
For performance reasons you may reduce the amount of metrics retrieved.
WebLogic has a tool to check with monitoring data - "WebLogic ServerAdministration Console". By default it is available on:
To view raw data JConsole application from Java suite can be used. To connect to WebLogic Server JMX point JConsole to:
If you are monitoring a Web application running on WebLogic server, you may find that the transaction always fails with a code 550 regardless of how you configure the script. This could be a result of the WebLogic server being behind an SSL proxy. When used in this configuration, WebLogic requires that a WL-Proxy-SSL header be added to the request so that it knows to redirect to HTTPS instead of HTTP.
To support this extra header in your Zenoss platform Web transaction, you must make the following changes on the script tab of your WebTx data source.
add_extra_header WL-Proxy-SSL true
By default this template not binded to WebLogic device.
WebLogic JDBC monitoring template is an example of configuration. It should be copied and modified to use with your JDBC datasources. In this template testds datasource name should be changed to actual datasource name.
To add additional JDBC metrics one may use http://WEB_LOGIC_HOST:7001/console/dashboard monitoring dashboard and set filters:
Metrics list will be populated with available options. These may be set as datasource params in WebLogic JDBC monitoring template.
To test these metrics on WebLogic dashboard new view (graph) may be created. Then it is required to click "Run" button at left top corner to run monitoring.
Depending on WebLogic server configuration it may happen that not all JMX datapoints are collected. This may occur when all monitoring templates are enabled. To deal with it turn off monitoring templates you not interested in as described in "Change the Amount of Data Collected and Graphed" section.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.