@wlcommunityusers

Hi,

Please install WLSDM again by following the steps below.

1. Shutdown AdminServer
2. Delete WLSDM Runtime Folder (If background information is not important; in this case the past will delete)
3. AdminServer start
4. Complete WLSDM configuration wizard by importing export configurations.

ImportConfiguration.jpg

Re-installation procedure also available in here : https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Kind Regards.
WLSDM Support
http://www.wlsdm.com

@wlcommunityusers

Hi,

Default interval is 120 seconds and you can change this value in “system.monitoring.genericmbean.harvest.frequency” property as below.

PS: If you change this value, it will effect all “Custom MBeans”.

6.png

Regards.

@wlcommunityusers

Hi,

Finally, I found the solution.
I changed java.security in WL-OPC disabling jdk.tls.disabledAlgorithms like this:

b0d4cae9-48f2-4ce0-9bf1-0afdaf93dcde-image.png

And then I removed all the arguments in JAVA_OPTIONS to default OPC installation.

I restarted OPC and I could add the domains without any problem.

Regards.

@can-sahin-wlsdmteam

Hi,

Could you try to add below parameter in AdminServer JAVA_OPTIONS please?

This parameter is purging WLSDM DB every AdminServer startup. Try this then let us know the result.

-Dwlsdm.system.dbShrinkOnStartup=true

Kind Regards.
WLSDM Support
http://www.wlsdm.com

@wlcommunityusers said in WLSDM Config- New managed server:

Hi,

We have added a new managed server to the domain. We want to configure alerts(Datasource, Backend Monitoring etc) like we configured for previous managed server. Please suggest.

Current config:
AdminServer
ManegedServer1
ManegedServer2

Regards.

Hi,

You can include new server to current configurations in “Response Time” monitoring but you need to add new back-end systems configuration for new server.

Please check below screen captures.

Response times configuration for newServer:

Go to “Configurations > Monitoring & Diagnostics” in WLSDM menu Follow below navigation and click “edit” button Select ManegedServer2 then save

reponse1.jpg

response2.jpg

Backend configuration for newServer:

Go to “Configurations > Monitoring & Diagnostics” in WLSDM menu Follow below navigation; click “page operations” button then select “New Back-end Systems Monitoring” Create new back-end configurations, add events ManegedServer2 then save

backend1.jpg

backend2.jpg

Kind Regards.

WLSDM Support
http://www.wlsdm.com

Hi,

We have resolved the DB purge issue in version 3.9.2. Which version is this WLSDM domain?

You have two options;

First is to upgrade WLSDM v3.9.2. (Keep in mind while you are opening the AdminServer; the purge operation would start automatically and it can took a lot time because of your db size)
https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Second is fresh re-installation which is explained as below steps. (Remember to take current configurations; if you have license issue we have already sent the trial license to skip config wizard)

Export WLSDM Configuration; follow the steps below

wlsdm_configuration.jpg

Shutdown AdminServer Delete WLSDM Runtime Folder (If background information is not important; in this case the past will delete) AdminServer start Complete WLSDM configuration wizard by importing export configurations

wizard_configuration.jpg

Re-installation procedure also available in here :
https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Kind Regards.

WLSDM Support
http://www.wlsdm.com

@wlcommunityusers

Hi,

Please follow screenshot’s steps and set the threshold as below.
–> WLSDM Dashboard Menu > Monitoring & Diagnostics > Back-end Systems tab

fileread2.jpg

fileread3.jpg

Kind Regards…

WLSDM Support
https://community.wlsdm.com

@wlcommunityusers

Hi,

WLSDM cron takes several minutes to return cycle. Reduce some minutes, Example 1430 rather then 1440.

Kind Regards…

WLSDM Support
https://community.wlsdm.com

Hi,

Did you upgrade the domain? Your latest screenshot says your WLSDM v3.7.2 but WL-OPC says WLSDM v3.9.2.

You can follow the below provided solution.

Check two way access between WL-OPC and WLSDM
WLSDMHostname$ telnet OPCHostname 8080
WL-OPCHostname$ telnet WLSDMHostname 7001 Open problematic domain’s wlsdm_agent.jar with winrar and check WLSDM-version in “META-INF> MANIFEST.MF” file. If there is old version just replace wlsdm_agent.jar with the new version in $DOMAIN_HOME\wlsdm_agent\ Unregister problematic WLSDM domain from WL-OPC Complete WLSDM installation wizard without WL-OPC registration Register WLSDM domain to WL-OPC in WL-OPC “Administration> WL Domain” page. If the problem is not resolved please send us $WL-OPC_HOME\bin\WLOPC\logs with the zip file

Kind regards.

Hi,

On the other hand, I’m trying to configure a script to be executed once I have a stuck thread alarm.
Is it possible to do that?

Yes, you can set alarm to scripts. Please check below tutorials.
OracleDB ACTIVE/INACTIVE Sessions monitoring on WebLogic: https://youtu.be/XjBz6zlKstM
Generic DevOps Disk Usage MBean Tutorial: https://youtu.be/OYkPEpxF66M

Kind Regards

Hi,

WLSDM fresh installation steps are below:

Replace the wlsdm_agent.jar file with the new release and keep wlsdm_agent.jar JVM arguments. *($JAVA_OPTIONS) Shutdown Administration Server Delete $DOMAIN_HOME/WLSDM runtime folder Replace wlsdm.war file with the new release to WebLogic domain’s console-ext folder Start WebLogic Administration Server and restart the Managed Server(s) which wlsdm_agent.jar installed That’s all! WLSDM will be reinstalled after restart processes Complete WLSDM configuration wizard

WLSDM wizard is going to be visible with the re-installation process

Reference: https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Kind regards…

Hi,

Could you check JVM Parameters for WLSDM? You can take the below page as a reference.

https://wlsdm.com/docs/README#VI.Installation

JVM Parameters for backend configurations:

jvmparameter.jpg

Kind Regards.

Hi,

SOA default dashboards are contains complete SOA monitoring and they are sufficient for monitoring SOA performance.

You can check https://medium.com/wlsdmforweblogic WLSDM Medium blog posts by WLSDM team and customer experiences.

You create new Devops MBean and new Dashbaord in WLSDM as below screnshots.

Also please check suggested blog posts:

https://medium.com/wlsdmforweblogic/how-to-create-server-machine-disk-usage-dashboard-and-trigger-delete-logs-devops-action-a267f439c68
https://medium.com/wlsdmforweblogic/how-to-create-a-custom-mbean-from-an-sql-query-in-weblogic-server-using-wlsdm-generic-devops-b978acb22401
https://medium.com/wlsdmforweblogic/advanced-weblogic-monitoring-develop-jmx-mbeans-and-automate-with-wlsdm-metric-actions-73580ca73782

• How to create new DevOps MBean in WLSDM

genericdevopsmbean.jpg

• How to create custom dashboard and create

create.jpg

Regards.

Hi,

Thanks, Incident: Clear.

Incident.png

Regards.

Hi,

You can change the JFR repository directory using the following JVM option:
WLSDM must delete those temp files which is older than two days (48 hours).

-XX:FlightRecorderOptions=repository=WLSDM/temp/JFR ( see: https://wlsdm.com/docs/#VI.Installation )

If you choose not to define (or remove) this JVM option, by default the files will be stored under the operating system temporary directory.

For more information see: https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
repository.png

Also, jfr files are static profiling files, not library files. You can delete them safely even runtime.

For the second question: You can achieve that using the “Downtime” feature:

1 – Go to WLSDM console / “Monitoring & Diagnostics” page.

schedule.png

2 – Open the page operations and click the “New Scheduled Job / Downtime”
newschedule.png

3 – Configure the downtime and click save.

At this point, you have two action option:
1 – Stop all notifications but keep monitoring
2 – Stop all monitoring

action.png

scheduletime.png

Regards.

Hi,

You can follow WLSDM installation instructions in https://wlsdm.com/docs/#IV.Installation page.

There are notes as below for installation:

I. Known Issue: After the complete WLSDM installation if the “Smart Dashboards > JVM System Resources” page is not working well and does not show the metric values properly then add “-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder” JVM argument to the relevant Managed Server(s) and restart the server(s).
II. Do not install agents for whole servers. same cluster or same machine not needed WLSDM agent (as below screenshot).
III. Care “with Nodemanager” and “without Nodemanager” parameter step in wlsdm installation document then use one of them which are you using.

a2.jpg

Regards.

Hi,

It looks like SMTP Server that you are using requires authentication.
535 Authentication required com.sun.mail.smtp.SMTPSendFailedException: 535 Authentication required

Please make sure the SMTP username and password are set on the WLSDM.

smtp1.png

After that, you can check the setting by using the “Test Email Settings” button under the page operations dropdown menu.

smtp2.png

smtp3.png

smtp4.png

Regards.

Hi,

OPC default port is 8080, When you need to register domain to OPC first of all; check firewall rules for below ports with telnet.

OPC and agent both are communicating each other you need mutual firewall request.

From: ${WLSDM_AGENT’S_IP}
To: ${OPC_SERVER’S_IP:8080}

From: ${OPC_SERVER’S_IP}
To: ${WLSDM_AGENT’S_IP:WEBLOGIC_ADMIN_PORT}

Regards…

Hi,

Sometimes WebLogic blocks the direct access to the Java Native MBean Server from inside it for various reasons.
And that affects some modules functionality.

Please add the following startup argument to your managed server.

İf it does not solve the problem, please zip and send the “wlsdm.log” file to us for the detailed examination.
${DOMAIN_HOME}/WLSDM/logs/wlsdm.log

agent4.png

https://wlsdm.com/docs/#IV.Installation

Regards.

Hi,

This bug has fixed in v3.9.1 WLSDM version.

Regards.

Hi,

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.

https://medium.com/wlsdmforweblogic/how-to-create-server-machine-disk-usage-dashboard-and-trigger-delete-logs-devops-action-a267f439c68

Kind Regards…

Yup. It work’s. Thanks.

Hello,

When we skip the monitoring of DataSource and JMS server, setup finishes successfull.

Regards.

Hi,

Email alert’s default sender value is “[email protected]”.

You can edit sender(from) as below.

Regards.

1.Go to “Configuration > WLSDM System Settings” in WLSDM menu.
menu.jpg

2.Be sure you are in “mail.account” tab then edit “mail.account.smtp.username” property.
sender.jpg

Set property value in modal window then save.
111111.jpg

Hi,

You can select any range by using date field. But the maximum backward range is the WLSDM monitoring start time.

Kind regards.

Hi,

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.

Kind Regards…

Log viewer text filter:
1.png

File Explorer:
2.png

Hi,

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.

Kind regards.

WLSDM: Configuration > WLSDM System Settings > system.archive
77.jpg

WL-OPC: Administration > System Settings > Notification
88.jpg

Hi,

Non-adminstrator users not allowed for administrative operations by default as below screenshots.

Metric configuration for monitor user:
2..png

Metric configuration for adminstrator user:

3..png

File explorer for monitor user:

4..png

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.
56.jpg

Hi,
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?
Regards…

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.

Regards…