aspose file tools*
The moose likes Websphere and the fly likes Start or stop server with WAS v5 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Start or stop server with WAS v5" Watch "Start or stop server with WAS v5" New topic
Author

Start or stop server with WAS v5

c laflamme
Greenhorn

Joined: Nov 06, 2003
Posts: 3
Hi!
Anyone know how to start or stop servers using the admin console on the browser with WAS 5 base (no network deployment). We only have the button new or delete when we click on servers.
Thanks
Krupa Eng
Ranch Hand

Joined: Sep 05, 2003
Posts: 60
For WAS base 5 you cannot start or stop your Server from the browser. You have to use startserver, stopserver scripts.


Krupa
Scott Duncan
Ranch Hand

Joined: Nov 01, 2002
Posts: 363
Yes, Krupa is correct. IBM has found yet another way to extort money from their WebSphere customers. Turns out there are a number of things you could do with WAS 4 fat client but not with the WAS 5 browser console. For example, even when you create a new server instance under the base edition, the apps you put on it cannot be administered through the console because the console resides on the server1 instance by default and therefore is running on a different JVM than the apps on the other server instances. To get around this, you can take the adminconsole.ear and install it on each of your server instances but it still will not help you stop and start the server instances themselves. For this, you will still have to use the stop/start server .bat files. What we ended up doing is writing a crapload of wsadmin scripts to manage our stuff and this works well but there is a small learning curve involved. The goal is to automate deployments though and wsadmin will serve us well here. My advice is to either put ND on or use wsadmin.


No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
leonardo battagli
Ranch Hand

Joined: Aug 28, 2003
Posts: 33
Originally posted by William Duncan:
Yes, Krupa is correct. IBM has found yet another way to extort money from their WebSphere customers. Turns out there are a number of things you could do with WAS 4 fat client but not with the WAS 5 browser console. For example, even when you create a new server instance under the base edition, the apps you put on it cannot be administered through the console because the console resides on the server1 instance by default and therefore is running on a different JVM than the apps on the other server instances. To get around this, you can take the adminconsole.ear and install it on each of your server instances but it still will not help you stop and start the server instances themselves. For this, you will still have to use the stop/start server .bat files. What we ended up doing is writing a crapload of wsadmin scripts to manage our stuff and this works well but there is a small learning curve involved. The goal is to automate deployments though and wsadmin will serve us well here. My advice is to either put ND on or use wsadmin.

I tried to build adminconsole.ear using EXPORT.
EXPORT is able to build a file but it is a 0Kb file.
Where else can you build it?
Mahesh Chalil
Ranch Hand

Joined: Jan 24, 2002
Posts: 147
build admin.ear file? It already comes with Websphere. You have to just install it in Websphere server instance you create.
leonardo battagli
Ranch Hand

Joined: Aug 28, 2003
Posts: 33
Originally posted by Mahesh Chalil:
build admin.ear file? It already comes with Websphere. You have to just install it in Websphere server instance you create.

Yes thks I used that I found in directory 'Installable Apps'
Now I have been able to:
- create a new application server
- start this new application server
- install the admin console in the new application server
But I have not been able to START this admin console.
I have browsed the wsadmin command tools (admincontrol, adminconfig) to look for a way to start the ADMIN CONSOLE ENTERPRISE APPLICATION, but no result 'till now
btw I understand it should be simpler, I'll let you all know
Mahesh Chalil
Ranch Hand

Joined: Jan 24, 2002
Posts: 147
Try using $AdminApp with wsadmin.
Karan Sahni
Greenhorn

Joined: Jul 21, 2003
Posts: 2
AdminControl stopServer not working on base install of WAS5.1
It says

WASX7209I: Connected to process "server1" on node CTIDEVWEB02 using SOAP connect
or; The type of process is: UnManagedProcess
WASX7022E: Problem running command "$AdminControl stopServer JMillenniaHourly_Server" -- exception information: com.ibm.ws.scripting.ScriptingException: WASX725
2E: Unable to locate running server "JMillenniaHourly_Server".

I know that the server JMillenniaHourly_Server is there because I started it using startserver. Similarly, starting/stopping app on other servers (apart from server1) is failing too.
Nitish Bahadur
Ranch Hand

Joined: Aug 25, 2003
Posts: 118
This typically happens when you have port conflicts between your various servers. Check the End Points and HTTP Transports.

I am in a similar boat.
K Nally
Greenhorn

Joined: Sep 30, 2003
Posts: 13
Hi:

Speaking of writing wsadmin scripts, I am encountering a problem on only one cell using the $AdminControl stopServer command. I am receiving the following error:

javax.management.ListenerNotFoundException: Did not find listener com.ibm.ws.scripting.AdminControlClient@4464c914

I can issue other $AdminControl commands such as getCell, getHost, etc. Again, it is only on one cell - the other three cells work.

Anyone out there experience this one? Thanks very, very much.

Karen
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Start or stop server with WAS v5