2024/12/24
After accepting the license agreement, WLSDM offers two options:
If you do not have a valid WLSDM license key, choose this option for the evaluation. After 30 days WLSDM will ask for a valid license.
If you have a valid WLSDM license key, choose this option and enter the appropriate license information. The license key will be checked offline and activated instantly if it is a valid key.
In step 3, the SMTP settings and email recipients can be configured easily. These settings can be left blank, but it is highly recommended to configure these settings successfully.
By setting up email configuration WLSDM will send notifications and HTML email alerts.
Use "Send" button for testing SMTP settings. If you configured the SMTP settings successfully, you will get a test email as below.
If any error occurs then check wlsdm.log file which is located under $WL_DOMAIN_HOME/WLSDM/logs folder.
WLSDM reads WebLogic domain and lists the domain resources to configure monitoring settings.
There are four main groups which WLSDM offers to monitor: Servers, Deployments, Data Sources and JMS
Select domain resources to monitor. All important domain resources are selected by default. These can be unselected in this step.
This is most important step and highly recommended to complete carefully. WLSDM offers important WebLogic MBean metrics to monitor according to domain’s available resources.
1. Check metric values: | All available metrics are grouped by WebLogic servers. All the sub instance threshold values can be set on main metric record. Click on threshold editbox and see current instance values. |
2. Set threshold values: | Give reasonable threshold values according to the WebLogic domain characteristic. |
3. Enable/Disable alarm: | It can be done by using ON/OFF button on “Alarm” column. |
4. Delete metric instance: | It is also possible to remove the metric instance. |
5. Reset values and configurations: | All the configurations, values and deletion processes can be reset by clicking on refresh icons on metric group tabs. |
It is unable to access to the wizard page after completing WLSDM monitoring wizard steps. But all the configurations and values can be updated on Configuration/Metrics and Dashboard pages.
MBean node type : weblogic.management.runtime.ThreadPoolRuntimeMBean
metric : ActiveExecuteThreads
instance : com.bea:Name=ThreadPoolRuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=ThreadPoolRuntime
MBean node type : weblogic.management.runtime.ThreadPoolRuntimeMBean
metric : HoggingThreadCount
instance : com.bea:Name=ThreadPoolRuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=ThreadPoolRuntime
MBean node type : weblogic.management.runtime.ThreadPoolRuntimeMBean
metric : PendingUserRequestCount
instance : com.bea:Name=ThreadPoolRuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=ThreadPoolRuntime
MBean node type : weblogic.management.runtime.ServerRuntimeMBean
metric : OpenSocketsCurrentCount
instance : com.bea:Name=WEBLOGIC_SERVER_NAME,Type=ServerRuntime
MBean node type : weblogic.management.runtime.JRockitRuntimeMBean
metric : HeapFreePercent
instance : com.bea:Name=WEBLOGIC_SERVER_NAME,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JRockitRuntime
MBean node type : weblogic.management.runtime.JRockitRuntimeMBean
metric : JvmProcessorLoad
instance : com.bea:Name=WEBLOGIC_SERVER_NAME,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JRockitRuntime
MBean node type : weblogic.management.runtime.JVMRuntimeMBean
metric : HeapFreePercent
instance : com.bea:Name=WEBLOGIC_SERVER_NAME,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JVMRuntime
MBean node type : weblogic.management.runtime.JVMRuntimeMBean
metric : JvmProcessorLoad
instance : com.bea:Name=WEBLOGIC_SERVER_NAME,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JVMRuntime
MBean node type : weblogic.management.runtime.JTARuntimeMBean
metric : ActiveTransactionsTotalCount
instance : com.bea:Name=JTARuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JTARuntime
MBean node type : weblogic.management.runtime.ThreadPoolRuntimeMBean
metric : Throughput
instance : com.bea:Name=ThreadPoolRuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=ThreadPoolRuntime
MBean node type : weblogic.management.runtime.ThreadPoolRuntimeMBean
metric : Throughput
instance : com.bea:Name=ThreadPoolRuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=ThreadPoolRuntime
WebLogic WLDF
MBean node type : weblogic.management.runtime.JTARuntimeMBean
metric : TransactionRolledBackTotalCount
instance : com.bea:Name=JTARuntime,ServerRuntime=WEBLOGIC_SERVER_NAME,Type=JTARuntime