+

Search Tips   |   Advanced Search

 

Migrate a previously non-root configuration to root

 

You can run either a deployment manager or appserver as root in WAS V6.1 when you previously used a non-root user ID on Linux and UNIX platforms in V5.x or 6.0.x. See Overview of migration, coexistence, and interoperability and Premigration considerations.

 

Procedure

Set the ownership of the profile or deployment manager directory to be the same as the user under which WAS is to run.

This must be done in order for the deployment manager or appservers to run correctly. As a root user, run the following commands:

cd $WASROOT/profiles/   chown -R wasadmin dmgr/   chgrp -R wasndgrp dmgr/   chmod -R 755 dmgr/  
...  cd $WASROOT/profiles/dmgr/bin
./startManager.sh
where the profile name is dmgr run as a user in wasadmin with the primary group wasndgrp.

For help in troubleshooting problems when migrating, see Troubleshooting migration.

 

Results

You can now run either a deployment manager or appserver as root.



Running an appserver from a non-root user and the node agent from root

 

Related information


Running the deployment manager with a non-root user ID