VisualAge(R) for Java(TM)
Version 3.5

Documentation

RELEASE NOTES

This document is divided into two parts. 

Part I contains a list of critical changes to the online information (sorted by component in alphabetical order) that were not translated. All of  the information listed in Part I, except for the Enterprise Toolkit for AS/400, is available from the English PDF files, which can be found in the "pdf" directory on the product CD. Some of the updated English information for the Enterprise Toolkit for AS/400 is not included in the English PDF files.

Part II contains any corrections to the English documentation that is not associated with a specific VisualAge for Java component. Part II also contains information about articles, scenarios, and examples related to VisualAge for Java found on VisualAge Developer's Domain (VADD) Web site.

Table of Contents

Part I

  1. C++ Access Builder
  2. Distributed Debugger for AS/400 (R)
  3. Distributed Debugger for Workstations
  4. Domino Access Builder
  5. Domino AgentRunner
  6. EJB Development Environment
  7. Enterprise Access Builder for Transactions
  8. Enterprise Toolkit for AS/400 
  9. Enterprise Toolkit for OS/390 (R)
  10. External Version Control
  11. Getting Started Guide
  12. IDL Development Environment
  13. IMS(TM) TOC Connector
  14. Integrated Development Environment
  15. JSP/Servlet Development Environment
  16. SAP Access Builder
  17. Team Programming Environment
  18. WebSphere(TM) Test Environment 
  19. XMI Toolkit
  20. XML Parser for Java
  21. Persistence Builder

Part II

  1. Getting Started Guide - English updates
  2. VisualAge for Java articles, scenarios and examples

Part  I

1. C++ Access Builder

VisualAge for Java no longer supports the command-line interface as a development environment for the C++ Access Builder.

In the Java 2 platform, V1.2.2, tighter security restrictions exist for applets that access files. To avoid the complexities associated with these tighter security restrictions, applets used in the C++ Access Builder sample have been rewritten as applications instead.

Before using the C++ Access Builder, you must set up your C++ compiler environment. If you want to set up the C++ compiler environment from the command line, you can use the ivjenv.bat file found in the following path (where path is the install path of VisualAge for Java): 

path\ide\program\ivjenv.bat

This will start the VisualAge for Java IDE from the command window where you ran ivjenv.bat. 

For additional information, see the English version of the PDF file for the C++ Access Builder.

2. Distributed Debugger for AS/400

  1. A feature of the debugger that has only been documented ináEnglish is the ability to debug servlets, JavaServer Pages (JSP), and Enterprise JavaBeans (EJB). Debugging these requires that the IBM Distributed Debugger for AS/400, Object Level Trace (OLT), and The Administrator's Console for WebSphere Application Server (WAS), Version 3.02 or 3.5 be installed and used on the client machine during debug preparation. In addition, the WebSphere Application Server, Version 3.02 or 3.5, must be installed and used on the AS/400 server.
  2. The following concept file has been added:
  3. The following task files have been added:
  4. The following reference files have been added:
  5. The following task file have been changed:

3. Distributed Debugger for Workstations

  1. The "Starting the debugger on Solaris" (TM) file also applies to debugging programs running on HP-UX.
  2. The "Attaching to a running virtual machine" file is missing the following information for the Java 2 platform:

    You can attach to an already running Java Virtual Machine (JVM) if you start your Java 2 platform application with the following command:

    java -Xdebug -Djava.compiler=NONE
    -Xbootclasspath:<path\YourAppJarFile>;<path\dertrjrt.jar>;
    %JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\jre\lib\rt.jar;%CLASSPATH%
    yourapp fdf

    where:

    <path\YourAppJarFile> is the fully qualified path to your client application JAR file.
    <path\dertrjrt.jar> is  /usr/idebug/lib/dertrjrt.jar on AIX(R),  /opt/IBMdebug/lib/dertrjrt.jar on Solaris (TM), and  x:\IBMDebug\lib\dertrjrt.jar on Windows(R) yourapp is the fully qualified path to your program. 

For example, C:\MyApps\MyAp

4. Domino Access Builder

1. The following task file has been changed - "Verifying your installation"
2. The documentation for samples that contain applets has been changed. 

5. Domino AgentRunner

None of the the Domino AgentRunner help files were translated for this release. All of the NL documentation is at a Version 3.02 level. 

Please refer to the English PDF for the latest version of the documentation. Please note that all of the samples have changed since the last release of VisualAge for Java.

6. EJB Development Environment

The following notes describe the more important changes to the EJB Development Environment that have occurred since the documentation was last translated. For detailed information about these changes, see the English PDF.

  1. Information about EJB migration is now found in the new VisualAge for Java Installation and Migration Guide.
  2. Information on access beans has generally been enhanced and a new reference topic has been added entitled "Example: Using copy helper and rowset access beans". Also, a new lass com.ibm.ivj.ejb.runtime.AccessBeanEnumeration has been added. Additionally, a paper is now available from he VisualAge Developer Domain (VADD) Web site (www.ibm.com/software/vadd) entitled "Developing EJB Access Beans in VisualAge for Java".
  3. Information on developing enterprise beans in a team environment has been enhanced. See the topic "EJB development in a team environment", as well its list of related topics. Additionally, a paper is now available from the VisualAge Developer Domain (VADD) Web site (www.ibm.com/software/vadd) entitled "EJB Team Development in VisualAge for Java".
  4. Information about how to deal with EJB serialization problems is found in a new topic entitled "Handling EJB serialization problems". Additional information is also found in a paper that is now available from the VisualAge Developer Domain (VADD) web site (www.ibm.com/software/vadd). The paper is entitled "Handling EJB Serialization Problems in VisualAge for Java".
  5. You need to change your installation of DB2 so that it uses JDBC(TM) 2.0 instead of JDBC 1.0. Information is found in the topic "Adding a JDBC driver to the class path".
  6. A new Edit CMP Field SmartGuide has been added. You can use this SmartGuide to edit existing fields. Information is found in the file "Adding or editing CMP fields".
  7. The Properties dialog for enterprise beans no longer has a Methods tab and you can no longer set control descriptors from the Properties dialog. Instead, control descriptor properties ate now set from the Members pane using menu items. Information is found in the topic "Setting EJB deployment and control descriptor properties".
  8. The Persistent Name Server (PNS) must still be started before you can start the EJB Server, but the PNS is no longer managed from the EJB Server Configuration browser. It is now managed from the new WebSphere Test Environment Control Center. If you want to change properties for the PNS or start it, from the Workspace menu, select Tools > WebSphere Test Environment. When the WebSphere Test Environment Control Center appears, click the Persistent Name Server entry. (Information about the PNS is found in the online help for the WebSphere Test Environment component.)
  9. The properties dialog for the EJB Server has several new controls. Information is found in the topic "Setting EJB server properties" or by pressing F1 in the EJB server properties dialog.
  10. The EJB test client has been significantly redesigned and you no longer need to generate it. You can now use a single instance of the test client to test multiple enterprise beans. Additional information is found in the topics "Running the test client" and "Using the advanced features of the test client".
  11. If you are deploying your enterprise beans to the WebSphere Application Server, Enterprise Edition, you no longer need to deploy the run-time JAR file that is required for the support of your access beans and associations (if any). Additional information is found in the topic "Deploying the run-time JAR file for access beans and associations".
  12. VisualAge for Java generates code for associations that is different from that in versions 3.0 or 3.02. Metadata for all associations in an EJB group will be migrated the first time you add, edit, or delete an association in the group.
  13. Support for Sybase databases has been added. Information on data-type support has been added: See the "Type compatibility by database vendor." file. See also the release notes for limitations on support of some data types in certain database products.
  14. Support for deployment to the Component Broker tools of WebSphere Application Server, Enterprise Edition has been expanded. See the following files:
  15. In association with the Stored Procedure Builder component, an example has been added to illustrate the usage of stored procedures in an EJB environment. For details, see the file "Example: Wrapping a stored procedure in a session bean."
  16. An example of creating custom finder methods for many-to-many  associations has been added. See the file "Implementing custom finders in home interfaces for CMP entity beans."

7. Enterprise Access Builder for Transactions

The following tools have not been documented in the NL version of the documentation:

  1. The 3270 Importer tool 
    This tool now imports terminal source code and outputs record type and record classes, all in one operation. Get and set methods can be suppressed to reduce generated code size. 
  2. The Record Type Editor pane
    This pane now includes a terminal view of the fields you are diting showing where a field maps to a position on the screen.
  3. IMS Support in the COBOL Importer
    Support for IMS conversational transactions has been added to  the COBOL Importer
  4. Create Business Object SmartGuide
    This new visual tool lets you create an EAB Business Object, which formerly had to be hand coded. Since Procedural Adaptor Objects extend EAB Business Objects, the tool lets you also create PAOs for Component Broker applications accessing data and applications through CCF connectors.
  5. EAB Test Client
    Prior to this tester, Commands and Navigators could only be tested by writing an application to execute them. Now they can be tested anytime after they have been created. This tester lets you check that the returned values are what you  expect, before you have done extensive development. 

The following files have been added or changed significantly:

Concepts
"Enterprise Access Builder for Transactions"
"EAB Test Client"
"Procedural Adaptor Objects"

Tasks
"Importing COBOL source"
"Importing 3270 terminal screen source"
"Creating an EAB Command"
"Testing EAB Commands and Navigators"
"Creating an EAB Business Object and its key"

Reference
"Frequently Asked Questions (FAQs)"

Samples
Most samples incorporate the new tools. Check all of them.

8. Enterprise Toolkit for AS/400

The majority of the Enterprise Toolkit for AS/400 (ET/400) help has changed since it was translated. 
  1. Features of ET/400 that have only been documented in English include:
  2. The following concept files have been added:
  3. The following task files have been added:
  4. The following reference files have been added:
  5. Some samples pertaining to the new DFU, Object List, and JFormatted beans have been added.
  6. The following concept file has been changed:
  7. The following reference files have been changed:
  8. The following feature has been removed since the online help for ET/400 help was last translated:
  9. The following file task has been removed since the online help for ET/400 was last translated:
  10. The following reference files has been removed since the online help for ET/400 was last translated:
  11. The following samples have been removed since the online help for ET/400 was last translated:

9. Enterprise Toolkit for OS/390

  1. The following concept file was added:
  2. The following task files were added:

For other information not contained in the ET/390 documentation, refer to the Run-Time Library Readme and Compiler Readme for VisualAge for Java, Enterprise Edition for OS/390.

10. External Version Control

The "Interface to external version control systems" concept file has been changed.  As well, some of the contextual help files contain titles of fields that do not match the GUI, but the functionality is as described in the file.

11. Getting Started Guide

Please refer to the "Getting Started Guide - English Updates" section in Part II for corrections or additions to the English version of the Getting Started guide.

The following files have been changed:

Refer to the product README for the location of the Server Setup and Administration  guide.

12. IDL Development Environment

If you have been using the IDL-to-Java compiler provided by either the IBM Component Broker Series or the CICS(R) IIOP Server Support feature, you will need to manually define the IDL-to-Java compiler invocation string in the following dialogs:

The IDL-to-Java Compile page of the Options dialog (accessible from the Windows menu)
and the IDL-to-Java Compile Options dialog (accessible from the IDL menu) 

Additional information is found in the English version of the PDF for the IDL Development Environment.

13. IMS Connector for Java 

  1. IMS Connector for Java 3.5.0 was enhanced to support  IMS conversational transactions. Documentation for this support is only available in English and includes a discussion of the IMS Connector for Java programming models  as well as samples that illustrate the programming models.
  2. IMS Connector for Java 3.5.0 includes a new feature,  IMS Connector Samples. This feature includes the new  conversational samples, as well as the samples provided with earlier releases of IMS Connector for Java. Documentation of this feature is only available in English.
  3. IMS Connector for Java 3.5.0 documentation has been updated to use WebSphere Application Server 3.5.0, where applicable. This includes an IVP (Installation Verification Program) servlet used to verify your WebSphere environment. 
    This documentation is only available in English.

14. Integrated Development Environment

  1. The following concept files have been changed:
  2. The following reference files have been changed: 
  3. The following tasks files have been changed: 
  4. The following task files have been added:
  5. The following task files have been removed (no longer applicable):
  6. In the Options dialog, the option "Resources and Paths" is now "Resources".
  7. Several contextual help files only exist in English. Consequently, you may receive a "File not  found" or similar error message if you try to access these files.

15. JSP/Servlet Development Environment

All of the task and sample files have changed since the last time they were translated. As well, two new files were added:

Please refer to the English version of the PDF for the JSP/Servlet Development Environment for the latest version of this information.

16.  SAP Access Builder and Connector 

  1. Two features of the Access Builder and Connector for SAP R/3  have only been documented in English, namely "Connection pooling" and "Generating proxies from command line". Connection pooling  enables you to reuse existing connections to the SAP R/3 system  rather than creating new ones. The second feature enables you to 
    generate proxy beans for SAP Business Objects and RFC modules  from the command line. Please refer to the corresponding tasks in the English PDF for these features. 
  2. The documentation of how to deploy and use EJB bean proxies in WebSphere Application Server Enterprise Edition has been  moved from the readme file of the Access Builder and Connector for SAP R/3 component to the English documentation. This covers the following tasks:
  3. The following task files have been changed:
  4. The following concept files have been changed:
  5. The following sample files have been removed from the Access Builder for SAP R/3 Samples and Connector for SAP R/3 Samples projects and from the documentation:
  6. The following sample file has been added to the Connector for SAP R/3 Samples project and the documentation:

17. Team Programming Environment

  1. The following concept files have been changed:
  2. The following task files have been changed:
  3. The following concept files have been added: 
  4. The following reference files have been removed:
  5. The following task files have been added:
  6. General information that applies to the UNIX platforms (Solaris, AIX, and HP-UX) also applies to LINUX, unless otherwise indicated.

18. Websphere Test Environment

All of the Websphere Test Environment files have changed since they were last translated. Please refer to the English PDF for the latest version of all of these files.

19. XMI Toolkit

  1. Version 1.2.2 of the JDK must be installed on the file system to run the XMI Toolkit,  not version 1.1.2 as documented.
  2. The reference file for the DTDGen bean has changed.

20. XML Parser for Java

  1. The following task information has been changed:
  2. The information about running the samples has been changed.

21. Persistence Builder

The following notes describe the more important changes to the Persistence Builder that have occurred since the documentation was last translated.

  1. Migration information is now found in the new VisualAge for Java Installation and Migration Guide.
  2. Information on migrating Persistence Builder models to the EJB Development Environment has been added. This information is found in the topic "Migrating Persistence Builder models to the EJB Development Environment".
  3. Support for Sybase databases has been added. See the Type compatibility table within the "Defining a Schema" topic. See also the release notes for limitations on support of some data types in certain database products.
  4. Information on using Persistence Builder in the WebSphere Server Environment has been enhanced. A section outlining deployment has been added. See "Deployment issues with Persistence Builder and WebSphere" for details.
  5. New custom query examples and best practices information has been added. Information on creating Business Object (BO) and non-BO custom queries has also been added. See the Custom queries section of "The persistence layer" topic.
  6. The use of parm marker binding in generated service classes greatly improves performance. The caching section of "The persistence layer" topic contains additional information on the use of parm marker binding in Persistence Builder.
  7. OS/390 restrictions on exporting a schema are no longer valid.

PART II

1. Getting Started Guide - English updates

  1. Domino AgentRunner is only available with the Enterprise version of VisualAge for Java.
  2. The PTF level used is PTF5. 
  3. The last paragraph in the "Enterprise Toolkits and optimizing code performance" is now: 
    "In the example below the Enterprise Toolkit for AS/400 has been selected, so you can see its functions (Export, Compile, Run, Debug, Start OLT Viewer, and Start ET400Daemon) and SmartGuides (Create Program Call and Convert Display file). You can select any of these functions or SmartGuides to start using the toolkit."

    The image below the file has been changed as well to match the text.
  4. This information has been added to the "Enterprise Toolkit for AS/400" file:
    "If you wish to debug ET/400 servlets, JavaServer Pages, or enterprise beans, you must also have Object Level Trace (OLT) installed, start the OLT Viewer, and you must be using J2SDK v1.2.2."
  5. As well, the list of beans in the second last paragraph has been changed to: 
    "Included in this set of beans are the following: JFormattedTextField,
    JFormattedLabel, JFormattedComboBox, DefaultFieldModel, AS400FieldModel,
    JFormattedTable, JFormattedTableColumn, JFormattedTextFieldCellEditor,
    JFormattedComboBoxCellEditor, and JFormattedLabelCellRenderer."

The most up-to-date versions of these files (which contain these changes) can be found in the hard copy of the Getting Started Guide. The online documentation and the PDF do not contain these changes.

2. VisualAge for Java articles, scenarios and examples

You can find links to downloads, demos, tutorials, samples, documentation, integrated scenarios and more on the VisualAge Developer Domain (VADD), http://www7.software.ibm.com/vad.nsf. The Library page in the VisualAge Developer Domain site contains links to technical articles, tutorials, white papers, books, magazines, IBM Redbooks, and FAQs about a wide range of Java programming topics. VADD is only available in English.