test

Sun Java System Portal Server 7.1 Update 2 Release Notes

Known Issues and Limitations

The following are the known issues and limitation of the Portal Server.


In the Japanese locale, after upgrading Portal Server 7.1 to 7.1 Update 2, you can not use a Japanese wiki name. (#6569515)

Solution:

While upgrading, manually set following variable before running the psupdate command:

export LC_ALL=en_US.UTF-8

export LANG=en_US.UTF-8


Portal Server administration console help is displayed in English. (#6513360)

Description:

In the fr-FR locale, Portal Server administration console help is displayed in English.


Localized help is not displayed for channels in the Admin and Portlet Samples tab. (#6421034)

Description:

In the Japanese locale, help is displayed in English for channels in the Admin and Portlet Samples tab.


Messages are not translated. (#6480324, 6540250)

Description:

Portal Server 7.1 Update 2 has the following localization issues:

  • In the Community sample, some of the messages are not translated.

  • Some of the messages are old and they need to use the new translated messages.


Allow or deny access to URLs functionality does not inherit to the users in an organization. (#6553271)

Description:

Do the following:

  1. Create an organization, gatewayorg, and create a user, g, in it.

  2. Log in to Portal Server administration console. Select SRA -> Access Control.

  3. For the user, g, add http://www.yahoo.com and deny access under the Allow/Deny access to URLs option.

  4. Restart the gateway profile.

  5. Log in to gateway as user, g, and from the bookmark provider invoke http://www.yahoo.com. This shows access denied.

  6. For g, allow access to http://www.yahoo.com.

  7. Restart the gateway profile.

  8. Log in to gateway as user, g, and from the bookmark provider invoke http://www.yahoo.com. The user can access http://www.yahoo.com.

  9. Delete the rule for the user and add a rule that deny access to http://www.yahoo.com for the gatewayorg.

  10. Log in to gateway as user, g, and from the bookmark provider invoke http://www.yahoo.com. The user can access http://www.yahoo.com.


Configuring time out property for persistent HTTP connection does not work. (#6568269)

Description:

Time out property for persistent HTTP connection does not work when you do the following:

  1. Log in to Portal Server administration console.

  2. Select the SRA tab.

  3. Select a gateway profile.

  4. Enable HTTP connections to the gateway on port 80.

  5. Select the Performance tab of that profile.

  6. Enable HTTP persistent connection.

  7. Set the Timeout for Persistent Socket Connections to 15 seconds.

  8. Telnet to the gateway on port 80 and type the following commands:


    GET /amconsole HTTP/1.1
Connection:keep-alive

    Headers are displayed.

  9. Wait for 20 seconds and try step 8.

    You will notice that the session time out did not occur.


When you select a proxy instance in the Monitoring tab of Secure Remote Access, an exception is displayed. (#6569625)

Description:

Exception is displayed when you do the following:

  1. Log in to Portal Server administration console.

  2. Select the SRA tab.

  3. Select the Monitoring tab.

  4. From the Select Proxy Instance, select the profile name. For example, profile:default.


On the Linux platform, you are not able to add shares for FTP in NetFile. (#6574393)

Description:

If you have enabled ipv6 on the Linux platform, you are not able to add shares for FTP in NetFile. If you are not using ipv6, disable it. You can use ipv4 instead of ipv6.


Blog portlet has issues in Portal Server. (#6557448)

Description:

Blog portlet has the following issues:

  • Some of the FCK Editor's functionality such as Browser Server, Upload File, and Create New Folder do not work with Blog portlet.


On the Japanese locale, the portlets in the Admin and Sample Portlets tabs display help in English. (#6421034)

Description:

The help needs to be localized.


You can not create a new channel or a container with a localized name under AJAXTableContainerProvider. (#6542381)

Description:

AJAXTableContainerProvider is not localized.


You can not add a local user to NFS share in Netfile. (#6545795)

Description:

User id should be in NIS to add a user to NFS share in Netfile. Also, only the shares listed in the /etc/dfs/dfstab file can be added to NFS share in Netfile.


Localized help is not displayed for the channels in the Admin and Portlets Samples tabs. (#6421034)

Description:

Help in the Admin and Portlets Samples tabs needs to be localized.


The Calender channel displays date in incorrect format. (#6411476)

Description:

The Calender channel displays date in incorrect format in Developer Sample.


Mobile Access supports only the default UWCMail channel that is provided with the Portal Server. (#6491303)

Description:

You can not add MailProvider or MailJSPProvider to the JSPRenderingContainer.


Clicking Clean Up HTML icon deletes the wiki page. (6545358)

Description:

While editing a Wiki page, if you click the Clean Up HTML icon and click OK, the wiki page is deleted.


From a Wiki page, you can not refer to another community url.(#6536333)

Description:

From a Wiki page, you can not refer to another community url that exists in the same host.


Wiki portlet jumps out of the portal context. (#6533753)

Description:

If you access undefined wiki page (as authless), wiki portlet jumps out of the portal context.


Some strings are truncated when you launch a Proxylet. (#6447909)

Description:

Some strings are truncated when you launch a Proxylet.


Taskadmin setup must set administrator role desktop service attributes. (#6519875)

Solution:

Do the following:

  1. Before running the taskadmin setup, ensure that the following Portal Desktop service attribute values for the admin role dns, found in the taskadmin.properties file: content.admin.role.dn and user.admin.role.dn.

  2. Match the organization Portal Desktop service attribute values.

    For example, if the EnterpriseSample organization Portal Desktop service attribute values are: Parent Container: ASCTabContainer, EditContainer: JSPEditContainer, and Default Type: enterprise_sample. The admin role DNs are both set to "cn=Organization Admin Role, o=EnterpriseSample, dc=siroe, dc=com".

  3. Ensure that the Portal Desktop service attributes for the admin role DN "cn=Organization Admin Role, o=EnterpriseSample, dc=siroe, dc=com" matches the organization settings. Otherwise, when a user that belongs to the admin role authenticates to the Portal Desktop, that user may be presented with the incorrect Portal Desktop.


UWC Calendar does not come up through gateway. (#6218353)

Description:

Clicking the Launch Calendar link displays the following error message, "Unable to load the requested page. Cookies are blocked."


SunOne Address Book does not work if Portal Server and Access Manager are installed on two different nodes. (#653732)

Solution:

Restart web container.


If Portal Server is installed on an Application Server cluster, you can not delete only one Portal Server instance. (#6506689)

Description:

You need to remove all Portal Server instances. Use the psconfig --unconfig command to unconfigure Portal Server or use the psadmin delete-portal command to delete Portal Server.


IPC can not be used with WSRP. (#6509086)

Description:

Inter Portlet Communication (IPC) cannot be used with WSRP. You can publish the portlets that participate in Inter Portlet Communication through WSRP. But the IPC functionality does not work.


The UserRoleAdmin-AdminTab is not visible for users with the OrganisationAdmin role. (# 6511559)

Solution:

Edit the /etc/opt/SUNWam/config/AMConfig.properties file on Portal Server or Access Manager SDK machine to set com.iplanet.am.session.client.polling.enable property to False. Then, restart Portal Server web container.


Portal Server is sensitive towards multiple JRE versions. (# 6510536)

Description:

If multiple JREs are present on the client machine, there may be issues in launching Java Web Start on Netscape and Mozilla browsers.

Solution:

Retain only one JRE on the client machine and uninstall others.


Due to the weak security status of SSL2, customers are advised to disable SSL2 and leave it disabled. (#6507762)

Solution:

Do the following to disable SSL2.

  1. Log in to the Portal Server administration console.

  2. Click SRA > Profile > Security.

  3. Under TLS And SSL, clear the SSL Version 2.0 Enable option.

  4. Click Save.


Using the Internet Explorer, when you try to deploy a portlet or create a new producer in WSRP, you are logged out. (#6491413)

Solution:

For Portal Server administration console, use a browser other than Internet Explorer.


Portal Server does not support a different web container for Access Manager. (#6470425)

Description:

Use the same web container for Portal Server and Access Manager.


You can not work with the strutssample.war if Portal Server is installed on Web Server 7.0. (#6505547)

Description:

If Portal Server is installed on Web Server 7.0 and strutssample.war is deployed, the psadmin commands that modify Web Server configuration do not work. For example, the psadmin deploy-portlet command.


Shared events and tasks are not able to create an event and task. (#6486930)

Solution:

During installation and configuration of shared events and shared tasks, in the tokens.properties file, set the IS_HOSTED_DOMAIN_ENV= property to true.

The tokens.properties file is located in the /var/opt/SUNWportal/portals/portal1/portletapps/sharedevents/tokens.properties directory.


The file system structure for all instance in the same portal should be similar. (#6348452)

Description:

The file system structure for all instance in the same portal should be similar.


Enterprise Sample Portal is not localized. (#6337500)

Description:

Enterprise Sample has not been localized.


Internal ports are revealed if proxylet is enabled in a gateway profile. (#6326785)

Description:

If the gateway is running on any non-default port, the browser displays the port value in the URL. This applies even if gateway is made to run on a non-default SSL port other than 443 with proxylet disabled. When proxylet is enabled, an addition socket listener is introduced in the gateway. The socket listener runs on the default port and the gateway is made to listen on a non-default port. So, the non-default port is displayed in the URL.

Solution:

In the /etc/opt/SUNWportal/platform.conf.default file, add following lines.


gateway.enable.customurl=true
gateway.httpurl=https://hostname:port/

Inter Portlet Communication for multiple WAR does not work, if the portlet channel is minimized or closed. (#6271542)

Description:

Currently, the scope of the event processing is limited to the portlets in the same tab. Hence, portlets in minimized or closed channel do not appear in the list of portlets participating in Inter Portlet Communication. Inter Portlet Communication does not not work in case the portlet channel is minimized or closed since the events will not be sent to closed or minimized channels.


Proxylet does not function properly in Java Runtime Environment. (#6409604)

Description:

Proxylet does not function properly in Java Runtime Environment 1.4.2_03, 1.5.0_04, 1.5.0_08, and 1.5.0_09 versions. Proxylet functionality is not supported in any Java Runtime Environment version that is less than 1.4.2. It is recommended to use Java Runtime Environment 1.5.0_06. If you have any other version of Java Runtime Environment, unistall the same.


Cannot add or change contacts in address book with special characters. (#6490665)

Description:

When using the address book component of Mobile Access, a user cannot add or change contacts that contain special characters, such as < >, &, ', and ". This happens if the address book is configured with Communications Express (UWC).

Solution:

Use Communications Express (UWC) HTML client (not mobile device) to manage contacts with special characters.


Google APIs not fully supported. (#6335501)

Description:

Google APIs currently do not fully support double-byte character search, particularly in Chinese, Japanese, and Korean.


Portal Server should be installable with Access Manager in Realm mode (#6381856, 6499572)

Description:

Portal Server should be able to be installed when Access Manager is installed in Realm mode.

Solution:

When you install Access Manager in Realm mode from the Java ES installer, you can ignore the popup message that lists Portal Server as being able to be installed only in Legacy mode. Portal Server installs successfully with Access Manager installed in Realm mode.

Here are some considerations when using Portal Server in Realm mode:

  • Migration from Portal Server 7.0 running in Legacy mode to Portal Server 7.1 running Realm mode is not supported.

  • When Portal Server is configured with Access Manager in Realm mode, after the configuration restart of common agent container is required. Without restart, when SSO Adapter tab in Portal Server administration console is accessed, there will be no meta adapters. If SSO Adaptor does not have the meta adapters, then UWC and communication channels available on the Portal Server desktop do not work. Applications such as Exchange and iNotes do not work .

  • Portal Server supports Realm mode only if Directory Server and the Access Manager SDK plug-in are installed and configured.

  • The realm mode administration console can be accessed from http://host.port/amserver/console. Refer to the Access Manager documentation for information on using the Realm mode administration console, because the Legacy mode administration console is not available.


For Proxylet to appear as a console window, browser settings needs to be changed in Netscape 8.0.4. (#6483268)

Solution:

Do the following to make Proxylet appear as a console window in Netscape 8.0.4:

  1. Click Tools —> Options —> Site Controls —> Site List —> Master Settings.

  2. Clear Open unrequested pop-ups in new tab and Allow unrequested pop-up windows check boxes.

  3. Click Tools > Options > Tab Browsing.

  4. Select Open links from other applications in New window check box. Clear Open a new tab instead of a new window and Open non-requested pop-ups in a new tab check boxes.

  5. Restart the browser.


Using the NetFile option, you cannot open any files. When you try to open a file, the Save As dialog box is displayed. (#6465918)

Description:

Ideally, the file should be opened if it is a known file type. If it is an unknown file type, it should display the Save As dialog box that prompts the user to save the file. Firefox 1.07 does not allow the user to specify actions for any file extensions. So, when the user tries to open a file through NetFile, it displays the Save As dialog box. Firefox 1.5 or higher versions allows the user to open the known files.


Netmail functionality is removed from Java Enterprise System 5. (#6448968)

Description:

Netmail functionality is removed from Java Enterprise System 5.


Portal links are redirected to the wrong install if portal is not deployed on Access Manager in a multi-portal installation. This issue occurs only with Internet Explorer 6 Service Pack 1. (#6325586)

Solution:

Use Internet Explorer 6 Service Pack 2 in Windows XP or use Mozilla Firefox.


psconsole misbehaves after modifying site configuration. (#6446355)

Solution:

Restart common agent container and Access Manager after site configuration is modified.


ESP portal community portlet does not display any content. (#6506357)

Solution:

Refresh the ESP portal community portal.


Portal admin log level should be set to FINEST during creation of multi-portal and multi-instance. (#6446151)

Solution:

Before running psadmin commands, such as create-portal, create-instance, create-search, and so on, set the log level to FINEST to get detailed logs during configuration. You can use the following command to set the log level to FINEST:

psadmin set-logger -u uid -f password-filename -m component-type -L FINEST

Switch the log level to SEVERE after you complete running the psadmin command using the following:

psadmin set-logger -u uid -f password-filename -m component-type -L SEVERE


The pac file does not get created in JNLP mode for Netscape 8.0 browser. (#6319863)

Description:

pac file does not get created in JNLP mode for Netscape 8.0 browser.


Some of the Secure Remote Access attributes are not present in the psconsole. (#6301784)

Description:

The following Secure Remote Access attributes can be modified only from the Command—Line Interface.

  • sunPortalGatewayDefaultDomainAndSubdomains

  • sunPortalGatewayLoggingEnabled

  • sunPortalGatewayEProxyPerSessionLogging

  • sunPortalGatewayEProxyDetailedPerSessionLogging

  • sunPortalGatewayNetletLoggingEnabled

  • sunPortalGatewayEnableMIMEGuessing

  • sunPortalGatewayParserToURIMap

  • sunPortalGatewayEnableObfuscation

  • sunPortalGatewayObfuscationSecretKey

  • sunPortalGatewayNotToObscureURIList

  • sunPortalGatewayUseConsistentProtocolForGateway

  • sunPortalGatewayEnableCookieManager

  • sunPortalGatewayMarkCookiesSecure