Agent Controller - release notes

1.0 Introduction
2.0 Known problems and limitations
   2.1 The Agent Controller is not installed automatically with the product
   2.2 Setup will upgrade Windows Installer to 2.0
   2.3 Error 1920 during installation
   2.4 Installing Agent Controller on an iSeries system
   2.5 Installing Agent Controller Version 5.0.2 on Linux
   2.6 Updates to the Installation Guide
   2.7 Classes residing on network drives are not accessible

1.0 Introduction

2.0 Known problems and limitations

2.1 The Agent Controller is not installed automatically with the product

The Agent Controller is no longer installed automatically when you install WebSphere Studio. For more Agent Controller installation information, refer to the Installation Guide.

2.2 Setup will upgrade Windows Installer to 2.0

If the Windows Installer is older than 2.0, setup will automatically upgrade it. This will require a reboot. The Agent Controller installation will resume automatically after system reboot.

2.3 Error 1920 during installation

If you encounter Windows Installer error 1920 during installation, there is a problem starting the IBM Agent Controller service. Do the following:

  1. Cancel the IBM Agent Controller setup.
  2. Uninstall the IBM Agent Controller from the Add/Remove program dialog.
  3. Open Windows' Task Manager window and terminate any "NTVDM.exe" and "wowexec.exe" processes.
  4. Navigate to the GSK install directory on the CD (or the ESD image) under "IBM_Agent_Controller\windows\gsk". Run setup.exe and an error dialog should come up. Dismiss the dialog.
  5. Reinstall the IBM Agent Controller from the CD (or the ESD image) under "IBM_Agent_Controller\windows", or by re-inserting the CD.
  6. In some cases, if the cancellation of the Install was unsuccessful, you will need to reboot the machine.
This won't happen if security is disabled.

Sometimes, it is caused by the existence of a file called Program under the system drive. For example, if Windows is installed under the D: drive, the existence of a file called Program under D:\ will stop the Agent Controller service from starting if it is installed under the default location D:\Program Files\IBM\IBM Agent Controller. This is because Windows is trying to start the Agent Controller service as D:\Program with a parameter Files\IBM\IBM Agent Controller\bin\RAServer.exe, which is not correct. You can work around this problem by performing one of the following:

  1. Remove or rename the file called Program.
  2. Install the Agent Controller using a directory without spaces (for example, D:\IBM_Agent_Controller).
  3. Add double quotes around the Agent Controller executable name in the Windows registry under the key name HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBM Agent Controller\ImagePath. For example, "D:\Program Files\IBM\IBM Agent Controller\bin\RAServer.exe".

2.4 Installing Agent Controller on an iSeries system

This information replace the "Installing and uninstalling on iSeries" section in the WebSphere Studio Application Developer Installation Guide.

To install Agent Controller on an iSeries system, follow these steps:

  1. On the iSeries host, create a library called IBMRAC.
  2. In the IBMRAC library, create an empty save file called IBMRAC.SAVF.
    Note for iSeries V5R2 only: In the IBMRAC libarary, create an empty save file called PROFILER.SAVF.
  3. FTP the file IBMRAC.SAVF to the library IBMRAC.
    Note for iSeries V5R2 only: FTP the file PROFILER.SAVF to the library IBMRAC using BINARY mode transfer.
  4. Restore the save file IBMRAC.SAVF to the library IBMRAC.
    Note for iSeries V5R2 only: Restore the save file PROFILER.SAVF to the libary IBMRAC.
  5. Create, on the IFS, the /opt/IBMRAC directory.
  6. Restore the save file config.savf in IBMRAC to the IFS directory /opt/IBMRAC. For example, RST DEV('/QSYS.LIB/IBMRAC.LIB/CONFIG.FILE') OBJ('/opt/IBMRAC')
  7. After you have installed Agent Controller, change the directory to the installed location's bin directory /opt/IBMRAC/bin, and run the setup script by typing: ./SetConfig.sh
  8. Reply to the following prompts:
    1. For the Specify where the Java Runtime file (java) is located: prompt, type the location where the java file can be found (for example, /QSYS.LIB/Q5BVAJVM.PGM).
    2. For the WebSphere Application Server V5 installed location: prompt, type the location of WebSphere Application Server Version 5, if it is installed (for example, /QIBM/ProdData/WebAS5/Base). You can leave this prompt blank.
    3. For the Security (yes/no): prompt, specify whether or not you want to enable the security feature.
    4. If security is enabled, for the Secured users IDs (separated by commas): prompt, type the user log in names on the system who are granted access to Agent Controller. The operating system must be able to authenticate these user log in names. For more information, refer to "Using Agent Controller security feature" that is described in the WebSphere Studio Application Developer Installation Guide.
    5. For the Allow hosts (ALL/LOCAL/CUSTOM): prompt, specify which computers can access Agent Controller. To allow only this computer, type LOCAL. To allow any computer to connect, type: ALL. To specify a list of computers, type: CUSTOM.
    6. If CUSTOM is selected, for the Allowed host names (separated by commas): prompt, type the host names which can access Agent Controller. Host names do not have to be fully qualified. You may also specify IP addresses.
  9. Add the IBMRAC library to the library list entry: ADDLIBLE IBMRAC
  10. To start Agent Controller, type the following command: SBMJOB CMD(CALL RASERVER) JOBD(RASTART)

To stop Agent Controller, type: ENDJOB JOB(RASTART)

There is no upgrade capability. However, you may uninstall the version currently on the system and perform the installation steps described in "Installing and uninstalling on iSeries" section in the WebSphere Studio Application Developer Installation Guide.

To uninstall Agent Controller on iSeries, remove the IBMRAC library and the IFS directory /opt/IBMRAC (including all subdirectories and files).

2.5 Installing Agent Controller Version 5.0.2 on Linux

On Linux, if you have either Agent Controller Version 5 (shipped in Version 5 General Availability) or Agent Controller Version 5.0.1 (in efix), then you must uninstall this version before installing Agent Controller Version 5.0.2. Note that all the files in /opt/IBMRAC will be erased.

2.6 Updates to the Installation Guide

2.7 Classes residing on network drives are not accessible

The IBM 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. If you want to let the Agent Controller 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 the Agent Controller's access rights to whatever the current user has.

Return to the main readme file