Hi @stevediaz
Could you please check SOA datasource that WLSDM created? Is that datasource is active and working?

@lvzhongx said in How Jboss EAP MDB can connect to Weblogic queue:

I have a MDB deployed in Jboss EAP 7.4 and the destination is Weblogic queue. (Consume the messages in Weblogic queue) . I need to install weblogic JMS resource adapter , I would like to know if we have any reference guide to install this Weblogic JMS resource adapter in Jboss EAP , Thanks.

To connect JBoss EAP MDB to a WebLogic queue; deploy the WebLogic JMS resource adapter RAR in JBoss and configure it in standalone.xml. Check the JBoss EAP documentation for detailed steps on resource adapter configuration & JMS integration; or visit the JBoss Community for more support.

@traceyrawlings said in Log monitoring configurations are blocked:

Log monitoring are blocked but there are no files with .out0, or .log0
in the directory.

I see wlsdm.agent.DEServer1.log_.lck
and i see older log files wlsdm.agent.DEServer1.log
and i see older log files wlsdm.agent.DEServer1.log.1

Which files are we supposed to remove?

Hi,
These notifications are based on WLDF queries for your WebLogic server logs. If querying WebLogic logs through WLDF tooks long time, this notification visible to WebLogic administrators.
You need to check WebLogic logs not WLSDM logs. Keeping rotated WebLogic (*.out0, *.log0) logs cleaned and tidy would improve your WebLogic domain performance.

@arturrgdietrich said in Weblogic 14 option wlsdm.agent.extendedBackendMonitoringEnabled=true dont start server:

Weblogic 14:
if “-Dwlsdm.agent.extendedBackendMonitoringEnabled=true” option is included in start options from managed server it does not start. Removing this option it stars correctly!

ERROR:
.
.
.
<May 3, 2024 11:33:00 AM ART> <Unable to connect to the Administration Server. Waiting 5 second(s)
to retry (attempt number 1 of 3).>
<May 3, 2024 11:33:05 AM ART> <Unable to connect to the Administration Server. Waiting 5 second(s)
to retry (attempt number 2 of 3).>
.
.
.

Is there any solution for this ? What benefit will I lose if I don’t use this option?

If -DUseSunHttpHandler=true parameter is added to your WebLogic managed server probably you are having below known issue. Please consider to apply below solution to your case.

Known Issue - Conflict Between DUseSunHttpHandler and Dwlsdm.agent.extendedBackendMonitoringEnabled: When both -DUseSunHttpHandler=true and -Dwlsdm.agent.extendedBackendMonitoringEnabled=true are added to a WebLogic ManagedServer instances simultaneously, an error occurs: "java.lang.NoClassDefFoundError: com/vopm/collector/HTTPData" To resolve this issue, remove one of the conflicting parameters. Consider removing "-DUseSunHttpHandler=true" argument for monitoring remote HTTP(s) outbound connections if it is technically possible

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

cb9db498-96b6-4248-a5f1-882f9e42ad7d-image.png

@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

@jbrinker We have released v4.1.1. Could you please give a try with this version and let us know the result. https://wlsdm.com/download

@alan_aguinaga said in Console Admin Server is being down after install wlsdm:

It is pretty hard to understand why my AdminServer console went down before I installed this. I am searching in logs and just getting info and warning levels.

This deployment is shutting down my console. I just see some thread concurrence here.

Have you ever see this?

Hi Alan,
We were unable to hear you about our data requests. We had an experience like this before; “One of our client was deployed wlsdm.war as a web application by using Oracle WebLogic console instead of putting file to $DOMAIN_HOME/console-ext folder.” It might be also your case.
I am adding this information for any other person who might have face this.
Regards…

@fevzi-korkutata-wlsdmteam Thanks much Fevzi. Bypassing loadbalancer url, I’m able to complete the configuration.

Regards,
T N Prasad

@cody-west Glad to hear that ! 🤗

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

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

@can-sahin-wlsdmteam

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

@haydar-seyfi-wlsdmteam Thanks for the info

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