BigAdmin: Sun Java Enterprise System (Java ES) 5 Update 1
What's New
Begin Tab Sub Links At a Glance Active SubWhat's New

What's New in Java ES

Java ES 5 Update 1 is the First Update Release of Java ES
This is the first update release of Java ES. At Java ES 5, Sun instituted a new release model for Java ES that provided for major releases, minor releases, and update releases. Update releases, like Java ES 5 Update 1, focus on providing bug fixes and a constrained set of feature enhancements such that the release is suitable for rapid adoption by the majority of existing users. Other than in rare exceptions, an update release is 100% backwardly compatible with the prior release.

Because update releases are intended for rapid adoption, they use different delivery mechanisms from major and minor releases. See Getting the Java Enterprise System 5 Update 1 Software in Sun Java Enterprise System 5 Update 1 Release Notes for information about the delivery mechanisms for Java ES 5 Update 1.


What's New in Access Manager

The Access Manager software has not changed: both Java ES 5 and Java ES 5 Update 1 include Access Manager 7.1. However, a new manual has been added to the Access Manager 7.1 product documentation set:

Technical Note: Sun Java System Access Manager Localization Guide. This document describes the organization of localized Sun Java System Access Manager software resource files. It also explains how to add a new language to the list of languages supported by Access Manager and how to customize an existing language's resource files.


What's New in Directory Server Enterprise Edition

The following sections describe what's new in Directory Server Enterprise Edition 6.2 as compared to Directory Server Enterprise Edition 6.0, including what was new in Directory Server Enterprise Edition 6.1.

What's New in Directory Server Enterprise Edition 6.2

Directory Server Enterprise Edition 6.2 is a patch release that adds the following new features to the Directory Server Enterprise Edition 6.1 release:

What's New in Directory Server Enterprise Edition 6.1

General DSEE Enhancements
General DSEE enhancements include the following:

  • A Web archive (WAR) that contains the DSCC. This WAR file can be deployed on an application server, allowing you to install the DSCC when using the ZIP distribution.

New Features in Directory Server 6.1
Directory Server 6.1 includes the following new features and enhancements:

  • Database data compaction. Directory Server now allows you to compact the database files to gain space and reduce backup time.

    For more information about compacting your database files, see the dsadm(1M) man page.

  • Migration tools to help you upgrade from Directory Server 5.1. Directory Server provides the dsmig tool to help you migrate your schema, security information, and configuration information including replication.

  • Improved write and search performance. Directory Server includes improvements to the performance of almost all operations.

New Features in Directory Proxy Server 6.1
Directory Proxy Server 6.1 includes the following new features and enhancements:

  • Data views can be used in multiple joins. Directory Proxy Server allows you to create a new join that combines a new data view with an existing data view without any restrictions.

  • Extended JDBC support. JDBC now supported for Java DB® 10.2 , Oracle® 9i and 10g, DB2® v9.1, and MySQL® 5.0.

  • Improved write and search performance. Directory Proxy Server includes improvements to JDBC performance and RDBMS operation response time.

  • Support modifications to multiple RDBMS tables. Directory Proxy Server can now take a single LDAP modification and apply it to multiple RDBMS tables.


What's New in Portal Server

The following sections describe what's new in Portal Server 7.1 Update 2 as compared to Portal Server 7.1.

AJAXTableContainerProvider and AJAX Desktop
The Portal Server software now includes AJAXTableContainerProvider that provides AJAX based interaction for all container controls and features.

The AJAXTableContainerProvider integrates Asynchronous JavaScript and XML (AJAX) capabilities at the portal framework level. The container provides asynchronous loading of individual channels and portlets. Therefore, a slow channel or portlet will not affect the loading time of the other channels and portlets on a page, improving overall performance.

On the desktop, the AJAXTableContainerProvider provides rich user interface functionality such as:

  • Drag and drop positioning of channels and portlets on the page.
  • Asynchronous interaction for channel controls such as minimize, remove, and maximize.
  • Independent refresh for individual channels and portlets without refreshing the complete page.
  • Edit channels and portlets inline without refreshing the complete page.
  • Easy addition and removal of channels.
  • Multiple layouts for the portal desktop.

Blog Portlet
The Blog portlet allows portal users to manage weblog posts from a portal page utilizing the Atom Publishing Protocol (APP). Users can create, edit, and delete weblog entries. Additionally, this portlet provides a simplified interface for creating weblogs and weblog user accounts utilizing the Atom Admin Publishing Protocol (AAPP).

Community Management
Portal administrators can now perform administrative tasks on communities from the desktop, Portal Server management console, and psadmin command-line utility.

Portal administrators can now:

  • Create and Edit a community.
  • Enable, disable, delete, and undelete or destroy a community
  • List communities, community templates, community display profile names, and community users
  • Add and remove community users
  • Approve and deny community membership to users
  • Ban and unban community users
  • Add and remove community owners

Private Communities and Community Access Control
The communities portal now supports private communitites. A public community is open for anyone to join and gain membership. A private community is the most secure form of a community. It is hidden from the community categories and thus cannot be browsed or searched. It restricts membership by requiring users to request for and be granted a membership. Alternatively, the community owner can invite or manually add users to the community. The content of the community is protected from non-members such that they will not be able to view or search any posted content.

In addition, the individual aspect of community access can be customized based on the specific needs of the community. Community owners can now set up:

  • Restricted membership (private communities) or unrestricted membership (public communities) to communities.
  • Communities to be listed (public communities) or unlisted (private communities).
  • Community content to be secured (private communities) or unsecured (public communities).

Community URLs
Community URLs can now be accessed directly. Users can:

  • Bookmark the page in a browser.
  • Email the URL to another user who can click on the link from their mail reader to access the community.
  • Enter the URL directly into a browser, by hand.

The community URLs are of the form http://server:port/portal/dt?dt.community=community_name.

BigAdmin
  
 
BigAdmin Upgrade Hub