iPlanet Application Builder

Release 6.0 Service Pack 1

Release Notes

Updated January 4, 2001


Contents


What's New

04 Jan 01: Added bugid 526144


System Requirements

The hardware and software requirements for installing and running the Application Builder are as follows:

  NT Machine Solaris Machine
Operating System: Intel Pentium microprocessor running Microsoft Windows NT version 4.0 with Service Pack 5 Solaris 2.6 or 8.0
Memory: 128 MB minimum; 256 MB recommended 128 MB minimum; 256 MB recommended
Available disk space: 220 MB, plus 120 MB temporary space 220 MB, plus 120 MB temporary space
Network software: TCP/IP TCP/IP
Web server: iPlanet Web Server (Enterprise Edition) version 4.1 iPlanet Web Server (Enterprise Edition) version 4.0 or 4.1
Application server: 1 iPlanet Application Server Version 6.0 SP 1 iPlanet Application Server Version 6.0 SP 1
Database connectivity: (optional)
Database Client Database Server
Oracle 8.1.5 and 8i Oracle 8i and 7.3.4
ODBC 3.5.1 and 3.6.0 MS SQL Server 7.0, OBDC 3.5.1 and 3.6.0
Sybase Open/Client System 11.1.1 Sybase 11.9.2, 12
Informix 2.4 Informix 9.1.4
DB2 5.2 DB2 5.2, 6.1
Database Client Database Server
Oracle 8.1.5 and 8i Oracle 8i and 7.3.4
Sybase Open/Client System 11.1.1 Sybase 11.9.2, 12
Informix 2.4 Informix 9.1.4
DB2 5.2 DB2 5.2, 6.1

1 It is assumed that you are installing the Application Server along with the installation of the Application Builder.


Before You Begin

Before you install the Application Builder tool, you need to:

For more information on upgrading the Application Server installation, see the iPlanet Application Server Installation Guide V6.0 SP1. It is also recommended that you read the Release Notes for the Application Server Service Pack 1 Revision B release.

Please note that the EZSetup installation option is NOT recommended for upgrading your release. It is intended for quick installations for evaluation purposes ONLY.


Known Issues and Limitations

Resolved Issues

The following issues have been resolved in the iPlanet Application Builder 6.0 Service Pack 1 release.

ID Summary
388231 Links created in the HTML Designer are now getting removed.
393005 You now can start the web server from within the Application Builder even if the server is stopped.
393211 The EJB wizard now persists options.
393303 Edit/Replace now works.
393655 Arbitrary filetypes can now be added to a project. They show up under miscellaneous files and are packaged with the project.
394186 Remove EJB now removes from the file system.
394464 The Deployer no longer converts filenames to lowercase.
396719 Pressing the enter key no longer submits null data in the Search page.
397114 The CMP mapping is now correct with the database fields.
397215 Projects with EJBs now save properly.
397948 The correct code is now in the EJBname-ias-cmp.xml for findByPrimaryKey().
398149 Database wizard using existing query file with condition problem has been fixed.
398190 The problem with copying from the Application Builder to other applications has been fixed.
399612 EJB support files now get deployed into the .jar file.
404721 An application built with NAB 3.0 does not work on iAS 6.0. It generates a class not found exception. In the <ias>/lib/java directory, there is a NAB25.jar. User kregedit to add this to the application server's CLASSPATH.
445611 The problem with EJB compilation throwing an error in some cases has been fixed.

Known Issues

The following issues have been addressed in this release and a workaround is provided.

ID Summary
339646 The iAS/iAB uninstaller will revert the iWS configuration file to the state it was in when iAS/iAB was installed.
Workaround: See the Java Programmer's Guide for complete instructions on backing up your configuration file.
360537, 434909 Undo for creating a link/form by dragging a servlet to a page now works.
362410 Problem with change of IP Address.
Workaround: Open kregedit and select the "Change IP Addresses" option to edit the IP Address as desired.
368603 Uninstall takes approximately 40 minutes or more to uninstall.
381104 Arbitrary binary data, like uploaded files or images, can be problematic, since the web connector translates incoming data into name-value pairs by default.
Workaround: By default, the Application Server Version 6.0 tries to translate the incoming binary data from Post into name-value pairs. If you need to pass this data as is to the AppLogic/Servlet, you need to perform the following changes:

  1. Edit your registry to include a new key called SendRawPostData of type DWORD with a value of "1" under the HTTPAPI key. (restart your web server)
  2. The post data you upload to the Applicaiton Server will be sent through to the servlet as a valIn/Request parameter with the name "HTTP_POST_BODY"... When using valIn, please use getValBlob() to get the data.
  3. If you want to change the name of this valIn/request parameter add another key under HTTPAPI called PostDataToken of type string and enter the name you want your valIn name/request parameter to be called. For example, "MyPostData."
387657 NAB/NAS 4.0 currently does not support DHCP.
Workaround: Set a static IP Address by manually changing the IP Address and setting it to the loopback IP Address of 127.0.0.1.
392373 The Editor window, once minimized it could not be closed at all.
Workaround: instead of minimizing the Editior window, exit and restart.
392555 From the Project menu, selecting Deploy does not work if the server was started from within the Application Builder. During local deployment from within the Application Builder, only the KXS and KJS engines are started because they are the only engines necessary for testing from within the Application Builder.
Workaround: Start the Application Server from the services, then select Deploy from the Project menu for your local deployment. This overwrites your current classes.
393001 The Format/Alignment menu does not support multiple lines of text.
Workaround: Select each line and align it separately or use a third party tool to format your HTML pages.
393210 Dragging RDBM tags does not add the taglib directive.
Workaround: You will need to do this for each taglib you reference.
365142 Unable to locate a Project or Directory after changing the Project/Directory name.
Workaround: Create a new project and import the files from the old project to the new project. The project information is stored in a lot of places so it is not easy to change them all.
392123 The supported version of Visual Cafe is not specified in the User's Guide.
The supported version is Visual Cafe Enterprise Edition 4.0.
397216 Problems connecting to Oracle database from within the Application Builder.
Workaround: Make sure ORACLE_HOME variable is set in the environment properties.
397951 No code generated in the XML file for custom finder methods.
Workaround: You will need to edit the XML file to add custom finder methods.
401453 Problems connecting to MS SQL Server from within the Application Builder.
Workaround: Make sure you are using ODBC drivers 3.5.1 or 3.6. Later driver versions are not supported in this release.
402515 On solaris if you don't have write permission to <ias>/APPS and <ias>/APPS/ejb you won't be able to create projects successfully.
Workaround: Users should only run the Application Builder with the same permissions as the user that installed the Application Builder and the Application Server.
431290 When importing a packaged servlet outside of the Application Builder and placing it into a package such as com.company.myapp, the deployment fails.
Workaround: You must change the name of the servlet path from /com/company/myapp/serv to just serv.
434909 Some Undo actions are not undoable.
Workaround: If Undo does not work, then you will need to manually revert the change.
473689 While using the Application Server Visual Cafe Integration instructions, an error message appears while running the main class of the project.
Workaround: You must include the \iPlanet\iAS6\ias\usr\java\lib\ext\iioprt.jar in your project/options/ directories setting.
505681 During the deployment process, the deployer locates your HTML files under the iAS root directory.
Workaround: To access your HTML page, you must:
  1. Copy the HTML files to the webroot directory on the deployed machine.
    For example: http://foo.bar.com/bar/index.html
  2. Make sure the links in your file work properly.
Additionally, you can workaround this issue by leaving the HTML files as they are and changing the URL pointer to http://foo.bar.com/NasApp/bar/index.html and making sure the URL in your file are still pointing to the correct files.
512615 The Application Builder installer puts a new entry called iPlanet server products in the start menu.
Workaround: Ignore the ReadMe icon under this menu.
514980 Insert Table based on Resultset not putting complete code.
Work around: A sample code generated by this process is <rdbm:loop id="aa" query="vij"> Which should be <rdbm:loop id="mainLoop1" query="vij" start="vijStart" max="1" execute="true">
515191 If some text in JSP/HTML is selected and then made into a link, when the user selects the Destination URL in the Properties window, the Normal java files also show up.
Workaround: Select only the servlets, Not the plain java files.
515197 Sticky bit problem.
If you intend to have load balancing in a disrtibuted fashion, the sticky bit for the serlvet in the servlet Descciption should be set. This option is under the Application Server tab in the servlet meta Editor. By default this is not set.
526144 Do not use '&' or any other non-alpha characters in any file names.
NONE EZSetup is problematic when upgrading from 6.0 to Service Pack 1 release.
Workaround: It is recommended that you DO NOT use the EZSetup feature when upgrading.
NONE Third party JDBC drivers are NOT supported through the wizards.


Documentation Resources

The product readme.txt file directs you to an incorrect pointer for the iPlanet Application Builder documentation. The correct location for the iPlanet Application Builder 6.0 Service Pack 1 documentation can be found at: http://docs.iplanet.com/docs/manuals

Select the Application Server link, then find the Application Builder link to access the latest documentation including:


Reporting Problems

Online and telephone Technical support can be found at: http://iplanet.com/support/online/ For all iPlanet Application Builder documentation, including the Installation Guide, and updated release notes, refer to: http://docs.iplanet.com/docs/manuals/


Uninstalling

To uninstall the iPlanet Application Server and the Application Builder Version 6.0:

  1. From the Start menu, select the iPlanet Application Server Uninstaller.

    Make sure the directory is up and running before proceeding with uninstallation. If it is not running, you will encounter a timeout delay while the Uninstaller attempts to access the directory.

  2. Select the following components to uninstall:
    • iPlanet Application Server 6.0
    • Administration Services
    • Application Builder
  3. Proceed with the rest of the uninstall program.
  4. Run the uninstall program once more.

    The program will not be available from the Start menu. However, you can locate it on your system.

  5. Select the following components to uninstall:
    • Directory Suite
    • Netscape Server Family Core Components
  6. Proceed with the rest of the uninstall program.
  7. Reboot your machine.
  8. Delete the iAS install directory. Remember to keep the ias\APPS directory which contains your projects.


Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions copyright © 2000 Netscape Communications Corp. All rights reserved.