File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes BEA/Weblogic and the fly likes Java (JMX) vs WLST Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Java (JMX) vs WLST" Watch "Java (JMX) vs WLST" New topic

Java (JMX) vs WLST

Nitish Kumar Singh

Joined: Aug 16, 2013
Posts: 5

I know that there are two ways to admin weblogic server. One way is by WLST scripts which we write in WLST console. Second way is by JMX which we write in JAVA language.

I know that java language gives more flexibility but still all the scripts present in my companies Weblogic servers are WLST scripts.

Can anyone tell me about all the benefits and advantages I can have if I change them to Java (JMX) code.

One of the Flexibility is that I can implement multithreading and start multiple AdminServer (in multiple domain) at same time.

Nitish Kumar
German Gonzalez-Morris
Ranch Hand

Joined: Nov 16, 2009
Posts: 191

jmx is an api but you need to use wls mbeans so still it is proprietary.

wlst uses jython which generates an overhead maybe this could be an issue (at the end it connects with jmx underneath)

two different flavor that will depend on programmer profile
Nitish Kumar Singh

Joined: Aug 16, 2013
Posts: 5

I can understand that internally WLST calls MBeans. I want to know the advantages if I use JAVA (JMX) code instead of WLST scripts. Oracle has provided two ways, there must be a reason.

1- I am writing a Linux Script and calling WLST script in it.
2- I am writitng JAVA (JMX) code and administrating weblogic.

Which of the two above will have more advantages and why?
German Gonzalez-Morris
Ranch Hand

Joined: Nov 16, 2009
Posts: 191

The reason of WLST is to use a simpler code (language) for the same task.

Java has an exponential learning curve, in the other hand, Python is very straightforward.

WLST is more focused for Administrators than developers.



Peter Rooke
Ranch Hand

Joined: Oct 21, 2004
Posts: 805

I prefer WLST (maybe called from within an ANT script) - simple reason is that its a higher level tool.
Of course if you need to do something special then JMX would be the way to go. Never needed to do so myself...

Regards Pete
Abhinav Sonkar

Joined: Nov 20, 2013
Posts: 16
It depends on what you are creating. For e.g., if you are creating a web app in JSP/Servlets (say for monitoring a domain), JMX is the obvious choice. Just include the wlfullclient.jar in the classpath and you are good to go.

On the other hand, if all you need is to quickly automate administration stuff like deploying apps, monitoring server health, generating alerts, stop/start servers etc then you should use WLST as it is quick and simple.

Performance wise there is hardly any difference in overhead. It would rarely be a factor in deciding between the two.
I agree. Here's the link:
subject: Java (JMX) vs WLST