Weblogic WSLT,Websphere wsadmin, DB2 CLP

Today I compared the design of WSLT (from BEA) as a scripting solution (written in Jython) for WebLogic admin tasks, Websphere ‘s wsadmin and DB2 CLP.

For the last couple of days, I implemented a mini CLP to admin some Websphere DynaCache. It is simple and quite extensible. I followed the DB2 CLP design.

This brings me an interesting thought on this issue.
Which way is better?

DB2 CLP way or Jython/Jacl way (which used in wsadmin and WSLT)?

#1: design CLP commands only in a list of string seperated by white space characters and let
platform shell to take care of flow control, variable,name space if any.

#2: a full scripting language such as WebSphere ‘s wsadmin and Weblogic’s WSLT. It provides flow control, variable, etc. That’s why Jacl or Jython has been directly exposed to the end user (i.e. administrator).

Personally, i think #1 is better in that after a while, I don’t need to look at the command reference any more. If I want to control it, always go back to my favorite shell. Secondly, for anyone who don’t know Tcl or Jython (as most admin from Perl or Shell) syntax well, to look up the reference is pain in the butt. Overall #1 is a lot more simple and stupid to use, i.e. it KISSed.

Victor

Advertisements
This entry was posted in weblogic. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s