When an installer installs a maintenance package that contains
service for a profile that a non-root user owns, the installer owns any new
files that the maintenance package creates. The installer can change the ownership
of the new files so that a non-root user can successfully start the product.
Before you begin
This task assumes a basic familiarity with the Update Installer wizard
and system commands.
Before you can update a profile,
you must install the product, and create a profile.
About this task
This example assumes
that the installer completes the following actions:
- Applies service that creates new files in a profiles
directory that the wsdemo non-root user owns
- Changes ownership
of new profile files from the installer to the wsdemo non-root user.
If the installer does not change ownership, then when the
non-root user starts the product, the application server encounters an error
and issues a message that is similar to the following example:ADMR0104E:
The system is unable to read document
cells/express1Cell/nodes/express1/node-metadata.properties:
java.io.IOException: No such file or directory
Procedure
- Run the Update Installer wizard to
install maintenance packages for the product.
The installer owns the new files
that the Update Installer wizard creates in the profile_root directory.
The original owner of existing files continues to own those files that the
Update Installer wizard only modifies.
- Reassign ownership of the entire profile directory to the wsdemo
non-root user.
The profile_root variable
in the following examples is the profile directory that the non-root user
owns.
Follow instructions in the Windows documentation to reassign
ownership of the profile_root profile
directory to the wsdemo non-root user.
Results
The installer
installed a maintenance package 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 the product without receiving the
ADMR0104E error message.