Hi,

Thanks for your kind support.
JMS Servers resources added successfully.

Hello,

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

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…

@jeba

Hi Jeba,

Also, check “store data” for back-end monitorings. It may generate too large data sets. especially if the “WebLogic Diagnostic Volume” set high for the related managed server.

Capture4.PNG

I enabled the store option for all of our datasources. So, in total there were around 75. Would this be an issue?

75 data sources cost you avg ~30 Mb per day (it depends on your metric instance count). If you have enough disk space it is not an issue.

How can I control the retention period for these metrics collections?

You can change the archive date range from the “Configuration> WLSDM System Settings” page. Archive module purges your data beyond the given date range. But do not reduce the date range instantly. You have too much data on your database and it may cause too much memory consumption. Prefer gradual reduction (like 3 or 5 days).

“system.archive.metric.data.range”

Capture2.PNG

Regards.

ok, thanks

@Stephen That’s great, looking forward to hearing from your “Custom Action” scripts 🙂

@takika said in Oracle JDK 11 vs WLSDM FlightRecorder:

@fevzi-korkutata-wlsdmteam
I just checked the README, but didn’t find anything about Java 11 and FlightRecorder. There is no JAVA_OPTIONS for Java 11.

Hi Takika,
You can find the JDK 11 update in Readme as stated in below screen capture. Cloud you please give a try again and let me know the latest status about your case. You should not get any error anymore with the v4.1.1 also please tell me your exact WLSDM for WebLogic version.

Latest Readme: https://wlsdm.com/docs/README

c86d391b-2889-4c61-8cbf-844d3804edf1-image.png

@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

Oh, that’s lovely, thank you very much!
Have installed 3.9.1 in out sandbox environment after receiving the newsletter last week, will give this a shot right away!

Thanks a lot !

It is working fine now after removing the boot.properties file.

Regards,

@whching said:

Hi @wlsdmsupport

I am just start looking at WLSDM, what is the difference of having one agent per cluster against one agent per managed server?

BTW, where I could find the resource overhead when WLSDM is used on managed servers? say, how much more heap memory it will use and how about any extra I/O it would introduced?
Thanks

Regards,
Rock

Hi,

If you have two member cluster and these members are on different machine then install two agent. If you have 4(four) member cluster and these members on two machine (two managed server per machine). Then install two agent (same with previous). Much agent, much traffic. Same behavior, same machine… Then go for one agent.

More information is available on README: http://www.wlsdm.com/docs/README#IV.Installation

WLSDM runs on AdminServer and you should not install any application on WebLogic admin console. So, it’s run-time console, should not affect your domain. WLSDM’s AdminServer overhead is negligible; one of the least overhead in the market; because we are not injecting any code to run-time classes. Maximum overhead for the managed server (considering backend monitoring is open) is about 3%-4%.

You had better, test on your current domain; because your domain is extra ordinary and you will see that WLSDM would be one of the best solution for this domain and its infrastructure.

Regards…

@jeba

Hi Jeba,

WLSDM does not have the feature for your requirement which is giving a threshold for the specific IP/hostname.

But it could be a nice feature, we will evaluate this feature for the next releases.

Regards.

Hi @jorfergo,

The current WLSDM release doesn’t support this feature.

Please add your exact requirement on this topic: http://community.wlsdm.com/topic/18/wlsdm-new-features-requests

We will implement in the next release if our analyze team approve.

Regards.

@Ramanpreet_Singh

Yes, everthing was just fine. If you want to remove buffer on WebLogic decrease the buffer size to “0” on “WebLogic console > $Server_Name > Logging > HTTP Logs > Advanced > Buffer Size” section.

Regards…

@Ramanpreet_Singh Hi,

Export/Import feature is used for WLSDM settings. Nothing related about WebLogic configuration.

i.e. If you configured SMTP settings on WLSDM; these values will come from export file or DevOps Mbeans and any other WLSDM configuration you have done.

Kind Regards…

@Ramanpreet_Singh yes you can customize the subject.

@Punit-Porwal said:

Hi Team,

I have successfully configured WLSDM into my domain, but due to some reason my system IP got changed, I have updated my new IP in all my weblogic domain files and is working as expected, but when I am launching WLSDM from console its redirecting me to my domain login screen everytime. I tried undeploying and deploying WLSDM as well but no luck, is their any file where I need to update my IP for WLSDM or were I am missing anything please help.

Thanks

Hi Punit,
WLSDM works native just as WebLogic and there’s nothing to configure about IP addresses of WebLogic unless you did not setup boot.properties. We’ve tested your case and everything worked fine as expected.
If you’re still facing the same problem, could you please upload wlsdm.log which is located under “$WEBLOGIC_DOMAIN_HOME\WLSDM\logs” path.
Waiting your update about last status.
Thanks in advance and keep follow us 🙂
Regards…

Thanks for sharing this detailed analysis. I ran into a similar JMX class conflict on WebLogic 12.2.1.4 while testing monitoring agents. It covers some useful background on JVM service initialization issues. Removing -DUseSunHttpHandler=true from the startup args fixed it in my case as well.

@wlsdmadmin

Check this tutorial 🙂 http://community.wlsdm.com/topic/27/new-video-tutorial-how-to-monitor-weblogic-managedserver-jvm-resources

@prakash_2006

It seems incompatible Java version error. Please confirm the correct Java version by following below document?

Download and install the latest JDK 1.8.x compatible with your OS platform

https://wlsdm.com/wl-opc/docs/readme#prerequisites

We are very glad that you have resolved the issue and it was a great pleasure to support you.

Best regards

@wlsdmsupport Hi, I was able to run and configure WLSDM smoothly.
Thank you very much for the excellent and swift work!

@blanchettevdm said in import / export WSLDM configuration:

@fevzi-korkutata-wlsdmteam

Thanks Frevzi! True! a full reset will be a lot easier, although that brings another questions.

When you import configuration from another domain, is it a full overwrite ?

Thanks for your prompt answer…

You’re welcome. Yes, deleting the WLSDM runtime folder (make sure AdminServer is not running) is the easiest and safest method to import WLSDM configurations.

For your second question; yes it is a full overwrite. But remember; when you reset the config, there is nothing to overwrite 🙂

But at least; import is working as; "If same settings exists; update with the new one, if new config available add as new and keep already existing settings.

Finally, We use import feature all the time to facilitate WLSDM wizard completion and setting up a standart WebLogic domain monitoring configurations.

Regards…

Hi,

We found the problem. It was really weird and it’s about replacement. Because, your managed server names contains “IP” string.
It’s fixed and and going to be added to the next version.

Thank you for the bug report.

Regards…

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

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,

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.

Kind regards.

@bibarrav

Hi Bibarrav,

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?

Kind Regards…

Hi,

We have another product named WL-OPC for systems that have many domains and these requests can be made in there.Otherwise, you can define many rules as you want in WL-OPC.

Even there is no need for email, when you using WL-OPC console, you can monitor every notification from all domains in one operation center. More information http://www.wlsdm.com/wl-opc/index

Regards.