IBM Tivoli Composite Application Manager for Applications, Version 7.2.1.2

Running the agent as a non-administrator user

You can install and configure the Sybase ASE agent with a non-root user ID.

For UNIX and Linux operating systems, you can install, configure, and run the agent with a user ID other than root. However, you must complete some additional steps.

Installing the agent with a non-root user ID

Complete the following tasks for installing the agent with a non-root user ID:

The user ID that is used to install the agent must have appropriate access to Sybase files to query the database and write to the agent tablespace. For example, if the user ID that was used to install Sybase is a member of the sybase group, then the user ID that is used to install the agent must be a member of the sybase group.
Make sure that the user ID that is used to install the agent has write access to any pre-existing directories in the installation path. For example, if you want to install the agent in the /opt/IBM/ITM directory, and the /opt/IBM directory already exists, then the user ID that is used to install the agent must have write authority /opt/IBM.
For installing the agent locally, complete following steps:
1. When the following message is displayed during installation, complete these steps: Enter root password to configure automatic restart of agents.
  1. Press Enter without entering a password
  2. Enter i to ignore. This action disables the agent from starting automatically.
  If you enable autostart by entering the root password, see Upgrading and restarting the agent by using non-root for information about ensuring that the agent has started automatically with the desired user ID.
2. Run the SetPerm command when the following message is displayed at the end of installation: install.sh warning: root user must run bin/SetPerm from ITM home to complete setup.
3. Run the following commands:
```
cd install_dir 
chown root */bin/kddos 
chmod u+sx */bin/kddos
```
For installing the agent remotely, the following steps are required:
- During installation, the following message might occur even though the monitoring agent was deployed successfully:
  KUICAR020E: The addSystem command did not complete because a deployment error occurred. Refer to the following error returned from the server: The monitoring server encountered an error while deploying the managed system.
- After you deploy the monitoring agent, log on to the remote computer and run the following commands as root:
```
cd install_dir
bin/SetPerm
chown root */bin/kddos
chmod u+sx */bin/kddos
```
- If you want to enable autostart, then see Upgrading and restarting the agent by using non-root for information about ensuring that the agent has started automatically with the desired user ID.

Configuring the agent with a non-root user ID

If you install the UNIX OS agent or the Sybase agent as root, and you want to configure the Sybase agent with a non-root user ID, make sure that the user ID has the appropriate directory and file permissions to update the files in install_dir directory.

For Linux operating systems, auto-discovery of databases is not available when a non-root is used for configuring the agent. On the console, select 3) No automatic search. Manual update only. Do not select 1) Confine automatic search to running databases. or 2) Also search for non-running databases(slower). unless you are running the configuration as root.
When you are prompted to enter the root password to enable the configuration to run the auto restart script, Info - TO update auto restart script, you have to enter root password., press Enter if you do not want to enable this function at this time.

Running the agent with a non-root user ID

Start and stop the monitoring agent locally or remotely by using the same user ID that was used to configure the agent. All monitoring agent instances on a computer must use the same user ID when starting and stopping the monitoring agent. You cannot use root to start and stop the syb instance and use sybase to start and stop the test instance in the same installation directory. Data for attributes that are related to operating system metrics cannot be collected when a non-root user ID is used.

Feedback