| Application Server Toolkit - release notes |
1.0 Introduction
2.0 Third party license terms and conditions, notices and information
3.0 Installing the Application Server Toolkit
4.0 Version 5.1.0 release notes
5.0 National language versions of the release notes
This readme file describes the known problems and limitations that are associated with the Assembly Toolkit and the Application Server toolkit debuggers. It also covers the Agent Controller and the performance and memory profiling and analysis tools that are available from the Profiling perspective of the workbench (including the Log views). In addition, this readme file provides install instructions for the Application Server Toolkit.
The debuggers in the Application Server toolkit provide the tooling necessary to debug Web applications, JavaScript, Java, and compiled languages.
The online help for the profiling tools contains more information on WebSphere test environment and Java restrictions, and on working around them.
For the latest information about Application Server Toolkit problems, limitations, and install instructions, please see the English online version of the Application Server Toolkit Version 5.1.0 Release Notes at http://service.boulder.ibm.com/ibmdl/pub/software/websphere/astk/readme/readme_ast.html. Updated national language versions of the Release Notes are also available at this Web site, however, the English is considered to be the up-to-date version.
The license agreement for this product refers you to this file, or to a file referenced by this file, for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. If you received this product on a CD-ROM, the relevant terms and conditions, notices and other information are provided in the "LICENSE.TXT" file on the root directory of the first installation CD-ROM for this product. In either case, the "LICENSE.TXT" file is installed into the root installation directory as part of the installation process. Please note that any non-English version of the information in this file is unofficial and is provided to you for your convenience only. The English version of the file is the official version.
To install the toolkit, run the setup executable and follow the prompts on the resulting windows. If you are installing the toolkit on a multi-user system, you must be a super user on the system.
The Application Server Toolkit installer includes a compressed JVM that is used for the install. This JVM is extracted to a temporary location at the start of the install. If there is insufficient disk space in the default temporary location, the install will fail. Alternate temporary locations may be specified by starting the installer with the following command line arguments, setup -is:tempdir <temp>, where <temp> is a directory with sufficent temporary disk space.
IBM Agent Controller
The IBM Agent Controller allows you to test your J2EE application on a standalone WebSphere Application Server that is installed on a remote machine. By default, Agent Controller is installed in the system_drive:\Program Files\IBM\IBM Agent Controller\ directory (where system_drive is the hard drive where Windows(R) is installed). On the Java Runtime Environment page of the wizard, you must specify the location of the Java run-time file (java.exe). For example, if the java.exe file is located in the directory c:\jdk\bin, specify c:\jdk\bin as the folder containing the Java run-time file. If you are installing on the same computer as the Application Server Toolkit, this field is automatically primed with the location of the Java run-time file included with the Application Server Toolkit. On the Host List page of the wizard, you specify computers that can access the Agent Controller you are currently installing. Usually these are the computers on which the Application Server Toolkit is installed.
- The This computer only radio button does not allow any computer other than this one to access Agent Controller. This is the default.
- The Specific computers radio button allows you to specify the host name or the network name of one or more computers that can access Agent Controller. The host names are specified as a space delimited list.
- The Any computer radio button allows all computers to access Agent Controller.
On the Security page of the wizard, specify whether Agent Controller will require encrypted and authenticated communications. If security is disabled, only the host list is used to control access to Agent Controller. If security is enabled, clients are only able to connect to Agent Controller if they contain the necessary certificates to authenticate Agent Controller for Secure Socket Communications. Also, all clients are required to log in to Agent Controller. By default, security is disabled. By default, Agent Controller service starts automatically when it is installed and then whenever you start your system. Refer to the online help for more information about working with Agent Controller.
The following links will only resolve from the English version of the release notes.
(C) Copyright IBM Corporation 2002, 2003. All Rights Reserved.