+

Search Tips   |   Advanced Search

 

Installing maintenance as an installer and changing the ownership of profile related files

 

The installer can install maintenance packages for WAS 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 installer 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 WAS. This task assumes a basic familiarity with the Update Installer wizard and system commands.This task uses the following terms:

Before you can update a profile, install WAS and create a profile.

 

Overview

This example assumes that the installer:

If the installer does not change ownership, when the non-root user starts WAS, 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

 

Procedure

  1. Run the Update Installer wizard to install maintenance packages for WAS.

    The installer owns the new files that the Update Installer wizard creates under the profile_root directory. The original owner of existing files continues to own those files that the Update Installer wizard only modifies.

  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 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 WAS without receiving the ADMR0104E error message.



Installing maintenance packages