Sun Java System Portal Server 7.1 Update 1 Release Notes

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:

Start DAS on each secondary node.
Delete Portal Server instances on each secondary node by running the psadmin delete-instance command.
Delete Portal Server instance on the primary node.
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:

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
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:

Log in to Portal Server console and select DeveloperSample DN.
Select Manage Containers and Channels —> CommunityParentContainer —> CommunityHomeContainer —> CommunityPortlet.
Select PortletPreferances —> availableDatabase.
Type Blog and save the page.
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:

Download the display profile.
Rename the tab manually in the display profile.
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:

Log in to Access Manager administration console.
Click Service Configuration —> Client Detection.
In the Client Detection screen, click the Edit link displayed with the Client Types field.
In the Client Manager pop-up window, select the third page.
Click the Edit link displayed with genericHTML.
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:

Access the var/opt/SUNWportal/portals/portalID/config/instanceID directory.
In this directory, rename security to security.backup.
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:

Log in to the Application Server administration console.
Select click on resources -> JDBC Resources -> jdbc/communitymc.
In the right frame, click Targets tab, and click Manage Targets.
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:

Log in to the Portal Server administration console.
Click Identity Management -> Services.
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:

Solution:

Perform the following steps:

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.
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.

In the Portal Server administrator console, select the Portals tab.
Select an organization or add the user for whom the Application list needs to be provided in the DP list.
Select the Manage Tabs and Container link under the selected organization or user.
In the left pane, select proxylet.
In the right pane, select the AppUrl link.
Add the application in the application url page.
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.

In Access Manager administrator console, create a user under developersample.
In Portal Server administrator console, create the proxylet rules for developersample.
Log in to Portal Server desktop as the proxylet user.
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:

Log in to the Portal Server administration console.
Select the SRA tab and click the proxylet tab.
Change the COS priority to anything less than the Highest for the organization.
Change the COS priority for o=DeveloperSample to anything less than the Highest.
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:

Log out from the current session and close the browser window.
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:

Log in to Portal Server console as administrator.
Click the Secure Remote Access tab and click Rewriter Rulesets.
Select generic_ruleset option in the Rewriter Rulesets table, and click Download.
Download file as generic_ruleset.xml to a temporary directory.

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"/>

Save the modified file.
In the Portal Server administrator console, select generic_ruleset in the Rewriter Rulesetstable, and click Delete.
Click Upload New and upload the modified the generic_ruleset.xml file.
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:

Add the following line in the containers startup script: export LD_PRELOAD=/usr/lib/libpam.so.
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:

In the Portal Server administration console, enable cookie management in the Gateway profile.
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.
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.
In the UWC machine, using configutil, change the session cookie for Messaging Server to iPlanetDirectoryPro1.
Add the UWC, Calendar, and Messaging Server URLs in Non-Authenticated URL list of UWC.
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:

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.
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:

Create a search server.
Change the search server instance using the following command:

chown -R nonrootuser.nonroot search_instance
Restart the Web Server as a non-root user.
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:

Create a truststore and import the CA certificate of the SSL server on to this truststore using the keytool command.
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.
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.

Go to the /portals/Upgraded/desktop directory.

cd PortServer-Data_Directory/portals/Upgraded/desktop

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

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 toyyyy 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:

Log in to Portal Server administration console.
Select the Portals tab.
Select the configured portal.
Select the User Behavior Tracking tab.
Click the Setting tab.
Select portal instance.
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:

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
Search for the <filter> entry in both the xml files.
Uncomment the entry for the amcontroller and save the file.
Restart Web Server.

Do the following if the web container is Application Server:

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
Search for the <filter> entry in both the xml files.
Uncomment the entry for the amcontroller and save the file.
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 WebLogic^TM or WebSphere^TM 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:

Log in to amconsole.
Click Service Configuration > Client Detection.
In the Client Detection screen, click the Edit link displayed with the Client Types field.
In the Client Manager pop-up window, go to the third page.
Click the Edit link displayed with genericHTML.
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:

Log in to the Portal Server administration console.
Select the DN as Enterprise Sample.
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:

Log in to administration console of the web container.
Click on the Resources link.
Click on the JDBC link.

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

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:

Change the directory to the Filesharing portlet location.

/var/opt/SUNWportal/portals/portal1/portletapps/filesharing/
Create an XML file, for example, update.xml.

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>

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:

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
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:

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.
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.
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.

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.

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.
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.