IBM VisualAge for Java

Access Builder for SAP R/3 - autoCreateRfcModule() does not work for parameterless RFC Description This fix is to correct the following problem which exists in VisualAge for Java, v2.0 and in the Access Builder for SAP R/3 fix pack 2.02.1 autoCreateRfcModule() does not work for a parameterless RFC e.g. RFC_PING. Applicable product versions Product Version: 2.0 Product Platforms: All Languages: All Files com\ibm\sap\bapi\bor\RfcFunctionInfo.class SAPRfcPing.htm (this readme file) Prerequisites VisualAge for Java, Enterprise Edition, v2.0 Rollup 2 Access Builder for SAP R/3 and C++, Fix pack 2.02.1 Installation Unzip the zip file into an empty directory Apply the fix to your VisualAge for Java Workspace as follows: Start VisualAge for Java Select the project "IBM Access Builder for SAP R3 Libraries" Select menu "File->Import" Choose to import from a directory Select the directory where you unzipped this fix. Select ".class" files as the files you want to import Make sure that the option "Create new/scratch edition of versioned projects/packages" is checked Click the Finished button Apply the fix to your application running outside VAJ Put the class file in a directory where you may also provide other Java classes. Ensure to keep the directory structure as used in the zip file. Edit the CLASSPATH and make sure that this directory is found *before* ivjsap11.jar Apply the fix to your Access Builder for SAP R/3 tool Unzip the zip file into the Access Builder for SAP R/3 tool directory (<root>\ide\tools\com-ibm-sap-bapi)

TITLE: Multiple breakpoints DESCRIPTION =========== This fix is to correct a problem which exists in fixpack2, rollup1 and rollup 2. Changes to methods which affect more than one breakpoint will result in a message indicating that the Workspace is corrupt. Following this the user will not be able to save the Workspace. APPLICABLE PRODUCT VERSIONS =========================== Product Version: 2.0 Product Platforms All Languages: All FILES ===== 1f41ux2.tfs 1f41ux2.tfi 1f41ux2.txt (this readme file) INSTALLATION ============ 1. Unzip 1f41ux2.zip into the directory in which you installed VisualAge for Java. 2. Start VisualAge for Java 3. Choose Workspace -> Tools -> Fix Manager 4. Select: 1f41ux2 - Multiple breakpoints Click the >> button Click OK Confirm that on the left side of the Fix Manager dialog there is now a * (asterisk) to the left the line 1f41ux2 - Multiple breakpoints Click Close 5. File -> Exit VisualAge Click OK Important: You must exit VisualAge for Java and restart it before this fix takes effect.

TITLE: Can't open VCE after installing rollup 2 Important! This fix was previously available as 1f6xh0w.zip. It has now been replaced with 1f6kurp.zip. If you have previously installed 1f6xh0w.zip, you must replace it with 1f6kurp.zip by following steps 1 to 3 below. Otherwise, directly install 1f6kurp.zip. 1.Delete the following files from INSTALLDIR\ide\_update: 1f6xh0w.tfs 1f6xh0w.tfi 1f6xh0w.txt 2.Reinstall Rollup2. Make sure you read the instructions before you reinstall Rollup2. 3.Install 1f6kurp.zip. Follow the instructions below. DESCRIPTION =========== This is another problem similar to 1f6xh0w. After installing Rollup2 if you try to open or use a class who is inheriting features, you will get an exception or a debugger. APPLICABLE PRODUCT VERSIONS =========================== Product Version: 2.0 + Rollup2 Product Platforms All Languages: All NL FILES ===== 1f6kurp.tfs 1f6kurp.tfi 1f6kurp.txt (this readme file) INSTALLATION ============ 1. Unzip 1f6kurp.zip into the directory you install VisualAge for Java. 2. Start VisualAge for Java 3. Choose Workspace -> Tools -> Fix Manager 4. Select: 1f6kurp - Can't open VCE after installing rollup 2 Click the >> button Click OK Confirm that on the left side of the Fix Manager dialog there is now a * (asterisk) to the left the line 1f6kurp - Can't open VCE after installing rollup 2 Click Close 5. File -> Exit VisualAge Click OK Important: You must exit VisualAge for Java and restart it before this fix takes effect.

TITLE: Failure to generate code for settings on TableColumns DESCRIPTION =========== This fixes the problem with TableColumn properties not being saved and generated properly in Rollup2. APPLICABLE PRODUCT VERSIONS =========================== Product Version: Rollup2 Product Platforms All Languages: All NL FILES ===== 1f6mn8x.tfs 1f6mn8x.tfi 1f6mn8x.txt (this readme file) INSTALLATION ============ 1. Unzip 1f6mn8x.zip into the directory you install VisualAge for Java. 2. Start VisualAge for Java 3. Choose Workspace -> Tools -> Fix Manager 4. Select: 1f6mn8x - Failure to generate code for settings on TableColumns Click the >> button Click OK Confirm that on the left side of the Fix Manager dialog there is now a * (asterisk) to the left the line 1f6mn8x - Failure to generate code for settings on TableColumns Click Cancel 5. File -> Exit VisualAge Click OK

README - IBM(R) VisualAge(R) for Java(TM), Enterprise Access Builder for Persistence Rollup2.0 Fixpack DESCRIPTION =========== This fixpack contains fixes to problems that occur with Persistence Builder when the Rollup2.0 update is installed. FILES ===== pbrollup2.zip readme.txt (this readme file) INSTALLATION ============ IMPORTANT: This fix should be installed only after installing the Rollup2.0 update for VisualAge for Java. 1. Unzip the pbrollup2.zip file into your ide\ directory (e.g., C:\IBMJava\ide). 2. Start the IDE 3. Choose Workspace -> Tools -> Fix Manager 4. Select pbrollup2 - Persistence Builder fix for Rollup2 Click the >> button Click OK Confirm that on the left side of the Fix Manager dialog there is now a * (asterisk) to the left of the line pbrollup2 - Persistence Builder fix for Rollup2 Click Close

The Sun Java Server Development Kit (JSDK) provided by Sun Microsystems does not support double-byte characters unless the charset is specified by setting the content-type as indicated above. The IBM WebSphere Application Server will use the character set of the incoming request as specified by the web browser to set the character set of the response. A modified version of the JSDK is available from IBM which provides this capability. When imported into VisualAge, this updated version of the JSDK has a version number of 2.0 NL on the "Sun JSDK class libraries" project. Instructions for loading the updated JSDK: 1) Download the new JSDK and unzip into a .dat file (VisualAge import) 2) Import the project: "Sun JSDK class libraries" version 2.0 NL from the .dat file. 3) Go to your console and close any running processes 4) Load the Servlet Builder feature if not already loaded 5) Load the 2.0 NL version of the Sun JSDK class libraries project ====================================================================== VisualAge for Java Version 2.0 Servlet Builder RELEASE NOTES for Windows, AIX, and OS/2 December 21, 1998 ======================================================================= Table of Contents ----------------- 1.0 Where is it? 2.0 *Important* Deployment Information 3.0 Documentation 4.0 National Language "char-set" and JSDK Considerations 5.0 JSDK Post Problem on Windows 95(tm) 6.0 Slow First Open 7.0 HTTP Server Configuration 8.0 Browser Configuration 9.0 IP Configuration 10.0 Production Server Must Support 1.1 Servlets 11.0 404 Class Not Found on Production Server 12.0 Troubleshooting Tip 13.0 JDBC Sample 14.0 Create Visual Servlet Smart-guide with New Projects and Packages 15.0 Default CODE Value in HtmlServlet Bean 16.0 Run Button Considerations ================================== 1.0 Where is it? To enable the Servlet Builder, go to the Workbench File menu, select "Quick Start", "Features", "Add Feature", and select "IBM Servlet Builder 2.0". You must load the Servlet Builder feature using the Quick Start menu; if you just load the projects from the repository, the visual construction and run button support will not be properly initialized. These release notes apply to all versions of the Servlet Builder, including: 2.0 on Windows, AIX, and OS/2 2.0.2 NL on Windows, AIX and OS/2 2.0.3 on Windows 2.0 *Important* Deployment Information When deploying servlets built using the Servlet Builder, your visual servlets must be in the class path as well as in the Web server's "/servlets" directory. The symptom is that form data button press events are not processed. The easiest way to do this is to add the servlet directory to the class path. When using WebSphere Application Server, the class path is set in the administration applet (http://myserver:9090). This requirement will be removed in a subsequent release of the Servlet Builder. In addition, to run visual servlets from a production web server, you must include the project "IBM Servlet Builder class libraries" in your class path. This project is exported in the following files in your VisualAge directory tree: /eab/runtime20/ivjsb20.jar, and /eab/runtime20/ivjsb20.zip. When using WebSphere, the .jar file must be added in the class path using the administration applet. 3.0 Documentation Please refer to the documentation for help getting started using the Servlet Builder feature. From VisualAge IDE, select "Help"->"Concepts", then from the Web Browser, expand, "Visual Composition" and "Servlets", then select "Servlet Overview". 4.0 National Language "char-set" and JSDK Considerations The Sun Java Server Development Kit (JSDK) provided by Sun Microsystems does not support double-byte characters unless the charset is specified by setting the content-type as indicated above. The IBM WebSphere Application Server will use the character set of the incoming request as specified by the web browser to set the character set of the response. A modified version of the JSDK is available from IBM which provides this capability. When imported into VisualAge, this updated version of the JSDK has a version number of 2.0 NL on the "Sun JSDK class libraries" project. Instructions for loading the updated JSDK: 1) Download the new JSDK and unzip into a .dat file (VisualAge import) 2) Import the project: "Sun JSDK class libraries" version 2.0 NL from the .dat file. 3) Go to your console and close any running processes 4) Load the Servlet Builder feature if not already loaded 5) Load the 2.0 NL version of the Sun JSDK class libraries project The Servlet Builder does not specify a charset when generating servlets. If your servlet needs to specify a "char-set" property, you must do one of the following: a) On the free-form surface, connect the "request received" event to the "contentType" property of the servlet (i.e., connect from the free-form surface to the free-form surface). Then open the properties of the connection, and use the "Set Parameters" button to change the parameter of the connection. Change the parameter to specify the content type including the char-set value. For example: Simplified Chinese: \"text/html; charset=iso-2022-cb-ext\" Traditional Chinese: \"text/html; charset=x-euc-tw\" Japanese: \"text/html; charset=iso-2022-jp\" Korean: \"text/html; charset=euc-kr\" b) Modify the initialize method of the servlet to set the content type and charset by adding one of the following lines of code: setContentType("text/html; charset=iso-2022-cb-ext"); setContentType("text/html; charset=euc-tw"); setContentType("text/html; charset=iso-2022-jp"); setContentType("text/html; charset=euc-kr"); There are many other charset's; some places to go to find them are: http://people.netscape.com/ftang/meta.html ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets In order to test using double-byte character sets (DBCS), your Web Browser must be properly configured to do so. This includes setting the view encoding and font supported by the browser. Some browser versions do not support DBCS characters. In some cases it is easier to configure the Web Browsers available on Windows operating systems rather than AIX and OS/2. In this case, you may consider using a Windows system to open a web browser with a URL that points at your development system on AIX or OS/2. The JSDK also has documented problems related to the use of Session data with the Japanese (ja_JP) UNIX locale. Due to these problems, please use the Japanese (JA_JP) UNIX locale for Session data support with the Servlet Builder component. DBCS strings in cookies is currently not supported in servlets. On some DBCS systems (e.g., Korea), the "Swing" Beans Palette will be the default palette when visual servlets are opened. In this case, you must switch to the "Servlet" (or translation of "Servlet") category which appears in the list of palette categories on the left-hand side of the Visual Composition Editor. 5.0 JSDK Post Problem on Windows 95(tm) Some version of the Sun JSDK (and Sun JavaServer) do not support POST on some configurations of Window 95(tm). The symptom is a message in the browser that says "connection reset by peer". The Servlet Builder samples which use POST may not work on Windows 95. If you are running Windows 95 and experience this problem, you can change the "method" property on the form parts from "POST" to "GET" and the servlet will work properly. 6.0 Slow First Open The first time you open a visual servlet, there may be a significant delay as some initialization is done and caching is set up. Subsequently, opening a visual servlet will be much faster. 7.0 HTTP Server Configuration In version 2.0.2 NL and 2.0.3, the configuration file is located in: (directory name is wrapped): ...project_resources/IBM Servlet IDE Utility class libraries/com/ibm/ivj/ servlet/runner/configuration.properties In version 2.0 of the Servlet Builder, the configuration file is located in (directory name is wrapped):: ...project_resources/IBM Servlet Builder class libraries/com/ibm/ivj/ servlet/runner/configuration.properties contains several properties which can be set to change the way HTTP servers are started and the web browser is launched. Since some systems do not work when the browser is launched against IP 127.0.0.1, you may need to change this file to point at "localhost", or your PC's host name or IP address. The default server port is 8080; if you want to run a production web server on your system which uses port 8080, then you can change the default port in the configuration file to another value, such as 8081. This way you can easily test in both production and development modes. If you install version 2.0.2 NL or 2.0.3 over version 2.0, you should rename or delete the 2.0 configuration file in .../IBM Servlet Builder class libraries/... 8.0 Browser Configuration The default web browser launched for servlets is the same one used for VisualAge help. Changing the option on the help page for browser configuration will change it for servlet launching too. The configuration file in the above item can be changed to change the browser launch characteristics, such as the IP and port on which to launch the browser. On Windows, if the default configuration says "use file association", then the Servlet Builder will only launch the browser properly is a "URL association exists. A URL association is established when newer versions of Netscape and Internet Explorer are installed. The "file association" with .html files is not sufficient since the Servlet Builder launches the browser on a full URL prefixed by "http://". 9.0 IP Configuration Some system which use Microsoft Internet Explorer as their default browser cannot access IP 127.0.0.0, which is the default value used to point back to the current machine when the "run" button is pressed for visual servlets. There are two ways to fix this. First, you could modify the configuration file mentioned above to change the "serverAddress" value to your host name or IP address. Second, you can modify Internet Explorer to accept 127.0.0.1. From Internet Explorer, select view -> internet options -> connection tab -> Check Access Internet using a proxy server -> Click "Advanced..." button to see the Proxy Settings Window -> In the "Exceptions" group in the "Do not use proxy server for addresses beginning with:" area, enter 127.0.0.1 -> OK -> OK. 10.0 Production Server Must Support 1.1 Servlets When you deploy your servlet in your production environment, you must use a Web server which supports Sun's 1.1 version or later of the JDSK. To upgrade your Web server to the support the latest version of servlets, you can configure it for use with the IBM WebSphere Application Server (which includes the software formerly known as ServletExpress). IBM WebSphere Application Server runs on major industry HTTP servers including Netscape Enterprise Server, Netscape FastTrack Server, Microsoft Internet Information Server, Apache Server, and the Lotus Domino Go Webserver. For more information, see: http://www.software.ibm.com/webservers/appserv/ When using WebSphere, the class path is set using the administration applet loaded by referencing: http://myserver:9090 The ivjsb20.jar file and the servlet path must be added to the class path using this interface for runtime visual servlets to be work properly. In version 2.0.3, the servlet path no longer needs to be added to the class path. 11.0 404 Class Not Found on Production Server When you deploy a servlet in the /servlets directory of your production system, you will get a "404 Class Not Found" error if the class cannot be constructed. This often occurs if other classes such as Swing TableModel classes are not in the class path for the servlet being loaded. Make sure that the classes that your servlet uses are in the class path for your server. 12.0 Troubleshooting Tip If you are having trouble loading your servlet from a Web browser, you may want to try it using the Router class by using a URL that looks like this (the URL is wrapped): http://myserver:8080/com.ibm.ivj.servlet.http.Router/ com.ibm.ivj.servlet.sample.HelloWorldSample This will load the Router servlet which then loads the target servlet (HelloWorldSample in this case). For your tests, change the HelloWorldSample class to your servlet class. 13.0 JDBC Sample To use the JDBC sample, you must have JDBC properly installed and configured. See the README servlet in the com.ibm.ivj.servlet.sample.jdbc package. 14.0 Create Visual Servlet Smart-guide with New Projects and Packages The "Create Visual Servlet" smart-guide does not function correctly when creating new projects or packages. Instead, use the browse buttons to select projects and packages that have already been loaded into your workspace. 15.0 Default CODE Value in HtmlServlet Bean When dropping the HtmlServlet bean, the default value for the 'code' property is None (NULL). This value will not allow you to save the bean you are editing in the VCE. If you want a value of None, select the code property in the property sheet editor and choose the 'Service Handler:' radio button. Then select '<None>' from the drop down list box. 16.0 Run Button Considerations Under some conditions, when pressing the run button, the browser will launch before the web server has started. If this occurs, simply press the run button again after the server starts. In version 2.0.3, the serverPollingCount option in the configuration.properties file may be adjusted to increase the maximum time spent waiting for the server to start. When a class in VisualAge is changed by adding a field, all processes associated with that class are terminated. So, if you press the run button from a servlet to start your web server, then change the servlet and re-save, the server process may be terminated. To prevent this, press the run button for a sample or other visual servlet which you will not be changing. Thus, the server will not be terminated when the servlet you are working on has changed.

================================================================== VisualAge for Java Version 2.0 Rollup 1 INSTRUCTIONS ================================================================== TITLE: Rollup 1 DESCRIPTION =========== Rollup 1 contains fixes for a number of bugs in different areas of VisualAge for Java 2.0 FILES ===== 1f1xwqq_xxx.zip (where xxx is win, os2 or aix) readme.txt (this file) INSTALLATION ============ Note: As part of the installation of Rollup 1, the Workspace will be replaced. This new Workspace will only have the system Projects added. Workspace Recovery will rebuild the Workspace by adding all the user Projects that were in the Workspace before Rollup 1 was applied. The Projects (and all their contents) will be at the exact version/edition level they were at prior to installing Rollup 1 (including all tool data). Workspace Recovery will NOT recover scrapbook contents or Visual Composition Editor contents. 1. Prepare for Rollup 1 - Save any Scrapbook pages - Save any open Visual Composition windows - Exit the Workspace by choosing File -> Exit VisualAge... Note: If you do not want Workspace Recovery to rebuild your Workspace, at this point you should version all of your Projects and delete them from the Workspace. 2. Unzip 1f1xwqq_xxx.zip (where xxx is win, os2 or aix) into the install directory created when VisualAge for Java was originally installed. Note: Unzip should be set to OVERWRITE existing files of the same name and path. 3. Run VisualAge for Java. If there were User Projects in the Workspace before Rollup 1 was installed, Workspace Recovery will try to rebuild the Workspace. A dialog will appear with the following text: The Workspace is not consistent with the Repository Attempting to rebuild the Workspace Please wait... Note: The process could take a few minutes, depending on the amount of work in the Workspace before Rollup 1 was applied. Note: If your workspace does not get recovered automatically, then you can manually add your projects to the workspace 4. Confirm that Rollup 1 has been installed properly. Select Workspace -> Tools -> Fix Manager. Check that Rollup 1 is listed on the left hand list: *1f1xwqq_xxx - Rollup 1 (where xxx is win or os2 or aix) NOTE: If *1f1xwqq_xxx - Rollup 1 is not present, the probable cause is that Rollup 1 was unzipped into the wrong base directory. A common error is to unzip Rollup 1 into the ide directory. Rollup 1 should be unzipped into the directory that contains the ide directory. 5. If Step 4 was successful, save the Workspace before continuing. Select File -> Save Workspace Click OK

This is a fix for problems with DBCS development using the CICS Access Builder in versions 1.0x of VisualAge for Java. To install this fix you need to import the three replacement class files in the IBM Enterprise Access Builder Libraries project within the COM.ibm.ivj.eab.cics package. To do this: Select the "IBM Enterprise Access Builder Libraries" project and Import the three class files in this zip file. You will not need to regenerate any of the COMMAREA beans. You should also change the two archives which are in the \IBMVJava\eab\runtime directory called "ivjeab.zip" and "ivjcics.jar". These two archives both contain the runtime packages for the CICS Access Builder which you would use when you deploy your application. You can use any zip program you like to replace the class files within these archives, but you must make sure that the replacement class files, have the exact same directory structure as what is already in these archives.

name: Choice does not send ItemChangedEvent on Patch Set 2. product-version: 1.0 product-patch-level: Patch Set 2 platform: all depends-on: incompatible-with: supercedes:

Name: JNI function GetMethodID() fails for inherited methods (FP1) Product-Version: 1.0 Product-Patch-Level: (Patch Set 1), Patch Set 2 Platform: ALL Depends-On: Incompatible-With: Supercedes:

Question: Why does Data Access Builder fail when I try to reload or resave a session? Answer: If the table you have mapped to has foreign keys, then Data Access Builder traps when you try to reload or resave the session, depending on how the builder was launched. If you launched Data Access Builder from the Integrated Development Environment Workbench and then mapped to a table with foreign keys, you will not be able to reload the resulting session. In this situation, you must be sure to correctly map and generate code before you exit the session the first time. If you launched Data Access Builder from the command line and then mapped to a table with foreign keys, you will be able to reload and regenerate code from the saved session, but you will not be able to make and save any changes to the mapping once you reload. Tempfix: Please replace the corresponding dll on your VisualAge for Java installation. On OS/2, this dll is found in IBMVJAVA\EAB\DLL.