Install profile maintenance

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 WAS ND.

This task assumes a basic familiarity with the Update Installer wizard and system commands.This task uses the following terms:

• Root users refers to:

  • (Linux) [HP-UX] [Solaris]

    [AIX] Root users

  • (Windows) Administrators

• Non-root users refers to:

  • (Linux) [HP-UX] [Solaris]

    [AIX] Non-root users

  • (Windows) Non-administrators

• Installer refers to a root user or a non-root user.

Before we can update a profile, install WAS ND, and create a profile.

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 WAS ND, the appserver 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

 

1. Run the update installer wizard to install maintenance packages for WAS ND. profile_root

2. 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.
   [Linux] [HP-UX] [Solaris]

   [AIX] Issue the chown command.

   chown -R wsdemo profile_root
   

   (Windows) 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.

 

Next steps

The non-root user can start WAS without receiving the ADMR0104E error message.