I can't monitor weblogic cause fips enabled

Hi everyone

I need help to monitor weblogic on 3 linux server.

Already agent installed on linux servers and work fine but as I assign "oracle weblogic (jmx) 12.x and higher " template to nodes it tell me fips mode enabled so jmx monitoring is disabled.

Can anyone tell me how can I monitor weblogic or any step by step document?

My orion version is 2020.2.6

And fips also disabled on os but I think it is enabled on orion so monitoring weblogic is impossible

Find more posts tagged with

sam

weblogic

fips

solarwinds

Accepted answers

All comments

saeron

Is there any one who can help me?

christopher.t.jones123

@saeron, unfortunately i don't have any experience monitoring weblogic, so I dont think i can be much help from that perspective. Because FIPS is enabled for your Orion platform, JMX monitoring will be disabled within SAM, you're only options are to investigate monitoring weblogic without the use of JMX, or disable FIPS for the Orion suite (i do not recommend, FIPS is something you have to go out of your way to enable so likely not done by accident) so you can regain JMX monitoring capabilities

saeron

Thanks for reply but as you read I have no any option but using jmx monitoring and I am wondering why solarwinds still have jmx option when fips doesn't let him.

Also I can't find how to diable fips on orion. Even I don't remember that when I enable it.

So still need help

christopher.t.jones123

@saeron, i cant speak to why JMX monitoring is disabled for FIPS but here is an article on disabling FIPS

ecklerwr1

Kinda seems like a catch-22.

Bill

HerrDoktor

There is a whole KB on the oracle website that deals with monitoring weblogic https://docs.oracle.com/middleware/1212/wls/INTRO/monitoring.htm#INTRO291

if you can’t use JMX monitoring due to FIPS restrictions, there seems to be a bunch of different ways to do this.

The referenced document even lists SNMP as an option.

probably worth checking those options

saeron

All of my word is now solarwinds should remove jmx monitoring from it's component list if it is so dangerous based on fips and if it's not so makes re-enabling this component so much easier.

Still I can't disable this shi...y fips

saeron

Also as you read inside link that you sent me most of parameters read from api so the one and only way is using jmx for calling API.

So problem is still on

saeron

@HerrDoktor

@christopher.t.jones123

@shuth

@ecklerwr1

Dear friends

Right now there is no way to enable jmx monitoring or disable fips on last version of solarwinds based on articles that you sent here.

Even I try it on a fresh installed test server.

Please understand it that without jmx now monitoring of java based applications ars not possible. And this is a shi....y situation.

I think someone must talk with central team directly cause as I asked from my colleagues they made a ticket but same answer return from solarwinds team. And they stop answering.

Now I am sure also they have no idea.

The funny things is this situation is because of log4j vulnerability but right now may other monitoring solutions even fips compatibles have not this issue.

Even weblogic default monitoring solutions update it's libraries that impacted with log4j but it is wonder for me why solarwinds instead of patching impacted libraries just disabled the feature!!!!!!!

It is unbelievable.

This situation is like cutting off your hand to stop taking poison mushrooms. Bro it is easy just know it is poisonous so know normal ones and pick them why you cut your hand?!!!!!!!!!

HerrDoktor

Have you taken any steps into disabling FIPS Compliancy if FIPS is not something that is required by your organization? You just mentioned "It's like a one-way road" ... did you even bother starting the mentioned FIPS tool? It allows to enable and disable.

ecklerwr1

Seems worth trying to me!