@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

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 Can,

This error is the wrong path for java in setenv.properties file configuration.
Because in Linux alternative link using for java path.
If you are using this command in terminal. “echo $JAVA_HOME” then it gives a true java path.
ex: echo $JAVA_HOME --> /usr/lib/java/jdk1.8.0_201
In setenv.properties file JAVA_HOME line change with your full java path.

Then you can start WL-OPC.

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…

@maas
Hi,
By default WLSDM folder initialize in weblogic $DOMAIN_HOME folder. If you want to move this folder to another path just create soft link.

1- Shutdown WebLogic admin server properly
2- Move $DOMAIN_HOME/WLSDM folder to /path/to/folder/WLSDM
3- Create link under $DOMAIN_HOME folder.
Linux: ln -s /path/to/folder/WLSDM WLSDM