@salman said in Installation of WLSDM on Saperate Server:

We do not want to install WL-SDM on same server where Oracle Weblogic Is installed, is possible to install WLSDM on separate server?. It will be better not only w.r.t security prospective but also because monitoring Weblogic from outside the Weblogic server is more beneficial.

Hi,
WLSDM installation and montoring is very simple and works like native WebLogic console extension. If you want to monitor your domains from outside the WebLogic admin server we have another standalone solution which is WL-OPC ( https://wlsdm.com/wl-opc/ ) This product is the central WLSDM Operation Center product.
Hope this would help…

@wlcommunityusers
Hi,
We are glad that your problem has been solved for WLSDM installation. If you encounter any other problems, you can send an e-mail to our WLSDM Support team.

Kind regards.

Hi @wlcommunityusers,

You can change your mail configuration by following the steps below.

Go to WLSDM > Configuration > WLSDM System Settings > mail.account

feb9c61c-3584-4463-9119-2be0f0637fc5-image.png

Go to WLSDM > Configuration > WLSDM System Settings > mail.to

a1fd66ec-f3c3-4fd8-ad9b-10b7373183cb-image.png

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

Best regards

By default the JNDI resource is controlled by the Group: everyone policy and therefore anyone can access the resource using any method such as search or list. You need to make this authorization for WSDM. You can easily solve this problem by following the steps below:

Click on the managed server in the “RUNNING” state on WebLogic Consol. Click on the “View JNDI Tree” link just below the Configuration --> General tab.
b7ac04ff-f87d-4100-9701-a81cda39e599-image.png Switch to Security --> Policies tab from the “JNDI Tree Structure” page. Select “ALL” from the “Methods” drop-down list and click the “Add Conditions” button under the “Policy Conditions” heading.
bd632ff2-d19b-4449-9cdb-cfe46a10aeba-image.png Select “Group” from the “Predicate List” drop-down list. Click “Next”. Type everyone in the Group Argument Name: Textbox and click “Add” button.
c098eb25-f8ca-46c9-b7f9-ad615795a666-image.png Click Finish.

After the settings, Group : everyone will appear under Policy Conditions. Repeat these settings for each Managed Server where WLSDM Arguments are entered and restart all managed servers sequentially. Restart the Admin Server last. You will see that the problem is solved.

3412ed1a-f568-4ad8-8af4-6c25d57ccea1-image.png

98df401b-018c-4c00-ade5-4e989ce7ae5b-image.png

Best regards

@hedmondjohn

Hi Hedmond,

You can complete the WLSDM wizard by applying the solution below for the error you receive.

Solution:

WebLogic AdminServer port use which is pointed in below screen capture.

7ca7a3fd-932d-4302-96a7-f9274116909c-image.png

• Go to AdminServer > Protocols > General and increase the “Maximum Message Size” to “100000000”.

776232d7-7fda-4e92-bf70-3a854e221fc2-image.png

• Then click the HTTP section and make sure “Max Post Size” is “-1”.

e05ee5a3-9dbd-4d8e-9e8d-97df6562668c-image.png

Finally, activate your changes, restart the AdminServer and try to complete WLSDM Installation Wizard again.

Hello @Takika,
We are working on reproducing the issue. We will contact you as soon as possible.

Best Regards

@jonatanrocha

@jonatanrocha said in Monitoramento via API:

Gostaria de receber sugestões de como configurar e integrar o monitoramento do weblogic via api no zabbix.

Hi,
Please post in English. We can use Google Translate for this but we are preferring you do it instead 🙂
Regards…

@alan_aguinaga

Hi,
Could you please put wlsdm.log and WebLogic admin console log here. Without log we cannot predict what happened.
Regards…

@can-sahin-wlsdmteam

I was confused with console-ext folder before … issue resolved. Thank you very much!

@haydar-seyfi-wlsdmteam Thanks for the info

@ctuncel said in WLDSM Server resource dashboard:

Merhaba
OPC üzerindeki dashboard’larda, sunucuların fiziksel kaynaklarının güncel statülerini ve sağlık durumlarını görebilmek için zengileştirilmesi diğer monitoring uygulamaları ile hibrit kullanımın önüne geçerek, tek ekrandan sağlık durum takibinin yapılabilmesini sağlayacaktır.
Fiziksel sunucunun cpu, memory, swap, disk iops, nw I/O gibi kaynakların durumu host bazında izlenebilmeli, bunlar liste yada grafik şeklinde gruplanabilmesi MW yöneticileri için ilk arıza teşhisi için hızlandırıcı olacaktır.

Merhaba Cemal Bey,

OPC genel anlamda verinin tutulduğu değil de gelen alarmların ve canlı health’in tutulduğu uygulama olarak konumlandırmıştık. Fakat versiyon 2.0 ile beraber bu durumu değiştirme kararı aldık. Yeni versiyon’da veritabanı olarak MySQL ve Oracle DB seçenekleri ile daha fazla veriyi tutma imkanımız olacak.

Bu doğrultuda sunucu kaynakları için de last snapshot şeklinde bir dashboard’imiz olacak.

Öneri ve ilginiz için teşekkürler. Preview buraya ekliyor olacağız.

Bilgilerinize…

Hi Esnutd,

You can request evaluation license if you fill the below form correctly.

https://wlsdm.com/request-evaluation-key

@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

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

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

@djviolli said in LDAP Configuration Access:

Problem solved by the support team, due to using the OUD for access, a base version was made!
I congratulate the WLSDM team for their attention and timely solution.

Thank you @djviolli very supportive and valuable feedback from you to the community. 👏

Hi @sergei

Thank you for reaching out to us. Yes, WLSDM is totally free and almost fully featured for the developers. And it is called developer edition.

Could you please check your domain again and let me know is “Change Center” section is available or not? Please take below screen capture as reference.

fdf2d6f6-503b-4b58-a971-8948614095c6-image.png

If it is available on your domain; it is still production mode and you can not use free developer edition. Please check your domain and let us know the result?

Also, you still want a license you can contribute to us and win a free enterprise license; please follow this page for the submission: https://wlsdm.com/get-free-enterprise-license

Fevzi Korkutata

@wlcommunityusers

Hi,

We fixed this issue in v3.9.2. If you upgrade the WLSDM domain v3.7.2 to v3.9.2 you will not face this issue any more.

Kind Regards,

WLSDM Support Team
https://community.wlsdm.com

@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

@can-sahin-wlsdmteam

Hi,

You can disable alarms and monitoring of shutdown servers as below.

d6a701da-73c5-4994-945f-aecdca7489e6-image.png

Kind Regards,

WLSDM Support Team
https://community.wlsdm.com

Hi,

Try to hard restart OPC by using opc command. After restarting OPC the problem should have resolved? Could you please confirm the result?

We’ve created an issue to solve the problem permanently.

@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