Sun Java System Application Server Enterprise Edition Release Notes for Microsoft Windows |
Sun Java System Application Server Enterprise Edition Release Notes for Microsoft Windows
Version 8 2005Q1
Part Number 819-1576-10
The Sun Java System Application Server Enterprise Edition 8 2005Q1 product greatly simplifies the task of creating and administering web services applications. It provides superior performance, clustering, and high availability features for scalable services that continue to operate despite software and hardware faults. The Application Server provides a development path for web services that simplifies the development process while providing uniquely flexible growth opportunities.
These release notes contain important information available at the time of the Sun Java System Application Server 8 2005Q1 product release for Windows. Component requirements, platform summary, known problems, and other late-breaking issues are addressed here. Read this document before you begin using the Application Server product.
The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/app/docs/coll/ApplicationServer8_pe_04q4. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.
This document contains the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
Release Notes Revision HistoryThis section lists the changes that have been made in these release notes after the initial release of the Application Server 2005Q1 component
.
About Application Server 8 2005Q1The Sun Java System Application Server Enterprise Edition 8 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 section includes:
What’s New in Application Server 8 2005Q1
The Sun Java System Application Server Enterprise Edition 8 2005Q1 implements many new and enhanced features, described in the following sections:
Enhancements in This Release
The Application Server Enterprise Edition 8 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, programatic 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.
- 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.
- 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 UNIX� platforms contain the new high availability database (HADB) management system (HADB version 4.4). This eliminates the dependency on SSH/RSH, but requires that the network be configured for UDP multicast. See the Sun Java SystemApplication Server Enterprise Edition 8 Installation Guide for the details on HADB requirements and limitations.
J2EE Support
The Sun Java System Application Server 8 2005Q1 supports the J2EE 1.4 platform. The following table describes the enhanced APIs available on the J2EE 1.4 platform.
High Performance
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.
Scalability
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.
High Availability
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.
JavaServer Faces 1.1 Support
The Sun Java System Application Server Enterprise Edition 8 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 UI 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.
Hardware and Software Requirements
This section lists the requirements that must be met before installing the Sun Java System Application Server Enterprise Edition 8 product.
Platform Requirements
The following table lists the operating systems that are supported for Sun Java System Application Server Enterprise Edition 8 2005Q1 product. Additionally, the minimum and recommended memory requirements are identified for installing and running the Application Server
.
To check your operating system version, use the ver command. To check the disk space use the mem command.
JDBC Drivers and Databases
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:
For more information about i-net Software, see:
The following table identifies additional supported JDBC drivers; however these drivers are not J2EE compatible.
Table 4 JDBC Drivers not J2EE compatible
JDBC Vendor
JDBC Driver Type
Supported Database Server
Oracle
Type 4
Oracle (R) 9.2.0.3, 10G
Sybase
jConnector
Sybase ASE 12.5.1
Additional drivers have been tested to meet the JDBC requirements of the J2EE 1.4 platform with the JDBC Driver Certification Program. These drivers can be used for JDBC connectivity with the Sun Java System Application Server. While Sun offers no product support for these drivers, we support the use of these drivers with the Sun Java Enterprise System Application Server.
Configuring Oracle
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:
-Doracle.jdbc.J2EE13Compliant=true
In addition, for Type-2 drivers, both the ORACLE_HOME and 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.
Configuring PointBase
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 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:
To use the first method:
To use the second method, the procedure depends on the operating system.
Solaris and Linux
Edit the install_dir/pointbase/tools/serveroption/pbenv.conf configuration file, changing the line:
PB_JAVA=%%%PB_JAVA%%%
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.
Windows
Edit the install_dir\pointbase\tools\serveroption\pbenv.bat configuration file, changing the line:
set PB_JAVA=%%%PB_JAVA%%%
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.
Web Servers
This section lists the web servers that are supported for the Sun Java System Application Server Enterprise Edition 8 2005Q1.
Browsers
This section lists the browsers that are supported with the Sun Java System Application Server Enterprise Edition 8 2005Q1.
Table 7 Browsers Supported
Browser
Version
Mozilla
1.4
Netscape Navigator
4.79, 6.2
Internet Explorer
5.5 Service Pack 2, 6.0
High Availability Requirements and Limitations
The following high availability requirements must be met before configuring the Sun Java System Application Server High Availability component:
Other Requirements
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 300 Mbytes free for Sun Java System Application Server installation, and 250 Mbytes 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 admin instance) and 38080 (for AppServer1 instance) for the HTTP server, and 4850 for the Admin Server.
- The installation program will detect used ports and assign two others for you: Sun JavaTM System Message Queue (by default, 7679), and IIOP (by default, 3750 for IIOP and 3347 and 3360 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: Unless you are replacing the previously installed server, you should start it before you begin the Sun Java System Application Server 8 installation process. This allows the installation program to detect ports that are in use and avoid assigning them for other uses.
- Shutting down firewall: You must stop any firewall 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 Upgrade and Migration Guide at: http://docs.sun.com/app/docs/doc/819-0222
Standalone Version
The standalone version of Sun Java System Application Server Enterprise Edition 8 differs in several ways from the Java ES Enterprise Edition version; specifically:
- The 8 standalone product can be installed by any user, whereas Java ES can only be installed as root user.
- The HADB component is visible as a subcomponent in the standalone version, whereas in the Java ES installation it is a shared component.
- The standalone version installs all shared components required for the Application Server under one installation directory, whereas in JES these components are installed in different directories.
- Product files, domains, and configuration data for the Application Server are stored by default in a single directory with the standalone installer, whereas with Java ES they are stored in multiple directories.
- The standalone version allows installation on a system with an already existing Application Server installation of the same or different version without the need to uninstall the existing installation. This is achieved by maintaining unique installation directories across versions OR across instances of the same version.
- The standalone version supports “upgrade in place” of an existing Sun Java System Application Server Platform Edition 8.0 installation or a Sun Java System Application Server Platform Edition 8 installation to the Sun Java System Application Server Enterprise Edition 8.
Related Documentation
In addition to these release notes, the Application Server component includes an entire set of documentation that can be found at this location:
The following table summarizes the books included in the Application Server core application documentation set.
Bugs Fixed in This ReleaseNone.
Known Issues and LimitationsThis section describes the known issues and limitations of Application Server Enterprise Edition 8 2005Q1 for Windows. For a list of the known issues and limitations in the component, refer to the following Release Notes: http://docs.sun.com/app/docs/doc/819-0214.
This section describes known problems and associated workarounds for the Sun Java System Application Server Enterprise Edition 8 2005Q1 component. If a summary statement does not specify a particular platform, the problem applies to all platforms. This information is organized into the following sections:
Load Balancer
Entries to be made to the ASConfigurator.properties file before configuring Load Balancer in Configure Later mode (6228092)
The Load-Balancer Plug-in is configured to use ports 1111 and 1112 in the server used for AS_WSINSTANCENAME in the ASConfigurator.properties file. Following entries must be made into the ASConfigurator.properties file before configuring Load Balancer in Configure Later mode:
Workaround
None.
The Load-Balancer Plug-in is configured to use ports 1111 and 1112
The Load-Balancer Plug-in is configured by default to use ports 1111 and 1112 in the ASConfigurator.properties file.
Workaround
None.
Configuration
Initial configurator in Configure Later does not have GUI
The initial configurator used in Configure Later mode does not have a GUI support.
Workaround
You can manually update the ASConfigurator.properties and run DASConfigurator.bat and LBConfigure.bat
Impossible to enter AS master password and the master pswd is unknown to the user (6295958)
The configurator will take the admin password as the master password. The AS_ADMINPASSWD that is entered in ASConfigutraor.properties will be taken as the masterpassword also.
Workaround
None.
Redistributable FilesSun Java System Application Server Enterprise Edition 8 does not contain any files that can be redistributed.
How to Report Problems and Provide FeedbackUse the following resources to handle problems you may encounter with the Application Server product:
- J2EE-INTEREST list: A mailing list for J2EE questions.
- Bug database on Java Developer Connection: To view bugs or to submit a bug, use the Java Developer Connection Bug Parade.
- Java Technology Forums: An interactive message board for sharing knowledge and questions about Java technologies and programming techniques. Use the J2EE SDK forum here for discussions related to the Sun Java System Application Server 8 Platform Edition product.
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:
Please provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of these Release Notes document is 819-1576-10.
Additional Sun ResourcesUseful Sun Java System information can be found at the following locations:
Copyright � 2005 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright � 2005 Sun Microsystems, Inc. Tous droits r�serv�s.
Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.
Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.