The root user can install maintenance packages for WebSphere Application Server that includes required service for existing profiles that are owned by a non- user. Installing a maintenance package that contains service for a non-root profile makes the root user owner of any new files that the maintenance package creates. The following example shows how to install the maintenance and change the ownership of the new files so that a non-root user can successfully start WebSphere Application Server.
Before you begin
This task assumes a basic familiarity with the Update Installer wizard and system commands.You must have root authority to accomplish the following tasks.
Before you can update a profile, you must install WebSphere Application Server and create a profile.
Why and when to perform this task
ADMR0104E: The system is unable to read document cells/express1Cell/nodes/express1/node-metadata.properties: java.io.IOException: No such file or directory
Steps for this task
When the root user installs Refresh Pack 2, the root user owns the following new JDBC-related files:
The profile_root variable in the following examples is the profile directory that the non-root user owns.
chown -R wsdemo profile_root
Follow instructions in the Windows documentation to reassign
ownership of the profile_root profile directory to the
wsdemo non-root user.
Result
The root user installed maintenance that creates new files in a non-root user profile directory and changes ownership of the new files to the non-root owner.What to do next
The non-root user can start WebSphere Application Server without receiving the ADMR0104E error message.Related reference
Installing maintenance packages