| Author |
Message
|
| javagate |
 Posted: Thu Dec 15, 2005 3:29 am Post subject: WebSphere - GUI Panel changes vrs Scripts |
 |
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
For those working with WebSphere I am trying to get an idea which do you think is better making changes in the GUI panes or through a script? I prefer a script others want no part of script technology and want everyone to walk through the GUI panels.
Any thoughts?
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Dec 15, 2005 3:41 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
This will be fun.... 
I think both have their place. If I need to do something quick like define a queue or look at curdepth, I find it much easier and quicker to open a command prompt, go into runmqsc and execute the command. But I'm comfortable in that environment becuase I've been using it since MQ V2.0 came out.
For new user's, there is no doubt that the GUI explorers are useful. I use them for doing more compicated things like defining channels and testing where I need to see the curdepth of a family of queues.
_________________
-wayne |
|
| Back to top |
|
|
| javagate |
| Posted: Thu Dec 15, 2005 3:50 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
Here is the root of the problem....
There are a bunch of variables that are set to vaules that have a version # in it. An example is the DB2 JDBC driver path:
/usr/lpp/db2v7t/db2710
When new versions come in an admin change is requied to change the value. A pain in the neck!
I guess my question might have been how do others manage something like this. I perfer to invest the time in the setup. And fewer changes on install day. We have about 20 servers.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 15, 2005 4:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can we be a little more specific?
When you say "WebSphere", do you mean "the entire line of products that have the WebSphere brand"? I guess not, because not all of them have scripting options for all features or GUI options for all features. (Portal, in particular).
Or do you mean the family of WebSphere Application Servers, including WBISF and Process Choreographer?
I generally prefer to use the WAS admin console, but mainly because I just haven't taken the time to learn wsadmin scripting. If we get to the point with our deployments where we do not have to coordinate multiple activities across multiple people in order to do a single deployment... then I might look into hacking at it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| javagate |
| Posted: Thu Dec 15, 2005 4:03 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
I am talking about WebSphere Application Server.
I wanted to know how people manage the variables, do they put product version numbers in the value.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 15, 2005 4:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Of course, the typical way this is handled in unix in general (for Perl, specifically that I know of), is to create a symlink that is not version specific that points to the current version instance.
But even that requires an admin change when the version changes. Not in your console, but by the unix admin who did the installation of the newest version.
I think most people don't upgrade their JDBC driver paths that frequently that it makes a big deal of work for them to change the env variable. And it's a known change, and usually servers have to be restarted when the jdbc driver version changes anyway. So the impact of having to change the variable is low.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 15, 2005 4:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Now if you run WAS directly on top of zOS I do not know how you would give it something like a symbolic link. (no zlinux...)
In the Unix world it is common practice to put the new version in a directory like:
prod_ver#
and when the time comes just move the symlink
rm prod
ln -s prod_ver# prod (sometimes ln -s /abspath/prod_ver# prod)
Apps then use the symlink...
Enjoy  |
|
| Back to top |
|
|
|
|
