October 2006 [Revision number: V1-0]
This document provides installation instructions for the Java Platform, Enterprise Edition 5 (Java EE 5) Tools Bundle. The Java EE 5 Tools Bundle includes NetBeans IDE 5.5 (hereinafter referred to as IDE), NetBeans Enterprise Pack 5.5, and to "Java Platform, Enterprise Edition 5 SDK Update 1 or Update 2 (Java EE 5 SDK Update 1 or Update 2, hereinafter referred to as SDK). The NetBeans Enterprise Pack 5.5 includes XML schema tools modules, BPEL modules, Secure Web Services modules, Project Open ESB Starter Kit, Sun Java System Access Manager 7.1, and Sun Java System Policy Agent 2.2 for Sun Web Services.
Note: The UML functionality is no longer available in the final (FCS) release of the NetBeans Enterprise Pack 5.5 download. Instead, the UML functionality is offered separately on the Auto Update Center.
This topic specifies the prerequisites that must be met before you start to install the Java EE 5 Tools Bundle.
Required Software
The following software must be installed before you attempt to install the Java EE 5 Tools Bundle:
Note: For Mac OS X, at least JDK 5.0 release 3 is required.
Firewall Applications
Enabled firewall applications can prevent some components from being configured correctly during the installation process. Disable any firewall applications before you start the installation.
This topic provides configuration information that you may need in order to configure the software.
Sun Java System Application Server
The default username and password values for the default Application Server domain, domain1, are as follows:
username: admin
password: adminadmin
Sun Java System Access Manager
If you need to access the administration console for the Access Manager server, use the following values:
username: amadmin
password: admin123
This section contains instructions for installing the Java EE 5 Tools Bundle on the Microsoft Windows platform.
Before You Start
The following restriction applies to installation on the Microsoft Windows platform:
TEMP environment variable. If the amount of disk space in the temporary directory is less than required, the installation might fail or proceed incorrectly.
If you encounter this problem, you can increase the space allocated for the TEMP environment variable or specify a different temporary directory that has sufficient space. To specify a temporary directory for the installation, use the following commands from a command window:
> cd /d location-of-installer
> java-tools-bundle-windows.exe -is:tempdir temporary-directory
To Install
java-tools-bundle-windows.exe , double-click the installer's icon to launch the installer. The JDK installation directory selection page of the wizard opens.
You can also type the path to another installed JDK or use the Browse button to navigate to and select another installation.
Note: The wizard automatically highlights the most recent installation available on your machine.
Note: You can also specify a non-existing directory. The installation wizard will create the directory during the installation.
Note: Clear the BPEL and Secure Web Services checkboxes if you do not intend to use these modules. This enables the Skip Application Server configuration radio button in the following step and speeds up the installation process.
Note: Make sure you observe the dependencies listed in the table below when selecting the components for your installation.
| Required Component Name | Dependent Component Name |
|---|---|
| NetBeans IDE 5.5 |
Each of the Netbeans Enterprise Pack 5.5 components:
|
| XML component of the NetBeans Enterprise Pack 5.5 | BPEL component of the NetBeans Enterprise Pack 5.5 |
| Java Platform, Enterprise Edition 5 SDK |
The following of the NetBeans Enterprise Pack 5.5 components:
|
To Continue the Installation With the Bundled Java EE SDK
domain1, or accept the defaults and click Next.
The default username and password are admin and adminadmin.
Admin, HTTP, and HTTPS) for the default Application Server and change them if necessary. Then click Next. To Continue the Installation With a Preinstalled Application Server
domain1, exists in the selected Application Server, enter the username and password for the default Application Server domain and click Next.
The installation wizard verifies the username and password information you entered.
Note: The verification process may take some time.
-or-
If the default domain, domain1, does not exist in the selected Application Server, do the following:
domain1, or accept the defaults and click Next. admin and adminadmin. Admin, HTTP, and HTTPS) for the Application Server and change them if necessary. Then click Next. Note: If you encounter problems successfully completing the software installation, see Troubleshooting for complete descriptions and suggested workarounds for unresolved issues that could affect the installation process.
Following are instructions for installing the Java EE 5 Tools Bundle on the Solaris OS and Linux platforms.
In the instructions below, replace your_binary_executable with one of the following:
java-tools-bundle-linux.sh java-tools-bundle-solaris-sparc.sh java-tools-bundle-solaris-x86.shTo Install
your_binary_executable , navigate to the directory that contains the file. You can also type the path to another installed JDK or use the Browse button to navigate to and select another installation.
Note: The wizard automatically highlights the most recent installation available on your machine.
Note: You can also specify a non-existing directory. The installation wizard will create the directory during the installation.
Note: Clear the BPEL and Secure Web Services checkboxes if you do not intend to use these modules. This enables the Skip Application Server configuration radio button in the following step and speeds up the installation process.
Note: Make sure you observe the dependencies listed in the table below when selecting the components for your installation.
| Required Component Name | Dependent Component Name |
|---|---|
| NetBeans IDE 5.5 |
Each of the Netbeans Enterprise Pack 5.5 components:
|
| XML component of the NetBeans Enterprise Pack 5.5 | BPEL component of the NetBeans Enterprise Pack 5.5 |
| Java Platform, Enterprise Edition 5 SDK |
The following of the NetBeans Enterprise Pack 5.5 components:
|
To Continue the Installation With the Bundled Java EE SDK
domain1, or accept the defaults and click Next.
The default username and password are admin and adminadmin.
Admin, HTTP, and HTTPS) for the Application Server and change them if necessary. Then click Next. To Continue the Installation With a Preinstalled Application Server
domain1, exists in the selected Application Server, enter the username and password for the default Application Server domain and click Next.
The installation wizard verifies the username and password information you entered.
Note: The verification process may take some time.
-or-
If the default domain, domain1, does not exist in the selected Application Server, do the following:
domain1, or accept the defaults and click Next.
The default username and password are admin and adminadmin.
Admin, HTTP, and HTTPS) for the Application Server and change them if necessary. Then click Next.Note: If you encounter problems successfully completing the software installation, see Troubleshooting for full descriptions and suggested workarounds for unresolved issues that could affect the installation process.
Following are instructions for installing the Java EE 5 Tools Bundle on the Mac OS X platform.
Before You Start
The following restrictions apply to the installation on the Mac OS X platform:
.app.To Install
java-tools-bundle-macosx.jar, navigate to the directory that contains the file and double-click the installer's icon to launch the installer.
Note: If the default java version on your system is 1.4, you will not be able to double-click the .jar file to start the installation. In this case, run the .jar file manually from the command line using java 1.5.
The JDK installation directory selection page of the wizard opens.
You can also type the path to another installed JDK or use the Browse button to navigate to and select another installation.
Note: The wizard automatically highlights the most recent installation available on your machine.
Note: You can also specify a non-existing directory. The installation wizard will create the directory during the installation.
Note: Clear the BPEL and Secure Web Services checkboxes if you do not intend to use these modules. This enables the Skip Application Server configuration radio button in the following step and speeds up the installation process.
Note: Make sure you observe the dependencies listed in the table below when selecting the components for your installation.
| Required Component Name | Dependent Component Name |
|---|---|
| NetBeans IDE 5.5 |
Each of the Netbeans Enterprise Pack 5.5 components:
|
| XML component of the NetBeans Enterprise Pack 5.5 | BPEL component of the NetBeans Enterprise Pack 5.5 |
| Java Platform, Enterprise Edition 5 SDK |
The following of the NetBeans Enterprise Pack 5.5 components:
|
To Continue the Installation With the Bundled Java EE SDK
domain1, or accept the defaults and click Next.
The default username and password are admin and adminadmin.
Admin, HTTP, and HTTPS) for the default Application Server domain and change them if necessary. Then click Next. To Continue the Installation With a Preinstalled Application Server
domain1, exists in the selected Application Server, enter the username and password for the default Application Server domain and click Next.
The installation wizard verifies the username and password information you entered.
Note: The verification process may take some time.
-or-
If the default domain, domain1, does not exist in the selected Application Server, do the following:
domain1, or accept the defaults and click Next.
The default username and password are admin and adminadmin.
Admin, HTTP, and HTTPS) for the Application Server and change them if necessary. Then click Next. Note: If you encounter problems successfully completing the software installation, see Troubleshooting for full descriptions and suggested workarounds for unresolved issues that could affect the installation process.
If you installed the bundled Application Server, the uninstallation removes NetBeans Enterprise Pack 5.5, Sun Java System Application Server Platform Edition 9 Update 1, Project Open ESB Starter Kit, and Sun Java System Access Manager from your system. If you chose to use a preinstalled Application Server, the uninstallation removes NetBeans Enterprise Pack 5.5 from your system. In this case, to remove the Project Open ESB Starter Kit, you must uninstall the preinstalled Application Server.
To Uninstall on Microsoft Windows
To Uninstall on Solaris OS or Linux
bin/_uninst subdirectory of your Java EE 5 Tools Bundle installation directory. uninstall.sh script. To Uninstall on Mac OS X
bin/_uninst subdirectory of your Java EE 5 Tools Bundle installation directory. uninstall.jar executable file.
Note: If the default java version on your system is 1.4, you will not be able to double-click the .jar file to start the uninstallation. In this case, run the .jar file manually from the command line using java 1.5.
If you experience problems installing or running the software, see the list of issues below for workarounds. For a complete list of known issues, system requirements and other useful information.
Following are the unresolved issues for this release that may affect or disrupt the installation process:
temp directory.
Description: On Microsoft Windows, if your system is set up to use a temporary directory on your C drive, and that temporary directory does not have enough space for the temporary files needed by the installer, the installer will report that there is not enough disk space on the C drive. This will occur even if you chose to install to a different drive. The installer is in fact reporting that it needs additional temporary space.
The issue exists in the InstallShield framework.
Workaround: Start the installer with the -is:tempdir custom-temp-dir command line parameter. The custom-temp-dir should contain at least 130 MB of free disk space.
NoClassDefFoundError: cannot access amserver occurs during installation.
Description: If you try to install the software a second time without cleaning up the Access Manager directory, the configuration of Access Manager may fail during installation.
Workaround:
Delete the directory specified in: %SystemDrive%\Documents and Settings\ user-name\AMConfig_server_amserver_ and then remove the file %SystemDrive%\Documents and Settings\ user-name\AMConfig_server_amserver_ .
Delete the directory specified in: $HOME\AMConfig_server_amserver_ and then remove the file $HOME\AMConfig_server_amserver_ .
-console and -silent options.
Description: On UNIX platforms, if the installer cannot perform the installation process without the graphics mode, the installer suggests that you run the installer with the -console and -silent options. If you try this, the installer fails.
Workaround: Ignore the message from the installer and set up the GUI environment as described below to proceed with the installation.
The most common cause for this issue is that you are connecting to the target system via telnet/ssh/rlogin, which means you must redirect the GUI to the originating system. To do this successfully, the following two requirements must be met:
export DISPLAY= machine-name: display-number
Where machine-name is the IP address of the system from where you are connecting, and display-number is the number of the display, usually 0.0.
Description: If you try to install the product after performing a manual uninstallation by deleting files, the installation will fail because the data in InstallShield's VPD registry is not cleaned up.
Workaround: Before starting a new installation, remove the InstallShield VPD registry. This registry resides in %SystemDrive%\Program Files\Common Files\InstallShield\Universal or in ~/InstallShield.
.jar file.
Description: If the default java version on your system is 1.4, you will not be able to double-click the .jar file to start the installation.
Workaround: In this case, run the .jar file manually from the command line using java 1.5.
Description: On Microsoft Windows, if there is no preinstalled compatible JDK on the target machine, the InstallShield Windows launcher allows you to select a custom java.exe. After you select a custom java.exe the installer does not perform a validation for compatibility. This means that if you select a java.exe from a 1.4 JRE which is not compatible with the installer, you will encounter a number of exceptions. The issue exists in the InstallShield framework.
Workaround: Select a java.exe from a 1.5 JRE.
Description: The installer fails to start correctly on UNIX when is there is little or no disk space in the root directory of the filesystem. The problem exists in the InstallShield framework. This issue was observed on machines with less than 2.5 MB free in the root of the filesystem.
Workaround: Free up enough disk space in the root of the filesystem and restart the installer.