test

Sun Java System Portal Server 7.1 Update 1 Release Notes

Sun Java System Portal Server 7.1 Update 1 Release Notes

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

Note –

Portal Server 7.1 Update 1 on Windows can only be used as a developer platform or an evaluation platform. It can not be used as a deployment platform.

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  

August 7, 2007 

Release of Sun Java System Portal Server 7.1 Update 1 Release Notes. 

About Portal Server 7.1 Update 1

The Sun Java System Portal Server 7.1 gives end users a portal desktop, which provides access to resources and applications. The Portal Server also provides a search engine infrastructure that enables Internet content to be organized and accessed from the portal desktop.

Portal Server 7.1 Update 1 provides additional features, such as Blog portlet, community features, and AJAX desktop. You can install Portal Server 7.1 Update 1 using the Java ES installer or you can upgrade your existing Portal Server 7.1 installation to Portal Server 7.1 Update 1 using the patch on the Solaris and Linux platforms.

Portal Server 7.1 Update 1 can be installed on the Windows platform using the evaluation installer and is certified only to be a developer platform.

Portal Server also offers Secure Remote Access (SRA) 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 such as employees, business partners, or the general public.

This section includes:

What's New in This Release

The following new features are available in Portal Server 7.1 Update 1:

Deprecated Features

The following is a list of features deprecated in Portal Server 7.1 Update 1:

Deprecation Notifications and Announcements

Removed Features

The following is a list of features removed in Portal Server 7.1 Update 1:

Hardware and Operating System Requirements

The following table lists hardware and operating system requirements:

Table 2 Hardware and Operating System Requirements

Component 

Platform Requirement 

Supported platforms 

Sun BladeTM or comparable workstation or server

Operating system 

SolarisTM 9 or Solaris 10 on SPARC

Solaris 9 or Solaris 10 on x86 

Red Hat Enterprise Linux 3.0 Update 3 or 4.0 on x86 

Windows 2003/XP/Vista in 32-bit mode with latest Service Pack 

Note: Portal Server 7.1 Update 1 on Windows can only be used as a developer platform or an evaluation platform. It can not be used as a deployment platform. Use the evaluation installer to install Portal Server 7.1 Update 1. Access the evaluation installer from http://www.sun.com/download/products.xml?id=465e130d

The ReadMe file provided with the installer has information on how to install Portal Server. The evaluation installer provides you a pre-configured image of Sun Java System Portal Server 7.1 Update 1. You can get a working copy of Portal Server by unzipping the contents of this file. 

RAM 

1.5 Gbytes for regular deployment on Sun Java System Web Server 

2.0 Gbytes for regular deployment on Sun Java System Application Server 

Disk space 

1 Gbyte for Portal Server and associated applications 

Swap space 

Twice the amount of physical memory, for example, 2.0 Gbytes RAM and 4.0 Gbytes swap space. 

Supported Browsers

Portal Server is supported on the following browsers:

Installing or Upgrading Portal Server 7.1 Update 1

You can install Portal Server 7.1 Update 1 using the Java ES installer. On the Solaris and Linux platforms, you can upgrade the existing Portal Server 7.1 to Portal Server 7.1 Update 1 using the patch.

This section contains the following:

Installing Portal Server 7.1 Update 1

To install Portal Server 7.1 update 1, download the install bits and run the installer.

Note –

Portal Server 7.1 Update 1 can be installed on the Windows platform using the evaluation installer and is certified to be only a developer platform. The ReadMe file associated with the evaluation installer has information on how to install Portal Server on the Windows platform.

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

Upgrading Portal Server 7.1 to Portal Server 7.1 Update 1

On the Solaris and Linux platforms, you can upgrade Portal Server 7.1 to Portal Server 7.1 Update 1 using the patch. If your Portal Server installation is not Portal Server 7.1, you need to upgrade your existing Portal Server to Portal Server 7.1 and then upgrade to Portal Server 7.1 Update 1 using the patch. For more information on upgrading Portal Server, refer to Sun Java Enterprise System 5 Upgrade Guide for UNIX.

Use the following procedure to upgrade Portal Server 7.1 to Portal Server 7.1 Update 1.

ProcedureTo Upgrade Portal Server 7.1 to 7.1 Update 1 on the Solaris Platform

  1. Download the following patches from Sunsolve:

    For SPARC: 124301-01 and for the x86 platform: 124302-01.

    If you need to upgrade to the localized version of Portal Server 7.1 Update 1, download the patch, 125301-02.

    Note –

    If you have upgraded Portal Server 7.0 to Portal Server 7.1, use the following localization patches:

    On the Solaris platform: 123254-03

    On the x86 platform: 124590-03

  2. Change the directory to the patch location and run the following command to add the patch or patches:

    patchadd patch-id

  3. Restart the web container.

    For Sun Java System Application Server:

    /ApplicationServer_base/Appserver/bin/asadmin stop-domain domain1

    /ApplicationServer_base/Appserver/bin/asadmin start-domain --user admin --password password domain1

    For Sun Java System Web Server:

    /var/opt/SUNWwbsvr7/https-host.domain-name/bin/stopserv

    /var/opt/SUNWwbsvr7/https-host.domain-name/bin/startserv

  4. Restart common agent container.


    /usr/share/bin/cacaoadm stop 
/usr/share/bin/cacaoadm start

  5. Run the following command to ensure that the common agent container is working.

    /usr/share/bin/cacaoadm status

  6. If the localization packages have been upgraded, set the Portal Server console JVM's locale to en_US.UTF-8.

    export LC_ALL=en_US.UTF-8

    export LANG=en_US.UTF-8

  7. Run the following command to update Portal Server to 7.1 Update 1.

    PortalServer-base/opt/SUNWportal/bin/psupdate -a

    Refer to the following table for more information on how to run the psupdate script.

    Question 

    Action 

    Have you restarted all your servers (cacao, web container)? 

    Type Y if you have restarted the common agent container and the web container. 

    Type N if you have not restarted the common agent container and the web container. If you type N, the script aborts. You need to restart the common agent container and the web container, and invoke the psupdate script.

    Please enter the host name on which this installation resides (excluding domain name):  

    Enter the host name on which the installation resides. For example, i-planet-14. 

    Please enter the fully qualified host name on which this installation resides: 

    Enter the fully qualified host name on which the installation resides. For example, i-planet-14.red.iplanet.com 

    Please enter the name of the Portal configuration directory: 

    Default name of the configuration directory is /etc/opt/SUNWportal.

    Are Portal web applications installed using the web container name?

    The script automatically detects the web container that you used to install Portal Server 7.1. 

    Please enter the port of the web container's Administration Server

    For Sun Java System Application Server, default value is 4849. 

    For Sun Java System Web Server, default value is 8989. 

    Please enter the name of the web container's administrator

    Type the administrator ID. 

    Please enter the web container's administrator's password:

    Type the administrator's password. 

    Please enter the Access Manager administrator's id: 

    Type the Access Manager administrator's id. By default, the administrator ID is amadmin.

    Please enter the Access Manager administrator's password:  

    Type the Access Manager administrator's password. 

    Do you wish redeployment to be constrained to local Portal instances? 

    Type Y if you want redeployment to occur only on Portal Server instances hosted on this machine. Portal installations using web container clusters should not select this option. Type N if you wish redeployment to occur on all instances of all Portals for which this machine hosts at least one instance. This option is required for those Portal installations that are using a web container cluster. 

    Do you wish to (re)install the Enterprise Sample? 

    Type Y if you wish to reinstall Enterprise Sample. Default value is N. 

    If you have customized your sample and select Y, the sample will be overwritten. 

    Please enter the Access Manager LDAP User password:  

    Type Access Manager LDAP User password. Default value is N. 

    If you have customized your sample and select Y, the sample will be overwritten. 

    Do you wish to (re)install the Developer Sample? 

    Type Y if you wish to reinstall Developer Sample. Default value is N. 

    If you have customized your sample and select Y, the sample will be overwritten. 

    Do you wish to (re)install the Community Sample? 

    Type Y if you wish to reinstall Developer Sample. Default value is N. 

    If you have customized your sample and select Y, the sample will be overwritten. 

    Is the Community database running? 

    Type Y if the community database is running. 

  8. Restart the common agent container and web container.

ProcedureTo Upgrade Portal Server 7.1 to 7.1 Update 1 on the Linux Platform

  1. Download the following patch from Sunsolve:

    124303-01

  2. Change the directory to the patch location and run the update script.

  3. (Optional) If you want to upgrade to the localized version of Portal Server 7.1 Update 1, download the patch, 125302-02 , and install it.

    1. Install each rpm file using the following command:

      rpm -Fvh /patch-id/file-name.rpm

      For example, rpm -Fvh /125302-02/sun-portal-base-l10n-7.1-1.1.i386.rpm

  4. Restart the web container.

  5. Restart common agent container.

    /opt/sun/cacao/bin/cacaoadm stop

    /opt/sun/cacao/bin/cacaoadm start

  6. Run the following command to ensure that the common agent container is working.

    /opt/sun/cacao/bin/cacaoadm status

  7. If the localization packages have been upgraded, set the Portal Server console JVM's locale to en_US.UTF-8.

    export LC_ALL=en_US.UTF-8

    export LANG=en_US.UTF-8

  8. Run the following command to update Portal Server to 7.1 Update 1.

    PortalServer-base/opt/SUNWportal/bin/psupdate -a

  9. Restart the common agent container and web container.

ProcedureTo Remove the Patch

  1. Run the following command.

    patchrm patch-id

  2. Restart the web container and common agent container.

  3. Run the following command to roll back to Portal Server 7.1 .

    psupdate -r

  4. Restart the common agent container and web container.

Upgrading Portal Server 7.0 to Portal Server 7.1 Update 1

To update Portal Server 7.0 to Portal Server 7.1 Update 1, you need to upgrade Portal Server 7.0 to Portal Server 7.1. For more information on how to upgrade to Portal Server 7.1, refer to Sun Java Enterprise System 5 Upgrade Guide for UNIX.

Note –

Do not use the localization patches specified in the Upgrade guide.

When you upgrade from Portal Server 7.0 to Portal Server 7.1, use the following localization patches:

SPARC 

123254-03 

x86 

124590-03 

Linux 

123255-02 

Note –

If you have used the patches mentioned in the table above, you are not required to use the localization patches when you upgrade Portal Server 7.1 to Portal Server 7.1 Update 1.

For more information on upgrading, refer to Upgrading Portal Server 7.1 to Portal Server 7.1 Update 1.

Installing Portal Server 7.1 Update 1 on the Windows Platform

For more information on installing Portal Server 7.1 Update 1 on the Windows platform, refer to the README file present in the Windows installer zip file.

Bugs in this Release

This section contains information on the open bugs of the Portal Server 7.1 Update 1.

The following product areas are covered:

Installation


Patch needs to be applied as a root user. (#5080029)

Solution:

If you have followed any post-installation configuration to run Portal Server as a non-root user, you need to remove these changes, and run Portal Server as root before applying the patch.

After successfully applying the patch, follow the post-installation procedure to run Portal Server as a non-root user .


If Portal Server and Access Manger are installed on two different machines, creation of discussions and searching fail. (#6534761, 6534777)

Solution:

After upgrading Portal Server 7.1 to Portal Server 7.1 Update 1, restart the common agent container.

On the Solaris platform:


/usr/share/bin/cacaoadm stop 
/usr/share/bin/cacaoadm start

On the Linux platform:

/opt/sun/cacao/bin/cacaoadm stop

/opt/sun/cacao/bin/cacaoadm start


Restarting of the common agent container is required after creating a new portal. (#6521384)

Example:

In the Linux platform, if you use Application Server 8.2 as the web container for Portal Server, after creating a new portal, restart the common agent container.


/opt/sun/cacao/bin/cacaoadm stop
/opt/sun/cacao/bin/cacaoadm start

If Portal Server is installed on an Application Server cluster, to uninstall Portal Server, you need to delete the Portal Server instance on every node. (#6494878)

Solution:

Do the following:

  1. Start DAS on each secondary node.

  2. Delete Portal Server instances on each secondary node by running the psadmin delete-instance command.

  3. Delete Portal Server instance on the primary node.

  4. Run the uninstall command to uninstall Portal Server.

Administration with Command-Line Utilities


The --format option is missing in the generate-user-behaviour-tracking-report command help. (#6506032)

Description:

When you run the psadmin generate-user-behaviour-tracking-report --help command, the description for the -–format option is not provided.

The -–format option specifies the format of the report, such as PDF, HTML, or XML. By default, the report is stored in the PDF format.


The psadmin delete-instance command fails if one or more .war are not deployed on the server. (#6504630)

Description:

If a portlet is not successfully deployed, the psadmin delete-instance command fails because the command tries to undeploy the web application.

Solution:

Deploy the war files that were not deployed on the instance and then run the psadmin delete-instance command.


Undeploying a portlet war file from a DN (Distinguished Name), undeploys the .war file from all DNs. (#6495423)

Description:

Deploy a portlet war file at two DNs, for example DN x and DN y. Then, undeploy the war file from DN y. The desktop does not show the portlet for DN x because the web application is undeployed from the container.

Solution:

Do the following:

  1. Remove the display profile fragment for this provider from DN x.

    psadmin remove-dp -u admin-user -f password-file -d x -p portal1 -t provider -n blogportlet.blog

  2. Deploy the portlet war again at DN x.

    psadmin deploy-portlet -u admin-user -f password-file -d x -p portal1 -n blogportlet.war


By default, —overwrite option is true for import through Portal Server administrator console and is false for psadmin import command. (#6323091)

Solution:

When using the psadmin import subcommand with the --dp-only option, if the intention is to replace the whole display profile for the specified dn, use the --overwrite option. For example, type

./psadmin import -u amadmin -f ps_password -p portal-ID --dp-only --continue --overwrite


Portal directory is not deleted if the instance is on a host other than the portal host. (#6355651)

Description:

Run delete-portal from machine1. The directory /var/opt/SUNWportal/portals/portal1 is deleted from machine1. However, the same directory is not deleted from machine2.

Solution:

Delete the directory /var/opt/SUNWportal/portals/portal1 from machine2.

Collaboration and Communities


The Blog Search link is not available in the Community portlet. (#6504524)

Description:

The Blog link is not available for search that makes searching only Blog community difficult.

Solution:

Do the following:

  1. Log in to Portal Server console and select DeveloperSample DN.

  2. Select Manage Containers and Channels —> CommunityParentContainer —> CommunityHomeContainer —> CommunityPortlet.

  3. Select PortletPreferances —> availableDatabase.

  4. Type Blog and save the page.

  5. Log in to Portal Server desktop and select the MyCommunities tab.

    The Blog search link is available in the Community portlet.


In Surveys and Polls, wild card search using * is not supported. (#6426679)

Solution:

In Surveys and Polls, use the percentage sign (%) for wild card search.


When you access community portlet for the first time, it displays content not available error. (#6495254)

Solution:

Refresh the browser.

Desktop


You can not rename a desktop tab. (#6538352)

Solution:

Do the following:

  1. Download the display profile.

  2. Rename the tab manually in the display profile.

  3. Upload the display profile.


The JSP Menu Container is not able to switch between menu items. (# 6500729)

Solution:

Set refresh time of all leaf channels to zero.


Because of the cookie size, portlets fail for authless anonymous user. (#6460104)

Description:

For authless anonymous user, the properties are stored in a cookie. This includes all portlet render arguments and desktop arguments. When the render arguments reach a certain size, the portlets fail.

Solution:

Do the following:

  1. Log in to Access Manager administration console.

  2. Click Service Configuration —> Client Detection.

  3. In the Client Detection screen, click the Edit link displayed with the Client Types field.

  4. In the Client Manager pop-up window, select the third page.

  5. Click the Edit link displayed with genericHTML.

  6. In the pop up window, select Additional Properties option and add the property, authlessState=server.


When you try to access Portal Server desktop, the following error is displayed, “Invalid Keystore format.” (#6446218, 6488139)

Solution:

Do the following:

  1. Access the var/opt/SUNWportal/portals/portalID/config/instanceID directory.

  2. In this directory, rename security to security.backup.

  3. Restart the instance.

Portlet


Multibyte file names in psonsole under Deploy Portlet is corrupted. (#6368639)

Description:

When the default system locale and browser locale have different character encoding, names of files and directories in portal administration console under Deploy Portlet appear corrupted.

Solution:

Names of files and directories are encoded in a specific character encoding scheme. Set the default system locale to the same character encoding as the browser locale.


Portlet output values are cached. (#6273292)

Description:

Set the refresh time value to zero. For example, <String name="refreshTime" value="0" advanced="true"/>.


The Community portlet help displays the following error message: “Page cannot be found.” (#6547258)

Solution:

Access the online help using the Help button provided at the top right corner of the Community sample.

Portal Server Management Console


The Choose File option does not work when you import or export a portal. (#6545784)

Solution:

When you import or export a portal, provide the full path of the par file.


On Application Server 8.2, Datasources are not deployed on a new Portal Server instance. (#6515080)

Solution:

Do the following in the Application Server 8.2 administration console:

  1. Log in to the Application Server administration console.

  2. Select click on resources -> JDBC Resources -> jdbc/communitymc.

  3. In the right frame, click Targets tab, and click Manage Targets.

  4. Add the server instance.


Portal Server /portal/dt page does not load properly when there is TimeOut due to Instant Messenger. (#6200508)

Solution:

Do the following:

  1. Log in to the Portal Server administration console.

  2. Click Identity Management -> Services.

  3. Change Maximum Session Time to anything that is greater than the time out of the connection for SSO channel.


In Administration Console Help HTTPS should read HTTP, and URLs should read URI. (#6476607)

Description:

In the Profile Section under Secure Remote Access, the attribute reads "HTTP Port — Specifies the HTTPS port. Default value is 80." HTTPS should read HTTP. Rewriting of All URLs should read Rewriting of All URIs.


Help files not displayed on Web Server SSL machine. (#6351789)

Description:

Log in to psconsole and click the Help button. The Help contents are not displayed.

Solution:

Perform the following steps:

  1. Add a bean managed property, httpPort, to the managed bean declaration of JavaHelpBean in the ./web-src/common/common-fonfig.xml file. The common-config.xml file is located in the psconsole WAR file.

  2. Set the value of httpPort to an insecure port (http) that the web container provides.

Example:

The following example demonstrates setting the httpPort to port 8080:

<managed-bean>

<description>The backing bean for the Java Help component</description>

<managed-bean-name>JavaHelpBean </managed-bean-name>

<managed-bean-class>com.sun.web.ui.bean.HelpBackingBean</managed-bean-class>

<managed-bean-scope>request</managed-bean-scope>

<managed-property>

<property-name>jspPath</property-name>

<value>faces</value>

</managed-property>

<managed-property>

<property-name>httpPort</property-name>

<value>8080</value>

</managed-property>

</managed-bean>

The web container must support a http port for the above example to take effect. A unjar and re-jar of the psconsole WAR needs to be added to manage the bean property and set the value of the http port. After making the new psconsole WAR, a redeploy is required for the changes to take effect.

Proxylet


Proxylet help is available only from the proxylet channel. (#5036777)

Description:

Proxylet help is available only from the proxylet channel. If the user clicks the Help link from Edit Proxylet page, the Help link displays desktop online help.


For Firefox browser on the Solaris platform, Proxylet does not come up in Java Web Start mode. (#6464974)

Solution:

Copy istall_dir/defaults/profile/mimeTypes.rdf from Firefox for Windows to istall_dir/defaults/profile directory of Firefox for Solaris.


Logging out of Portal Server does not close the proxylet console. (#6496855)

Solution:

Stop the proxylet application and close the browser.


The portal desktop is not refreshed after selecting Automatic Download of Proxylet option. (#6493401, 6509603)

Description:

If there is not any proxylet application in the proxylet channel, when you click the Edit button and select the Automatic Download of Proxylet option, the portal desktop should get refreshed. If you use Mozilla 1.0.7 on Windows 2000 platform, the portal desktop does not refresh.

Solution:

When proxylet is configured for automatic download, the administrator needs to specify an application url for the portal desktop.

  1. In the Portal Server administrator console, select the Portals tab.

  2. Select an organization or add the user for whom the Application list needs to be provided in the DP list.

  3. Select the Manage Tabs and Container link under the selected organization or user.

  4. In the left pane, select proxylet.

  5. In the right pane, select the AppUrl link.

  6. Add the application in the application url page.

  7. The created application URL will be displayed in the portal desktop for the particular user display profile or for the selected organization.


For a non-default root proxylet user, the pac file does not contain any of the proxylet rules. (#6445867)

Description:

For a proxylet user, the pac file does not contain any of the proxylet rules.

  1. In Access Manager administrator console, create a user under developersample.

  2. In Portal Server administrator console, create the proxylet rules for developersample.

  3. Log in to Portal Server desktop as the proxylet user.

  4. Launch the proxylet.

    The proxylet gets downloaded in the Applet mode. But the generated pac file does not contain any of the proxylet rules.

Solution:

Do the following:

  1. Log in to the Portal Server administration console.

  2. Select the SRA tab and click the proxylet tab.

  3. Change the COS priority to anything less than the Highest for the organization.

  4. Change the COS priority for o=DeveloperSample to anything less than the Highest.

  5. Set all sub organizations under developer_sample COS priority to Highest.

    For the users created under the sub organization, the corresponding proxylet pac file gets generated.


Proxylet pac file does not generate after closing the applet window for the given session. (#6490738 )

Solution:

Do the following:

  1. Log out from the current session and close the browser window.

  2. Open a new session of the browser and start proxylet.

Rewriter


Rewriter ruleset for Ajax must be manually configured. (#6504423)

Solution:

To manually configure Rewriter rulset for Ajax, do the following:

  1. Log in to Portal Server console as administrator.

  2. Click the Secure Remote Access tab and click Rewriter Rulesets.

  3. Select generic_ruleset option in the Rewriter Rulesets table, and click Download.

  4. Download file as generic_ruleset.xml to a temporary directory.

  5. Edit the generic_ruleset.xml file and the following rules before the Function name="open" paramPatterns="y"/ rule.


    <Function name="*req*.open" paramPatterns=",y,"/> 
	<Function name="_81.open" paramPatterns=",y,"/>
	<Function name="http.open" paramPatterns=",y,"/>
	<Function name="sunportal.AJAXPageStyles" paramPatterns="y"/>

  6. Save the modified file.

  7. In the Portal Server administrator console, select generic_ruleset in the Rewriter Rulesetstable, and click Delete.

  8. Click Upload New and upload the modified the generic_ruleset.xml file.

  9. Restart the gateway.

    The above rules are only for container provider related to JavaScript. Other rules may be required for channel-specific JavaScript.


During a separate session configuration, SRA rewriter rule set is not loaded. (#6477552)

Solution:

Select Secure Remote Access -> Rewrite Rulesets. If you do not find the following entries: default_gateway_ruleset, exchange_2000sp3_owa_ruleset, exchange_2003_owa_ruleset, inotes_ruleset, iplanet_mail_ruleset, sap_portal_ruleset, and wml_ruleset, execute the following commands:


./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/DefaultGatewayRuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/OWA2003RuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/OWASP3RuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/SAPPortalRuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/WMLRuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/iNotesRuleSet.xml
./psadmin create-rewriter-ruleset -u amadmin -f /tmp/passwd  -F 
/opt/SUNWportal/export/rewriter_rule/iPlanetMailExpressRuleSet.xml

Netlet


Netlet is not working with the SSL_RSA_WITH_NULL_MD5 encryption cipher. (#6434314)

Solution:

Enable the Null Cipher option under the Gateway Profile > Security tab.

NetFile


You need to add NFS shares when Portal Server is installed on the Linux platform. (# 6511479)

Solution:

Do the following:

  1. Add the following line in the containers startup script: export LD_PRELOAD=/usr/lib/libpam.so.

  2. Restart the container

Secure Remote Access (SRA)


SRA services are not setup when you manually install the sample portals using the command line interface. (#6516280)

Solution:

Manually invoke the following ant targets to setup SRA services for each sample:

  • community_sra

  • developer_sra

  • enterprise_sra

Execute the following command after you install the sample portal.

/usr/sfw/bin/ant -f /opt/SUNWportal/samples/portals/build.xml community_sra developer_sra enterprise_sra -Dconfig.location= input-properties-file-location


In Secure Remote Access, you can add only one row at a time. (#6497988)

Solution:

In SRA screens, when you try to add multiple rows, save the details after you add each row.


Unable to access Unified Web Client (UWC) application through proxylet if UWC and Portal Server are installed on different machines. (#6348935)

Solution:

If UWC application and Portal Server are installed on different machines, do the following to access UWC machine through proxylet:

  1. In the Portal Server administration console, enable cookie management in the Gateway profile.

  2. In the URLs to which user session cookie is forwarded field, add UWC, Calendar, and Messaging Server urls. For example, add the following: http://port/uwc, http://calhost:calport, http://messaginghost:messagingport.

  3. In the AMConfig.properties file of UWC machine, change com.iplanet.am.cookie.name=iPlanetDirectoryPro to com.iplanet.am.cookie.name=iPlanetDirectoryPro1.

    Note –

    This is to have different cookie names in Gateway and Portal Server machines.

  4. In the UWC machine, using configutil, change the session cookie for Messaging Server to iPlanetDirectoryPro1.

  5. Add the UWC, Calendar, and Messaging Server URLs in Non-Authenticated URL list of UWC.

  6. Restart Gateway, UWC, and Portal Server.


certadmin ignores nickname while installing a renewed certificate. (#6360869)

Description:

certadmin ignores the nickname while installing a renewed certificate. This results in the gateway picking up the expired certificate, not the new one. It is not possible to distinguish between two certificates with the same nickname.

Solution:

Do any one of the following:

  1. Delete the old certificate before importing the new one. Do the following in Portal Server 7.1:


    cd PortalServer_base/SUNWportal/bin/certadmin -n config_name

    Choose 5 to delete the certificate.

  2. Do not renew the certificate. When a certificate expires, get a brand new one with the new keys.

Search, Subscriptions, and Discussions


Search server does not work when Web Server runs as non-root. (#6408826)

Description:

When Web Server runs as non-root, if you create a search server as non-root, the search server does not work.

Solution:

Do the following:

  1. Create a search server.

  2. Change the search server instance using the following command:

    chown -R nonrootuser.nonroot search_instance

  3. Restart the Web Server as a non-root user.

  4. Change permissions of Search instance using the following command:

    chmod -R og+rX search_instance

WSRP


WSRP producer with SSL does not work with non—SSL consumer. (#6292152)

Description:

WSRP producer with SSL does not work with non—SSL consumer. The common agent container requires the truststore to be populated with the SSL servers CA certificate into the truststore and the password of the truststore set.

Solution:

To set the truststore of the common agent container server:

  1. Create a truststore and import the CA certificate of the SSL server on to this truststore using the keytool command.

  2. Set the following JVM properties using the cacaoadm command:

    • Djavax.net.ssl.truststore

    • Djavax.net.ssl.truststorePassword

    For example, type cacaoadm set-param java-flags="`cacaoadm get-param java-flags -v` -Djavax.net.ssl.truststore=/tmp/truststore -Djavax.net.ssl.truststorePassword=truststorepass.

  3. Restart the common agent container server.


The registry server keystore location is always relative to /soar/3.0. (#6355673)

Description:

The SSO configuration of the registry server accepts a keystore location. This location is always assumed to be relative to /soar/3.0.

Solution:

Make a directory /soar/3.0/jaxr-ebxml/security and place keystore.jks obtained from Registry Server.

Localization


Under the KO (Korean) locale, the psadmin deploy-portlet command help does not have the following information: operand — Specifies the portlet war file. (#6533738)

Solution:

Run the psadmin deploy-portlet command in the C or English locale.


Help of Community Sample displays garbaged help. (#6538563)

Solution:

Access help by clicking the Help button displayed on the header present at the right side and click Working With Communities.


Bookmark and Application Channel have duplicate links and invalid links. (#6504004)

Description:

Bookmark and Application Channel have duplicate links and invalid links after migrating Portal Server from Java ES 4 to Java ES 5.

Solution:

Administrator needs to add or delete required links in the Application channel in Portal Server console. This channel is found under MyFrontPageTabPanelContainer of Developer Sample. In Properties of Application Channel, do changes to the following properties:

  • userApps: Delete the following values: -NetMail Lite and -NetMail. Add the following value: NetFile.

  • targets: Delete the following values: NetMailLite|NetMailServlet?nsid=newHTMLSessionNetMailLite|NetMailServlet?nsid=newHTMLSession NetMail|NetMailServlet?nsid=newAppletSession. Then, duplicate links for Instant Messenger targets.


Proxylet does not work in a global environment. (#6507488)

Description:

Proxylet does not work in a global environment after migrating Portal Server from Java ES 4 to Java ES 5.

Solution:

After portal upgrade process is over, delete Java ES 4 localized providers which no longer required.

  1. Go to the /portals/Upgraded/desktop directory.

    cd PortServer-Data_Directory/portals/Upgraded/desktop

  2. Delete directories or files from default_locale, except the following files or directories and user created ones. The locale can be any supported locale.

    Directories


    AddressBookProvider,
BookmarkProvider
CalendarProvider
LoginProvider
LotusNotesAddressBookProvider
LotusNotesCalendarProvider
LotusNotesMailProvider
MSExchangeAddressBookProvider
MSExchangeCalendarProvider
MSExchangeMailProvider
MailProvider
NotesProvider
PersonalNoteProvider
Register
SampleRSS
SampleURLScraper
SampleXML
TemplateEditContainerProvider
TemplateTabContainerProvider
URLScraperProvider
UWCAddressBookProvider
UserInfo
UserInfoProvider
XMLProvider
error

    Files


    message.properties

  3. Restart the web container.


Portal Server console online help is displayed in English for the fr-FR locale. (#6513360)

Solution:

Set fr for browser preferred language.


When you launch Instant Messenger from the Instant Messenger channel, it displays in English. (#6515726)

Solution:

Using the User Info channel, set language in the preferred locale.


The Channel Name field in the Portal Server console accepts only the following characters: A to Z, 0 to 9, or a to z. (#6522702 )

Description:

The Channel Name field in the Portal Server console accepts only A to Z, 0 to 9, or a to z.


Survey date format needs to be changed. (#6493352)

Description:

The To and From date format for Survey is dd mmm yyyy. It needs to be changed to yyyy mmm dd.


Ruleset id does not accept Japanese dot. (#5030713)

Description:

Multi-byte rewriter ruleset id is not supported in Portal Server.


The psadmin list-dp command does not generate correct output if the display profile is not for English. (#6502307)

Solution:

If the locale for display profile to be downloaded is not English, before executing the psadmin list-dp command, set the CLI jvm's locale to the locale for the display profile.

For example, if you need to download the display profile for French, do the following.


export LANG=fr_CA.UTF-8
export LC_ALL=fr_CA.UTF-8

Search channel displays file content improperly. (#6506365)

Description:

The third party converter did not convert the file content properly.


String in UBT generated reports not localized. (#6336394)

Description:

The generated reports are partially translated. This happens only for Japanese and Chinese locale.

Solution:

The garbled message is, "There is no tracking data pertaining to the selected report. So, there in no page to display." Do the following to overcome this:

  1. Log in to Portal Server administration console.

  2. Select the Portals tab.

  3. Select the configured portal.

  4. Select the User Behavior Tracking tab.

  5. Click the Setting tab.

  6. Select portal instance.

  7. Click Enable for UBT Log.


MAP displays deleted Address Book, Calendar, and Mail. (#6423989)

Description:

MAP displays deleted Address Book, Calendar, and Mail.


The filter entry for the amcontroller filter is commented in the web.xml file of the amserver web application. This results in the failure of log in functionality in the Mobile Access of the Portal Server. (#6437280)

Solution:

Uncomment the filter entry in the web.xml file of the amserver web application.

Mobile Access


You can not create mail views. (#6521744)

Description:

In the portal desktop, en error message is displayed when you try to create a mail view. Click Edit Mail channel -> Mobile Mail -> Device Views.

Solution:

Add an entry for the device in the /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/portal/ WEB-INF/classes/DeviceNames.properties file.


Mail channel does not appear in the mobile desktop. (#6521749)

Solution:

In the Device home page, click Options -> Contents and select the Mail option and click Done.


Portal is not rendered in openwave 6.2.2 simulator using the /amserver/UI/Login. (#6439565)

Solution:

Do the following if the web container is Web Server:

  1. Open the following files:

    /var/opt/SUNWwbsvr7/admin-server/config-store/host-name/web-app/host-name /amserver/WEB-INF/web.xml

    /var/opt/SUNWwbsvr7/https-host-name/web-app/host-name /amserver/WEB-INF/web.xml

  2. Search for the <filter> entry in both the xml files.

  3. Uncomment the entry for the amcontroller and save the file.

  4. Restart Web Server.

Do the following if the web container is Application Server:

  1. Open the following files:

    var/opt/SUNWappserver/domains/domain1/generated/xml/j2ee-modules/amserver/ WEB-INF/web.xml

    /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/amserver/ WEB-INF/web.xml

  2. Search for the <filter> entry in both the xml files.

  3. Uncomment the entry for the amcontroller and save the file.

  4. Restart Application Server.


The Options link in Mobile Access does not work if the wireless options are on a different page. (# 6500172)

Description:

Clicking on the Options link in the Mobile desktop should highlight the wireless options (Content and layout) on the Mobile desktop. If all these options are on a different page, wireless options are not highlighted.

Solution:

Move to the next page and click the Options link.


Creating an event without specifying the end time creates an event for one hour. (# 6479153)

Description:

Log in to Simulator and create an event using the Calendar Hm. If you do not specify the end time, the duration of the event is one hour.

WebSphere and WebLogic

Note –

If you are a Portal Server 7.1 customer who wants to upgrade to Portal Server 7.1 Update 1 on WebLogicTM or WebSphereTM and need a specific bug fix, contact your Sun support representative.


Web Services for Remote Portlet (WSRP) functionality is not working properly on Portal Server installation on WebSphere. (#6489684)

Description:

In Portal Server installation on WebSphere, the WSRP functionality is not working properly. The following errors are displayed:

  • The Weather portlet displays the following error: “Content not available.”

  • WSRP consumer creation fails.

  • Pre-configured web service channel displays the following error: “Error Parsing WSDL.”

Solution:

Remove the following files: qname.jar and webservices.jar. These files are available in the WebSphere-installation-directory/lib directory.


To enable secure communication between common agent container and Portal Server JVM, jar files need to be added. (#6341883)

Solution:

To enable secure communication between common agent container and Portal Server JVM, add the following jar files to /etc/cacao/instances/default/private/modules/com.sun.portal.admin.server.module.xml.

  • /IBM/WebSphere/Express51/AppServer/java/jre/lib/ext/ibmjsse.jar

  • /IBM/WebSphere/Express51/AppServer/java/jre/lib/ext/ibmjceprovider.jar

  • /IBM/WebSphere/Express51/AppServer/java/jre/lib/ext/ibmpkcs11.jar

  • /IBM/WebSphere/Express51/AppServer/java/jre/lib/ext/ibmpkcs.jar


On WebSphere, Weather portlet and pre configured Web Service Channel display errors. (#6396623,6415766 )

Solution:

Upgrade JDK to 1.4.2_10.


On WebSphere, a classpath modification is required for WSRP to function. (# 6509057)

Description:

If Portal Server is installed on WebSphere, add shared_lib_dir/xsdlib.jar at the beginning of the classpath entry in the server.xml file. In the Solaris platform, the shared_lib_dir is /usr/share/lib. On the Linux platform, it is /opt/sun/share/lib.


Portlet session failover does not work on WebLogic 8.1 SP4, because of a bug in this version of WebLogic.

Description:

Portlet session failover does not work on WebLogic 8.1 SP4, because of a bug in this version of WebLogic.

Solution:

Use WebLogic SP5 or a higher version.


Exception while deploying developer sample content on a new portal on administration server. (#6339522)

Description:

The WSRP sample consumer creation uses WSDL URL of sample producer. Because of configuration issues, the portal configuration fails to deploy portal war on WebLogic administration server. Portal .war needs be deployed manually. Because the portal is not up during configuration, the sample consumer creation process fails to contact sample producer and therefore sample consumer configuration fails.

Solution:

Create a consumer manually and copy the Configured Producer ID of the newly created consumer to the sample portlet under WSRPSamplesTabPanelContainer.


Selecting Proxylet help button displays exception. (#6363076)

Description:

Invoke Proxylet in applet mode and select the Help button. An exception is displayed in the Help page. This happens only in WebLogic setup.

Blog Portlet


Searching Weblog content does not return results. (#6568186)

Solution:

Restart common agent container.

On the Solaris platform:


/usr/share/bin/cacaoadm stop 
/usr/share/bin/cacaoadm start

On the Linux platform:


/opt/sun/cacao/bin/cacaoadm stop
/opt/sun/cacao/bin/cacaoadm start

The Post New option opens the corresponding window in another blog portlet channel. (#6545765)

Solution:

If you add more than one bolg portlet channels on a tab, clicking the Post New option opens the corresponding window in another blog portlet channel.

Solution:

Create only one blog portlet channel on the tab.


Blog Portlet channel displays the following message if appUrl is not set: "Error Content Not available." (#6546198)

Solution:

For the portlet, set the configMode option to any one of the following:

  • Wizard

  • Wizard-user-config

  • Manual


The Post New option does not work in Internet Explorer. (#6545771)

Description:

If you add more than one bolg portlet channels on a tab, clicking the Post New option does not work.

Solution:

Create only one blog portlet channel on the tab.

Wiki


In the Wiki editor, if you insert a link that starts with “www” the link does not work.(#6545362)

Solution:

Use “http” before “www.” For example, when you insert the link, “www.google.com,” insert it as “http://www.google.com.”


For a two column Wiki community, html editor does not allow to edit content if you are using Internet Explorer. (#6538009)

Solution:

Use Mozilla to edit content.


Because of cookie size, portlets fail for authless anonymous user. (#6460104)

Description:

For authless anonymous user, the properties are stored in a cookie. This includes all portlet render arguments, all desktop arguments, and so on. When the render arguments reach a certain size, the portlets fail.

Solution:

Do the following:

  1. Log in to amconsole.

  2. Click Service Configuration > Client Detection.

  3. In the Client Detection screen, click the Edit link displayed with the Client Types field.

  4. In the Client Manager pop-up window, go to the third page.

  5. Click the Edit link displayed with genericHTML.

  6. In the pop up window, select Additional Properties option and add the property, authlessState=server.

Sample Portals


Using the Show Hide Channels option in the Portal Server administration console, when you add Sample XML to Enterprise Sample portal, an error message is displayed on the portal desktop. (#6542355)

Solution:

Do the following:

  1. Log in to the Portal Server administration console.

  2. Select the DN as Enterprise Sample.

  3. Change the Sample XML's url option to file:///var/opt/sun/portal/portals/portal1/desktop/developer_sample /SampleXML/getQuotes.xml.


When you add a channel to AjaxTableContainerProvider and access it from the portal desktop, if you click the Help button and click the Contents or Index link, the corresponding window is opened on the portal desktop itself. You can not navigate back to the portal desktop. (#6506929)

Solution:

Click the Back button displayed on the browser.


On the Firefox browser, if you click the Help button provided with any channel on the Developer Sample's Ajax tab, the help is displayed on the portal window. If you click the Back button displayed on the browser, the channel layout is distorted. (#6528832)

Solution:

Click the Refresh button displayed on the Firefox browser.

Upgrade

For upgrade issues, refer to the Upgrade Issues in Sun Java Enterprise System 5 Release Notes for UNIX and Sun Java Enterprise System 5 Upgrade Guide for UNIX.


When you upgrade Portal Server 7.0 to Portal Server 7.1 Update 1, jdbc/WikiDB fails. So that Wiki portlets do not function. (#6536212)

Solution:

Do the following:

  1. Log in to administration console of the web container.

  2. Click on the Resources link.

  3. Click on the JDBC link.

  4. Create a connection pool for Wiki, for example, WikiDBPool.


     --Datasource Classname--org.apache.derby.jdbc.ClientDataSource
--Resources Type--javax.sql.ConnectionPoolDataSource
--serverName--Name of the server where derby is running
--portNumber---1527
--Password--portal
--user---portal
--databaseName---wikidb_portal1

  5. Create a JDBC resource, jdbc/WikiDB, for this connection pool.


Filesharing does not work after you upgrade Portal Server 7.0 to Portal Server 7.1 Update 1. (#6550408)

Solution:

Do the following:

  1. Change the directory to the Filesharing portlet location.

    /var/opt/SUNWportal/portals/portal1/portletapps/filesharing/

  2. Create an XML file, for example, update.xml.

  3. Copy and paste the following to the XML file.


    <project name="File Sharing Database Update for 7.0 to 7.1 " 
							default="update" basedir=".">
<target name="update">
      	<property file="build/conf/common.dbadmin"/>
      	<!-- Performs the Sql Tasks -->
      	<sql
            onerror="continue"        
	    delimiter="${sql.delimiter}"
	    delimitertype="${sql.delimiter.type}"
      	    driver="${db.driver}"
      	    url="${db.url}"
      	    userid="${db.user}"
      	    password="${db.password}"
      	    classpath="${db.driver.classpath}">
	    <transaction>
	    create table newfilesystem(
  repositoryId varchar(255) not null,
  directory varchar(255) not null,
  name varchar(255) not null,
  isDir smallint not null,
  creator varchar(255) not null,
  created bigint not null,
  modified bigint not null,
  datasize int not null,
  data blob(5000000),
  primary key(repositoryId,directory,name)
);

	    </transaction>
	    <transaction>
	    rename table filesystem to oldfilesystem;

	    </transaction>
	    <transaction>
	    rename table newfilesystem to filesystem;

	    </transaction>
	    <transaction>
	    insert into filesystem (repositoryId,directory,name,isDir,creator, 
				created,modified,datasize,data)
select repositoryId,directory,name,isDir,creator,created,modified,
				size as datasize,data from oldfilesystem;
	    </transaction>
       </sql>
   </target>

</project>

  4. Run the following ant script.

    ant -f update.xml


After upgrading Portal Server 7.1 to Portal Server 7.1 Update 1, the Search Provider and the Discussion Provider JSPs are not updated automatically. (#6534282)

Solution:

Do the following:

  1. Copy the Discussion provider JSP templates.

    cp PortalServer-base/par-src/default-portal/pbfiles/templateBaseDir/default /DiscussionProvider/*.jsp /var/opt/SUNWportal/portals/portal1/desktop/default/DiscussionProvider

  2. Copy the Search provider JSP templates.

    PortalServer-base/par-src/default-portal/pbfiles/templateBaseDir/default /SearchProvider/*.jsp /var/opt/SUNWportal/portals/portal1/desktop/default/SearchProvider


When you upgrade Java ES 4 to Java ES 5, the search migration fails. (#6440906)

Solution:

Do the following:

  1. Before running the psugrade script, open the Java ES 4 search.conf file.

    The search.conf file is located in the /var/opt/SUNWps/https-server/portal/config directory.

  2. In the search.conf file, change libdir="/opt/SUNWps/lib" to libdir="/opt/SUNWps.bak/lib:/opt/SUNWps/lib".

    where /opt/SUNWps is the Java ES 4 installation directory.

  3. Run the psupgrade script.

After the upgrade, some of the customization made to the search server configuration are not migrated to the UpgradeSearch. For the migration that is not handled by psugrade, manual carry over from upgraded Portal Server 6.3.1 is needed. These operations should be performed after stopping all search related processes, such as search webapp, robot, rdregister, autoclassify, and profiler.

  1. Copy the following files to the upgraded search server directory:


    cp $SRC/config/taxonomy.rdm $DEST/config
cp $SRC/config/filterrules.conf $DEST/config
cp $SRC/config/import.conf $DEST/config
cp $SRC/config/classification.conf $DEST/config
cp $SRC/config/schema.rdm $DEST/config

    where SRC is the path to the old search server directory and DEST is the path to the new upgraded search server directory.

  2. Depending on what was customized in Portal Server 6.3x, do the following:

    • For Robot, use the Portal Server 7.1 administration console's robot/properties to reconfigure the robot.conf's parameter such as proxy and authentication. Use the Portal Server 7.1 administration console's robot/filter to update the robot filter properties with the customization done on Portal Server 6.3.1's /var/opt/SUNWps.bak/server/portal/config/filter.conf file.

    • For federated search databases, refer to the Portal Server 7.1 configuration guide for more information on how to set up Federated Search.

  3. Restart the search server web container and search related processes.

Others


If the administration server is stopped, and you try to deploy a war file, you get the following error message, "Error deploying file file.war to instance node-name–80 on host node.domain-name. (#6506028)

Description:

Ensure that the instance on the host machine is running.


Before applying patch to update Portal Server 7.1 Update 1, if you have configured Portal Server to use Oracle database, you need to repeat some of the configuration steps after applying the patch. (#6530662)

Solution:

Refer to http://developers.sun.com/portalserver/reference/techart/databases.html.

Under the Setting Up Community Membership and Configuration section, repeat steps two and three.

Under the Configuring and Installing Portlet Applications section, repeat steps four to six.

Known Issues and Limitations

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


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

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.

  • Editing and posting in Blog portlet through a gateway is not possible.


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:

JAXTableContainerProvider is not localized.


On the Windows platform, the Category Search option does not return results. (#6555579)

Description:

This occurs during the initialization of Virtual Machine. The search server can not reserve enough space for object heap and can not create the Java Virtual Machine.

Solution:

In the PortalServer-product-directory/bin/rdmgr.bat file, change the following line from C:/Java/JDK15~1.0_0/jre/bin/java" -Xms32m -Xmx1000m -cp "%SEARCH_CLASSPATH%" -Djava.library.path="%PATH%" com.sun.portal.search.rdmgr.RDMgr % to C:/Java/JDK15~1.0_0/jre/bin/java" -Xms32m -Xmx800m -cp "%SEARCH_CLASSPATH%" -Djava.library.path="%PATH%" com.sun.portal.search.rdmgr.RDMgr %. Or, remove -Xmx1000m from the line.


The psupdate script throws exception while upgrading from Portal Server 7.0 to Portal Server 7.1 Update 1. (#6536216)

Description:

When you upgrade from Portal Server 7.0 to Portal Server 7.1 Update 1, the following exceptions are displayed:


can't open /var/opt/SUNWportal/portals/portal1/
	portletapps/wiki/tokens_ora.properties
egrep: can't open /var/opt/SUNWportal/portals/portal1/
	portletapps/wiki/tokens_ora.properties
egrep: can't open /var/opt/SUNWportal/portals/portal1/
	portletapps/wiki/tokens_ora.properties
egrep: can't open /var/opt/SUNWportal/portals/portal1/
	portletapps/wiki/tokens_ora.properties
mv: cannot access /var/opt/SUNWportal/portals/portal1/
	portletapps/wiki/tokens_ora.properties

However, the upgrade will be successful. If you want to use Oracle as a database, you need to do the following.

  1. Copy the PortalServer–70–product-dir/portletapps/filesharing/*ora.properties file to the PortalServer70–data-dir/portals/portal-id/portletapps/filesharing/ directory.

  2. Create a new directory, src_ora, under the PortalServer71–data-dir/portals/portal-id/portletapps/filesharing/ directory.

  3. Copy all the files from the PortalServer–70–product-dir/portletapps/filesharing/src_ora/ directory to the PortalServer–70–product-dir/portals/portal-id/portletapps/filesharing/src_ora/ directory.


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.


Under Community Service, the bog portlet name is incorrectly displayed. (#6549937)

Description:

Under Community Service, the bog portlet name is displayed as Menu Container Provider.


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

Description:

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


You can not drag the Search channel. (#6545839)

Description:

Using the AJAX desktop, you can not drag the Search channel.


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.


Community URL feature does not work if the Community tab is renamed. (#6538358)

Description:

Community URL feature does not work if the Community tab is renamed.


On the Linux platform, you are not able to add FTP shares on remote machines. (#6536164)

Description:

Do the following.

  1. Log in to portal desktop through a gateway or an open portal.

  2. Access Netfile through MyApplications channel in MyFrontpage.

  3. Add a system to network neighborhood .

    You are not able to add an FTP share.


On the Windows platform, the Notes provider is broken. (#6531699)

Description:

Create a tab on the Developer Sample with AjaxTableContainerProvider. Add some channels to it. Access the channel by logging as a user. Serious desktop error is displayed. This is because of the Notes provider. Notes provider has a string property location defined in the Display Profile. This property is used by the Notes provider to read or write notes from a specified file. The value for this property is /var/tmp/notes.txt and this property breaks for the Windows installations.


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.


Java DB patch needs to be applied to fix the bugs in connection cleanup. (#6521400)

Description:

Bugs in Java DB distribution causes portal hang while waiting for a connection. The details about the bugs are provided at https://issues.apache.org/jira/browse/DERBY-1856 and http://issues.apache.org/jira/browse/DERBY-2084. However, the likelihood of facing a portal hang is very low.

Solution:

Download and apply the following Java DB patches from sunsolve.

  • For Solaris SPARC – 125245-01

  • For Solaris x86 – 125246-01

  • For Linux – 125270-01


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.


Execution of the psadmin delete command takes a longer time on Web Server 7.0. (#6506037)

Description:

On Web Server 7.0, the psadmin delete-instance command runs the wadm deploy-config command on every execution of wadm remove-webapp. Hence it takes a long time.


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.


In the Deploy Portlet wizard, a message is not localized. (# 6508946)

Description:

In the Deploy Portlet wizard step 3, if no roles file or users file is defined, the message "Roles file not defined" or "Users file not defined" appears. These messages are not properly localized. The page displays garbled messages.


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.


If automatic proxy configuration is enabled on Mozilla browser, the Portal Server console hangs. (#6493377)

Description:

In the proxylet channel, if the proxylet user selects an application to download in JWS mode, the console appears properly. However, downloading stops at 30% and the console does not respond.


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.


Java DB should be manually restarted after the installation and configuration of Portal Server. (#6505149)

Solution:

The installer executes 00community.sql to create the Java DB user and to configure security on the database. Restart Java DB for those properties to take effect.


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

Redistributable Files

Sun Java System Portal Server 7.1 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 these Release Notes document is 820-0133.

Additional Sun Resources

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