Community WLSDM Support
The agent.jar was in the lib folder. The lib folder was on classpath.
I repaced the agent.jar. This solved the issue.
Thanks a lot.
I am happy that you are able to monitor your backend datasource JDBC monitoring. Yes, you can monitor all your datasources in the same dashboard.
Other APM tools injects runtime codes to your codes which creates a lot of overhead on your JVM instances. WLSDM uses native method and that’s why we call “native WebLogic monitoring”.
On the other hand; please follow “Generic DevOps MBean” tutorials and build your own dashboards and automate your WebLogic management.
Thanks for your kind support.
JMS Servers resources added successfully.
When we skip the monitoring of DataSource and JMS server, setup finishes successfull.
We checked the space in the database and it was without problems, what we did was to restart the opc application, thank you very much
Email alert’s default sender value is “[email protected]”.
You can edit sender(from) as below.
You can select any range by using date field. But the maximum backward range is the WLSDM monitoring start time.
WLSDM log viewer line limit is 1000 but you can search any string and find searched string where line is located in whole log file via “text filter”.
There is another way to view log files via WLSDM file explorer. Go to “Operational Tools & Utils -> File Explorer” pick “.log” file then click view button (max 1 mb view size). Also you can download log file to your local environment via file explorer.
The WLSDM and the WL-OPC have their own data-archive mechanism.
For the WLSDM, default data archive range is 90 days, and for the WL-OPC, default data archive range is 365 days.
You can find the settings below.
Non-adminstrator users not allowed for administrative operations by default as below screenshots.
Metric configuration for adminstrator user:
File explorer for monitor user:
You can change access restriction configuration in “WLSDM System Settings > system.authorization” page.
Default value is OFF in “system.authorization.page.access.fileexplorer.allgroups” feature. It means only administrators can access to “file explorer”. If you turn on this feature, you must set access path for non-adminstrator users then non-adminstrator users only can access the path(s).
You can restrict log viewer access configuration via “system.authorization.page.access.logviewer”. Default value is on, it means all users can access log viewer, if you turn off this feature, non-adminstrator users will not able to access logviewer.
On the other hand, Make sure you have not applied wlsdm_agent JVM arguments to the AdminServer?
If you send the whole details and logs we would like to help you to alter this problem. We have never seen this error before. It looks like this is something relevant to this environment. Have you tried the installation on another domain environment?
If you want to see File/Socket events you should increase your WLDF Diagnostic volume on WebLogic
Go to "Servers > $ManageServerName > General (tab)" page and set "Diagnostic Volume" high. Then you are able to see file read/write events.
Note: This option means additional overhead on your managedservers; just activate only one managedserver which file read/write monitoring is important.
No; this property is usefull when OPC is down. You had better enable it. Disabling that property will NOT disable for all domains.
You can still configure notification settings on WLSDM part; like ON/OFF backend notifications.. etc.
The configuration is still same; all the functionalities on WLSDM are still supported by OPC. If you have a specific case; then please let us know in detail to reproduce it.
This timeout value is a precaution to protect the system.
That's why we can’t let the increase the timeout value by users.
If you need a long-running process; you can trigger your WLST script using a shell command.
That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).
Also, this type of usage means; The script is out of the control to WLSDM.
You can’t call the stored WLST scripts from the scheduler module.
And you need a shell script (custom action) to run an external WLST script from the scheduler module.
WLSDM doesn't support the feature you ask.
But you can complete the installation quickly using the wizard.
-- How many domain installation planning you are exactly?
Is possible to have a CUSTOM LOGs or something like that to monitor various logs files generated dinamically on some folder in the Web Logic Server? In some cases we use these kind of files to register detailed transaction procesing to have a better understanding of application test cases under the hook, obviouslly in a DevTest Env.
Great work BTW!!
Thank you for your supportive comments. Custom log monitoring and every kind of log/text file management is available on WLSDM. Please check below documents and tech blog posts;
Tutorial for your CUSTOM LOG request --> https://blog.wlsdm.com/weblogic-log-monitoring-screencast-monitor-every-text-file-on-wlsdm/
Log file view/upload/download and File Explorer --> https://blog.wlsdm.com/weblogic-log-request-and-file-upload-solution-file-explorer-and-log-viewer-tailer/
Probably it is a WebLogic issue. If it is a "Devlopment Mode" WebLogic domain; you should not see the "Change Center" in WebLogic console. But, in your sceen capture "WebLogic Change Center" is available (attached below). We are recommending to setup your WebLogic domain from scratch as Development mode domain.
If you want a master degree on WebLogic Administration, you need to know how WebLogic JMX MBean objects works.. New tutorial about monitoring WebLogic JMX MBean objects...
How to monitor WebLogic MBean Object Metric values?
How to get Weblogic Thread Dump when hogger & stuck threads occur?
How to get Weblogic Heap Dump when OutOfMemory occurs?
How to get Weblogic Java Flight Recorder (JFR) Dump when performance problems occur?
How to get Weblogic Diagnostic Image when performance problems occur?
Get SMTP(email) or SNMP(trap) notifications instantly when something goes wrong on your WebLogic Domain.
A quick review and brilliant blog post by Oracle ACE Dirk Nachbar
How about yours? Is there anyone who used "User Defined JMX Metric Actions" on WLSDM for WebLogic console?
A quick look on WLSDM for WebLogic ServerWLSDM (WL Smart Dashboard & Monitoring) was already mentioned by some people within the Oracle WebLogic Community. The WLSDM tool is a Console extension with which you can monitor your Oracle WebLogic Server environment. But its not only a pure monitoring tool, its more than this, it provides on top even Notifications and Alarms for metrics. Current release for WLSDM is 2.3.1 which also comes with Oracle SOA Support :-) The installation is really straight forward as described in the installation document from the WLSDM, but the given 1 minute deploy time is a bit optimistic :-) its more 5 minutes, but this is still impressive how quick you can setup WLSDM :-) Just follow the instructions for the installation, after you start the WLSDM Dashboard, the configuration assistant will guide you through the necessary configuration and your Monitoring and Notification/Alarm System is ready to use. WLSDM comes is real Dashboard Style with provides you several views on your WebLogic Server environment. General Health Overview Dashboard:
Read the complete blog post by Oracle ACE Dirk Nachbar
This version is very stable and contains SOA module. It's very enjoyable to monitor Oracle FMW SOA Suite domains by using WLSDM.
v2.3.1 Change Log:
FMW SOA Monitoring Module is released. (Supports 11g and 12c)
WLSDM SOA Monitoring, Diagnostics & Report Modules
SOA Smart DashboardsMonitoring BPEL Engine (Only 11g) BPEL Engine Dashboard (Historical – Only 11g) Monitoring Composite Performance Monitoring Callback and Invoke Monitoring Composite Faults Monitoring Deployed Composites Trend Summarizing Composite List & Endpoint URIs SOA Notifications and Alarms BPEL Engine Notifications Composite Performance Notifications Callback and Invoke (DLV_MESSAGE) Notifications Composite Faults and Errors Notifications SOA Reports Reporting SOA BPEL Engine Reporting SOA Composite Performance Reporting SOA Callback and Invoke (DLV_MESSAGE) Reporting SOA Composite Faults and Errors SOA Daily Reports (EMAIL) Daily SOA Report for Composite Performance Daily SOA Report for Callback and Invoke (DLV_MESSAGE) Daily SOA Report for Composite Faults and Errors Daily SOA Report for Deployed Composites Trend
Auto archive feature is added. Configurable and integrated archive module for all the stored data types
JVM System Resources dashboard is renewed and enrichedMonitor JVM CPU Load , Heap (Usage, Free, Size) Alarm / Notification feature is added to JVM Resources dashboard Grid and Chart feature is added
Health dashboard is renewed and enrichedDonut charts are added: Health States (WebLogic Servers, Deployments, Data Sources, JMS) Server state feature is enriched WebLogic server activation time and counter feature is added
Deletion feature is added to “Monitoring & Diagnostics > Profiling Dumps” page. (Asynchronous file deletion for JFR, WLDF Diagnostic Image, HPROF, LOG)
New “Operational Tools & Utils > MBean Search” page is addedSearch any text in WebLogic MBean Instance Type Search any text in WebLogic MBean Attribute Type Search any text in WebLogic MBean Instance Name Search any text in WebLogic MBean Attribute Name See all the WebLogic MBean attribute values on search results Compare WebLogic MBean attribute values New “Domain Overview > Timeout Values” page is added.
WLSDM: Timeouts are the most important settings for keeping your WebLogic domain healthy, strong and responsive Important and Recommended WebLogic “Domain Timeouts” MBeans are listed with their values Important and Recommended WebLogic “JVM Timeouts” MBeans are listed with their values Important and Recommended WebLogic “Server Timeouts” MBeans are listed with their values Important and Recommended WebLogic “Data Source Timeouts” MBeans are listed with their values WebLogic Runtime JVM arguments and WebLogic console arguments values is added to “Domain Overview > Domain Summary” page WebLogic Domain Structure menu items are added as integrated and dynamic drop-down menu to all WLSDM pages WebLogic Admin Server monitoring plug&play application “monitorWLAdmin” is enriched. General performance and error handling improvements Several bug fixes
Read Complete List: http://www.wlsdm.com/download/#CL_V231
Start Native WebLogic monitoring now! http://wlsdm.com/download
Download #WLSDM v2.1.5 for #WebLogic.. Check out new features below.http://weblogiccommunity.com/2016/01/09/wlsdm-version-2-released-things-are-really-different-anymore/
WLSDM Version is really mature and assertive anymore..
No server, No Database... No additional resources. Don't waste your money and time.
WLSDM does not need any additional resources (Server, Database, Memory, CPU... etc.). This means you don't need to spend operational costs for your WebLogic monitoring tool. Only keep your WebLogic Admin Server UP and HEALTHY.
If you are a senior WebLogic Administrator then show your skills by using WLSDM. WLST Web Console, User Defined Custom MBean Actions... Administrators and Developers going to love it! Do you? Designed and Developed for WebLogic Administrators & Developers
See what's new on Version-2: New WLSDM Features
Free Developer Edition (Fully Featured) - WLSDM can be used by developers for free!
WLSDM Quick installation Wizard is more robust anymore. Monitoring & Diagnostics step is added
Suggest Button for Metric Thresholds on Wizard pages
Get manual profiling dumps for JFR, Thread Dump, WLDF Diagnostic Image and Heap Dump
Self-Tuning Thread Pool Threads detail is added for HoggingThreadCount and * StuckThreadCount EMAIL notifications
Back-end system monitoringJDBC Executement Statement Webservices JAXWS Endpoint EJB Business Method Invoke
Back-end Reports page is added
Operational Tools section is added
WLST Web Console Page
Storing and Executing WLST Scripts
Thread Dump Analyzer Page
Notifications are enriched
Log Inspector Notifications
Response Times Notifications
Back-end Systems Notifications
Enable/Disable Global Notifications for EMAIL and SNMP By One By
Enable/Disable All EMAIL-SNMP Notifications feature is added
SNMP Notification feature is added. Easy SNMP trap configuration:
SNMP Trap for WebLogic State and Health (Servers, Deployments, Data Sources and JMS)
SNMP Trap MBean Metric Values
SNMP Trap for WebLogic Server Logs
Test SMTP and SNMP settings operations are added to Configuration > System page
Log Inspector WLDF snippets are addedDead Lock Heap Space Stuck Thread Unchecked Exception General Severity Error
WebLogic Domain Summary Page is added
Data source passwords are listed on domain summary page (Decrypted and Encrypted) - All users are forbidden except administrators.
View WLSDM Log Page is added
Response Times Chart is added to Monitoring & Diagnostics > Response Times page
User Defined Metric Actions feature is added. WebLogic domains can be automated according to MBean values
Anymore all users and user groups able to login WLSDM console. Page authorization is enriched.
Installation and Introduction Video Tutorial
Another review on oraclemiddlewareblog.com by Radu Dobrinescu
The WebLogic application server can host business critical J2EE applications or can serve as a platform for just as important middleware systems such as Identity Management, Business Intelligence, Service Oriented Architecture and others. Either way, it is very important that WebLogic administrators have quick access to the most significant metrics that show how the system is behaving. And although there are very useful and versatile built-in monitoring tools included in the Fusion Middleware stack, such as the WebLogic administration console or the Enterprise Manager applications, these can still be further improved with features that can prove to be very helpful, especially for real time monitoring. One such extension to the already existing tools is the WebLogic Smart Dashboard and Monitoring application.
The tool integrates natively with the administration console and the links to its monitoring features conveniently show up as a portlet in the administration console portal.
The product itself is very easy to install and basically consists of copying the application war file in the console-ext directory of the domain followed by a restart the Admin Server. The WLSDM portlet that allows access to the main WLSDM pages is also reachable by a direct URL....
Thanks to Brett Walker that he addressed WLSDM. Absolutely, he redirected to the right place.
Now, we're going to explain how it's easy to do this by using WLSDM which is aimed to monitor WebLogic domains naturally :)
Normally, it's easy to do by shell and WLST scripting; but getting thread dump continuously can be challenge and risky. It can create an overhead on your WebLogic domain.
Let's say you're familiar with WLSDM. It's really easy to install WLSDM and use it. If you're not introduced with WLSDM for WebLogic just follow this blog post on WLSDM community portal. WLSDM Intorduction
Step-1: Go to "Configuration / System" Page and focus on "system.metric" tab. There are two important properties on WLSDM configuartion/system page. Metric harvest frequency and number of alarm count till alarm situation is valid. Screenshot is below and values are default.
The harvest frequency and number of alarm count can be changed. For the continues thread dump, just set it more than 1. Let's set the value to 10. Which means 10 alarms would be generated if the situation is still valid.
Step-2: Go to "System / Metrics" page. For instance, find ActiveExecuteThread MBean record, then click on "Edit" button. There is Actions button for each servers on WebLogic domain (Screenshot Number-1). Click on actions button and select "Thread Dump" action (Screenshot Number-2) and save. Check below screenshot:
Step-3: The alarm must be enable by setting a threshold value which is less than current ActiveExecuteThread MBean value in ThreadPoolRuntime.
After all, WLSDM would start notifying you via email by attaching "WebLogic Server Thread Dump" or "Dump Stack" files continuously. Check below screen shot.
It's possible to analyze thread dumps by using WLSDM's thread dump viewer and analyzer module.
Besides thread dump action, there are even more actions available on WLSDM. These are:Java Flight Recorder (JFR) Heap Dump (.HPROF) WebLogic Diagnostic Framework (WLDF) Image (.ZIP)
If you want to learn much about WLSDM actions, there is a good tutorial on Youtube. Here is link: https://www.youtube.com/watch?v=ec-MccMPCqY (WLSDM Actions)
Hope, you enjoy this detailed answer on WLSDM community portal.
WLSDM Support Team
3- Other YouTube tutorials available.
WLSDM v1.2.0 released and ready to monitor mission critical WebLogic production domains.
Check these basic insallation steps;
1- Download WLSDM product:WLSDM Download Page
2- Install WLSDM by following installation guide:WLSDM Installation Guide Document WLSDM Installation Tutorial on Youtube
** Or never mind just copy wlsdm.war to $DOMAIN_HOME/console-ext folder. That's all :)
3- Complete WLSDM wizard for the first installation by watching wizard tutorial:Wizard Completion Tutorial on Youtube
4- Watch other tutorials on Youtube for getting familiar with WLSDM. You'll see it's really easy to adopt :)Dashboard Usage Tutorial on Youtube Learn How to get Thread Dump, JFR (Java Fligh Recorder), JVM Heap Dump, WLDF Diagnostic Image Learn WLSDM Metric Usage and email configurations for ALERT and CLEAR notifications
Hope, WebLogic administators enjoy using WLSDM. We designed and implemented this product according to WebLogic administrators' requests.
If you have any problem, do not hesitate to post it on WLSDM community portal.
Keep smiling because you're using WebLogic and WLSDM :)