Most of us--when we're using straight WAS and not via RAD 6 or WSAD 5 (see The Relationship Between RAD 6 and WAS 6)--are used to starting a server like this (assuming our server has the default name of
C:\WebSphere\AppServer\bin> startServer server1
This still works in WAS 6. Usually. Well, always. Except it doesn't always start up the server1 we had in mind. Or when we specifiy to start MyFavoriteServer, it might find it and it might not. What's going on here?
Starting a server is a specific case of the more general issue: using command line tools has changed in WAS 6. And it's because of, you guessed it, application server profiles. (It's great writing for you guys, you pick up on this stuff so quick(ly)!)
In short, when you run a command from the WAS install's main
bindirectory (or anywhere else if that directory is on your OS's executable path), the WAS commands assume you mean the default profile (typically called "default" in WAS Base or "AppSrv01" in WAS ND; look in the
[was_home]\profilesdirectory). So assuming that's what you meant, everything magically works and you're happy. If not, things sometimes don't seem to work right and you become very very sad (or mad at IBM).
So how do you mess with the servers that aren't configured with the default profile? There are two approaches:
- -profileName option -- Specify the profile to use as an additional argument to the command.
- profile's bin directory -- Change to the profile's
bindirectory (such as
[was_home]\profiles\MyProfile\bin) and run the command from there.
Also, check out the Starting and stopping quick reference.