| Author |
Message
|
| teal |
 Posted: Wed Mar 02, 2005 7:07 am Post subject: wsadmin JACL with WSAD 5.1 |
 |
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
Hello all,
I have successfully written a few wsadmin JACL's that run great on the actual WebSphere Application Server 5.1.
However I want to run the same scripts for my test env. (WSAD 5.1)
problem is the node on the actual WAS server is CP444 and the server is server1.
but on my wsad config the node is localhost and the server is server1.
Even though I change this to localhost, it continues to throw an exception. I tried the same scripts on a different WAS (changing the node accordingly) it worked perfect also.
So it seems that only with WSAD, I am having this issue.
the lines in the JACL I'm referring to are:
| Code: |
set SVR [$AdminConfig getid /Node:localhost/Server:server1/]
set MsgLSVC [$AdminConfig list MessageListenerService $SVR]
|
error:
| Quote: |
WASX7209I: Connected to process "server1" on node localhost using SOAP connector
; The type of process is: UnManagedProcess
Creating NorthStar1 MessageListenerPort1
WASX7017E: Exception received while running file "setMLP.jacl"; exception inform
ation: com.ibm.websphere.management.exception.ConfigServiceException
java.lang.NullPointerException: java.lang.NullPointerException
|
Last edited by teal on Wed Mar 02, 2005 4:02 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 02, 2005 7:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can't really use the normal administration methods to administer a server defined under WSADs WebSphere Test Environment.
It's not quite a real WAS, from an administration point of view.
You should be able to do everything you want from the Server Configuration screen inside WSAD.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| teal |
| Posted: Wed Mar 02, 2005 7:42 am Post subject: |
|
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
thanks for the reply Jeff.
I found a post at developerworks that is saying:
| Quote: |
basically JACL/wsadmin is not supported with the WSAD TestEnvironment. Out of the box it does NOT work.
There is one single thing you have to do to make it work:
copy the whole folder structure of [WSAD_DIR]\runtimes\[YOUR_WAS_VERSION]\config\templates to [YOUR_WORKSPACE]\servers\[YOUR_SERVER]\templates.
Thats it!
|
but haven't quite gotten it to run yet either.
So you are saying there is no way to run scripts to create my JNDI object(QCF's Qdest's etc) in WSAD 5.1?
all must be entered manually through the wsad Admin console?
thanks again. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 02, 2005 8:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Let me try and be clear.
In WSAD, in the Server perspective, if you double-click your server in the list on the Server Configuration View, it will open up the Server Configuration for your server.
As far as I know, this window is the only place you can properly administer a WTE server.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 02, 2005 11:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Embedded MQ setup can be done through server tab config.
MQ JNDI setup on WSAD is really only done easily through the ADMIN Console.
Now you can look up the created XML file and determine the patterns created. If you have a high number of objects to be created you might be able to create the XML snippet and insert it into the respective resources config file.
DO NOT change the resource file without having taken a backup to fall back to. Do not change the resource file with the app server running.
Enjoy  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 02, 2005 11:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| MQ JNDI setup on WSAD is really only done easily through the ADMIN Console. |
But of course, you have to enable the Admin console IN the Server Config tab FIRST.
I wonder if that is also necessary to get the earlier note about copying templates from {WSAD}.../runtimes.... to {WORKSPACE}.../wte-server-folder.... to work.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| teal |
| Posted: Wed Mar 02, 2005 4:00 pm Post subject: |
|
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
Hey Fellas,
just a note, but I have my wsadmin JACl scripts working perfectly with WSAD 5.1 now.
I just followed the instructions from that previous post I found at developer works and VOILA!
..so now we can automate all the JNDI object creation for my QCF's Qdest's etc for WAS and WSAD without tediuously doing it through the console. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 03, 2005 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
First you said the instructions didn't work, and then you said the instructions did work.
What was different - how did you "fix" it?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| teal |
| Posted: Thu Mar 03, 2005 7:55 am Post subject: |
|
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
well, I said
| Quote: |
but haven't quite gotten it to run yet either.
|
not, the instructions don't work. 
I was basically putting the templates structure down in the server1 directory where I thought the person was actually getting to.
It actually needed to be put the higher level SERVER1.wsc to work
hope this helps other people.
I guess the botton line is you can use wsadmin to automate you configuration in WSAD 5.1 as well as regular WAS, You are not forced to use the admin cosole or wsad serverconfig screen.
cheers! |
|
| Back to top |
|
|
|
|
