Agent Controller Release Notes

© Copyright International Business Machines Corporation 2000, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Known limitations, problems, and workarounds
   1.1 Agent Controller does not work when installed in Windows Desktop folder
   1.2 Installing Agent Controller on Windows and Linux
   1.3 Agent Controller log file might not have public write permission on non-Windows platforms
   1.4 Classes residing on network drives are not accessible on Windows
   1.5 Cannot restart the Agent Controller process on non-Windows platforms
   1.6 Agent Controller cannot look up correct IP address
   1.7 SetConfig requires a JRE in the system path

1.0 Known limitations, problems, and workarounds

1.1 Agent Controller does not work when installed in Windows Desktop folder

Agent Controller does not work when installed in the Windows® Desktop folder on a Windows system. For example, Agent Controller will not work if you specify the install directory as C:\Documents and Settings\Administrator\Desktop.

To workaround this limitation, install Agent Controller in another directory.

1.2 Installing Agent Controller on Windows and Linux

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. 

1.3 Agent Controller log file might not have public write permission on non-Windows platforms

The log file AGENT_CONTROLLER_INSTALL/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, run the following command as root after installation:

chmod 666 <Agent Controller install location>/config/servicelog.log

1.4 Classes residing on network drives are not accessible on Windows

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 IBM® Agent Controller to use the classes on network drives, follow these steps:

  1. Open Windows Services window.
  2. Select IBM Agent Controller.
  3. Click the Properties toolbar button.
  4. Select the Log On pane.
  5. Select the This account radio button and fill in the user ID information. This is the user ID which connected (by net use or equivalent) to the drive.
  6. Click OK.
  7. Restart the IBM Agent Controller service.
  8. Relaunch the application.

Note: This will allow the use of network drives, but will limit Agent Controller's access rights to whatever the current user has.

1.5 Cannot restart the Agent Controller process on non-Windows platforms

Agent Controller cannot restart on a non-Windows platform.

To work around this problem, follow these steps:
Shutdown all Eclipse workbenches which are connected to Agent Controller
Issue the command
 kill -s HUP < process ID of the inetd process >
(must be root)
Use netstat to check whether port 10002 (default) is still occupied. Wait until it is freed before restarting Agent Controller
Alternatively, you can change the port from 10002 to another value inside the Agent Controller configuration file
AGENT_CONTROLLER_INSTALL/config/serviceconfig.xml
and restart Agent Controller immediately.
To prevent this from happening, always shutdown all connected workbenches before restarting the Agent Controller process.

1.6 Agent Controller cannot look up correct IP address

When the Agent Controller starts, it must look up the IP address of the local computer. The Agent Controller uses a call to InetAddress.getLocalHost() to perform this lookup. This call does not always return the correct IP address. An incorrect IP address will prevent the dynamic discovery feature from working correctly. The incorrect IP address can be returned in different situations:


To work around this problem, specify your computer's IP address and port manually when starting up the Agent Controller. Use the command line options "-peerAttachAddress=nnn.nnn.nnn.nnn" and "-peerAttachPort=x" when starting the RAServer process or ACServer process, where nnn.nnn.nnn.nnn is the computer's IP address and x is the port used for Agent Controller communication.

1.7 SetConfig requires a JRE in the system path

To use the SetConfig.bat or SetConfig.sh script, a JRE (version 1.5 or higher) must be available in the system path. Only advanced users should need to use the SetConfig script.