On AIX 6.1, when installing TPM on a file system, before mounting the file system, ensure the mount point for the file system has permission of at least 755.
Tivoli Provisioning Manager 7.1.1 uses Java installed by WebSphere Application Server for Network Deployment. Tivoli Provisioning Manager executes many commands as a non-root user. For example, the non-root user command to start Tivoli Provisioning Manager is executed by user, tioadmin.
After a new installation of TPM 7.1.1 on AIX 6.1, when executing $TIO_HOME/tio.sh start tpm, the TPM engine fails to start with the error message:
The java class is not found: com.ibm.class.LaunchLWI
This failure is because WebSphere Application Server's Java SDK does not initialize properly when run as a non-root user. Testing Java reveals specific errors, as shown in the example below.
Login as user tioadmin:
…… produces the error
JVM not found: libjvm.so
The error shown above occurs even though the libjvm.so file is present in the proper location and has correct permissions. Executing the above command as user root executes successfully.
If the mount point for the filesystem to which WebSphere is installed is not set up correctly, it can cause problems for Java initialization.
Resolving the problem
In situations where Java initializes properly when run as the root user but fails when run as a non-root user, check the following points:
1. The WebSphere Application Server V6.1 installation should be successful. Check the TPM middleware installation logs to ensure that the installation ended with a "success" message. $MWI_workspace/hostname/deploymentplan/MachinePlan_hostname/00009_WAS_ND_6.1/
install/01_BASE/[INSTALL_timestamp]/logs/ or <WAS_HOME>/logs/install/
2. A non-root user must have read access to all files installed with WebSphere Application Server V6.1, including all of the files in the product's "java" subdirectory. This can be accomplished by granting ownership of all the product's files to that non-root user.
3. A non-root user should also have access to the AIX system libraries, such as the libraries in /usr/lib and /usr/ccs/lib .
If each of the above points are checked and appear to be in good order, then there is one more aspect of the WebSphere configuration to review. Follow these steps to check and correct an issue which could lead to problems when initializing Java as a non-root user:
1. Locate the mount point of the filesystem where WebSphere Application Server V6.1 is mounted on.
2. Unmount that filesystem.
3. Check the permissions of the blank directory which acts as the mount point for the filesystem. The permissions should be at least "755". The ownership and permissions of that directory must be configured in a manner which allows the non-root user read access to that directory.
4. Check that the directory which acts as the mount point is empty. If the directory contains anything, remove that content so that the directory becomes empty.