The Sun Java System Application Server Enterprise Edition 8.2 is a J2EE 1.4 platform-compatible server for the development and deployment of J2EE applications and Java technology-based web services in large-scale production environments.
This chapter includes:
The Application Server Enterprise Edition 8.2 includes the following enhancements:
Improved Administration — The Application Server supports the remote secure management of complex multi-machine enterprise deployments using either a browser based console or a scriptable command line interface. It also provides a rich JMX based API allowing remote, secure, programmatic access to administrative and monitoring functions.
Message Broker — The Application Server is bundled with an integrated enterprise class message broker that features providing highly available, reliable, high performance, and scalable messaging.
Message Queue 3.7 — The Application Server now implements MQ 3.7.
Expanded Platform Support — Additional operating systems, databases, locales, and hardware are supported.
Sun Java Enterprise System — As a key component of the Sun Java Enterprise System, the Application Server is tightly integrated with portal and network identity services.
Migration and Upgrade Tools — These tools enable you to verify J2EE applications for standards conformance and portability, help with migrations from other J2EE Application Servers (JBoss, WebLogic, WebSphere), and aid in upgrading from previous versions of Sun ONE Application Server/ iPlanet Application Server.
Java 2 Standard Edition 5.0 Support — The Application Server supports the Java 2 Standard Edition 5.0, which includes enhanced management and monitoring features and many performance and scalability improvements.
Java Web Services Developer Pack 1.6 (JWDSP) Plugin Support — All JWSDP plugins are now supported. The JWSDP 1.6 can be downloaded for free from http://java.sun.com/webservices/downloads/1.6/index.html.
Java DB Database Support — Application Server includes the Java DB database, based onApache Derby. Backward compatibility with Pointbase database is maintained, but any new databases created on the server will use Java DB by default. After upgrading from Application Server 8.x, existing domains will continue to use PointBase, but any new domain created after the upgrade will use Java DB.
JDBC Drivers — The Application Server is bundled with Sun JDBC drivers.
Web Services Security — These container message security mechanisms implement message-level authentication (for example, XML digital signature and encryption) of SOAP web services invocations using the X509 and username/password profiles of the OASIS WS-Security standard.
WS-I Basic Profile 1.1 — As mandated by the J2EE 1.4 specification, this release implements Web Services Interoperability (WS-I) Basic Profile 1.1 to enable interoperability for web services applications.
Backend Connectivity with iWay Adapters — Sun Microsystems now resells and supports twenty-two iWay adapters to key backend systems (SAP, Siebel, Oracle, CICS, and IBM MQ Series) to help you leverage existing IT applications from within the Application Server environment. These adapters support the J2EE Connector Architecture 1.5 specification and Web services (SOAP) standards, and include developer tools to reduce time to connect to backend applications.
Latest HADB Management System — The UNIXTM platforms contain the new high availability database (HADB) management system (HADB version 4.4.3), which includes a Database Server, ODBC 2.5 driver, JDBC 3.0 type 4 driver, clusql (an interactive program to enter and execute SQL statements), and a management system. This version eliminates the dependency on SSH/RSH, but requires that the network be configured for UDP multicast. See the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide for the details on HADB requirements and limitations.
Solaris 10 Zones Support – The Application Server can be installed in either a global or non-global Zone on Solaris 10 systems. See the Solaris Zones page for more information about Solaris Zones.
Dynamic Content Technology Support Dropped — Dynamic content technologies, such as CGI-bin and SHTML, are no longer supported.
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 | |
---|---|---|---|---|---|
Sun Solaris 9, 10 (SPARC) Solaris 9, 10 (x86) |
512 MB |
1 GB |
250 MB free |
500 MB free |
J2SE_5_08 |
Sun Java Desktop System |
512 MB |
1 GB |
250 MB free |
500 MB free |
J2SE_5_08 |
Redhat Enterprise Linux 3.0 U1, 4.0 |
512 MB |
1 GB |
250 MB free |
500 MB free |
J2SE_5_08 |
Windows Server 2000 SP4+ Windows 2000 Advanced Server SP4+ Windows Server 2003 Windows XP Pro SP1+ |
1 GB |
2 GB |
500 MB free |
1 GB free |
J2SE_5_08 |
The system requirements listed above for Application Server and those listed for HADB in HADB Requirements and Supported Platforms are not exactly the same. This is not a documentation error. It is not uncommon to run Application Server and an HADB server on different machines.
On UNIX, you can check your operating system version using the uname command. Disk space can be checked using the df command.
You must use the NTFS file system rather than FAT or FAT32 when running the Application Server on any Microsoft Windows platform.
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.
It is recommended that Solaris 9, 10 (x86, SPARC) users have the “Sun recommended patch cluster” installed. This patch cluster is available under Recommended and Security Patches on SunSolve.
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
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, please refer to the following table.
Table 2–2 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.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.3 |
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 can be used to start 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/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 which 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 info regarding the Java DB environment
NetworkServerControl.ksh/bat — Script which provides a means of executing 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.
You can also optionally set the following properties:
For more information about these utilities, see the Derby Tools and Admin guides.
This example shows how to capture the DDL for a table in Pointbase and create the same table in Java DB using Netbeans 5.0. Another option for doing this is by using the commander tool and the unload database command:
./startcommander.sh Do you wish to create a new Database. (Yes (Y) or No (N))? [default: N]: Enter product to connect with: (Embedded (E) or Server (S))? [default: E]: e Enter driver to use? [default: [com.pointbase.jdbc.jdbcUniversalDriver]: Enter database URL? [default: [jdbc:pointbase:embedded:sample]: Enter Username? [default: PBPUBLIC]: Enter Password? [default: PBPUBLIC]: PointBase Commander 5.2 ECF build 294 size restricted version EMBEDDED Interactive SQL command language. SunOS/5.9 (C) Copyright 2004 DataMirror Mobile Solutions, Inc. All rights reserved. Licensed to: Sun_customer_demo_use For commercial version contact PointBase at: pointbase.com PHONE: 1-877-238-8798 (US & CANADA) 1-408-961-1100 (International) WEBSITE: www.pointbase.com SQL>unload database sampledb.sql; SQL> unload database sampledb.sql; SQL> 13 Row(s) Unloaded. (PBPUBLIC.CUSTOMER_TBL) SQL> 4 Row(s) Unloaded. (PBPUBLIC.DISCOUNT_CODE_TBL) SQL> 30 Row(s) Unloaded. (PBPUBLIC.MANUFACTURE_TBL) SQL> 11 Row(s) Unloaded. (PBPUBLIC.MICRO_MARKETS_TBL) SQL> 9 Row(s) Unloaded. (PBPUBLIC.OFFICE_TBL) SQL> 4 Row(s) Unloaded. (PBPUBLIC.OFFICE_TYPE_CODE_TBL) SQL> 15 Row(s) Unloaded. (PBPUBLIC.ORDER_TBL) SQL> 6 Row(s) Unloaded. (PBPUBLIC.PRODUCT_CODE_TBL) SQL> 30 Row(s) Unloaded. (PBPUBLIC.PRODUCT_TBL) SQL> 10 Row(s) Unloaded. (PBPUBLIC.SALES_REP_DATA_TBL) SQL> 10 Row(s) Unloaded. (PBPUBLIC.SALES_REP_TBL) SQL> 52 Row(s) Unloaded. (PBPUBLIC.SALES_TAX_CODE_TBL) SQL> 12 Table(s) Unloaded. SQL> quit;
The results from executing the unload database command is written in the above example to the file sampledb.sql. The sampledb.sql file contains all of the DDL required to create the necessary tables and indexes. It also contains the DML to insert the data back into the database. The commander command RUN is intended to be used import the data into another Pointbase database using the script that was generated. Here is an example of what the INSERT statements and associated data look like in the generated file:
INSERT INTO "ADVENTURE"."CATEGORY" ( "CATID", "LOCALE", "NAME", "DESCRIPTION", "IMAGEURI" ) VALUES( ?, ?, ?, ?, ? ); { 'ISLAND ','en_US','Island Adventures','Experience an island / paradise in a way fit for your needs.','Island_Adventures.gif' 'JUNGLE ','en_US','Jungle Adventures','Experience a jungle / paradise in a way fit for your needs.','Jungle_Adventures.gif' 'MOUNTAIN ','en_US','Mountain Adventures','Experience an / elevated paradise with a view.','Mountain_Adventures.gif' 'ORBITAL ','en_US','Orbital Adventures','Experience a vacuum / paradise with a beautiful view and where no one can hear you scream.', / 'Space_Adventures.gif' 'WESTERN ','en_US','Western Adventures','Enjoy the Wild West. / ','Western_Adventures.gif' 'SOUTH_POLE ','en_US','South Pole Adventures','Experience a / frozen paradise in a way fit for your needs.','SouthPole_Adventures.gif' };
You could easily edit the file generated from the commander unload database command so that it only consisted of the DDL (for example, it would not be hard to write a program which would process the insert statements). As a simple test, we use the unload database command against the Pointbase sample database, and then edit the generated script, making the following changes:
Removed the phrase Organization Heap from the end of all CREATE Table statements
Removed the COMMIT command
Changed the Boolean datatype to be smallint
Removed all of the INSERT statements and associated data
Next, a simple Ant script is used to execute the DDL using the sql target. Finally, the same experiment is repeated for the sun-appserv-samples database requiring the following additional changes to the generated SQL file:
Make all changes as described above for the sample database
Remove the create user commands
Remove the SET PATH commands
Change the Decimal precision from 38 to max of 31
Change the float precision from 64 to max of 52
The SPECIFIC keyword for CREATE PROCEDURE is not currently supported
Removed the GRANT commands
Converting Pointbase Java procedures to work with Java DB requires some changes to the Java code as well as to the CREATE PROCEDURE statements. Information on creating Java DB Java procedures can be found in the Derby Reference manual. Support for the Boolean datatype should be in the next release of Java DB.
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 |
6,0, 6.1, 7.0 |
Solaris SPARC 9, 10 Solaris x86 9, 10 Red Hat Enterprise Linux 3 and 4 |
Apache Web Server |
1.3+, 1.4, 2.0 |
Solaris SPARC 9, 10 Solaris x86 10 Red Hat Enterprise Linux 3 and 4 Windows Server 2003 Windows 2000 Advanced Server SP4+ Windows Server 2000 SP4+ Windows XP Pro SP1+ |
Microsoft IISTM |
5.0+ |
Windows Server 2003 Windows 2000 Advanced Server SP4+ Windows Server 2000 SP4+ Windows XP Pro SP1+ |
This section lists the browsers that are supported with 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 |
Netscape Navigator |
4.79, 6.2, 7.0, 8.x |
Internet Explorer |
5.5 Service Pack 2, 6.0 |
Firefox |
1.4, 1.5 |
In addition to the requirements listed in Hardware and Software Requirements, verify that your system meets the requirements listed below for running HADB.
HADB 4.4.3 is co-packaged with Application ServerEnterprise Edition 8.2
The system requirements listed in Platform Requirements for Application Server and those listed here for HADB are not exactly the same. This is not a documentation error. It is not uncommon to run Application Server and an HADB server on different machines.
The Java components of the system have been built with JDK 1.4.2_02 and has been tested on JDK 1.5_09.
Solaris (SPARC) – Solaris 8 MU7, Solaris 9 MU7, Solaris 10 RR.
Solaris (x86) – Solaris 9 MU7, Solaris 10 RR.
RedHat Enterprise Linux - 2.1 U5 (only ext2 file system is supported, not ext3), 3.0 U4 (both ext2 and ext3 are supported. Updates before U4 are not recommended due to excessive swapping). Note that HADB is tested on these operating system versions in 32–bit mode only. Also, note that HADB does not support RedHat Enterprise Linux 3.0 running in 64–bit mode due to a bug in the operating system (see known bug 6249685 in the High Availability section for details about impact on HADB).
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 MB per node.
Minimum free disk space - 70 MB for HADB binaries per host. In addition, disk space is needed for the data devices, 512 MB for a test installation per node.
Recommended memory - 1 GB per node.
Recommended free disk space - 70 MB for HADB binaries per host. In addition, disk space is needed for the data devices, 1200 MB for a test installation per node.
Make sure write caching is disabled on devices storing HADB data and log files. Write caching is enabled by default on some Solaris platforms; for example, Solaris x86.
Minimum memory - 128 MB
Minimum free disk space - 70 MB for HADB binaries per node
Minimum memory - 120 MB
Minimum free disk space - 20 MB
The in-place upgrade from any prior Application Server release is not supported. Refer to the Application Server Enterprise Edition Upgrade and Migration Guidefor complete instructions for upgrading from a previous version of the Application Server to the current version.
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 Java System Message Queue (by default, 7676), and IIOP (by default, 3700 for IIOP and 1060 and 1061 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 theSun Java System Application Server Enterprise Edition 8.2 Upgrade and Migration Guide.
This section lists the customer-escalated issues resolved for the Sun Java System Application Server Enterprise Edition 8.2 product.
Bug Number |
Description |
---|---|
6368745 |
AS: cannot upgrade from AS7 (Java ES 2) to AS8.2 (Java ES 5) |
6432308 |
AS, JES5b7a, asupgrade from JES2 to JES5 fails |
6378409 |
AS 8.2:backward compatibility broken because of jsf libraries that are included in 8.2 |
6371534 |
AS82EE:configure-ha-cluster hangs on Windows if the installation path contains space |
6242761 |
The node agent cannot be started by init as documented without generating errors |
6267772 |
Instructions about the configuration for Borland OptimizeIt are incorrect |
6273226 |
Add text explaining to add the -Xrs jvm option to run a server/NA running as a windows s |
6361145 |
Cannot upgrade LB plugin when in place upgrade from 8.1EE to 8.2EE |
6362881 |
Installer doesn't give upgrade option when upgrade 8.1ur2 to 8.2ee |
6325988 |
interop problem on first incoming RMI-IIOP request with FVD/codeBase |
6363689 |
JES5 ASEE8.2 build03 - Unable to stop the instance |
6364900 |
Session value lost at the time of fail over when 1 web app includes a second web app |
6370993 |
Session Failover collapses when the Application Context Root is Modified to “/” in Cluster |
6373729 |
Appserver 8.1 code cannot communicate with WebLogic 9.0 because of ORB conflict |
6377594 |
lookup problems with Weblogic initialcontext factory |
6381538 |
Standalone Client fails with NPE |
6406055 |
WARNING: “IOP00110205: (BAD_PARAM) Object reference came from foreign ORB” org.omg.CORBA. |
6388329 |
JSP compilation error in Application Server after Access Manager upgrade |
6419659 |
Requests not redirected correcly by the LB Plugin when transport-guarantee is CONFIDENTIAL |
6390584 |
OutOfMemoryError: PermGen space |
6401424 |
SEGV from service_plain_range in libns-httpd40.so when requested to byte serve a PDF file. |
6401704 |
Need WebDAV Support for AppServer 8.# |
6416478 |
jsp testsuite failue: javax.servlet.jsp.el.ELException |
6438908 |
Header location corruption when relativeRedirectAllowed=true |
6456553 |
java.lang.IllegalArgumentException when appending cookies to the response |
6295010 |
Connections in the steady pool are not checked for idle timeout which conflicts with firewalls |
6350435 |
Application Server fails to handle the failure of a database during an XA operation to two databases |
6377830 |
setAutoCommit to false gets propagated when the same connection is being the next user |
6399830 |
IT 319 : password alias feature not working in domain.xml |
6360040 |
SJAS 8.x : AppServer LDAP Realm Bind User tends to access all groups and members |
6370095 |
Cannot set acceptor-thread higher than 10. |
6399365 |
InvokerServlet is not working in Enterprise Edition only |
6303835 |
Excess logging: Misleading security messages in server log |
6349541 |
8.1 EE UR2 - SSL Listeners cannot be made to binding to a specific IP address... |
6380040 |
Automated cleanup of logfiles required |
6387278 |
Client authentication broken or not threadsafe(ProgrammaticLogin) |
6407896 |
HttpServletRequestWrapper that overrides getUserPrincipal() causes ClassCastException |
6321194 |
Round Robin policy not working |
6362269 |
Verifier does not run correctly on Windows when installation path contains a space |
6365888 |
Connections from the default connector connection pool are not enlisted in transactions |
6369554 |
connection pool need to validate a connection before giving it to application |
6370574 |
After AS upgrade with Confugre Later there is missing /var/opt/SUNWappserver directory |
6371723 |
lbplugin leaks memory for all webserver version (more for Apache mod_loadbalancer) |
6395390 |
Round Robin not happening on http requests that failover. |
6402713 |
Loadbalancer failing to connect to HTTPS requests. |
6409992 |
Upgrade failed with certificate from 8.1pe to 8.2EE |
6413224 |
upgradetool skipped upgrade certificate option |
6422893 |
HTTPS routing dosent work |
6424051 |
Need to use existing admin credentials and MP in 8.xPE to 9.1 EE upgrade |
6424053 |
8.XEE->9.1EE upgrade fails with a start-domain exception |
6430394 |
Messages are lost when there is a n/w outage. |
6444052 |
Integrate Generic RA for JMS version 1.5 into AS 8.2 EE |
6444308 |
AS 8.1 UR2 EE-> 8.2 EE SS: Unable to start 8.2's domain1; wrong 8.1UR2's domain star |
6444368 |
upgrade hangs from 8.0PE UR1 to 9.1 ee on win2003 side by side GUI |
6446558 |
Manual transaction recovery does not work for connector-connection-pool resources. |
6447895 |
Transction recovery not working for resources using embedded RA. |
6454007 |
Change the input required for upgrade tool |
6455396 |
Node-agent and instances fail to startup after an 8.1EE->9.1EE SBS upgrade. |
6374533 |
For performance and stability reasons Application Server should bundle XWSS 1.1 and not XWSS 1.0 |
6358422 |
Appserver 7.1/8.1 EE: web server LB proxy plug-in should properly support keep-alive connections |
6382063 |
Memory leak in com.sun.enterprise.iiop.IORToSocketInfoImpl |
This section describes important additional information about the HADB implementation included in Application Server 8.2.
A new management command hadbm setadminpassword has been implemented to allow changing the password used for database administration. The command takes options indicating which management agent to use, and the old and new password. For more information, see the hadbm setadminpassword man page.
The existing management command hadbm listpackages has been modified. Previously, the command took no operands, and listed all packages in the relevant management domain. The modifications introduces an optional package name operand, and lists only packages with that name. If the operand is not provided, all packages are listed. For more information, see the hadbm listpackages manpage.
The existing management command hadbm createdomain has been modified. The hostlist operand is extended to also specify the port number of the management agent. In this way, the domain is completely specified using only the hostlist operand. The old behavior is still supported for backward compatibility. For more information, see the hadbm createdomain manpage.
Some of the error messages from the management system have been modified. The modifications are intended to improve understandability, consistency and accuracy of the error messages. The actual modifications are not listed in these release notes.
The installation and uninstallation behavior has been slightly changed. Installing or uninstalling the HADB should always preserve the softlink /opt/SUNWhadb/4, but this has not always been the case.
The possibility of entering passwords on the command line as a command option is deprecated. This is relevant to all hadbm commands taking passwords as command line options. For hadbm commands, it has previously been possible to enter a password as:
A password file
A command line option
An interactive input
Method 2, the command line option, is considered unsafe, and is therefore deprecated. A warning message is issued if a password is entered in this way. Instead, use a method 1, password file, or method 3, interactive output. Using a password at the command line will become obsolete in the next release. Note this applies to all hadbm commands taking a command line password option.
HADB has been upgraded to use JGroups Version 2.2, and its source code is distributed along with the HADB. To support online upgrade from a previous HADB version, both JGroups 2.1 and 2.2 are delivered with HADB. For JGroups 2.1, byte code is delivered only.
There are several important considerations if you want to configure HADB to use one of the following file systems:
ext2 and ext3– HADB supports ext2 and ext3 file systems for Red Hat Application Server 3.0. For Red Hat Application Server 2.1, HADB supports only the ext2 file system.
Veritas– When the Veritas File System is used on the Solaris platform, the message “WRN: Direct disk I/O mapping failed“ is written to the history files. This message indicates that HADB cannot turn on direct I/O for the data and log devices. Direct I/O is a performance enhancement that reduces the CPU cost of writing disk pages. It also causes less overhead of administering dirty data pages in the operating system.
To use direct I/O with the Veritas File System, use one of the following:
Create the data and log devices on a file system that is mounted with the option mincache=direct. This option applies to all files created on the file system. See the mount_vxfs(1M) command for details.
Use the Veritas Quick I/O facility to perform raw I/O to file system files. See the VERITAS File System 4.0 Administrator's Guide for Solaris for details.
Note that these configurations have not been tested with Application Server 8.2.
Refer to the Application Server Enterprise Edition High Availability Administration Guide for information about installing and configuring HADB with Application Server software.
Users should keep the HADB history files, management agent configuration files, log files and repository, and all the data devices outside the installation path. If not, this should be done prior to the upgrade. To move the management repository and configuration files:
Stop all the old management agents and keep the HADB nodes running.
On each host, move the repository directory to the new location.
On each host, copy the dbconfig directory to the new location.
On each host, update the mgt.cfg file, and set the correct path for dbconfig and repository directory.
Start the management agents using the updated mgt.cfg file.
To upgrade from HADB version 4.4.x to version 4.4.3, perform the following steps:
Perform the pre-upgrade tasks mentioned above as necessary.
Install HADB version 4.4.3 on all HADB hosts (on another path than that of version 4.4.x, for instance on /opt/SUNWhadb/4.4.3).
Install the HADB 4.4.3 version on the hadbm client hosts, if they are different than that of the HADB hosts.
Stop all management agents running on all HADB hosts.
Start the management agent processes using the new version's software, but with the old configuration files. In the remaining steps, please use the hadbm command found in the new version's bin directory.
Register the package in the management domain (default package name becomes V4.4, so another package name may be required to avoid conflicts with existing packages having the same name):
hadbm registerpackage --packagepath=/opt/SUNWhadb/4.4.3 V4.4.3 |
Run the hadbm listpackages command and check that the new package is registered in the domain.
Restart the database with the new hadbm version 4.4.3. If it is necessary to move the devices and history files, run online upgrade combined with setting new paths for devices and history files in one single operation:
hadbm set packagename=V4.4.3,devicepath=new_devpath, historypath=new_histpath |
Otherwise, if the devices and history files are already outside of the installation directory, run the following command, which only does a rolling restart of the nodes:
hadbm set packagename=V4.4.3 database name |
Check that the database status is “running” (using the hadbm status command) and that it functions normally, serving the client transactions.
If everything is working, the old installation can be removed later. Before unregistering the old package, remove all references to the old package from the ma repository. Otherwise, hadbm unregisterpackage will fail with “package in use.” A dummy reconfiguration operation, for instance, hadbm set connectiontrace=same as previous value will remove all references to the old package. Now, unregister the old package:
hadbm unregisterpackage [--hosts=host-list] old pacakge name |
Remove the old installation from the file system.
On Solaris, to test that the upgrade was successful, check that the upgrade was performed properly:
Ensure that the running processes use the new binaries. Check the following in all HADB nodes:
new path/bin/ma -v new path/bin/hadbm -v |
Check whether the database is running. The following command should show that all the HADB nodes are in a “running” state.
new path/bin/hadbm status -n |
Ensure that the products using HADB have changed their pointers to point to the new HADB path.
The products using the HADB can run their upgrade tests to verify the HADB upgrade is also working.
After an online upgrade, if the new version does not work properly, go back to using the previous HADB version. However, if there has been a change to the management agent repository, the HADB itself can be downgraded, but the new management agent must be kept running.
This section lists additional information about HADB deployment and upgrading.
Store device, log and history files on local disks only, do not use remote-mounted file systems.
If more than one node is placed on a host, it is recommended to keep the devices belonging to each node on different disks. Otherwise, the disk contention would reduce the performance. Symptoms of this problem can be seen in the history files by the messages such as BEWARE - last flush/fputs took too long. When one single node has more than one data device file, it is recommended to use separate disks for these device files.
Use local disks (preferably separate disk than the one used for data devices) to install HADB binaries on HADB hosts. NFS delays or disk contention may cause node restarts with warning, “Process blocked for nnn, max block time is nnn” in the history files.
Do not place the HADB devices, history files, management agent directories and agent configuration files in the HADB package path. This will cause problems when upgrading to newer versions and deleting the old package path.
This release of HADB is officially supported for a maximum of 28 nodes; 24 active data nodes with 4 spares.
We recommend using the same version for the JDBC driver and the HADB server.
We do not support IPv6, only IPv4.
The command line length on Windows is restricted to 2048 bytes.
The network must be configured for UDP multicast.
Due to excessive swapping observed in RedHat Enterprise Linux 3.0, updates 1 through 3, we do not recommend it as a deployment platform. The problem is fixed in RedHat Enterprise Linux 3.0 update 4.
Possibility of running NSUP with real time priority.
The node supervisor (NSUP) processes (clu_nsup_srv) ensure the high availability of the HADB with the help of exchanging “heartbeat” messages in a timely manner. The timing gets affected when an NSUP is colocated with other processes causing resource starvation. The consequence is false network partitioning and node restarts (preceded by a warning “Process blocked for n seconds” in history files) resulting in aborted transactions and other exceptions.
To solve this problem, clu_nsup_srv (found in installpath/lib/server) must have the suid bit set and the file must be owned by root. This is achieved manually by the commands:
# chown root clu_nsup_srv # chmod u+s clu_nsup_srv |
This causes the clu_nsup_srv process to run as the user root when started, and this in turn allows the process to automatically give itself real-time priority after startup. To avoid any security impact by using setuid, the real-time priority is set in the very beginning and the process falls back to the effective uid once the priority has been changed. Other HADB processes will lower their priority to timeshare priority.
If NSUP could not set the real-time priority, it issues a warning, “Could not set realtime priority” (unix: errno will be set to EPERM), which is written out in ma.log file and continues without real-time priority.
There are cases where it is not possible to set real-time priorities; for example:
When installed in Solaris 10 non-global zones
When PRIV_PROC_LOCK_MEMORY (Allow a process to lock pages in physical memory) and/or PRIV_PROC_PRIOCNTL privileges are revoked in Solaris 10
Users turn off setuid permission
Users install the software as tar files (nonroot install option for the App.server)
The clu_nsup_srv process is not CPU consuming, its footprint is small and running it with real-time priority will not impact performance.
Configuring IP network multipathing for HADB for Solaris (tested on Solaris 9 only).
Sun recommends that Solaris hosts running HADB be set up with network multipathing in order to ensure the highest possible network availability. Network multipathing setup is covered in detail in the IP Network Multipathing Administration Guide. If you decide to use multipathing with HADB, refer to the Administering Network Multipathing section of the IP Network Multipathing Administration Guide in order to set up multipathing before you proceed with adapting the multipathing setup for HADB as described below. The IP Network Multipathing Administration Guide is part of the Solaris 9 System Administrator Collection, and can be downloaded from http://docs.sun.com.
Set network interface failure detection time
For HADB to properly support multipathing failover, the network interface failure detection time must not exceed 1000 milliseconds as specified by the FAILURE_DETECTION_TIME parameter in /etc/default/mpathd. Edit the file and change the value of this parameter to 1000 if the original value is higher:
FAILURE_DETECTION_TIME=1000 |
In order for the change to take effect, issue the following command:
pkill -HUP in.mpathd |
IP addresses to use with HADB
As described in the Solaris IP Network Multipathing Administration Guide, multipathing involves grouping physical network interfaces into multipath interface groups. Each physical interface in such a group has two IP addresses associated with it: a physical interface address and a test address. Only the physical interface address can be used for transmitting data, while the test address is for Solaris internal use only. When hadbm create --hosts is run, each host should be specified with only one physical interface address from the multipath group.
Example
Assume that Host 1 and Host 2 have two physical network interfaces each. On each host, these two interfaces are set up as a multipath group, and running ifconfig -a yields the following:
Host 1
bge0: flags=1000843<mtu 1500 index 5 inet 129.159.115.10 netmask ffffff00 broadcast 129.159.115.255 groupname mp0 bge0:1: flags=9040843<mtu 1500 index 5 inet 129.159.115.11 netmask ffffff00 broadcast 129.159.115.255 bge1: flags=1000843<mtu 1500 index 6 inet 129.159.115.12 netmask ffffff00 broadcast 129.159.115.255 groupname mp0 bge1:1: flags=9040843<mtu 1500 index 6 inet 129.159.115.13 netmask ff000000 broadcast 129.159.115.255 |
Host 2
bge0: flags=1000843<mtu 1500 index 3 inet 129.159.115.20 netmask ffffff00 broadcast 129.159.115.255 groupname mp0 bge0:1: flags=9040843<mtu 1500 index 3 inet 129.159.115.21 netmask ff000000 broadcast 129.159.115.255 bge1: flags=1000843<mtu 1500 index 4 inet 129.159.115.22 netmask ffffff00 broadcast 129.159.115.255 groupname mp0 bge1:1: flags=9040843<mtu 1500 index 4 inet 129.159.115.23 netmask ff000000 broadcast 129.159.115.255 |
Here, the physical network interfaces on both hosts are the ones listed as bge0 and bge1. The ones listed as bge0:1 and bge1:1 are multipath test interfaces (they are thus marked as DEPRECATED in the ifconfig output), as described in the IP Network Multipathing Administration Guide.
To set up HADB in this environment, select one physical interface address from each host. In this example. we choose 129.159.115.10 from host 1 and 129.159.115.20 from host 2. To create a database with one database node per host, use the following argument to hadbm create:
--host 129.159.115.10,129.159.115.20 |
To create a database with two database nodes on each host, use the following argument:
--host 129.159.115.10,129.159.115.20,129.159.115.10,129.159.115.20 |
In both cases, the ma.server.mainternal.interfaces variable on both hosts should be set to 129.159.115.0/24.
It is not possible to upgrade from 4.2 or 4.3 to 4.4 online. However, 4.4 supports online upgrade for the future versions. To upgrade from 4.4.1 to 4.4.2, perform the following steps:
Install 4.4.2 on all HADB hosts (On another path than that of 4.4.1 – for instance /opt/SUNWhadb/4.4.2-6).
Install the new version on the hadbm client hosts.
Stop all management agents running on the HADB hosts.
Start the management agent processes using the new version's software, but with the old configuration files. In the remaining steps, please use the hadbm command found in the new version's bin directory.
Register the package in the management domain (default package name here becomes V4.4, so another package name may be required to avoid conflicts with existing packages having the same name):
hadbm registerpackage --packagepath=/opt/SUNWhadb/4.4.2-6 V4.4.2 |
Restart the database with the new version (the following command does a rolling restart of the nodes):
hadbm set packagename=V4.4.2 database_name |
Check that the database status is “running” (using the command hadbm status) and that it functions normally, serving the client transactions.
If everything works, the old installation can be removed later.
Before unregistering the old package, remove all references to the old package from the ma repository. Otherwise, hadbm unregisterpackage will fail with “package in use.” A dummy reconfiguration operation, for instance, hadbm set connectiontrace=<same_as_previous_value> will remove all references to the old package. Now, unregister the old package:
hadbm unregisterpackage [--hosts=<host_list>] <old_package_name> |
Remove the old installation from the file system, as described in the HADB installation instructions.
It is not possible to create a UNIQUE secondary index on a table.
The expression (DISTINCT column) is not allowed in an aggregate expression, unless this is the only selected expression.
All tables must be created with a primary key specification (that is, tables without primary keys are not supported).
FULL OUTER JOIN is not supported.
IN subqueries that are table subqueries are not supported; for example:
SELECT SNAME FROM S WHERE (S1#,S2#) IN (SELECT S1#,S2# FROM SP WHERE P#='P2') |
Constraints other than NOT NULL and PRIMARY KEY are not supported.
It is possible to assign a new owner to a resource. When doing this, however, privileges granted to the current owner are not granted to the new owner.
Two or more nested NOT EXISTS subqueries where each subquery is not (directly) correlated to outer level of queries, is not supported.
Column privileges are not supported.
Row value constructors are allowed only in a VALUES clause.
Subqueries are not accepted as value expressions in row value constructors.
The following data types cannot be used when creating primary keys:
REAL
FLOAT
DOUBLE PRECISION
DECIMAL
NUMERIC
The Application Server includes load balancing for HTTP, IIOP, and JMS clients; HTTP session failover support; EJB clustering and failover support; highly available EJB timers; distributed transaction recovery; support for rolling application upgrades; and a high availability database for storing the transient state of J2EE applications.
Availability allows for failover protection of Application Server instances in a cluster. If one Application Server instance goes down, another Application Server instance takes over the sessions that were assigned to the unavailable server. Session information is stored in the HADB. HADB supports the persistence of HTTP sessions, Stateful Session Beans, and Single Sign On credentials.
In the next major release of the Sun Java System Application Server Enterprise Edition the following incompatibilities will be introduced:
While the HTTP Service will continue using a DNS cache for better performance, monitoring of the DNS cache will not be available.
The support for HTTP file caching will be revamped, resulting in changes to configuration and monitoring.
The format for the access log rotation suffix will be changed to the format supported by date and time objects as specified in http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html. The default value in this release, “%YYYY;%MM;%DD;-%hh;h%mm;m%ss;s,” will continue to be supported but no other variations will be supported.
Any domain.xml elements, attributes and properties no longer supported will be flagged as warnings in the server log and in the upgrade log file as having been deprecated.
The server.http-service.dns node will no longer be available in the monitoring view.
Some of the attributes from the server.http-service.file-cache node may be removed. Consequently, any asadmin monitoring command trying to access removed attributes from these nodes will fail.
Deploytool will no longer be available. The equivalent functionality is available in the NetBeans IDE. For more information, please see J2EE 1.4 tutorial for NetBeans 4.1 at http://www.netbeans.org/kb/.
Verifier GUI mode (invoked by verifier -u) will no longer be available. The equivalent functionality will be available in the NetBeans IDE.
The default mode for application verification when using verifier tool will change from “Verify J2EE rules” to “Verify J2EE rules and Sun Application Server Configuration Rules.” In other words, by default verifier will test whether an application meets J2EE rules and is configured to run on Sun Application Server. The verifier command will have a command-line switch to test an application for J2EE rules only.
In the current release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix attributes of domain.xml (application server configuration file) are available in the JVM system classpath. An application depending on this behavior might be using the following methods from the class java.lang.ClassLoader to access classes or other resources from JVM system classpath:
getSystemClassLoader()
getSystemResource()
getSystemResourceAsStream()
getSystemResources
In the next major release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix will no longer be available in the JVM system classpath. If an application uses one of the methods mentioned above, Sun strongly recommends using an equivalent method that does not assume that the resources are available in the system classpath. The equivalent methods that do not rely on the JVM system classpath are available in java.lang.ClassLoader and should be used when possible; for example:
java.net.URL url = ClassLoader.getSystemResource ("com/acme/tools/tools.properties");
java.net.URL url = this.getClass().getClassLoader().getResource ("com/acme/tools/tools.properties");
If it is not possible to change the code, then you may choose to use a new configuration option that will be added in the next release to set JVM system classpath.
Security for Web services can be configured using the files wss-client-config.xml and wss-server-config.xml. Please note that the content and names of these configuration files are unstable and likely to change. The equivalent functionality will continue to be available.
The Sun Java System Application Server Enterprise Edition 8.2 supports the J2EE 1.4 platform. The following table describes the enhanced APIs available on the J2EE 1.4 platform.
Table 2–5 APIs Available on the J2EE 1.4 Platform
API |
Description |
Components |
|
Application and Application Client |
Implementation of standard deployment descriptors by means of XML schemas |
Enterprise JavaBeans (EJB) 2.1 |
Timer service and EJB Web-service endpoint |
Java Servlet 2.4 |
Web-service endpoint filter |
JavaServer Pages (JSP) 2.0 architecture |
Expression language and tag library |
J2EE Connector Architecture 1.5 |
Inbound resource adaptor and Java Message Service (JMS) pluggability |
Web Services |
|
Java Web Services Developer Pack 1.5 |
Integrated toolkit for building, testing and deploying XML applications, Web services, and Web applications |
Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.1 |
Mapping for WSDL and Java technology and support for development of Web-service clients and endpoints |
WS-I Basic Profile 1.0 |
The enabling element for interoperability using WSDL and SOAP |
SOAP with attachment API for Java (SAAJ) 1.2 |
An API for SOAP-based messaging; fosters the creation of SOAP messages with attachments |
Java APIs for XML Registries (JAXR) 1.0 |
A uniform and standard API for accessing XML registries, such as those for Universal Description Discovery and Integration (UDDI and ebXML) |
Other |
|
J2EE Deployment 1.1 |
Standard APIs that enable deployments of J2EE components and applications |
J2EE Management 1.0 |
Definitions for the information model for managing the J2EE platform |
Java Management Extensions (JMX) 1.2 |
Standard management API |
Java Authorization Contract for Containers (JACC) 1.0 |
Definitions of security contracts between a J2EE Application Server and the authorization policy provider |
Java API for XML Processing (JAXP) 1.2 |
An API with which applications can parse and transform XML documents; also adds support for processing of XML schemas |
JMS 1.1 |
A messaging standard that enables J2EE application components to create, send, receive, and read messages; also adds support for uniform APIs for queues and topics |
JavaMail 1.3 |
A set of abstract classes that model a mail system; also includes minor updates to the APIs |
Sun Java System Application Server 8.2 requires J2SE 5.0 or greater as the underlying JVM. If you want to switch from one Java version to another, perform the following general steps. (Windows and Unix)
Download the Java SDK (not the JRE) and install it on your system, if you have not already done so.
The Java SDK can be downloaded from http://java.sun.com/j2se.
Completely stop the Application Server.
You can use the following command line:
as-install/bin/asadmin stop-domain |
Alternatively, you can use the Administration Console GUI:
Edit the install_dir/config/asenv.conf file (asenv.bat on Windows), changing the value for AS_JAVA to point to the new J2SE home directory.
Edit the as-install/samples/common.properties file, changing the line beginning com.sun.aas.javaRoot... to reference the new J2SE home directory.
Restart the Application Server.
as-install/bin/asadmin start-domain |
The Application Server includes a high performance EJB container, Web container and services, and supports concurrent message delivery with the Sun Java System Message Queue software.
The Application Server supports horizontal scalability through clustering of server instances and request load balancing. It also achieves class leading vertical scalability supporting large multi-processor machines. The integrated message broker can be clustered for better scalability and availability. Client access from HTTP clients, RMI/IIOP based Rich Client Applications, Web Services Clients, and JRM Clients can be load balanced to Application Server clusters.
The Sun Java System Application Server Enterprise Edition 8.2 supports JavaServer Faces 1.1 technology. The JavaServer Faces technology consists of a set of server-side APIs that represent user-interface components that manage their state, event, handling, and input validation. The APIs also define page navigation and support internationalization and accessibility. You can add custom user-interface components with a JSP custom tag library.
While developing with JavaServer Faces technology, each member of a development team can focus on a single piece of the process. A simple programming model then links the pieces, resulting in a much more efficient and simpler development cycle.