v3.1.2 | Released on 2017.06.24
The license agreement (EULA) can be found on wlsdm-license.html page which is located in "lic" folder
$wlsdm_package.zip file contains following directories and files:
war | contains wlsdm.war which is the main installation file and WebLogic Smart Dashboard & Monitoring Console extension |
jar | contains wlsdm_agent.jar file which is the WLSDM agent for the operational actions. Must be add to the server's JVM arguments |
docs | contains the help documents for WLSDM |
lic | contains license information files. wlsdm-license.html and other 3rd party license information files |
WLSDM improves administrative and DevOps WebLogic knowledge and skills. Use " / info" icons for MBean explanations and descriptions on WLSDM console
NOTE: No additional server, database, memory, CPU, operational cost... etc. is required!
Unix-Linux Windows MAC OS X
Easy installation!
WLSDM Installation Best Practice Architecture
Note: If there is no cluster configuration and ManagedServers are independent with the same configuration to serve same application(s) consider above CLUSTER wlsdm_agent.jar structure, too. Install wlsdm_agent.jar for one ManagedServer hosted on the same machine(s)
Optional: There is no need to install wlsdm_agent.jar for monitoring JMX MBean Objects, WebLogic Logs and Application Response Times. $wlsdm_package/jar/wlsdm_agent.jar must be installed for back-end monitoring and remote JVM actions. It is highly recommended to install at least on one managed server
Important Note: WLSDM agent has almost zero overhead on managed server resources and it is only used for RJVM operations. Its cost is negligible. WLSDM injecting nothing to runtime codes
Quick Step by Step Installation Guide
!!! Already RUNNING Domain !!!
1. copy $wlsdm_package/jar/wlsdm_agent.jar to /path/to/wlsdm_agent.jar on the managed server machine(s)
[user@machine]$ mkdir $DOMAIN_HOME/wlsdm_agent [user@machine]$ cp $wlsdm_package/jar/wlsdm_agent.jar $DOMAIN_HOME/wlsdm_agent/wlsdm_agent.jar
2. add wlsdm_agent.jar to WebLogic managed server´s JVM Arguments as below: --> *${JAVA_OPTIONS}
(Consider above best practice architecture...) *2.1. JRockit and JDK 1.6: Add the following WLSDM JVM parameters to WebLogic managed server´s JVM Arguments: -javaagent:/path/to/wlsdm_agent.jar -Dwlsdm.agent.logger.level=INFO -XX:FlightRecorderOptions=repository=WLSDM/temp/JFR *2.2. Lower JDK 1.7.0_40: Add the following WLSDM JVM parameters to managed server´s JVM Arguments: -javaagent:/path/to/wlsdm_agent.jar -Dwlsdm.agent.logger.level=INFO *2.3. JDK 1.7.0_40 and Higher and JDK 1.8: Add the following WLSDM & JFR JVM parameters to managed server´s JVM Arguments: -javaagent:/path/to/wlsdm_agent.jar -Dwlsdm.agent.logger.level=INFO -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=repository=WLSDM/temp/JFR
How to add WLSDM JVM Parameters to WebLogic managed server arguments? a) With WebLogic NodeManager: to instrument managed server instances started and stopped through the Node Manager, use the administration console
from the administration console, navigate to "Environments > Servers > (select your server) > Server Start > Arguments" add the above suitable JVM entry to Arguments section and save the page:
Environments > Servers > (select your server) > Server Start > Arguments
b) Without WebLogic NodeManager: add the following entry (add before Java executes) to the "startManagedServer" file UNIX / LINUX / MAC OS X:"startManagedServer.sh"export JAVA_OPTIONS="$JAVA_OPTIONS -javaagent:/path/to/wlsdm_agent.jar -Dwlsdm.agent.logger.level=INFO -XX:+UnlockCommercialFeatures -XX:+FlightRecorder"WINDOWS:"startManagedServer.cmd"set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:"C:\path\to\wlsdm_agent.jar" -Dwlsdm.agent.logger.level=INFO -XX:+UnlockCommercialFeatures -XX:+FlightRecorderNOTE: there is no need to install "wlsdm_agent.jar" to the WebLogic Admin Server!
3. (re)start WebLogic managed server(s) which wlsdm_agent.jar is installed. after restarting managed server(s), below logs must be seen in managed server log files. this means WLSDM agent is deployed successfully. ManagedServer Log:<Mar 4, 2015 1:13:24 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM agent loaded successfully. Version: v3.1.2> <Mar 4, 2015 1:13:24 PM PDT> <Info> <WLSDM> <BEA-000000> <RJVM operation is bound in the registry with the name wlsdm_agent_remote_operation.>
4. copy $wlsdm_package/war/wlsdm.war to ${WEBLOGIC_DOMAIN_HOME}/console-ext/. folder on the admin server machine
5. then (re)start WebLogic admin server. that is all, WLSDM console will deploy automatically after restarting admin server, below logs must be seen in admin server log files this means WLSDM console is deployed successfully and WLSDM console is ready to monitor WebLogic domain AdminServer Log:<Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM console deployed successfully. Version: v3.1.2> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM garbage collection monitoring initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM metric monitoring initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM health monitoring initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM performance monitoring initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM back-end monitoring initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM data archiver initialized successfully.> <Mar 4, 2015 1:12:12 PM PDT> <Info> <WLSDM> <BEA-000000> <WLSDM custom MBean handler initialized successfully.>
6. make sure all your WebLogic domain resources (wl servers, deployments, data sources, jms servers... etc.) are RUNNING and ACTIVE
7. access WLSDM console
How to access WLSDM console?
8. complete WLSDM quick configuration wizard carefully according to WebLogic domain characteristic
How to complete WLSDM wizard?
Installation and Introduction Video Tutorial
How to install and use WLSDM?This tutorial also contains basic information about usage
After the installation, login to WebLogic admin console then WLSDM portlet will be visible in WebLogic domain structure
Click "Smart Dashboard Console" on WLSDM menu
OR
Type WLSDM URL on browser's address bar for accessing directly
http:// $ADMIN_SERVER_IP : $PORT /console/WLSDM
https:// $ADMIN_SERVER_IP : $PORT /console/WLSDM
Main WLSDM menu is located on the left side and default is collapsed. It can be expand/collapse by menu icon
Page operations icon is located on the right top of every pages. Visual page settings and page functions can be listed on page operations menu
WLSDM Console has "Quick Tour" for the first login. WLSDM Console usage is very easy and user friendly. Just follow quick tour steps!
Visit all WLSDM default dashboards, pages and discover WLSDM console features. Especially "Operational Tools & Utils" pages will increase interactivity between Administrator/Developer/DevOps and WebLogic Domain. Enjoy your "Native WebLogic Monitoring and Diagnostic" solution.
Transform all kind of scripts to JMX MBeans
Use Generic DevOps MBean functionality and never miss any detail about WebLogic domain environment. Export the DevOps scripts and share with team members. Do not let valuable scripts have lost in CRON jobs.
This feature is named as DevOps MBean to increase the interactivity between WebLogic domains and deployed applications. It is possible to monitor i.e. Waiting orders, logged in user count, 3rd party webservice invocation response times... etc.
The left screen capture at below is the script part and the right screen capture is the Output on the assigned custom dashboard. Totally parametric and supports to define custom actions for the assigned threshold.
Step-1 Write Shell Script: Ping database and calculate database respone time using WebLogic API (weblogic.jar)
#Author: WLSDM | 2017
#Variables
_dbStatus=0
#0:DB_DOWN,1:DB_UP
#start DB Ping
_startTime=$(($(date +%s%N)/1000000))
_pingResult=`java -cp weblogic.jar utils.dbping ORACLE_THIN $YOUR_USER_NAME $YOUR_PASSWORD $YOUR_IP:$YOUR_PORT/$YOUR_SERVICE_NAME`
_endTime=$(($(date +%s%N)/1000000))
_dbResponseTime=`expr $_endTime - $_startTime`
if [[ "$_pingResult" == *"Success!!!"* ]]; then
_dbStatus=1
#echo "Database connection SUCCESS!!!"
#DB_UP
echo DatabaseStatus=$_dbStatus
else
_dbStatus=0
#echo "Database connection FAILURE!!!"
#DB_DOWN
echo DatabaseStatus=$_dbStatus
fi
echo DatabaseResponseTime=$_dbResponseTime
Shell Script Output:
DatabaseStatus=1
DatabaseResponseTime=1218
Step-2 Use WLSDM Generic DevOps MBean Wizard
"User Defined Generic DevOps MBean" wizard is availabe on "Configuration > Monitoring & Diagnostics" page. List records on "Generic DevOps MBeans" tab and use "New Generic DevOps MBean" button from "Page Operations" menu to open the wizard.
Easy upgrade!
Fresh Re-installation!
How to uninstall?
WLSDM offers complete monitoring infrastructure for WebLogic Application Server. monitorWLAdmin is a simple "Plug & Play" standalone application for monitoring WebLogic Admin Server externally. After the WLSDM installation and wizard setup completion, standalone monitorWLAdmin application will appear in runtime WLSDM folder as below content
($DOMAIN_HOME/WLSDM/monitorWLAdmin) Contents:
How to start?
Unix/Linux: nohup ./start_monitorWLAdmin.sh &
How does monitorWLAdmin work?
It monitors WebLogic Admin console periodically. When "Admin Server" goes down or slows down monitorWLAdmin sends alarm notification instantly
Help is available
Post your WLSDM or WebLogic monitoring issues on  Community Portal
Please follow us and get updates. Never miss a post about WebLogic monitoring issues!
Community / Support
Twitter Follow
YouTube Tutorials
LinkedIn Connect
Google+ Circle
Facebook Like
Instagram follow4follow :)
Email Send
v3.1.2:
v3.1.1:
v2.5.2:
v2.4.0:
v2.3.7:
v2.3.5:
v2.3.1:
v2.1.8:
v2.1.7:
v2.1.5:
v2.1.1:
v2.0.0:
v1.2.0:
v1.1.2:
v1.1.0: