Publish to WAS 5.0 Problem - Admin Console not starting

[Sybil Santos-Burgan]

Hi,
I'm having problems with my WAS 5.0 I first exported the ear file from WSAD and then went the WAS Admin Console to set up the applicationa and run it. ButI had problems. So I read from the Websphere help how to publish from WSAD to WAS. I was able to run my application on the remote websphere server. This was good but I didn't know that it running is tied to my WSAD running and if I shut down my WSAD the application is not running. So I went to the server's admin console to start my app up but I can't run admin console now. It says it can't find a config file.
I read somewhere somebody else having a problem where if you publish from WSAD then the WAS config gets hosed. Is this true? What do I do? What's the normal step by step to publishing to WAS?
Thanks
Sybil

[Rufus BugleWeed]

Which config file is missing?

[Scott Duncan]

Unfortunately, I cannot tell you what to do here because as a rule, I use the WSAD test environment for development and then publish to a websphere server for testing.
I can tell you that you could normally export an EAR file from WSAD by right clicking the EAR file project and selecting export (or use ANT to build the EAR). Then use the WebSphere Admin console or the wsadmin scripting tool to do the install.
My first step would be to remove the project from the WSAD remote server project. Go to the server perspective, make sure the server configuration window is open (if not go to window--> show view). Right click on the remote server/configuration entry and remove the project. Then go ahead and shut down WSAD.
After that I'd try to install the EAR file clean on WAS. If it is already installed, try to remove it. This probably will not work since it does not recognize it in the configuration. But I'd do it anyway just to make sure it was off. Then try to install it again.
That's how I'd tackle it without knowing what any of the errors are or having the logs anyway.

[Sybil Santos-Burgan]

The server has to be running for me to use the admin console right? When I go over to the server and look at the First Steps screen it says that I can stop the server. So I click Stop Server but then get an error message ADMU3522E No server by this name in the configuration: server1.
I originally did move the EAR etc myself before trying my hand at publishing through WSAD. But didn't get it to work. Now even if I wanted to go back and try it the prior way I cant get to admin console.

[Rufus BugleWeed]

Are you following IBM's instructions and created a new server? These instructions are in chapter 17, Deploying an Application, of redbook sg246195.
If you did, IBM is leading you down a dead end.
I am assuming you are still using the base edition, perhaps developer trail edition.
[ February 17, 2004: Message edited by: Rufus BugleWeed ]

[Scott Duncan]

If you did, IBM is leading you down a dead end.

Ahh, they would never do that would they?

The server has to be running for me to use the admin console right? When I go over to the server and look at the First Steps screen it says that I can stop the server. So I click Stop Server but then get an error message ADMU3522E No server by this name in the configuration: server1.

You are correct. The server instance where the admin console is installed must be running in order to use it. This is where I am not understanding you. Can you tell us what edition of WAS you are using? Unless you are using Network Deployment, I do not think you can use the admin console to stop or start the server instance. The error message implies that the server1 instance has been removed from the configuration which means that there is not an entry for it in the WAS_HOME/config/cells/CELL_NAME/nodes/NODE_NAME/serverindex.xml file. This would not be good. Are you using Network Deployment? If you are, I think ND would handle the configuration of your server instances (I do not use ND so don't quote me on this) and a direct attempt to use the admin console on the base WebSphere server would probably not work. I really do not know but if this is mission critical, I know an ND expert who may be able to help. Somehow, I think you are going to have to wipe the slate clean to get this thing to work properly as your configuration is bombed.

[Amer Arman]

did anyone find a solution to this problem and why it is happenning. I'm facing the exact scenario
Although I made sure that the configuration files are there for server1, the server is not starting and giving the error
ADMU0111E: Program exiting with error:
com.ibm.websphere.management.exception.NoServerDefinedException: No
configuration defined for server: server1
[ December 13, 2004: Message edited by: Amer Arman ]