IBM Tivoli Composite Application Manager for Application Diagnostics, Version 184.108.40.206
Permissions- UNIX - WAS agent
If the IBM Tivoli Monitoring framework is being installed on the host for the first time, root privileges are required for installation. Otherwise, a non-root user account can be used, but it must meet certain requirements.
The Agent requires the IBM Tivoli Framework; the agent installer will, by default, install this framework. The framework includes Global Security Kit (GSKit); installation of GSKit requires root permissions. Therefore, if the IBM Tivoli Monitoring framework was not installed on the host, use a root account to install the agent.
However, if the IBM Tivoli Framework is already installed on the host, you may use a non-root account for installation. This must be the account that owns all the application server profiles to be monitored by the data collector. The account must meet the following requirements for every application server profile to be monitored:
- The user must be able to start and stop WAS using the standard startServer.sh and stopServer.sh scripts.
- The user must have privileges (read, write and execute) for accessing the application server directory tree.
- The files in the AppServer_home directory must be owned by this user.
- The user must have read/write permission for the IBM Tivoli Monitoring home directory (by default, /opt/IBM/ITM) and the logs subdirectory in it.
- The user must have read and write privileges to the application server log directory: AppServer_home/profiles/profile_name/logs; if the files wsadmin.traceout and wsadmin.valout exist in this directory, the user must have read/write permission for these files.
- If you are performing an upgrade of the agent, this installation user must have read/write permission for the home directory for the previous versions of the monitoring agent and data collector.
- The user must have read and write privileges to one of the following system temporary directories. These directories will be used by the InstallShield portion of the installation program:
Default temporary directories for the InstallShield portion of the installation program
Operating system Directory Solaris or HP-UX It is one of the following paths:
- If it exists: /var/tmp/ibm_am_installer_dc
- If the /var/tmp/ibm_am_installer_dc directory does not exist, /var/tmp
Linux and all other UNIX platforms It is one of the following paths:
- If it exists: /tmp/ibm_am_installer_dc
- If the /tmp/ibm_am_installer_dc directory does not exist, /tmp
If WAS was installed by root, but all the instances to be monitored are owned by a non-root account before using this non-root account to install the agent:
- As the root user, run the following commands:chown -R wasuser:wasgroup AppServer_home/properties/version/history chown wasuser:wasgroup AppServer_home/properties/version
The wasuser and the wasgroup are the user and group of the application server instance.
- As your non-root user, run the following command:./versioninfo.shIf the application server version (not an error message) is displayed, you have performed the change successfully, and may use the non-root account to install the agent.
Parent topic:Required tasks before installation