Agent Controller does not work when installed in the Windows Desktop folder on a Windows system. For example, the Agent Controller will not work if you specify the install directory as C:\Documents and Settings\Administrator\Desktop.
To workaround this limitation, install the Agent Controller in another directory.
Installing Agent Controller on Windows and Linux will remove any existing Agent Controller installation. Make sure you have backed up necessary data before proceeding to the installation.
The Agent Controller installation may not detect any Java Runtime installed on the machine.
The default value specified in the "Java Runtime" installation dialog may point to a temporary Java Runtime shipped by the installer for installation purpose. You must provide an alternative Java Runtime installation which you want the Agent Controller to use.
The log file <Agent Controller install location >/config/servicelog.log might not have the required permission bits (666). This will prevent any non-root Agent Controller process from writing to the log file.
To workaround this problem just run the command
chmod 666 <Agent Controller install location>/config/servicelog.logas root after installation.
The Agent Controller service is configured to log on as "Local System Account". Therefore, it might not have the rights to access mounted network drives, which are usually accessed by means of net use, by the current user ID.
To enable Agent Controller to use the classes on network drives, follow these steps:
Note: This will allow the use of network drives, but will limit the Agent Controller's access rights to whatever the current user has.
The Agent Controller cannot restart on a non-Windows platform.
To work around this problem, follow these steps:
kill -s HUP < process ID of the inetd process >(must be root)
<Agent Controller install location>/config/serviceconfig.xmland restart the Agent Controller immediately.
If Agent Controller 4.0.3 is installed as a standalone product then it will be detected and properly uninstalled when installing version 6.0.0. If Agent Controller is installed as part of WSAD v4.0.3, the v6.0.0 installation cannot detect it and will not uninstall the older version. This is a Microsoft Installer limitation.
To work around this limitation, you need uninstall WSAD v4.0.3 completely, since it is the parent product that installed Agent Controller v4.0.3. Ensure that the Agent Controller v4.0.3 is properly removed by checking the Agent Controller install diretory is empty and verify that the registry values HKLM\SOFTWARE\IBM\IBM Agent Controller and HKLM\SYSTEM\*\SERVICES\IBM Agent Controller no longer exist.
A temporary file hgla.log is created in the system's temp directory under the same user ID that starts Agent Controller. If Agent Controller is restarted using another non-root user ID, the temporary file hgla.log will not be removable by the non-root user and causes remote log imports to fail.
To work around this limitation, remove the hgla.log file manually before importing logs remotely.
Security is not supported by the Autonomic Computing tools. Do not enable security when running the SetConfig script.
Return to the main readme file