This section lists the requirements that must be met before installing the Sun Java System Application Server Platform Edition 8.2 product.
The following table lists the operating systems that are supported for Sun Java System Application Server Platform Edition 8.2 2006Q1 product.
Table 1–3 Supported Operating Systems
Operating System |
Minimum Memory |
Recommended Memory |
Minimum Disk Space |
Recommended Disk Space |
JVM |
---|---|---|---|---|---|
Sun Solaris 8, 9, 10 (SPARC)Solaris 9, 10(x86) |
256 MB |
512 MB |
250 MB free |
500 MB free |
J2SE 1.4.2_06 |
Sun Java Desktop System |
256 MB |
512 MB |
250 MB free |
500 MB free |
J2SE 1.4.2_06 |
Redhat Enterprise Linux 2.1 Update 2, 3.0 Update 1 |
256 MB |
512 MB |
250 MB free |
500 MB free |
J2SE 1.4.2_06 |
Microsoft Windows 2000TM Advanced Server Service Pack 4+ |
256 MB |
512 MB |
250 MB free |
500 MB free |
J2SE 1.4.2_06 |
Microsoft Windows XPTM Professional Service Pack 1+ |
256 MB |
512 MB |
250 MB free |
500 MB free |
J2SE 1.4.2_06 |
On UNIXTM, you can check your operating system version using the uname command. Disk space can be checked using the df command.
It is recommended that Solaris 8, 9, 10 (x86, SPARC) users have the “Sun recommended patch cluster” installed. This patch cluster is available under “Recommended and Security Patches” on the SunSolve web site.
To run native components of this product, including installer, the following package, which is not part of the standard RedHat Enterprise Linux 3.0 distribution, should be installed: compat-libstdc++-7.3-2.96.118.i386.rpm
The package can be downloaded from http://rpm.pbone.net/index.php3/stat/4/idpl/843376/com/compat-libstdc++-7.3-2.96.118.i386.rpm.html
System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see System Virtualization Support in Sun Java System Products.
For the current list of required patches for Sun Java System Application Server Platform Edition 8.2 go to http://sunsolve.sun.com and select either “Patches” or “Patch Portal.” Follow the Sun Java System Application Server Platform 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 SunSolve, initially in the form of recommended patch clusters.
The Sun Java System Application Server Platform Edition 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, please refer to the following table:
Table 1–4 J2EE-Compatible JDBC Drivers
JDBC Vendor |
JDBC Driver Type |
Supported Database Server |
---|---|---|
i-net Software |
Type 4 |
Oracle (R) 8.1.7, 9i, 9.2.0.3Sybase ASE 12.5.2Microsoft SQL Server 2000 4.0 Service Pack 1 |
IBM |
Type 2 |
IBM DB2 8.1 Service Pack 3+ |
PointBase |
Type 4 |
PointBase Network Server 4.8 |
DataDirect |
Type 4 |
Oracle (R) 8.1.7, 9i, 9.2.0.3Sybase ASE 12.5.2Microsoft SQL ServerIBM DB2 8.1 Service Pack 3+ |
Oracle |
Type 4, Type 2 |
Oracle (R) 9.2.0.3, 10G |
For more information about i-net Software, see http://www.inetsoftware.de/.
For more information about DataDirect Technologies, see http://www.datadirect.com/.
Oracle JDBC drivers must be configured properly to be compliant with J2EE 1.4. Use the following configuration for Type 2 and Type 4 drivers:
Use the JDBC driver from 9.2.0.3 or later.
The Oracle database needs to have compatible=9.0.0.0.0 or higher in its parameter ( init.ora) file.
Use the ojdbc14.jar file.
Configure the Application Server to define the following JVM property:
-Doracle.jdbc.J2EE13Compliant=true |
In addition, for Type-2 drivers, both the ORACLE_HOME and LD_LIBRARY_PATH variables (which must include $ORACLE_HOME/lib) need to be defined in the environment in which the Application Server is started. For example, add them to the asenv.conf file and ensure they are exported.
Many sample applications use the PointBase database server included with the Application Server. When using Application Server Enterprise Edition, you must configure the PointBase database server before using it. Before using PointBase with the Application Server, however, note the supported configuration combination.
Table 1–5 Supported J2SE/PointBase Combinations
Application Server |
PointBase |
---|---|
Supported |
|
J2SE 1.4 J2SE 5.0 |
J2SE 1.4 J2SE 1.4 |
Unsupported |
|
J2SE 5.0 |
J2SE 5.0 |
There are two ways to configure PointBase:
Set the JAVA_HOME environment variable to the location of the J2SE. The PointBase implementation bundled with Application Server 8.2 is only supported with J2SE 1.4.2.
Edit the Application Server\qs PointBase configuration file.
Using the first method:
Make sure you have the J2SE installed that you want to use.
Download J2SE 1.4.2 if you do not already have it.
Using the command appropriate for your operating system and shell, set the JAVA_HOME environment variable to the directory in which J2SE is installed; for example:
% setenv JAVA_HOME "/opt/SUNWappserver/jdk" |
To use the second method, the procedure depends on the operating system.
Edit the install_dir/pointbase/tools/serveroption/pbenv.conf configuration file, changing the line:
PB_JAVA=%%%PB_JAVA%%%
to
PB_JAVA=J2SE_location
where J2SE_location is the directory where the J2SE is installed. If you installed J2SE with Application Server, it is installed by default to install_dir/jdk. After making this change, you can start PointBase using the startserver script.
Edit the install_dir\\pointbase\\tools\\serveroption\\pbenv.bat configuration file, changing the line:
set PB_JAVA=%%%PB_JAVA%%%
to
set PB_JAVA=J2SE_location
where J2SE_location is the directory in which the J2SE is installed. If you installed J2SE with Application Server, it is installed by default to install_dir\\j2se1.4. After making this change, you can start PointBase by running startserver.bat.
This section lists the web servers that are supported for the Sun Java System Application Server Platform Edition 8.2 2006Q1.
Table 1–6 Supported Web Servers
Web Server |
Version |
Operating System |
---|---|---|
Sun Java System Web Server |
6.0 Service Pack 6+ |
Solaris SPARC 8 9, 10Solaris x86 9, 10Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1 |
Apache Web Server |
1.3+, 1.4, 2.0 |
Solaris SPARC 9, 10 x86, Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1 |
Microsoft IIS |
5.0+ |
Windows Server 2003Windows 2000 Advanced Server Service Pack 4+ |
Support for additional platforms, including Windows and HP-UX, will be available at a later date.
This section lists the browsers that are supported with the Sun Java System Application Server Platform Edition 8.2 2006Q1.
Table 1–7 Browsers Supported
Browser |
Version |
---|---|
Mozilla |
1.4, 1.5, 1.6, 1.7.x |
Netscape Navigator |
4.79, 6.2, 7.0 |
Internet Explorer |
5.5 Service Pack 2, 6.0 |
Refer to the Installation Guide for complete instructions for upgrading from a previous version of the Application Server to the Sun Java System Application Server Platform Edition 8.2 2006Q1.
The following additional requirements should be met before installing the Sun Java System Application Server software.
Free space– your temporary directory must have a minimum of 35MB free for Sun Java System Application Server installation, and 250 MB of free space for the SDK installation.
Using the uninstall program– If you need to remove the Application Server from your system, it is important to use the uninstall program that is included with the software. If you attempt to use another method, problems will arise when you try to reinstall the same version, or when you install a new version.
Free ports– You must have seven unused ports available.
The installation program automatically detects ports in use and suggests currently unused ports for the default settings. By default, the initial default ports are 8080 for HTTP, 8181 for HTTPS, and 4849 for the Administration Server.
The installation program will detect used ports and assign two others for you: Sun JavaTM System Message Queue (by default, 7676), and IIOP (by default, 3700 for IIOP and 3820 and 3890 for IIOP/SSL). If these default port numbers are in use, the installation program will assign a random port number from the dynamic port range (note that this may not be the next available port number).
Starting previously-installed servers (UNIX) – Unless you are replacing the previously installed server, you should start it before you begin the Sun Java System Application Server 8.2 installation process. This allows the installation program to detect ports that are in use and avoid assigning them for other uses.
Replacing previously-installed servers (UNIX) – If you have an older version on the Sun Java System Application Server installed that you wish to replace with the current Application Server, you should stop it before installing the new server. Use the installation program upgrade wizard to upgrade the server.
Shutting down firewall (Microsoft Windows) – You must stop any firewall software before installing the Sun Java System Application Server software, because some of this software disables all ports by default. The installation program must be able to accurately determine which ports are available.
For further compatibility information, see the Sun Java System Application Server Platform Edition 8.2 Upgrade and Migration Guide.