These installation notes apply to WebSphere Development Tools for iSeries V5.1. This version is designed to be installed only on a PC workstation with one of the Windows operating systems listed below. This version of WebSphere Development Tools for iSeries is only available on CD and DVD.
The README document contains prerequisite information, limitations of the product, and information not included in the documentation.
The Release Notes document describes product components, detailed system requirements, and migration scenarios, as well as the VisualAge(R) for Java(TM) Version 3.5.3 Enterprise Toolkit for AS/400(R) Release Notes.
VisualAge for Java for iSeries 3.5.3 is on CD disk 5 and can be installed before or after the rest of the product. We suggest that you install VisualAge for Java first so that you will be given the option of installing Enterprise Tookit for AS/400 (which requires VisualAge for Java) with the rest of the product. Reboot the workstation after installing VisualAge for Java.
A brief description of the installation process:
When you are asked if you want to reboot during the installation, click Yes, except after MS JVM or IBM's S2JDK installation (if required).
WebSphere Studio installs software that does not have a Microsoft digital signature. When the Digital Signature Not Found dialog box asks "Do you want to continue the installation?", click Yes.
WebSphere Development Tools for iSeries V5.1 cannot be installed on Windows 95.
The product installs one language according to the user locale. If you change the locale after the installation is complete, product components and help screens might not display the correct language. To change languages, completely uninstall the product as described in the How to uninstall section, change the locale and then install the product again.
To view the Distributed Debugger in Spanish, ensure that your machine locale is set to Spanish (Traditional Sort) or Spanish (Spain) before you install the product.
The custom installation allows you to select components provided by this product. Some components must be selected depending on other selections. The table below shows which components have dependencies. The necessary selections are automatic. For example, if you select WebFacing Tool, then CODE and AS/400 Toolbox for Java are also selected.
| This component | requires these components |
|---|---|
| The base for WebSphere Development Tools is always installed | |
| VisualAge RPG | |
| AS/400 Toolbox for Java | |
| CODE | AS/400 Toolbox for Java |
| WebFacing Tool | CODE AS/400 Toolbox for Java |
| Enterprise Toolkit for AS/400 | VisualAge for Java for iSeries 3.5 or later (installed separately) |
| WebSphere Studio for iSeries | |
| Distributed Debugger and NetQuestion are always installed. NetQuestion provides the help system search features. Distributed Debugger, which includes Object Level Trace, can debug both interpreted and compiled Java, as well as other compiled languages, such as C++. | |
| Program | Included with product | Reboot necessary | Installation type | Comments | |
|---|---|---|---|---|---|
| MS JVM | Yes | No | Interactive - launched from installation | Must be installed for Studio DTCs to function properly, but does not need to be the system JVM. | |
| A Java Development Kit | J2SDK 1.2.2 from IBM | Yes | No | Interactive - launched from installation | Required for all CODE/400, VARPG, and WebFacing Tool functions to work. See also README JDK Notes. |
| JDK from Sun | No | No | Manual installation | Version 1.2.x | |
| A frames-capable Web browser | Netscape Communicator | No, obtain from vendor |
No | Manual installation of version 4.7 or higher | Required if no other browser is installed |
| Microsoft Internet Explorer | No, obtain from vendor |
Yes | Manual installation of version 4.0 or higher | Required for some major Studio functions. Not required if Studio is not installed. Version 5.0 is required for WebFacing Tool and other components. For details, see Release Notes Software Requirements. | |
| Other | No, obtain from vendor |
Depends on product | Manual install. Version depends on product. | Other browsers are not supported. | |
To ensure that all components will install and run properly, make the following change:
config.sys file and open it with NotepadSHELL=C:\WINDOWS\COMMAND.COM /p /E:32768If you receive an error message indicating that NetQuestion cannot be installed, it is because the PATH statement in your autoexec.bat file is longer than 200 characters. Shorten the PATH statement to correct this problem.
When NetQuestion is uninstalled (by uninstalling any IBM product that uses it), NetQuestion does not remove its entry in the PATH statement. Repeated uninstalls can result in the statement exceeding 200 characters. Shorten the PATH statement to correct this problem.
Due to a change to Microsoft Installer in the use of environment variables in Windows NT and 2000, follow these rules:
x: refers to the drive where the product is installed.
| System variable name | must include this entry |
| CLASSPATH | x:\wdt400\java |
| HELP | x:\wdt400\help |
| IPF_PATH32 | x:\wdt400\system |
| LOCPATH | x:\wdt400\system |
| PATH | x:\wdt400 |
Note that an Administrator must uninstall the product as well.
To ensure that all components will install and run properly, make the following change:
command.com file32000When NetQuestion is uninstalled (by uninstalling all IBM products that use it), NetQuestion does not remove its entry in the PATH system variable. Repeated uninstalls can result in the variable string exceeding 200 characters. Shorten the PATH to correct this problem.
There are five CD-ROM disks. Disks 1 to 4 contain WebSphere Development Tools for iSeries. Disk 5 contains VisualAge for Java for iSeries 3.5.3. After closing the CD-ROM drive, wait until the drive light is out before clicking OK.
X:setup, where X is the CD-ROM drive letterX:setup, where X is the CD-ROM drive letter
X:setup, where X is the DVD drive letterX:setup, where X is the DVD drive letterA response file is a record of the installation location and components that were selected for an installation. An installation on another workstation that uses a response file will install the product exactly as the installation that created the response file, without screens and dialogs. See Note below for exceptions.
To create a response file, press the Create Response File button on the Installation wizard. The default path and name of the response file is C:\Program Files\IBM\v5r1rspn.wdt. You can change the default path and file name.
If you install with a response file then another response file is not created. Using a response file also means you have accepted the License Agreement. See the Legal Information section of the README document for the location of your License Agreement.
To use the response file, enter the setup command with the parameters as shown in this example:
setup -f "C:\Program Files\IBM\v5r1rspn.wdt"
where the drive and path of the response file are in quotation marks.
If the response file installation ends on an error, the error message can be found in the most current log file. See Log File in the Troubleshooting section.
Note: Installation using a response file will not install MS JVM and IBM's J2SDK, which are required for several components. If these programs are not already installed, then install them manually before installing WebSphere Development Tools for iSeries. You can find MS JVM on DVD or CD disk 4 in directory \extras. Run msjavx86.exe, then reboot. Install IBM SDK 1.2.2 SR10a by executing \extras\ibmsdk\install.exe, then reboot.
An administrator or user can copy all the files on the CDs or DVD onto a LAN server. This allows the user to install from the server to a workstation.
To copy from CD to a server:
xcopy X:*.* y:\wdtimage /e /q where X is the CD-ROM drive letter and Y:\wdtimage is an existing destination drive and path.To copy from DVD to a server:
xcopy X:*.* y:\wdtimage /e /q where X is the DVD-ROM drive letter and Y:\wdtimage is an existing destination drive and path.net use command to connect the LAN server drive where the product was copied to. Ensure that at least 1.3 GB are available on the workstation.X:\wdtimage\setup (where X is the LAN server drive) and follow installation instructions.X:\wdtimage\setup -f "C:\Program Files\IBM\wdtrspn.wdt"
where the drive and path of the response file are in quotation marks.
An administrator or user can copy all the files on the CDs or DVD onto an iSeries server. This allows the user to install from the iSeries server to a workstation.
To copy CDs or DVD on to an iSeries server, perform the following steps:
md install where "install" is the name of the storage directory. xcopy X: *.* m:\install /e /q where X is the CD-ROM drive letter and m:\install is the destination drive and path on the iSeries server.After the product is copied to the iSeries server (see How to put the product on an iSeries server), it can be installed onto a workstation from the server. The installation must be done on the workstation.
m:\install directorysetup.On Windows NT and Windows 2000, a user with Administrator authority must uninstall the product.
To add or remove components, use Start>Settings>Control Panel>Add/Remove Programs. Click IBM WDT400 V5R1M0 only, then click Change/Remove for Windows 2000 or Add/Remove for other Windows OS to start the Modify wizard. Select the Modify product option button to open the Modify wizard that allows you to select components to add or remove. If you add components, you need the original installation CD-ROMs, DVD, LAN drive, or iSeries server. Always reboot your machine after modifying the product.
When the Modify product option is selected, checkmarks control which components are added or removed. Initially, components that are currently installed are shown with checkmarks. To add a missing component, ensure its checkbox is selected. To remove a component, clear its checkbox. When you are finished selecting, only those components selected will be installed, if necessary. Do not remove a check mark if you do not want to remove a component that is already installed.
| Point | Comments |
|---|---|
| Ensure the environment Path variable is not too long. | This is relevant for Windows 98 and ME. See installation notes for Windows 98 and Windows ME. |
| Ensure you have enough temporary disk space available. | The installation process uses disk space in the directories specified by the TEMP and TMP environment variables. If an "out of temporary storage" message occurs during installation, change the TEMP and TMP variables to another drive that has enough space. The installation might require up to 400 MB of temporary storage. Reboot Windows 98 amd ME to ensure the change takes effect. |
| Check for causes of long installation. | If installation does not appear to be progressing:
|
| Enterprise Toolkit for AS/400 cannot be installed without VisualAge for Java for iSeries. | ET/400 requires VAJava for iSeries. Install VAJava, then the product. If you have already installed the product, add ET/400 with the install Modify option described in How to add or remove components after installation. All component dependencies are described in Custom Installation. |
| If you click Cancel during installation then determine which components are installed. | If you click Cancel while a component is being installed, then:
|
| If uninstalling VisualAge for Java for AS/400, which was installed when V4R5M1 was installed, generates an error message then use the cleanup file. | The cleanup file is on CD4 as \extras\cleanvaj.exe. |
| Check the installation log file. | Each product installation or modification is recorded in a separate log file: C:\Program Files\IBM\V5R1_xxx.log, where xxx is a sequential number from 001 and up. Log files have information on installed or uninstalled components and error messages. The most recent log file has the highest sequential number. |