StandAlone app Server profile - WAS 6.1
Posted on 2010-11-24
This is something intersting and wierd.
Well as a specific user I created a StandAlone app server profile on WAS 6.1 binaries. I Twas working fine till I applied a an upgrade package.
Well I had to apply a fixpack to the integrated solution console for the same profile. So I applied this fixpack and augmented this profile to this fixpack . All the fixpack process and augmenting was doen as a root user. Since Root was the only who could run the update installer, well I got what I wanted in the integrated solution console. But when I try to restart the server as the same user who created binaries and profile from the WASHOME/bin directory it gives me an error
"WCMD0002E: Command "startServer.sh" requires a profile. No default profile exists and a profile name was not specified. Ensure that a default profile exists or use the -profileName parameter to specify the name of an existing profile." Root was able to start the server from the same directory
I was able to start the server with the same user id from WASHOME/profiles/Appserver/bin/
So I want to know what got changed when I augmented the profile using root . Is ther any way I can let the user ID gain control of the profile . If you are wondering what the hell am I doing " I am working on IBM license metric tool and it needs some upgrades to the integrated solution console"