Documentation - release notes

1.0 Introduction
2.0 Known problems and limitations
   2.1 Struts documentation updates
   2.2 JNDI name of Onlineitem bean incorrect in Online Auction scenario document
   2.3 Installing Agent Controller on an iSeries system
   2.4 Installing Agent Controller Version 5.0.2 on Linux
   2.5 Updates to "Creating a JDBC connection using a Cloudscape driver"
   2.6 Web project folder names
   2.7 5.0.1 is an English-only release

1.0 Introduction

This readme file pertains to the online documentation provided with WebSphere Studio.

2.0 Known problems and limitations

2.1 Struts documentation updates

Getting Started Guide Struts sample

In the Getting Started Guide under "Loading the Struts Trade Sample," 4.0 should be changed to 5.0 and 8080 should be changed to 7080 in the following bullet item: Created a server project named Trade Server, which runs in the WebSphere version 4.0 test environment and listens on TCP/IP port number 8080.

2.2 JNDI name of Onlineitem bean incorrect in Online Auction scenario document

In the 'Test the business methods section' of the 'Working with the Online Auction sample application' topic, all instances of the word OnlineitemHome should be replaced with OnlineitemLocalHome. The corresponding screen capture for this task is also incorrect. For example, step 3 of that subsection should read:

3. Click the OnlineitemLocalHome link.

2.3 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.4 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.5 Updates to "Creating a JDBC connection using a Cloudscape driver"

Steps 7 to 9 in the relational database tools help topic called "Creating a JDBC connection using a Cloudscape driver" should read:

  1. If connecting to an existing Cloudscape database, type the fully qualified location of the Cloudscape database in the Database location field. To create an empty Cloudscape database used to test your applications, type:
    <Cloudscape_dbdir>\<database_name>;create=true
    (where <Cloudscape_dbdir> is the directory on your file system where you want the Cloudscape database to be located, <database_name> is the name of the database that you provided in step 2, and "create=true" creates the Cloudscape database).
  2. Type the class location containing the JDBC driver in the Class location field. For example, <WS_instdir>\runtimes\base_v5\lib\db2j.jar (where <WS_instdir> is the path where you have installed WebSphere Studio). If Other Driver was selected from JDBC driver pull-down list, then the Class location field is enabled allowing you to either type or select the appropriate driver class location.
  3. The Connection URL field is pre-filled and disabled with the URL connection. This URL is in the form of jdbc:db2j:<subsubprotocol><database_name> (where <database_name> is the name of database that you provided in step 2 and <subsubprotocol> is the location where Cloudscape looks for a database, such as in a directory, in a class path, or in a jar file). Refer to the Cloudscape Developer's Guide (located at www.ibm.com/software/data/cloudscape/pubs/collateral.html) for examples of database connection URLs. However, if Other Driver was selected from JDBC driver pull-down list, then the Connection URL field is enabled allowing you to either type or select the appropriate URL connection.

2.6 Web project folder names

The correct default names for the configurable folders in a Web project are Web Content and Java Source, not WebContent and JavaSource.

2.7 5.0.1 is an English-only release

5.0.1 is an English-only release. Translated documentation is not available.

Return to the main readme file