Installing maintenance packages as a root user and changing the ownership of profile-related files

The root user can install maintenance packages for the product that includes required service for existing profiles that are owned by a non-root 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 root user 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.
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

You must have root authority to accomplish the following tasks.

Before you can update a profile, you must install the product, and create a profile.

About this task

This example assumes that the root user completes the following actions:
  • Applies Refresh Pack 2-required service for the Java Database Connector (JDBC) resource provider templates and that the service creates new files in a profiles directory that the wsdemo non-root user owns
  • Changes ownership of new profile files from the root user to the wsdemo non-root user.
If the root user 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

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

    When the root user installs Refresh Pack 2, the root user owns the following new JDBC-related files:

    [Linux] [HP-UX] [Solaris] [AIX]
    • profile_root/logs/updateProfileJdbcTemplate.log
    • profile_root/config/templates/system/jdbc-resource-provider-only-templates.xml
    • profile_root/config/templates/system/jdbc-resource-provider-templates.xml
    [Windows]
    • C:\profile_root\logs\updateProfileJdbcTemplate.log
    • C:\profile_root\config\templates\system\jdbc-resource-provider-only-templates.xml
    • C:\profile_root\config\templates\system\jdbc-resource-provider-templates.xml
  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 root user 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.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 5:25:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=tpro_root_service
File name: tpro_root_service.html