test

Sun Java System Portal Server 7.2 Release Notes

Sun Java System Portal Server 7.2 Release Notes

This Release Notes contains important information available at the time of release of Sun JavaTM System Portal Server 7.2. The document addresses new features and enhancements, known issues and limitations, and other information that supplement Sun Java System Portal Server 7.1 Update 2 documentation already available at docs.sun.comSM. Read this document before you begin using Portal Server 7.2.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: docs.sun.com. 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.

These release notes contain the following sections:

Third-party URLs may be referenced in this document and provide additional, related information.

Note –

Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Release Notes Revision History

Table 1 Revision History

Date  

Description of Changes  

May, 2008 

Release of Sun Java System Portal Server 7.2 Release Notes. 

About Portal Server 7.2

The Sun Java System Portal Server 7.2 is the first distribution release in open source. OpenPortal will include the source and binaries while the sun branded version will be available on http://www.sun.com as Sun Java System Portal Server 7.2. This release includes the Desktop Design Tool (DDT), Delegated administration features, Application Server 9.1 support, integration with Content Management System (CMS), Sun Java Composite Application Suite, and the requirements that emerge from open sourcing of the portal product.

The Sun Java System Portal Server product is localized in the following seven languages.

This section includes:

What's New in This Release

The following new features are available in Portal Server 7.2:

Deprecated or Removed Features

The following is a list of features deprecated in Portal Server 7.2:

Deprecation Notifications and Announcements

The Display Profile Locale tag may no longer be used to define the locale-specific properties in Portal Server 7.2. Use the ConditionalProperties tag with the locale type instead. For example:


<Locale language="en" country="US">
<String name="title" value="Sample JSP Channel"/>
<String name="description" value="This is the sample for the Jsp Provider"/>
</Locale>

Replace the above Locale tag with


<ConditionalProperties condition="locale" value="en_US">
<String name="title" value="Sample JSP Channel"/>
<String name="description" value="This is the sample for the Jsp Provider"/>
</ConditionalProperties>

Installing Portal Server 7.2

To install Portal Server 7.2, download the install bits and run the installer.

Portal Server 7.2 is supported on the following platforms:

For more information about installation on the Solaris and Linux platforms, refer to Chapter 1, Installing Sun Java System Portal Server 7.2, in Sun Java System Portal Server 7.2 Installation and Configuration Guide. The Installation and Configuration guide contains information, such as hardware and operating system requirements, software requirements, and verifying the Portal Server 7.2 installation.

Bugs in this Release

This section contains information on the open bugs in Portal Server 7.2.


Portal Server 7.2 cannot be installed remotely to Java ES 4 Access Manager. (# 6715798)

Description:

Access Manager and Directory Server in Java ES 4 are not supported in Portal Server 7.2. To install Portal Server 7.2, install the Access Manager and Directory Server from Java ES 5 Update1.


Deploying portlets on more than one server fails. (#6696161)

Description:

Deploying a portlet to multiple servers using psadmin works on the first server. However, the deployment fails for all subsequent servers.


Primary Domain Controller (PDC) does not work when Access Manager and Portal Server are on separate zones running on Web Server 7. (#6680401)

Description:

PDC breaks when you install Access Manager, Portal Server, and Gateway on separate zones or machines. Due to this PDC cookie cannot be set and hence cannot enable PDC authentication.


In Java Web Start (JWS) mode, Proxylet does not work on Firefox web browser. (#6692624)

Description:

In JWS mode, Proxylet works only on Internet Explorer 6.x and 7, but not on Firefox web browser.


In the Content Management System (CMS), Approver and Publisher's comments are corrupted. (#6690702)

Description:

In the CMS workflow channel, the comments provided for a task by the Approver and Publisher are corrupted.


In Simple API for Workflow (SAW) portlet, task cannot be searched using Start Date. (# 6683192)

Description:

In SAW portlet, you cannot search a task using Start Date. SAW sample portlet date functionality does not work when you start the web container in a locale other than English.

Solution:

Start the web container in C locale.


In the File sharing Portlet, adding multibyte file name shows garbled name. (# 6683144)

Description:

In the Enterprise Sample Portal, click Community and navigate to the File Sharing portlet. Add a new file with a multibyte name. The multibyte name of the file appears as garbled in the text box, where it displays all the files.

Solution:

Ensure that Derby and web container are running on the same locale.


In Mobile Access, client detection does not work. (#6677779)

Description:

Device profile does not get created when you try to access Portal Server with a new device.

Solution:

Follow the steps as a workaround for this issue.

  1. Add a new device and then change to required template such as wml or xhtml.

  2. The new device name that you have added can contain a part of the string of the device. For example, if the device name is OPWsimulator7.0.34, you can create a device with the name OPW and all the openwave devices of different versions will get detected and they will be given the required template (wml/xhtml) content.


psconfig fails in localized environment. (# 6677142)

Description:

Portal Server 7.2 configuration fails on a localized (non English) environment.


In Content Management System (CMS), the uploaded files have file names with reference to local disk location. (# 6699226)

Description:

When you upload a file to the CMS, the uploaded file has the file name with reference to the local disk location instead of the exact file name.

Solution:

Use Firefox browser to upload files instead of Internet Explorer browser.


Desktop Design Tool (DDT) does not change the images/logo, if the image names are not same as image names in skin file. (#6695404)

Description:

If you change the name of the image file other than the one mentioned in the skin file and preview the skin file, the changed names does not appear.

Solution:

Provide the same image name as the name available in the images directory of the skin folder.


In CMS, when you Revert a Template, the Action table does not display the checkout link. (# 6679539)

Description:

After updating a template, when you click the Revert Changes link, the Action table does not show the Checkout link. Instead, it shows the Edit Revert-Changes link.

Solution:

As a workaround, you can either logout from CMS and login again or click the Revert Changes link once again to display the Checkout link.


The usermanager.jar used in Workflow portlet does not log to portal logs. (# 6677130)

Description:

The logs generated by Workflow portlet does not show up in the Portal logs.


In Windows SharePoint Services (WSS) portlets, junk characters appear with localized list names. (# 6676121)

Description:

In WSS portlets, localized list names are displayed as junk characters in the channel title bar.

Solution:

Remove all escape()() functions in the normal.jsp file.


In CMS, when you click Manage Content without selecting the content, corrupted strings are displayed. (# 6675449)

Description:

In the CCD channel, when you click Manage Content without selecting the content, corrupted strings are displayed.

Solution:

As a workaround, click Ok on the pop up window. Select a content and click Manage Contents.


In CMS, maximizing the CCD portlet when creating or modifying a template makes the editor unusable. (# 6673749)

Description:

When you create or modify a template, if you maximize the CCD channel, you cannot see the table and the editor becomes unusable


Portal Logs are not generated in Windows Vista. (# 6673200)

Description:

Portal Server Logs are not generated in Windows Vista.


Few of the portlet deployment fails during deploying of samples after re-install of portal. (# 6670822)

Description:

When you uninstall Portal Server and reinstall it, you will get an error while deploying sample portals.


Installer window is not flexible to translated text. (# 6667228)

Description:

The Portal Server 7.2 GUI installer is not flexible to the translated text in few localized languages.

Solution:

Increase the size of the Portal Server 7.2 GUI installer panel.


WSRP sample configuration fails in realm mode with split root suffix. (# 6664099)

Description:

When you configure WSRP samples, you will get exceptions in realm mode with split root suffix. Due to this, the WSRP samples configuration fails.


Gateway does not startup on Windows Vista. (# 6646367)

Description:

Gateway does not startup due to the non-availability of SRA in Windows Vista .


In Windows SharePoint Services (WSS) Search, duplicate Site Names should not be allowed from GUI/CLIs. (# 6604678)

Description:

If you access WSS Search from CLI or GUI, it allows you to create duplicate site name and modify the existing site name with the duplicate name.


In PDC, Proxylet does not not work in JWS mode. Throws HTTP 400 error, when you click the Continue button. (# 6597459)

Description:

In PDC authentication, Proxylet works only in applet mode but not in JWS mode. When you click the Continue button, it throws HTTP 400 error.


Directory Server 6.2 (part of Java ES 5 Update1) hangs, when you install Portal Server 7.2 b13a in a multi-node environment. (# 6672742)

Solution:

You can follow the procedure below as a workaround for this issue.

  • Export data from Directory Server instance

  • Patch Directory Server 6.2 to Directory Server 6.3

  • Create new instance of Directory Server

  • Import data to the new Directory Server instance

Documentation Updates

Redistributable Files

Sun Java System Portal Server 7.2 does not contain any files which you can redistribute.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Portal Server, contact Sun customer support using one of the following mechanisms:

To assist you in resolving problems, please have the following information available when you contact support:

If you have problems with Sun Java System Portal Server, Mobile Access, please have the following information available when you contact support:

If your problems seem to be associated with a client, have the following information available:

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:

http://www.sun.com/hwdocs/feedback

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 this Release Notes document is 820-2045.

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations: