Sun Java™ System Portal Server Release Notes for Linux

Version 6 2004Q2

Part Number 817-6988-05

These Release Notes contain important information available at the time of release of Sun Java System Portal Server 6 2004Q2. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Portal Server 6.

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/prod/sunone. 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:

Release Notes Revision History
About Portal Server 6 2004Q2
Important Information
Known Issues and Limitations
How to Report Problems and Provide Feedback
Additional Sun Resources

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
June 22, 2004	Updated for Linux
May 18, 2004	Initial release of Sun Java™ System Portal Server 6 2004Q2 Release Notes.

---

About Portal Server 6 2004Q2

The Sun Java System Portal Server 6 product gives end users a portal Desktop, which provides access to resources and applications. The Portal Server software also provides a search engine infrastructure that enables intranet content to be organized and accessed from the portal Desktop. Additionally, in this release, the Communication Channels are now installed with the Portal Server software. The communication channels consist of mail, calendar, address book, and instant messaging channels.

Portal Server also offers Secure Remote Access support, which enables remote users to securely access their organization’s network and its services over the Internet. Additionally, it gives your organization a secure Internet portal, providing access to content, applications, and data to any targeted audience--employees, business partners, or the general public.

This section includes:

What’s New in This Release
Hardware and Software Requirements

What’s New in This Release

Sun Java Systems Portal Server 6 2004Q2 includes these new features:

Linux: RedHat EL AS 2.1 u2 now supported.
Web Services for Remote Portlets (WSRP)— This implementation of the OASIS standard simplifies integration of remote applications and content into portals. As a result, WSRP becomes the means for content and application providers to provide their services to organizations running portals with no programming effort required.
SSO Adapter—This feature provides a uniform infrastructure for providing middleware SSO functions.
Proxylet—This feature implements a web proxy as a downloadable applet. This provides the same functionality as the gateway reverse proxy without rewriting rules.
Support for OWA with Microsoft Exchange 2003 and Domino Server through Lotus iNotes web access.
Support for multiple Portal Server instances in multiple Java™ Virtual Machines (JVM™) on a single node of the Application Server—This feature provides the capability to support multiple separate portals on a single system. Each portal instance can be designed, deployed, and administered independently.
Autoclassification— This function of the Search service classifies documents into different categories automatically by a set of matching rules. Autoclassification can be executed on demand or scheduled to run at a specific time.
Profiler—This function of the Subscriptions service provides e-mail notifications when the content of specified interests has changed. The Profiler is scheduled to run at a specific time.
Identity Server/Portal Server Separation—Portal Server 6 2004Q2 does not require that Identity Server 6 2004Q2 be installed on the same physical server. Portal Server 6 2004Q2 can run with an instance of Identity Server 6 2004Q2 that has already been installed and configured on a separate physical server.
Mobile Access—Mobile Access is now installed with the Sun Java System Portal Server. The Mobile Access software extends the services and capabilities of the Portal Server platform to mobile devices, such as mobile phones and personal digital assistants. It also provides a framework for voice access. Mobile Access software enables portal site users to obtain the same content that they access using any HTML browser.

Hardware and Software Requirements

The following hardware and software are required for this release of Portal Server.

Table 2  Linux Hardware and Software Requirements 

Component	Platform Requirement
Operating System	Linux: RedHat EL AS 2.1 u2
RAM	512 Mbytes of RAM for evaluation install 1.2 Gbytes of RAM for regular deployment
Disk space	1 Gbyte of disk space for Portal Server and associated applications

For software requirements, see the Sun Java Enterprise System Release Notes at http://docs.sun.com.

---

Important Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes
Deprecated Features

Installation Notes

This section contains installation information for:

Portal Server
Web Containers

Portal Server

For Java Enterprise System 2004Q2, Portal Server can be installed and configured to run with either:

Identity Server installed and configured in the same installation session on the same physical machine
Identity Server previously installed and configured on a separate machine

To Run the Liberty Samples

The liberty samples are designed for a Portal Server and Identity Server installation on same system.

To run the Liberty samples on a Portal Server/Identity Server separated install, do the following:

Make sure the SP_HOST_DOMAIN value in configSP.sh points to the Identity Server full install host.
In the administration console of Identity Server that is acting as Service Provider, set the Provider Home Page to URL=http://portal-server-host:port/portal/dt

To set this value:

Select the federation management tab.
Select the service provider in navigation frame.
Select provider in the drop-down in data frame.
Scroll down to Identity Server Configuration section.
Set the Provider Home Page to URL=http://portal-server-host:port/portal/dt.

For Liberty Sample 3 only, perform Step 3 and Step 4.

Change “Single Sign-On Failure Redirect URL” and set it to http://portal-server-host:port/portal/dt?libertySSOFailed=true

To set this value:

Select the federation management tab.
Select the service provider in navigation frame.
Select provider in the drop-down in data frame.
Scroll down to Identity Server Configuration section.
Set the Single Sign-On Failure Redirect URL to http://portal-server-host:port/portal/dt?libertySSOFailed=true
Set the PreLoginURL to http://portal-server-host:identity-server-port/amserver/preLogin?metaAlias=is-host&goto=http://portal-server-host:portal-server-port/portal/dt

To set this value:

Go to Identity Management, Select Users from the drop down Menu.
Click on authlessanonymous user and then select Portal Desktop from the View drop down list in the Navigation Frame.
Click on the Edit link.
Click on Manage Channels and Containers.
Click on Edit properties of the Login Channel
Set the PreLogin URL to http://portal-server-host:identity-server-port/amserver/preLogin?metaAlias=is-host&goto=http://portal-server-host:portal-server-port/portal/dt.
Set the following in the AMConfig.properties file on the Portal Server host:
com.iplanet.am.notification.url=http://portal-server-host:port/servlet/com.iplanet.services.comm.client.PLLNotificationServlet
com.iplanet.am.session.client.polling.enable=false

Web Containers

After Portal Server and Identity Server SDK have been installed using Java Enterprise Server installer, use the following procedure to install JSR168 sample portlets or WSRP samples.

For detailed instructions on installing the Sun Java Server component products, refer to the Sun Java Enterprise System Installation Guide at http://docs.sun.com/db/doc/817-5760

The following manual steps are needed after the Portal Server and Identity Server SDK have been installed on Sun Java System Web Server 6.1 and Sun Java Server Application Server 7:

Restart the Web Server or Application Server instance
Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.
Execute the following commands to configure the WSRP samples.
portal-server-install-root/portal/samples/wsrpproducer/producersampleconfig

Provide the Identity Server admin password when prompted.

portal-server-install-root/portal/samples/wsrpconsumer/consumersampleconfig

Provide the Identity Server admin password when prompted.

Deprecated Features

The NetMail application is being deprecated in this release of the Sun Java System Portal Server product.

---

Known Issues and Limitations

This section contains a list of the known issues with Portal Server 6. The following product areas are covered:

Installation
Administration Console
Multi Server Instance
Secure Remote Access
Desktop
NetFile
Rewriter
Proxylet
Eproxy
Communication Channels
WSRP
Netlet
Mobile Access
Online Help
Localization

Installation

On the Linux platform, Portal Server tries to use a non-existent user portalbld during the installation of portal rpms. (5045274)

During installation, the installation logs at /var/opt/sun/install/logs, contains the following warning message:

warning: user portalbld does not exist - using root.

This message can be ignored.

Workaround

None.

On Linux, errors occur in the post-installation script. (5056584)

The following message is seen in the install log files when Netlet proxy or Rewriter Proxy components of Portal Server SRA are installed:

“[: : integer expression expected.”

This message can be ignored.

Workaround

None.

Portal Server Configurator fails because of domain specific issues after minimal mode installation. (5061212)

The following problems are associated with this bug:

Issue 1     The configurator does not work if the /var/sad/install/logs directory is not present. The configurator tries to write install logs into the /var/sad/install/logs directory. If the directory is not present the configurator fails.

Workaround

If the directory /var/sad/install/logs is not present, create the directory as root before running the configurator.

Issue 2    

For domains in which the DNS domain name is different from the domain part of the fully qualified domain name, the Portal Server and Portal Server, Secure Remote Access services URLS are formed with the DNS domain name instead of the correct fully qualified domain name.

For example, if the DNS domain name of the machine is mydomain-03.sesta.sun.com though the fully qualified domain name of the machines is host-name.sesta.sun.com., the following problems occur:

While entering Portal Server Information (even if the LoadBalancer check box is checked and the correct Portal Server URL is entered as the Load Balancer URL) the Portal Server and Portal Server, Secure Remote Access services URLS are formed with the host name host-name.mydomain-03.sesta.sun.com instead of host-name.sesta.sun. As a result of this issue it is not possible to administer the Portal Server using the admin console.

Workaround

None.

Because of this domain specific issue, deployment of Portal Server fails since the deploy command is unable to communicate with host-name.mydomain-03.sesta.sun.com.

Workaround

Redeploy the portal application after correcting the values of the variables PS_HOST and DEPLOY_ADMIN_HOST in the PSConfig.properties file at /etc/opt/sun/portal.

Issue 3     In the Portal Server, Secure Remote Access Panels, the subdomain text field contains the wrong name if the DNS domain name is different from the domain part of the fully qualified domain name.

For example, if the DNS domain name is mydomain-03.sesta.sun.com and the fully qualified host name is myhost.sesta.sun.com, then the sub-domain text field contains mydomain-03 as the value. Even if the user clears the text, mydomain-03 gets replaced.

Workaround

If the host name is myhost-01.sesta.sun.com , enter the details in Secure Remote Access panel as follows:

HostName: myhost-01

Sub-Domian: sesta

DomianName: sun.com

Portal Server SRA cannot be configured to run as a separate node on RedHat Linux. (5063218)

Portal Server SRA cannot be configured to run as a separate node on RedHat AS2.1U2, if the sun-portal-configurator rpm is not installed on the gateway. This problem occurs if the previous installation was incomplete.

The installation and configuration appears to be successful, but the gateway cannot start. Gateway startup fails with the following error:

/etc/init.d/gateway: //lib/psmacros: No such file or directory

Workaround

Cleanup only the box containing the gateway, and perform a fresh install of the Identity Server SDK and Portal Server.

To cleanup the gateway box:

Use the Java Enterprise System uninstaller to uninstall all components.
Check to see if all Java Enterprise System rpms are removed. Use the following command to see if the rpms are removed:

rpm -qa | grep -i sun should show no entries.

If any Java Enterprise System rpms are still on the box, manually remove them using:

’ rpm -e ’

Manually remove the following directories (assuming the default install locations are used):
/opt/sun
/etc/opt/sun
/var/opt/sun

Perform a fresh install of Identity Server SDK and Portal Server.

In a Portal Server-Identity Server installation, incorrect URL redirection occurs when authless is disabled. (5046549)

In a Portal Server-Identity Server separated install, if authless is disabled, the user is redirected to the URL portal-server-host/amserver/UI/Login which results in an error. The error message “Not found” is displayed.

Workaround

Specify the fully qualified login URL in the platform service of Identity Server. This URL can be the load balancer URL.

Note	When different Identity Server SDKs use a different Identity Server instance talking to the same Directory Server, this solution will not work.

Administration Console

Sample portlets not shown when a new container is added. (5048822)

After adding a new container channel, whenever a create new container page is displayed, the new portlet page will show an empty portlet list.

Workaround

Click on Portal Desktop in the navigation frame and then add the portlet channel.

Multi Server Instance

The Portal Server multiserverinstance script does not work. (5056218)

During the configuration of Portal Server on a new Web Server or Application Server instance using the “multiserverinstance” script at the location portal-install-dir/portal/bin, and error occurs.

Workaround

For the Web Server container:

Edit the multiserverinstance script and replace the following at line number 1170 in the ConfigureInstance() function:

$PS_BASEDIR/$PS_PRODUCT_DIR/bin/pss1ws61config

with

$PS_BASEDIR/$PS_PRODUCT_DIR/lib/pss1ws61config

For Application Server Container,

Edit multiserverinstance script and replace the following at line number 1172 in the ConfigureInstance() function.

$PS_BASEDIR/$PS_PRODUCT_DIR/bin/pss1as70config

with

$PS_BASEDIR/$PS_PRODUCT_DIR/lib/pss1as70config

Secure Remote Access

Gateway fails to start if Portal Server port is different from Identity Server port. (5044508)

The following command fails to start the gateway if the Portal Server port is different from the Identity Server port:

./gateway -n default start

Workaround

Use one of the following methods to workaround this problem

Edit the AMConfig-default.properties file and change the occurrences of the Portal Server port value to the Identity Server port value.
Use the gwmultiinstance script to delete and recreate the instance.

Clicking on Public folders prompts for user name, password, and domain name. (5022049)

When using Exchange 2003 through the gateway, users are prompted for user name, password, and domain name information when attempting to access public folders. This problem prevents users from being able access public folders.

Workaround

On the Exchange server, set the public folders authentication properties to use HTTP basic authentication.

Log off does not work for Exchange 2003. (5013288)

This problem is similar to bug 5022049. If the public folders in Exchange 2003 are not accessible, the user is unable to log off gracefully. The Exchange server settings should use only basic HTTP authentication for public folders.

Workaround

On the Exchange server, set the public folders authentication properties to use HTTP basic authentication.

If two gateways are installed on two portals, the gateways point to only one portal. (4915600)

The Forward Cookie URLs and the Portal Server list point only to one Portal.

Workaround

The Portal Server list field and the Forward Cookie URL field must be modified to include the second portal server.

In the administration console:

Click the Service Configuration tab.
Under SRA Configuration, click Gateway.
Click on the profile that you want to edit.
In the field, “URLs to which User Session Cookie is forwarded,” add the second Portal URL.
In the field, “Portal Servers,” add the second Portal URL.
Click Save.

Not all gateway services can be started when multiple gateway interfaces exist. (5020354)

When installing a Portal gateway, the gateway binds to the primary interface and not to all interfaces. This presents a problem when starting the gateway services. At startup the gateway sends its node Id and other credentials to the Portal-Identity Server services to authenticate and become an authorized Portal gateway. After successfully authenticating against the Portal-Identity Server, the response to the gateway is an SSO Login Token. This token gets lost because the gateway is listening to the external IP address and not the internal IP address.

Workaround

If the machine on which the gateway is installed has more than one interface, set the property value gateway.bindipaddress to 0.0.0.0 in the following file:

/etc/opt/sun/portal/platform.conf.instance_name

Doing so will make the gateway listen on all interfaces on the specified port.

Desktop

A memory leak occurs when running on RedHat ES Linux 2.1. (5059662)

A slow increase in the memory usage of the JVM occurs when running Portal Server on RedHat ES Linux 2.1.

Workaround

None.

NetFile

NetFile Java2 saves a change even when the user chooses not to save the session. (5031464)

After adding a share to a server, the share is automatically saved in the session regardless or not we save the session.

Workaround

Manually remove the change before closing NetFile Java2.

The NetFile Java2 drag and drop function does work properly. (5031489)

NetFile Java2 supports Drag & Drop of Files/Folder from “Remote Hosts” to “Local Hosts” and Drag & Drop of files from “Local Hosts” to “Remote Hosts.” It does not support Drag and Drop of files from “Local Hosts” to “Local Hosts” or “Remote Hosts” to “Remote Hosts.”

Workaround

None.

NetFile Search is not working for hosts of type Netware. (5049696)

Workaround

None.

In NetFile Java1 or Java2, shares cannot be added to hosts of type NFS. (5055447)

Workaround

None.

Rewriter

A security info window is displayed when user searches for an existing string in Microsoft Exchange.(5063981)

When a user searches for an existing string, a security info window is displayed asking if the user want to view non-secure information.

This bug occurs when using Microsoft Exchange 2003 through a gateway.

Workaround

None.

Unnecessary security windows and Javascript errors occur when using Microsoft Exchange 2003 and Microsoft Exchange 200 sp3 through a Personal Digital Certificate (PDC) enabled gateway. (5063991)

Security windows are displayed for every page while navigating through Exchange.

Workaround

None.

Proxylet

The Portal Server Desktop cannot be accessed in SSL mode after Proxylet is downloaded. (4990035)

After the successful download of Proxylet, the gateway is not able to access the SSL installation of the Portal Server.

Workaround

None.

If the browser proxy setting, “Use the same proxy server for all protocols” is unchecked, and Proxylet is running, the desktop fails. (4990975)

Proxylet will be downloaded successfully, but the Desktop page does not load.

Workaround

None.

If cookies are disabled, Proxylet does not get downloaded and an exception is thrown. (4996257)

Proxylet does not work in cookieless mode for this release.

Workaround

None.

User input is required for Proxylet in Netscape Navigator 7.1 if a proxy is required to reach the gateway. (5010160)

A popup comes up to take input from user for the proxy settings. This popup comes only if the proxy setting is not direct and only for Netscape.

Workaround

None.

Unable to logout of Desktop in Mozilla 1.4 in Solaris if Proxylet is running. (5061250)

After successfully downloading Proxylet, the user cannot logout of the desktop. This problem occurs only when using Mozilla on a Solaris workstation while the server is on Linux.

Workaround

None.

Some applications do not work through Proxylet. (5045138)

Applications that require the socket connection to remain open after a response is sent from the destination server do not work with Proxylet.

Workaround

None.

Eproxy

The certadmin script does not delete the certificate in the same session. (4981061)

If you use the certadmin script to delete a certificate, and then try to re-create the certificate in the same session, a message is displayed that indicates the certificate already exists.

Workaround

Launch the certadmin utility in:

gateway-installation-dir/portal/bin

Choose the option “Delete Certificate” to delete the certificate.
Exit the certadmin utility by choosing “Quit.”
Relaunch the certadmin utility to re-create the certificate with the same name.

An error message thrown during creation of the gateway profile. (5009348)

Workaround

None.

Cannot Login through the gateway if proxy authentication is used for a Portal Server Domain. (5010775)

The user cannot log in from the gateway if a domain or subdomain is configured to use a proxy. This causes the gateway instance to be unusable.

Workaround

In the Administration Console

Select Service Configuration, and click on Gateway.
In the Proxies tab, add the fully qualified Portal Server URL to the “Do Not Use Web Proxy URLs” List.

The “launch calendar” link does not work when accessed through PDC enabled gateway. (5063964)

This occurs only in Internet Explorer.

Workaround

None.

Reliability tests fail due to StackOverFlow errors. (5043753)

If the Application session created by the Secure Remote Access is invalidated due to incorrect handling of appSession creation in SrapClient.java the Gateway ends up in an recursive loop and ultimately becomes unresponsive due to StackOverFlowErrors.

Workaround

None.

The client IP Address is not accessible in secure mode. (5044891)

The client’s IP Address cannot be obtain when directly connected to the gateway.

Workaround

None.

The gateway does not start in a chroot environment. (5045136)

In the chroot environment the host name resolution is not happening correctly and the gateway fails to start.

Workaround

None.

The mkchroot command does not work on Linux. (5046586)

When running the mkchroot command, all the environment variables are shown on the console, and later fails at the first step after providing chroot directory.

Workaround

None.

Communication Channels

The current MailProvider implementation will not work with SSL secured IMAP. (4919693)

Currently out of the box Java mail only supports IMAP and POP3.

Workaround

None.

WSRP

The consumer fails to connect to a producer that uses a dynamic IP address. (5005082)

Although this can be a rare situation in a real production system, a connection failure can occur when a producer is run on a system with no static IP address assigned to it. Due to a feature in the Java network layer which keeps a cache table of host names to IP addresses, when the producer host gets reassociated with a new IP address, this change does not get picked up, causing the consumer to encounter a network connection failure. A server restart is required to clear out the cache table.

Workaround

You can define a Java security property to control the TTL value of the cache entries. Currently the default value of networkaddress.cache.ttl has the default value of -1. This value must be changed to an appropriate value that is greater than -1.

The following is an excerpt from Java™ 2 Platform, Standard Edition (J2SE™) Javadoc™ which explains the current default value:

networkaddress.cache.ttl (default: -1)

Indicates the caching policy for successful name lookups from the name service. The value is specified as an integer to indicate the number of seconds to cache the successful lookup.

A value of -1 indicates “cache forever.”

Registration data is fixed rather than dynamic. (4996094)

The registration data sent by a consumer is fixed per installation— it is a hidden, global property. In a future release, defining registration data per consumer (or per producer) should be supported. Support for user profile mapping is somewhat limited in the current release.

Only one-to-one mapping is possible
Mapping is fixed per installation user profile mapping is to be re-designed in an upcoming release, possibly implemented as a Service Interface Provider (SPI) to allow maximum flexibility.

Workaround

Global registration data must be edited by using the amadmin command line interface.

The portletmanagement interface should be fully and properly implemented. (5027036)

The WSRP producer portlet management port type is not fully implemented.

The WSRP consumer implementations that access the portal WSRP producer should not depend on the portlet management port type’s operations.

Workaround

None.

WSRP sample script doesn’t work when Portal Server is installed on Appserver container. (5059667)

Workaround

Configure Producer, consumer, and remote portlets manually through the administration console. Refer to the Admin Online Help.

Netlet

Netlet does not work for SSL_RSA_WITH_NULL_MD5 Encryption Cipher. (5011629)

Workaround

Disable the “Enable Null Ciphers” attribute in the gateway profile.

Internet Explorer crashes while loading Netlet with the default Microsoft JVM. (4982582)

The netlet.cab file for Internet Explorer does not get signed correctly, which causes Internet Explorer to crash.

Workaround

Disable the JIT compiler in the browser.

Mobile Access

Portal Desktop

The native JSP desktop does not handle the case when the frontPageSize exceeds the maximum deck size (WmlDeckSize). (4950078)

Workaround

None.

Accessing the login link from an anonymous authentication page on a WML device fails. (4919061)

A translation error occurs on WML devices when login link is accessed from anonymous authentication page.

Workaround

Change the file path from wml/ to aml/wml.

To do this, complete the following steps:

Log in to the Identity Server administration console as the administrator.

By default, Identity Management is selected in the location pane and Organizations is selected in the Navigation Pane.

Select the Service Configuration tab.
From the Service Configuration pane on the left, under the Identity Server heading, click the arrow for Client Detection.

The Client Detection global preferences appear in the right pane.

Click the Edit link following the Client Types label.

The Client Manager interface appears. Details about HTML devices are displayed by default.

Select the base profile and then the device you have problems with.

For example, for OpenWave 4.1 simulator, select the WML base profile and then be OWG1_UP_4.1.20a_UP.Browser_4.1.20a-XXXX_UP.Link_4.1.HTTP-DIRECT.

Click Edit.
Change the value for The file path to pick up templates from: to aml/wml.
Click Save.

Mobile Mail Application

Using the Address Book option may cause an error when a user has multiple address book accounts. (4949726)

When a user selects the Address Book option when composing an email message using the Sun Java System mail application, the default address book is presented. The Address Book option launches the address book application that is first in alphabetical order in the configurations, which might not be the Sun Java System Address Book application.

For example, if the user has both Exchange address book and Sun Java System address book, composing a message from the Sun Java System mail application will bring up the Exchange address book instead of the Sun Java System address book.

Workaround

The portal administrator can change the address book configuration name of the address book so that it appears as the first choice for all users.

To do this:

Log in to the Identity Server administration console as the administrator.

By default, Identity Management is selected in the location pane and Organizations is selected in the navigation pane.

Click the Service Configuration tab.
From the list of Service Names in the location pane, click the arrow for SSO Adapter. The SSO Adapter configurations appear in the right pane.
From the SSO Adapter Configurations list, highlight the configuration for the address book.

The text appears in the text box so that you can change it.

Change the configName value and click Add. The new configuration appears in the list.
Highlight the original configuration and click Remove to delete it.
Click Save.

Mail is sometimes displayed as HTML document. (4938743)

Email messages sent with HTML in the body are displayed with the HTML source.

Workaround

No workaround is available. However, one known problem is a mail application setting that forces all email messages to be sent as HTML. To preserve the original formatting of messages, change the setting to plain text. To do this, use the mail client to complete the following tasks:

From the Edit option on the menu, select Preferences, then Mail & Newsgroups.
From the Mail & Newsgroups menu, click Send Format to display the Send Format preferences.
Click the Convert the message to plain text option.
Click OK.

When a View name contains a trailing space, the View link does not display. (4961620)

The View link does not display on a device if the View name ends with a space. Clicking Edit View results in a null pointer exception.

Workaround

Do not use leading or trailing spaces in view and rule names.

Cannot access an SSL instance of Portal Server, Mobile Access from the Nokia 6310i. (5038063)

Workaround

None.

Cannot login from simulator through the gateway in cookieless mode. (5027961)

Workaround

Enable the “Obtain Session from URL” parameter in the Administration Console:

Go to Service Configuration.
Select Gateway.
Select Gateway Profile.
Enable “Obtain Session from URL.”
Restart the gateway.

Voice is not working in Secure Remote Access domain. (5008540)

Workaround

None.

Online Help

The View-Hits Description is Incorrect. (4906369)

The description for the View-Hits attribute in the administrative help for the Search service is incorrect.

The description should be “View-Hits is a set of numbers that match resource descriptions to import. For example ‘2..5’ will display four resource descriptions RD 2 to RD 5.”

Workaround

None.

The SSO Adapter Index Page Does Not Work. (5016726)

The SSO Adapter administrative help index page has broken links. You can access the SSO Adapter administrative help by selecting Identity Management > Services>Portal Server Configuration > SSO Adapter or Service Configuration > Portal Server Configuration > SSO Adapter and clicking the Help link.

Workaround

None.

The Index link on some Online Help pages is broken. (5023307)

In localized versions of the Portal Server online help, the index link on the following Online Help files displays HTML comment out marks.

addressbook.htm
calendar.htm
imchan.htm
mailhelp.htm

Workaround

None.

Portal Help file is not retrieved in an Identity Server/Portal Server separation. (5028084)

Workaround

Create a symbolic link “online_help” in the docroot pointing to Portal_Server_Basedir/SUNWam/public_html/online_help.

Online Help for Proxylet attributes is missing. (5036777)

The help window does not show any help for Download Automatic, Client Bind IP and Port attribute.

This information is documented in the Sun Java System Portal Server, Secure Remote Access Administrator’s Guide; see the “Configuration Attributes” appendix.

Workaround

None.

The Help file link doesn’t work from admininistration console. (5045913)

The Secure Remote Access Admin Online Help link does not work when Portal Server is installed in Portal Server-Identity Server separated mode.

Workaround

None.

Localization

Portal Server

The search function in Netmail Lite does not work if the date format is incorrect. (4920181)

Date format specified for Search function in Online Help is wrong. The formats are depend on the locale.

Workaround

None.

The search function in Netmail Lite does not work if correct date format for a locale is not used. (4923793)

The date format when performing a search in Netmail is locale specific.The search function in Netmail Lite does not work if correct date format for a locale is not used.

Workaround

Depending on your locale, the date format can be:

yyyy/mm/dd
mm/dd/yy
dd/mm/yy
yyyy-mm-dd
yy-mm-dd

Detached My Applications and Bookmark channel links does not redirect. (4934285)

Workaround

Do not detach channels when you invoke the application.

The Filter Definition Move Up and Move Down buttons do not work. (4990897)

The Filter Definition Move Up and Move Down buttons for the search robot in the administration console do not work.

Workaround

Change the amAdmin locale from ja to en.

The Portal Desktop Notes channel does not use semi-colon as separator. (4990900)

The Desktop online help states that a semi-colon is used as a field separator. Semi-colons are treated as regular text by the Notes channel, not as a field separator.

The pipe “|” symbol is now used as a field separator.

Workaround

None.

Subscription admin online help needs update. (5004156)

The online help for the subscriptions admin missing some information for the field description. See Documentation Errata, Sun Java System Portal Server Admin Online Help for additional information on user attributes.

Workaround

None

Instant messenger starts in English from IM channel. (5019291)

Workaround

To run a localized version of Instant Messenger, click the Instant Messenger link in the “My Applications” channel.

Simplified Chinese Portal Server packages had broken links. (5029834)

This problem does not affect the functionality. The error messages can be ignored when running the Identity Server backup command am2bak.

The Netmail Local Installer fails to launch with an I/O error. (5030103)

The user cannot use the Netmail local installer.

Workaround

None.

The Calendar channel uses the wrong date format for EMEA locales. (5033728)

The date format in the Calendar channel for EMEA locales is Month, Day, Year and cannot be changed according to local conventions.

The date format should be Day, Month, Year.

Workaround

None.

Events in calendar channel have wrong time format for EMEA. (5033735)

Events displayed in the Calendar channel have only a 12-hour time format. They should have a 24-hour format as it is set in Calendar Server.

Workaround

None.

Moving a subfolder between folders in Netmail Lite throws an exception. (5035260)

Workaround

Before moving or deleting any subfolder, update the list of favorite folders.

After renaming folder in Netmail Lite, the content of the listbox with Favorite Folders is not updated. (5035338)

Workaround

Update the contents of the listbox manually.

“Subject or Body” is mistranslated in the ko locale. (5036201)

“Subject or Body” should be translated “Subject and Body.”

Workaround

None.

The default locale in UserInfo editing page is English when logging in to the Portal as a user in the simplified Chinese locale. (5036625)

Workaround

If logging in to the Portal Desktop as a user in the simplified Chinese locale, set the preferred language to simplified Chinese when modifying items in the UserInfo Channel.

Multibyte Resource Description Source does not work in the Search Import Agent. (5040410)

Resource Description source file name shall be in multibyte.

Search import from local file does not work on Windows 2000. (5044428)

Workaround

None.

Couldn’t start Instant Messenger with Java Web Start for chinese user in IM channel by Internet Explorer 6.0. (5045175)

Workaround

If you want start Instant Messenger with Java Web Start by Internet Explorer 6.0, invoke it by using the link in “My Applications” channel.

Mobile Access

The Date in the Calender is displayed according to the server’s locale instead of the user’s locale. (4971337)

Workaround

For the Japanese locale, restart the Application Server instance in the Japanese locale. Restart the Web Server in the Japanese locale.

Cannot display Korean characters in the “Subject” field. (4971926)

This problem occurs when a user sends mail with Messenger Express, but views in a mobile emulator.

Workaround

None.

The summer time feature should not exist for repeating tasks or events in the Japanese locale. (4976102)

Workaround

In the Japanese locale, change PS time zone to Asian/Tokyo.

HDML - Calendar, Mail and Addressbook entries become garbage. (4980304)

Mobile desktop (top page) and the first page of Calendar, Mail and Addressbook work, but when trying to browse contents, the pages become garbage.

The same mobile desktop can be displayed properly in Japanese from iHTML and XHTML emulators.

Workaround

None.

Invalid Rule/View URL Syntax error occurs when trying to add a rule. (4981706)

The user can’t use mobile mail view.

Workaround

None.

The registered event/task on CS or sending Mail via hand set can’t display Japanese. (5016588)

Workaround

None.

The address book name is “First name” “Last name” on Japanese locale. (5016687)

This is not a Japanese convention.

Workaround

None.

On JHTML phones, an http Post in cookieless mode fails with a server error. (5016717)

Workaround

None.

The “Repeat until Date” does not work, register on 1970/01/01 as completion. (5018683)

Users cannot register monthly due date event if the date format is “yyyy/mm/dd”

Workaround

The date format needs to be “mmddyyyy.”

Openwave 6.2.2 simulator login fails on cookieless mode. (5023264)

Workaround

None.

A corrupt group name is registered when the group name and member name are changed at the same time. (5023944)

The problem prevents the group name and member from being changed at the same time.

Workaround

Select the corrupt group name then correct only the group name. Do not change the other properties.

KDDI hand set can’t display contents after login. (5031441)

Workaround

None.

Wrong translation on the Mail in the ko locale. (5031791)

The message “Folder is empty. Delete” is displayed instead of “Folder is not empty. Delete.”

Workaround

None.

JHTML: Self-registration fails. (5036621)

Self-registration always fails for Chinese locale by emulator. (5034252)

Workaround

Self Register by Mozilla or Internet Explorer browser first.

Internet Explorer displays a server error at edit pop collection. (5038941)

Workaround

Use Netscape 7.1

Cannot create or update a calendar event or task if a field contains a Euro character. (5042089)

Workaround

None.

Portal Server, Secure Remote Access

Multibyte NetFile file name appears as Garbage in the File dialog box while saving. (4692046)

Workaround

Rename upon saving.

Netlet fails for multibyte rule name. (4892050)

Netlet does not accept multibyte rule names.

Workaround

None.

Cannot send mail using NetFile Java1. (4910252)

Users can send files with the file path containing single byte characters only.

Workaround

None.

In NetFile Java1, a created sub folder graphic appears in the wrong location. (5030798)

Workaround

Close the session and save the session change, then connect to NetFile Java1 again.

Netlet and Proxylet are still in English when a user in a non-English user logs in to the Desktop. (5031306)

Workaround

Change the password for the Identity Server admin, the Identity Server Ldap user and the Directory Server admin in the following two scripts according to your machine’s setting. Run these two scripts after Netlet and Proxylet are successfully installed. If you install Portal to a directory other than /opt/sun/portal, please update these scripts according that base directory before you run it.

----------------------------------------------------

#!/bin/sh /usr/jdk/entsys-j2se/bin/java

-DPS_CONFIG_DEBUG=y -DDEPLOY_ADMIN_PASSWORD= -DDS_DIRMGR_PASSWORD=
\DIDSAME_LDAPUSER_PASSWORD= -DIDSAME_ADMIN_PASSWORD=adminadmin -cp
\opt/sun/portal/lib/config.jar:/opt/sun/portal/lib/configL10N.jar com.sun.portal.config.ConfigureL10N configure Portal Server /etc/opt/sun/portal

------------------------------------------------------------------------

#!/bin/sh -x .

/etc/opt/sun/portal/PSConfig.properties /opt/sun/portal/bin/deploy deploy -instance $DEPLOY_INSTANCE -uri /portal -deploy_admin_password admin-password

Incorrect file path to admin Online Help in NetFile and Netlet properties. (5031330)

The Netlet Online Help is displayed on the NetFile page and the NetFile help is displayed on the Netlet page.

Workaround

To view the NetFile Online Help, go to the Netlet window and click Help.

To view Netlet Online Help, go to the NetFile window and click Help.

Unable to unzip the multibyte zip files created by NetFile. (5033641)

Multibyte file names get corrupted by using the unzip command.

Workaround

Use the gzip command.

Can’t open local file in NetFile due to wrong path setting. (5033644)

Workaround

None.

Mail cannot be sent to yahoo web mail from NetFile Java2. (5034264)

In NetFile Java2, mail cannot be sent from Local host to Yahoo webmail.

Workaround

Use NetFile Java1 to send a mail to Yahoo webmail.

Note	There is a limitation for using NetFile Java1. The path of the file should not contain multibyte characters.

Proxylet applet depends on server locale. (5034648)

This problem prevents the Desktop from being correctly displayed.

Workaround

None.

---

Documentation Errata

Sun Java System Portal Server Administrator’s Guide

Chapter 14; “Configuring the Communication Channels”

The following information is an addendum to Chapter 14 of the Sun Java System Portal Server Administrator’s Guide. It provides instructions for enabling access to Mail and Calendar applications.

Messaging Server and Calendar Server both verify the Internet Protocol (IP) address of the host where the browser requests a login session ID. If the IP address differs from the host IP address where the session ID is issued, Messaging Server and Calendar Server reject the session with a session time out message.

You must change the value of the parameter that enables and disables an IP security check to allow the user to access mail through Portal Server. The parameter that specifies whether to restrict session access to the login IP address, is:

service.http.ipsecurity

To disable ipsecurity for Messaging Server, perform the following steps in the command line on the machine running the mail server.

Log in to the Messaging Server.
Type the following command:

messaging-server-install-directory/sbin/configutil -o service.http.ipsecurity -v no

Change to root using the su command.
Stop Messaging Server using this command

messaging-server-install-directory/sbin/stop-msg

Start Messaging Server using this command:

messaging-server-install-directory/sbin/start-msg

To disable ipsecurity for Calendar Server, perform the following steps in the command line on the machine running the Calendar Server:

Log in to the Calendar Server.
Assuming calendar server is installed in /opt/SUNWics5, type the following:

cd /opt/SUNWics5/cal/config/

Edit the ics.conf file and set ipsecurity to no. For example:

service.http.ipsecurity = "no"

Assuming calendar server is installed in /opt/SUNWics5, restart Calendar Server by typing:

/opt/SUNWics5/cal/sbin/stop-cal

/opt/SUNWics5/cal/sbin/start-cal

Refresh or re-authenticate to the Portal Desktop; the “Launch Calendar” link should work.

Chapter 18; “Creating and Deleting Instances of the Server”

The guide includes a note stating that multiple-instances of the server are supported only with Sun Java System Web Server. This statement is incorrect—multiple instances of the server are supported on Sun Java System Application Server as well as Sun Java System Web Server.

Chapter 18; “Creating and Deleting Instances of the Server”

The procedure for creating and deleting instances of the Identity Server are incorrect. The commands amserver create or amserver delete are no longer used. For instructions on deploying or ininstalling additional instances of Identity Server see Chapter 1 of the Sun Java System Identity Server 2004Q2 Administration Guide at: http://docs.sun.com/source/817-5709/.

Sun Java System Portal Server, Secure Remote Access Administrator’s Guide

The following configuration information should be included in the Sun Java System Portal Server, Secure Remote Access Administrator’s Guide.

When the gateway is configured to use a Personal Digital Certificate (PDC), use the following procedure to access NetFile, Netlet, or Proxylet.

Export the client certificate from the browser in one of the following formats:
PKCS
JKS

After exporting the client certificate, the Java plugin should have the following JVM parameters that enable the VM to use the certificate:

javax.net.ssl.keyStoreType

javax.net.ssl.keyStorePassword

javax.netl.ssl.keyStore

Go to the Control Panel and launch the Java plugin.
From the Advanced Tab select Java Runtime Environment.
Specify the Java Runtime Parameters.

For example:

-Djavax.net.ssl.keyStore=<location of the client certificate in the local machine>

-Djavax.net.ssl.keyStoreType=pkcs12

-Djavax.net.ssl.keyStorePassword=<client _certificate_password>

Click Apply.
Close the Java plugin and restart the associated browsers.

Note	Only Virtual Machines (VMs) with Java™ Secure Socket Extension (JSSE) support Netlet with PDC.

Sun Java System Portal Server Admin Online Help

The Online Help for Subscriptions is missing some attribute information. The following additional descriptions apply to the subscription user attributes.

Code | Figure | Table describes the dynamic attributes for the Subscriptions Service (when viewed from the Service Configuration or Identity Management tab).

The table contains three columns: the first column identifies the attribute, the second column provides the default value for the attribute, and the third column describes the attribute.

Table 3  Subscriptions Server - User Attributes

Attribute	Default Value	Description
Category Subscriptions	No default subscriptions	minimum rating is the threshold rating above which subscription yields content. This field is a numeric value (-1,0,1,2,3) that corresponds to end user rating choices (Irrelevant, Routine, Interesting, Important, Must read). search server url is the URL of the target search server. This field is URL encoded
Category Subscriptions	No default subscriptions	search server url is the URL of the target search server. This field is URL encoded. target database is the database to be searched
Saved Search Subscriptions	No default subscriptions	search server url is the URL of the target search server. This field is URL encoded. target database is the database to be searched

---

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:

Sun Software Support services online at
http://www.sun.com/service/sunone/software

This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.

The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps

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

Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
What patches (with patch numbers) are installed
Whether the problem is seen on the phone, the emulator, or Mobile Access server
Whether the problem is specific to any particular type of device (for example, Sony Ericsson P800 or Nokia 3650)
Whether problem occurred on default installation of Mobile Access software (if applicable)
When the problem was first seen
Whether the problem occurs all the time or randomly
What changes, if any, were made just before the problem started
How many users are affected by the problem
The number instances of Mobile Access software and how they are linked to Portal Server software and Identity Server software
The number of machines and how they are set up with regard to Mobile Access software
What error messages or exceptions are reported in the log files under /var/opt/sun/portal/debug  or /var/opt/sun/identity/debug
What error messages are reported in the information window for emulators
What the web server port is where Mobile Access is installed

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

What client types are new
What default client type settings have changed and how
What errors or exceptions are reported in the /var/opt/sun/identity/debug/render.debug file or the /var/opt/sun/identity/debug/MAPFilterConfig file
What exceptions are reported in the taglibs log file /var/opt/sun/identity/debug/mapJsp

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 these Release Notes document is 817-6988-05.

---

Additional Sun Resources

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

Sun Java System Documentation
http://docs.sun.com/prod/sunone
Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone
Sun Java System Software Products and Service
http://www.sun.com/software
Sun Java System Software Support Services
http://www.sun.com/service/sunone/software
Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software
Sun Support and Training Services
http://training.sun.com
Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone
Sun Java System Developer Information
http://sunonedev.sun.com
Sun Developer Support Services
http://www.sun.com/developers/support
Sun Java System Software Training
http://www.sun.com/software/training
Sun Software Data Sheets
http://wwws.sun.com/software

---

Copyright � 2004 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 � 2004 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.