This section lists the requirements that must be met before installing the Sun Java System Application Server Enterprise Edition 8.2 product.
The following table lists the operating systems that are supported for Sun Java System Application Server Enterprise Edition 8.2 product. Additionally, the minimum and recommended memory requirements are identified for installing and running the Application Server.
Table 2–1 Sun Java System Application Server 8.2 Platform Requirements
Operating System |
Minimum Memory |
Recommended Memory |
Minimum Disk Space |
Recommended Disk Space | |
---|---|---|---|---|---|
Windows 2000 Advanced Server SP4 Windows XP SP2 Windows 2003 Enterprise Server SP1 (32 bit) Windows 2003 Enterprise Server SP1 (64 bit) |
1 GB |
2 GB |
500 MB free |
1 GB free |
J2SE 1.4.2_10, J2SE 5_06 |
You must use the NTFS file system rather than FAT or FAT32 when running the Application Server on any Microsoft Windows platform.
For the current list of required patches for Sun Java System Application Server Enterprise Edition 8.2, see http://sunsolve.sun.com and search for “app server 8.1 patch.” Follow the Sun Java System Application Server Enterprise Edition 8.2 links. As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on the SunSolveSM web site, initially in the form of recommended patch clusters.
The Sun Java System Application Server is designed to support connectivity to any DBMS with a corresponding JDBC driver. For a list of components that Sun has tested and found to be acceptable for constructing J2EE compatible database configurations, refer to the following table.
Table 2–2 J2EECompatible JDBC Drivers
JDBC Vendor |
JDBC Driver Type |
Supported Database Server |
---|---|---|
i-net Software |
Type 4 |
Oracle® 8.1.7, 9i, 9.2.0.3+, 10.1.x, 10.2.x Sybase ASE 12.5. Microsoft SQL Server 2000 4.0 Service Pack 1 |
IBM |
Type 2 |
IBM DB2 8.1 Service Pack 3+ |
Java DB |
Type 4 |
Apache Derby 10.1.2.1 |
PointBase |
Type 4 |
PointBase Network Server 5.2 |
DataDirect |
Type 4 |
Oracle (R) 8.1.7, 9i, 9.2.0.3+, 10.1.x, 10.2.x Sybase ASE 12.5.2 Microsoft SQL Server IBM DB2 8.1 Service Pack 3+ |
MySQL |
Type 4 |
5.x |
Sun Java System JDBC Driver for Oracle |
Type 4 |
Oracle (R) 9.2.0.3, 10G |
Sun Java System JDBC Driver for DB2 |
Type 4 |
IBM DB2 8.1 Service Pack 3+ |
Sun Java System JDBC Driver for Sybase |
Type 4 |
Sybase ASE 12.5.2 |
Sun Java System JDBC Driver for Microsoft SQL Server |
Type 4 |
Microsoft SQL Server 2000 4.0 Service Pack 1 |
Oracle |
Type 4, Type 2 |
Oracle (R) 9.2.0.3, 10G |
This section provides instructions for using the Java DB database implementation bundled with Application Server 8.2.
Sun Java System Application Server 8.2 introduces two new asadmin commands for starting and stopping the Java DB Network Server.
The start-database command starts an instance of the Java DB network server:
start-database [--dbhost 0.0.0.0] [--dbport 1527] [--dbhome "path/derby"] |
The default value for the host is 0.0.0.0, which allows for Java DB to listen on localhost as well as the IP and hostname interfaces. The value for the dbhome property is the location of the Java DB databases. The default path is appserver_install_dir/derby.
The asadmin stop-database command is used to shut down an instance of the Java DB network server that is running:
stop-database [--dbhost 0.0.0.0] [--dbport 1527] |
The Java DB configuration that ships with Application Server 8.2 also includes several useful scripts that can help you use Java DB. The following scripts are available for use in the appserver_install_dir/derby/frameworks/NetworkServer/bin directory:
startNetworkServer.ksh/bat – Script to start the network server
stopNetworkServer.ksh/bat – Script to stop the network server
ij.ksh/bat – interactive JDBC scripting tool
dblook.ksh/bat – Script to view all or part of the DDL for a database
sysinfo.ksh/bat – Script to display versioning information regarding the Java DB environment
NetworkServerControl.ksh/bat – Script that provides a means of running commands on the NetworkServerControl API
Set the DERBY_INSTALL environment variable to point to the appserver_install_dir/derby directory.
Unset your CLASSPATH environment variable.
(Optional) You can also set the following properties:
Set DERBY_SERVER_HOST to the host on which the network server will listen.
Can also be set to 0.0.0.0 to enable all listeners.
Set DERBY_SERVER_PORT to the port number on which the network server will listen.
For more information about these utilities, see the Derby Tools and Admin guides.
This section lists the web servers that are supported for the Sun Java System Application Server Enterprise Edition 8.2.
Table 2–3 Supported Web Servers
Web Server |
Version |
Operating System |
---|---|---|
Sun Java System Web Server |
7 |
Windows 2000 Advanced Server SP4 Windows XP SP2 Windows 2003 Enterprise Server SP1 (32-bit) Windows 2003 Enterprise Server SP1 (64-bit) |
This section lists the browsers that are supported by the Sun Java System Application Server Enterprise Edition 8.2.
Table 2–4 Supported Web Browsers
Browser |
Version |
---|---|
Mozilla |
1.4, 1.5, 1.6, 1.7.x |
NetscapeTM Navigator |
4.79, 6.2, 7.0, *** |
Internet Explorer |
5.5 Service Pack 2, 6.0 |
Firefox |
*** |
In addition to the requirements listed in Hardware and Software Requirements, verify that your system meets the following requirements for running HADB.
The Java components of the system have been built with JDK 1.4.2_02 and the system has been tested on JDK 1.5.
Microsoft Windows – Microsoft Windows 2000 Advanced Server Service Pack 4 and Microsoft Windows 2003 Enterprise Edition. Note that HADB does not support any of the forthcoming Microsoft Windows operating system versions in 64–bit mode.
Minimum memory – 512 MBytes per node.
Minimum free disk space – 70 MBytes for HADB binaries per host. In addition, disk space is needed for the data devices: 512 MBytes for a test installation per node.
Recommended memory – 1 GByte per node.
Recommended free disk space – 70 MBytes for HADB binaries per host. In addition, disk space is needed for the data devices: 1200 MBytes for a test installation per node.
Minimum memory – 128 MBytes
Minimum free disk space – 70 MBytes for HADB binaries per node
Minimum memory – 120 MBytes
Minimum free disk space – 20 MBytes