test

Sun Java System Portal Server 7 Release Notes

Sun JavaTM System Portal Server 7 Release Notes

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

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

March 24, 2006 

Updated for Portal Server 7 patch1 release. 

December 21, 2005 

General availability release of these release notes. 

October 17, 2005 

Beta refresh release of Sun JavaTM System Portal Server 7 Release Notes.

June 9, 2005 

Beta release of Sun JavaTM System Portal Server 7 Release Notes.

About Portal Server 7

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

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 Sun Java System Portal Server 7 has the following new features:

Administration Portlets and Tag Library

The administration tag library can be used to develop administration portlets for allowing administrators to administer portal through their portal desktop. Administration through portal desktop allows administrators to designate delegated administrators by providing access to administration tasks as portlets. A delegated administrator can be responsible for managing various tasks such as resetting passwords, creating and deleting users, tabs, and portlets, and arranging role based tabs, in a particular organization or a sub-organization. The tag library provides tags for achieving these tasks by writing portlets.

The administration tag library, associated with the portlets, can be used to modify out-of-the-box administration portlets or develop portlets with new administration functionality. The tag library supports user management, provider management, and portlet and WSRP management tasks. The tags in this library can be used for creating and administering channels based on JSPProvider. It is possible to write custom administration portlets with custom GUI using the tags in the tag library. The tag library can be used to write administrative portlets to administer any custom channel.

The sample set of administration portlets, included in this release of the Portal Server software, can be used to perform the administration tasks from the administrator's portal desktop. The administration portlets provide portal-based access to content and user administration tasks. The administration channels not only showcase the utilization of the administration tag library, but can also be used to design a simple portal desktop for a delegated administrator. The delegated administration display profile exists in the OrganizationAdministration role.

To access the sample portlets, log in to the Developer Sample as developerAdmin/developerAdmin and select the Administration tab. For more information on these channels, see the channel's online help.

New Management Console

This release of Portal Server introduces a new console for managing Portal Server functions. You can access the console using a browser client from a distinct URL. The Portal Server 7.0 management console enables portal administrators to manage the following:

The administration console allows administrators to manage a variety of tasks. Many of these tasks are available through the management console's Common Tasks tab. They include the following:

The new management console:

Other changes include the following:

The Portal Server command-line interface also provides a number of new psadmin subcommands for managing your portal. These include subcommands for:

For information about all psadmin subcommands, see the Sun Java System Portal Server 7 Command-Line Reference.

Command Line Tools for Administration

This release of the Portal Server software includes command line administration and management tools.

Overview

The Portal Server 7 administration CLI introduces a new administration CLI utility called psadmin. This utility facilitates all Portal Server management capabilities using the new Portal Server Administration Framework. The CLI contains functionality to administer and manage the following portal components:

All of the CLIs are called from one single utility called psadmin. Each CLI serves as one subcommand of psadmin. The Sun Java System Portal Server 7 Command-Line Reference describes the psadmin utility and its subcommands.

psadmin Utility Usage

psadmin
psadmin {--help | help | -?} [component=componentName]
psadmin command {--help | -?}
psadmin {--version | -V} --adminuser|-u userName --passwordfile|-f passwordFile

When component is specified, list of component specific commands are displayed. The valid component names are: portal, desktop, logging, monitoring, portlet, rewriter, search, sra, ssoadapter, subscriptions, ubt, and wsrp.

Communities and Collaboration

The portal collaboration feature allows end users to create and join communities, and interact with other community members through a set of collaborative portlet applications (community services). Communities is, therefore, an association of members and services. These services are: file share, shared tasks & events, polls & surveys, wiki, and discussions.

Communities are created and administered by end-users. The creating user becomes the delegated administrator for that community. The portal administrator can define community templates that defines the layout mechanism and the available services, and end-users can create communities within categories using the available template(s). Users must join to take part in community collaboration. All communities are public, in that any user may join a community.

An end-user can

Logging

The Portal Server software uses the Java logging API (JSR 47) for logging across all components. The logs and log configuration are uniform across portal components. There are seven standard log levels from severe to fine grain classification of log messages. The logs can be routed to different files or data sinks and can consist of a single file or multiple files; that is, one for each component.

Log levels can be set for each module, sub-module and logs can also be routed to separate files for each module, sub-module within each component. Each portal component logging can be configured through a specific properties file.

The following are the three psadmin subcommands used to configure logging in a Portal Instance:

list-loggers

Lists all the loggers. Optionally, it displays the detailed information of the root logger which includes the log level, and the log file name.

set-logger

Sets the level for logger and also separate file for the logger.

reset-logger

Resets the log level and log file to that of the root logger.

Administration Audit Logging

Portal Server includes a Portal Administration Server (PAS) which rides on the CACAO server. Many of the Administration work done through this PAS can be tracked using the audit logging. For example, when portal CLIs use PAS in the background to do the administration, such jobs are logged through the PAS audit logging. This logging rides on the JDK logging feature and follows other formatting and log handler requirements met by Portal Logging feature.

Monitoring

Monitoring captures runtime information about the performance of portal components such as the desktop, Channels and Secure Remote Access Gateway. Monitoring helps the system administrator to understand the state of their system, track system utilization, and monitor system health and security.

Monitoring data is available for querying using the portal command line interface (psadmin CLI). The system administrator can make this information available to third-party management tools to configure alerts and notifications when performance targets are not met. Additionally, the administrator can set different debug log levels for different logs without requiring a restart.

RSS Portlet

RSS Portlet is a simple syndicated content reader. It allows the end user to manage a set of syndicated content feeds (URLs) and select between them for viewing. The end user is allowed to customize the portlet and control several aspects of feed display. The RSS Portlet caches RSS Feeds. Any particular feed, uniquely identified by it's URL, may be cached up to the number of seconds defined by the portlet's cacheTimeout preference.

New Samples

In this release, the Portal Server software includes two new samples besides the Developer sample. This section describes the following samples:

Community Sample

The community sample is an example portal based around the community feature. The community sample can be accessed by clicking on the community sample link from the portal welcome page, and then logging in as test/test. To participate in the community sample, users must be in the CommunitySample organization.

Enterprise Sample

The Enterprise Sample demonstrates key features of the Portal Server software. The Enterprise Sample desktop uses a fictitious company, Adventure Sports Cafe (ASC), to show the daily operations of typical company employees. The sample allows you to view the desktop as an anonymous user, without logging in. Three log-ins are available to show how pages can vary according to who is logged in.

The Enterprise Sample resides in an Access Manager organization and provide sample users. The Enterprise Sample exists in the organization EnterpriseSample and supplies the following sample users:

Mary Manager (Username: mary; Password: mary)

Runs the New Tour project and the Australia Expansion project. She needs to keep up-to-date with organization news and events, and she manages content specific to the ASC projects she runs. Mary uses the ASC intranet portal's collaboration tools to communicate with her team.

Chris Content-Editor (Username: chris; Password: chris)

Works on the Customer Tour Project and reports to Mary. Chris uses the portal to keep up-to-date with organization news and events, and to collaborate with members of the Customer Tour Project team.

Ed Employee (Username: ed; Password: ed)

Works on the Australia Expansion Project and reports to Mary. Ed also uses the portal to keep up-to-date with organization news and events, and to collaborate with members of the Australia Expansion Project team.

The ASC web site pages can be accessed by tabs. The pages display several channels, arranged in columns and contain user-specific content. For example, a user could have a channel for a task list, a channel to display their email and their calendar, and one for Instant Messaging. The content and layout can be modified to suit the user.

Support for Inter Portlet Communication

The Portal Server software includes an API which is an extension to JSR-168 Portlets, in the com.sun.portal.portlet Java package. Using this API, JSR-168 portlets will be able communicate with each other even if they are in different web applications. It is assumed that all these portlets will be on the same instance of a Portal Server and running inside the Portal Server Portlet container. This API uses event generation and notification to convey the information/data among portlets. The event notification will be for the portlets which have registered themselves for listening to that particular event.

Support for JSF Application

To enable an existing JSF based applications to work in Portal Server as portlets, the Portal Server software includes a JSF support library, which allows easier conversion of the existing applications into a portlets with minimal changes. JSF based portlets must run inside the Portal Server and respond to the calls made by Portal Server.

For detailed information on deploying JSF application as a portlet on Portal Server, see Chapter 9, Deploying JSF Application as a Portlet in Portal Server, in Sun Java System Portal Server 7 Configuration Guide.

Support for Multiple Portals

This release of the Portal Server enables you to support multiple portals using a single user repository. You can design, deploy, and administer each portal independently.

This feature allows you to:

These terms are key to multiple portals:

The Portal Server command-line interface provides commands for performing the following tasks:

Support for Struts Application

With this release, an entire struts application can be displayed within a channel on the portal server desktop as a JSR 168 portlet application. The Portal Server provides sample struts applications to demonstrate the capability of the struts portlet bridge. This application is the Struts Mailer Demo application (strutssample.war file).

For information on deploying a standalone struts application as a portlet application, see Chapter 8, Deploying Struts Application as a Portlet in Portal Server, in Sun Java System Portal Server 7 Configuration Guide.

Support for Weblogic and WebSphere

In this release, the Portal Server supports the web containers Weblogic 8.1 SP and WebSphere 5.1.1.5.

User Behavior Tracking

User Behavior Tracking (UBT) tracks user activity on the portal desktop. UBT consists of three main features:

  1. UBT configuration provides interfaces to configure UBT logging and UBT reporting features.

  2. UBT logging logs UBT data dynamically as per the user actions on portal desktop.

  3. UBT reporting provides a set of sample reports generated based on the data collected by UBT Logging system.

The tracked user activity is logged into external storage systems so that third party tools can analyze user behavior with respect to the portal.

Enhancements in this Release

Enhancements to the following features are included in this release of the Portal Server software:

Communications Channels

This sections contains the following:

Mail

The following enhancements are included in this release of the Portal Server software. The Mobile Access mail provider did not do any time stamp conversion of the email. The Mobile Access displays the same timestamp that was stored on the Mail server. If the Mail server did not maintain consistency in the time stamps, then the user saw various timestamps in their emails. With this release, based on the user time zone preference as set in the User Info Provider, the time stamp of the email is changed accordingly and the Email timestamp in Mail Provider is consistent with user time zone.

Calendar

The Calendar channel includes support for adding events and tasks in this release of the Portal Server software.

SSO Adapter

The following enhancements are included in this release of the Portal Server software.

Display Profile

The isTopLevel property (Boolean) has been added to the global Developer and Enterprise Sample portal display profile documents. The isTopLevel property is, by default, set to true for the following containers and providers.

Containers

JSPDynamicSingleContainer, JSPTableContainer, JSPDynamicSingleContainer, JSPTabContainer, FrameTabContainer, WirelessDesktopDispatcher, WirelessTemplateContentChannel, TemplateNativeContainer, JSPNativeContainer, VoiceJSPDesktopContainer, JSPRenderingContainer, and ASCTabContainer

Providers

JSPTabContainerProvider, TemplateTableContainerProvider, TemplateTabContainerProvider, DynamicAggregationContainerProvider, WirelessDesktopDispatcherProvider, WirelessTemplateDesktopProvider, WirelessTemplateContentProvider, WirelessJSPDesktopProvider, and JSPRenderingContainerProvider

Mobile Access

Mobile Access enhancements include:

Print to Fax

The fax gateway feature allows mobile device users to send a document to a fax machine located anywhere. In this release, Mobile Access software addresses one feature where you can fax one or more documents which are available as a received email attachment(s).

MSISDN Support

The MSISDN Number is the standard international telephone number used to identify a mobile subscriber. MSISDN authentication eliminates the need for authentication from users. Automatic authentication is achieved by determining the user based on the MSISDN number of the subscriber.

Image Transcoding

Mobile Access includes functionality to convert different types images into forms that can be displayed on mobile devices.

Support for email Attachments

The List attachment(s) option appears when one or more attachments are attached to the message. Users can click the link to view the attachment provided the attached file format is supported by the mobile device's browser. If the file format is not supported by the mobile device's browser, you can download the file and view it later with a suitable software.

Mail Voicelet

The Mail Voicelet provides email access to the user through the voice interface. You should be able to perform basic email-related operations such as receiving email messages, obtain an email summary, listen to the headers and body of a specific message, and delete an email message.

Usability Improvements

Redundant pages and unnecessary email summary information has been removed for easy email access from mobile devices.

Support for Native cHTML

CHTML is now fully supported, when in native mode with rendering turned off.

Support for Java Server PageTM Comm Channels

The Mobile Access communication channels JSPs can utilize the new SSO adapter tag library, in addition to the current Mobile Access tag libraries. The URL builder tag libraries that are used by the Portal Server communication channel JSPs are not applicable to Mobile Access, as they generate URLs for unsupported clients.

Proxylet

Proxylet can be deployed for the entire enterprise domain or for a few selected applications on the enterprise domain. This is achieved by means of Proxylet rules. For more information, please refer to Chapter 6, Modifying Proxylet Rules, in Sun Java System Portal Server 7 Configuration Guide.

If Proxylet is deployed for the entire enterprise domain, then all applications including the main portal page will be served through Proxylet. If Proxylet is deployed only for a few selected application, it provides an option to configure application URLs. These application URLs will be displayed on the Proxylet channel.

When a user clicks on a link, Proxylet is launched if it is not already running. Once Proxylet is launched, the user is redirected to the application URL page or the portal desktop page based on the deployment option. The Proxylet UI contains controls to stop and start Proxylet. Clicking the stop button restores the proxy settings and stops the server.

Please advise your users that when using the Proxylet applets, browser pop-up blockers must be disabled. When the user clicks on the Proxylet channel, a pop-up box appears much like Netlet and other applet applications. If the user is logged in to Portal Server, invoked Proxylet, and is using Netscape 7.0, the user must restart the Netscape browser.

Federated Search

The Federated Search feature enables users to submit a search query to multiple search engines concurrently and have the search results displayed in a unified format. The Federated Search feature provides a single interface for the user to post a search query to both a web meta-repository, such as google.com, and an internal directory system, such as a local personnel directory. The search results from these two different sites are presented to the user in a single web page.

Subscriptions

The following enhancements are included in this release of the Portal Server software.

URLScraper Authorized Access

The URLScraper includes a mechanism to get authenticated content from different URL and scrape content from password protected site. The URLScraper makes a request to the specified URL along with the user credentials and the returned cookies are used for session tracking and in subsequent invocation to this site.

The administrator provides:

loginUrl

The loginUrl is the action attribute of the HTML form that is presented for user authentication. The loginUrl is different from the URL to be scraped . For example, to scrape http://my.yahoo.com, the loginUrl is http://login.yahoo.com/config/login.

loginFormData

The loginFormData contains user credentials as HTTP query parameters (such as the HTML form attributes that must be passed for authentication). Here, the keys are the HTML form attributes and the values are the user credentials that need to passed. The values in square brackets will be filled during runtime.

isHttpAuth

Specifies whether or not it isHttpAuth. Only Http-Basic Auth is supported at this time. The HTTP header is set with Authorization header using the user credentials.

formData

This is the data that needs to be posted while invoking the URL.

Deprecated Features

The following features are being deprecated with this release of the Portal Server software.

NetMail

The NetMail feature is being removed from this release. This includes the NetMail Java applet, NetMail Lite, the MailcheckProvider and Mailcheck channel, the NetMail LDAP service, and NetMail-related features of the UserInfoProvider.

Template Based Containers

The template-based containers, tab and table, are being deprecated. This includes the display profile Provider elements, templates, TemplateTableContainerProvider class, and TemplateTabContainerProvider class. The same functionality is provided by the JSP-based versions of the containers.

Command Line Utilities

Most of Portal Server CLIs from previous releases are deprecated and psadmin is the new CLI utility for the Portal Server. The only CLIs used by the Portal Server from previous releases are: psconfig, perftune, pstune-portal, pstune-env, and rdmgr. The following table shows the command-line utilities that are being deprecated in this release and the new command-line utility that support the same functionality.

Table 2 CLI — Deprecated Commands Map to New Commands

Deprecated CLI 

New CLI 

deploy

psadmin redeploy

dpadmin

psadmin merge/modify/add/remove/list-display-profile

gateway

psadmin start-sra-instance/stop-sra-instance

netletd

psadmin start-sra-instance/stop-sra-instance

par

psadmin import/export/list-par

pdeploy

psadmin deploy-portlet and psadmin undeploy-portlet

rwadmin

psadmin create-rewriter-ruleset

psadmin delete-rewriter-ruleset

psadmin get-rewriter-ruleset

psadmin list-rewriter-ruleset

psadmin set-rewriter-ruleset

rwproxyd

psadmin start-sra-instance/stop-sra-instance

Java 1 Applets

Java 1 applets are being deprecated. This deprecation affects browsers that do not support plug-in JVMs (such as Netscape 4.7x and IE 5.0). To avail of the new features in Portal Server, use newer browsers.

Deprecation Notifications and Announcements

Support for Microsoft Internet Explorer 5.5 is being deprecated and it will not be supported in future releases.

Support for Netscape Navigator versions 6.2.1 and 7.0 is being deprecated and they will not be supported in future releases.

Portal Server Patch Information

A required patch has been released for the Portal Server 7 software. The patch contains some upgrade related fixes and other miscellaneous fixes. The patch IDs for this consolidation are:

The patch README.txt file contains installation and configuration steps and the list of bugs that are fixed in the patch. To download the patch and view the patch README.txt, go to http://sunsolve.sun.com and type the patch ID in the PatchFinder field.

Steps Required for WebSphere Installation

The following order should be followed to install WebSphere software:

  1. Prepare WebSphere install.

  2. Install Portal Server 7 in the configure later mode.

  3. Apply the patch.

  4. Configure the portal using psconfig utility.

Installing Sun Java System Portal Server 7 Software

For a fresh installation of the Portal Server software and stack components, see Chapter 2, Installing the Sun Java System Portal Server 7 Software, in Sun Java System Portal Server 7 Installation Guide.

To install the Portal Server software on existing stack components, note that you must upgrade the stack components to Sun Java Enterprise Systems 4 release of the components before installing the Portal Server software. See the Sun Java Enterprise System 2005Q4 Installation Reference for information on upgrading the stack components.

To uninstall the Portal Server software, see Chapter 6, Un-installing Sun Java System Portal Server 7 Software, in Sun Java System Portal Server 7 Installation Guide.

Bugs in this Release

This section contains information on the open bugs of the Portal Server 7 software. The following product areas are covered:

Administration via Command Line Utilities


The psadmin import command does not update the Display Profile using the -—dp-only option. (#6323091)

Description:

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, then --overwrite option has to be used. For example, type ./psadmin import -u amadmin -f ps_password -p portal-ID --dp-only --continue --overwrite dporig.par.


Changes to classification.conf file are not displayed in Portal Server management console. (#6323167)

Description:

The Classification Rules do not reflect the rules added via the new classification.conf file and changes to the classification rules can be seen in Portal Server management console only after restarting the web container and CACAO server.


Unable to search using --searchportletdata or --searchorgdata options. (#6333299)

Description:

Unable to search using --searchportletdata or --searchorgdata options.


Upgrade: psadmin create-portal does not deploy the war files. (#6354710)

Description:

After the Portal Server upgrade is complete, the psadmin create-portal creates the war files, but they are not deployed.

Solution:

The war files have to be deployed manually.


Creating a Portal Server instance does not upload the Portal Server directory archive. (#6357588)

Description:

When you run psadmin create-instance command from machine1, the directory structure /var/opt/SUNWportal/portals/portal1 of machine1 is zipped and uploaded on machine2. This does not work.

Solution:

Run psadmin create-instance on machine2 and it will be downloaded from machine1.


Portlet is not deployed if the instance is in the same domain (on ASApplication Server 8.1). (#6357650)

Description:

When you run psadmin deploy-portlet, the portlet should be deployed on all the instances of the portal. But the portlet is not seen when the instance desktop is accessed. The portlet is, however, deployed if the instance is on a different domain.


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

Description:

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


Installation of portal hangs when installed on SSL instance on web server. (#6352637)

Description:

Portal hangs when you do the following:

  1. Install web server, Access Manager and Directory server on machine1.

  2. On machine2 install web server and make it SSL.

  3. Install AM-SDK on machine2.

  4. On machine2 install portal in config latermode.

  5. Configure CACAO using example2.xml.

  6. Make the following changes to webcontainer.properties:

    WebcontainerScheme:https

    WebContainerCertificateDBPassword:password

  7. Execute psadmin create-portal on the SSL instance of web server.

The CLI hangs.

Solution:

After you see successfully completed message in /var/opt/SUNWportal/log/admin/portal.o.o.log,you can force to terminate psadmin.


Incorrect configuration is created in multiportal when two portal installs use different file systems. (#6348452)

Description:

The portlet and desktop administration fails since they take wrong values for configuration.

Solution:

After create-instance zips, download the existing portal instance configuration from the remote host and unzip it on to the local host. All properties under /var/opt/SUNWportal/portals/portal1/config can be replaced by <portal-install>/template/portal/config and the token replacement can be done based on file system on the local host.


Portal not accessible after redeployment on WebSphere. (#6378407)

Description:

With WebSphere as web container, the portal webapp is not accessible after the psadmin redeploy is executed

Solution:

To access the portal after redeploying on WebSphere, do the following:

  1. Go to WebSphere administration console.

  2. Start the portal webapp.


Redeploying portal on Weblogic managed server gives exception in the log file. (#6374906)

Description:

An error message and exception is displayed on the Weblogic console when you execute the following commands:

/space/PS/SUNWportal/bin/psadmin redeploy —u amadmin —f

/space/PS/SUNWportal/bin/ps_password -p pserv197011

Solution:

Delete the portal.war that is already deployed from Weblogic admin console. Deploy the war file manually from Weblogic administration console from the following directory:

/var/opt/SUNWportal/portals/portal1/war/portal.war

Access Manager Administration Console


Portal services in amconsole should provide proper message. (#6314550)

Description:

In the Access Manager administration console, if you click on any of the Portal Server services at Service configuration level, it displays There is no information to display for this service, at Org/role/user level, it displays Save/Reset/Delete buttons, and for some services, it displays Indicates required field.

Solution:

You must administer the Portal Server services through psconsole.


Portal services in Access Manager console should display a descriptive message. (#6314550)

Description:

From the Access Manager console, when you select aPortal Server service, the following message is displayed:


There is no information to display for this service
Solution:

The Portal Server services should be administered using the Portal Server management console or the psadmin command line utility.


User Behavior Tracking reports not generated. (#6373731)

Description:

Enable User Behavior Tracking for a particular org from psconsole. When you click Generate Reports from the portal desktop, an unknown error message is displayed.

Solution:

Set —Djava.awt.headless=true in server.xml of the web server on which psconsole is deployed.

Collaboration and Communities


Shared Events Portlet: Search for events shows multiple entries for the same event. (#6305026)

Description:

When you create a repeating (recurring event), five instances of that event is created.


Unable to access the Wiki through Gateway, (#6329795)

Description:

After logging in to the Community Sample, the Wiki (HTML editor) portlet does not load through Gateway.


The delete event button does not work on the Shared Events portlet on Linux. (#6335175)

Description:

In the Community Sample, if you create an event and then try to delete the event, the delete button does not get activated.

Solution:

Select the edit button for the event to delete the event.


Exception occurs while attaching certain file types (#6360141)

Description:

From the wiki, an exception occurs while attaching any file of type .txt, .html or .xml.

Solution:

None.


Community portlets failing intermittently. (#6336646)

Description:

The community portlets are failing intermittently on the community home page when installed on Application Server.

Solution:

Perform the following steps:

  1. Disable parellel-execution flag in the desktopconfig.properties file:

    portletRenderModeParallel=false

    The desktopconfig.properties file is located in the <portal-server-data-directory>/portals/<portal-instance>/config directory.

  2. Restart the application server.

Communication Channels


Lotus Address Book and Calendar does not work with old NCSO.jar. (#6216069)

Description:

Lotus Address Book and Calendar need the latest version of NCSO.jar to work.

Solution:

Use the latest version of Domino, for example NCSO.jar from Domino 6.5.1.


Administrator proxy authentication disables end user credentialing. (#6229105)

Description:

When administrator proxy authentication is enabled, the communication channels (JSP version) do not display any server or user provisioning fields in the edit pages.

Solution:

The values need to be specified by the portal administrator in either the SSO adapter templates or SSO adapter configurations.

Desktop


Name of new tab created from desktop not visible in psconsole. (#6363585)

Description:

When you create a new tab tab1 from the portal desktop, the new tab still has the name as JSPTabCustomTableContainer1 and sometimes it is JSPTabCustomTableContainer0.


On selecting layout successive new frames are opened. (#6347765)

Description:

Log on to the portal desktop and select the provider as FrameTabContainer. Click Layout and choose any layout by clicking the radio button. The changed layout appears in a new tab frame and not in the original frame. Successive new frames are opened whenever the layout is changed in the new frame.


Value field needs to be made compulsory for Integer Property creation. (#6364215)

Description:

Try creating an Integer Property without a value. Property creation fails.

Solution:

Do not leave the Integer Property value field empty.


Clicking help links on portal desktop displays error. (#6340627)

Description:

Log on to portal desktop and click the help link for any of the channels and an error message is displayed.


WebSphere Weather portlet displays error. (#6396623)

Description:

Log on to portal desktop and click the portlet samples tab, the Weather portlet displays an error. Instead, it should display “The service is currently not available.”


User's time zone is not reflected in Showtime portlet. (#6401315)

Description:

After logging in to portal desktop, click Edit under User Information. Change Timezone to BMT and click Finished. The User Information still shows IST (Calcutta).

Installation


The import and modify display profile fails when deploying samples on a new portal on Linux. (#6301873)

Description:

The import and modify display profile fails when deploying samples on a new portal on Linux.


GUI installer cannot be used for multi-portal installation. (#6329786)

Description:

When the GUI installer is used for multiple portal installation, it displays successfully completed message but the portal is not installed on the second machine.

Solution:

To perform a multi-portal installation using GUI installer, do the following:

  1. Install AM-SDK and web server on the second machine.

  2. Start the web container.

  3. Invoke the GUI installer and install the portal bits with Configure Later option.

  4. Copy the /etc/opt/SUNWcacao/security directory from the machine where. the first portal resides to the second machine and then restart the CACAO server on the second machine.

  5. Copy /opt/SUNWcacao/bin/cacaoadm restart in case of Solaris and /opt/sun/cacao/bin/cacaoadm restart in case of Linux.

  6. Install the portal using psconfig --config example6.xml (this file may vary depending on what the user wants to install).

    The example files can be accessed from <PS_INSTALL_DIR>/SUNWportal/samples/psconfig in case of Solaris and <PS_INSTALL_DIR>/portal/samples/psconfig directory in case of Linux. README.txt in the same directory explains the configuration of each example file.

  7. Start the CACAO.


Deleting a portal and creating it again with the same name fails. (#6361883)

Description:

The instance ID of a portal continues to exist in the directory server even after a portal is deleted and prevents creation of another instance with the same name.


Portal install document lacks sample configuration file examples. (#6385520)

Description:

Sample default configuration file with appropriate values needs to be provided in the document.

Example:

The following is sample values for the configuration file:

INST_GWNAME% — "default"

URI% -"/portal"


Deleting portal on Weblogic does not remove portal information. (#6376297)

Description:

Install Portal Server 7 on Weblogic managed server. Run psadmin delete-portal command. This does notremove all portal related information from startmanagedWeblogic.sh and brings it back to its initial fresh state.


Portlet needs to be deployed from console for portal running on admin server. (#6338787)

Description:

When you add a portlet channel to the desktop and load the user desktop, it displays an error message.

Solution:

The portlet will appear on the user's desktop if deployed again from Weblogic console.


Portal installation on Weblogic managed server fails. (#6347297)

Description:

When Access Manager and Portal Server are on the same Weblogic managed server, the portal installation fails. However, if Access Manager and Portal Server are on different managed servers, then the portal installation works.


In multiple portal instances deleting one instance corrupts the others too. (#6376216)

Description:

After creating three portal instances on three managed servers deployed on Weblogic, runningpsadmin delete-instance corrupts startManagedWeblogic.sh script and you cannot run the other two portal instances.

Solution:

Backup the startManagedWeblogic.sh script before performing the psadmin delete-instance operation. After you delete the portal instance, restore the backed up startManagedWeblogic.sh script and the other portal instances on the same domain will continue to work.

Inter Portlet Communication


Inter Portlet Communication (multiple war) does not work in case 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 will not work in case the portlet channel is minimized or closed since the events will not be sent to closed or minimized channels.

Localization


Users cannot unzip multi-byte files in Internet Explorer 6.0. (#4935010)

Description:

When using Internet Explorer 6.0, users are unable to unzip multi-byte zip files created by NetFile. This problem occurs if the zip utility is used to unzip files in the Windows environment.

Solution:

If using the Windows platform, use the gzip utility to unzip multi-byte files.


Community Sample Portal is not fully localized. (#6337499)

Description:

Some of the channels in Community Sample Portal is displayed in English. The introduction channel contents, document channel content links on the bottom of the page, channel titles are displayed in English.


Enterprise Sample Portal is not localized. (#6337500)

Description:

Enterprise Sample has not been localized.


Developer sample English online help is displayed from channel help. (#6338191)

Description:

Following channels do not have localized online help:

  • My Front Page tab

  • IM channel

  • Proxylet channel

  • Netlet channel

  • Communications Express Mail

  • Communications Express Calendar

  • Communications Express Address Book

  • WSSSO Portlet

  • Sample tab

  • Sun News channel

  • Syndicated contents tab

  • RSS feed channel

  • Portlet Sample tab

  • Bookmark portlet

  • Show Time portlet

  • Notepad portlet

  • Weather portlet

  • JSF GuessNumber portlet


In Developer Sample some of links in the anonymous desktop are in English for zh locale. (#6339912)

Description:

In zh locale, Home , Help , Welcome links and Developer Sample are displayed in English for anonymous user.


Clicking Edit button on channel having multi-byte name throws serious desktop error. (#6342711)

Description:

Create a channel with a multi-byte name or a tab with a multi-byte name and add channels to it. Click the Edit button of these channels and you get serious desktop error message.

Solution:

Give multi-byte title and description for channel and tab in English.


Partially localized psadmin CLI. (#6349624)

Description:

Some psadmin CLI messages are not localized. They are in English.


Community Sample online help is not localized. (6357704)

Description:

Click the Help button on Community Sample portal and it displays the English online help page.

Solution:

To display localized online help, add the following locale to the help URL:

http://<host.domain>/portal/community/content/Help/index.html becomes http://<host.domain>/portal/community/content/<locale>/Help/index.html.

Example:

For Japanese locale, the URL is http://<host.domain>/portal/community/content/ja/Help/index.html


Help file index.html not present for de and es locale. (#6363713)

Description:

Community Sample portal help file index.html not present for de and es locale.


In Community Sample, multi-byte filenames are garbled in File Sharing portlet. (#6357711)

Description:

File Sharing portlet is not able to parse multi-byte file names correctly.


English desktop is not displayed when web server is started on locale other then English. (#6347770)

Description:

When web container is started in locale other then English, and if content is requested by setting browser-preferred locale to English, then some of the desktop contents will be in the locale in which the server was started.

Solution:

Start Web Container in English locale.


No NetFile links on My Applications channel to Java1 and Java2. (#6338816)

Description:

In My Application channel, NetFile Java1 and NetFile Java2 links are not present in localized desktop. The links are present only when the desktop is in English.


Japanese psconsole online help has non-reviewed file. (#6357536)

Description:

The Japanese language online help displayed on the PSConsole is non-reviewed. It also contains some special characters.


Current time and edit page error messages are in English. (# 6266477, 6266492)

Description:

In the Weather portlet, current time and edit page error messages are in English.

Log


Log file for Portal Server is empty on WebSphere 5.1. (#6301159)

Description:

Complete configuration steps for WebSphere 5.1. When you check the portal logs, they are empty. The sequence of portal server performance is not logged.

Solution:

Perform the following steps:

  1. Remove the following JVM options:

    Djava.util.logging.manager=com.sun.identity.LogManager

    Djava.util.logging.config.class=com.sun.identity.log.s1is.LogConfigReader

  2. Add the following JVM options as the first two JVM entries:

    DLOG_COMPATMODE=off

    Ds1is.java.util.logging.config.class=com.sun.identity.log.s1is.LogConfigReader


Unable to set log files for logger name. (#6333966)

Description:

Unable to set log files for logger name with set-logger when the component is gateway, nlproxy, and rwproxy.

Solution:

Change permissions to read, write, and execute for the SRA logging directory and all the files in the directory.

Example:

chmod -R a+rwx/var/opt/SUNWportal/logs/sra

Mobile Access


Installing patch to Mobile Access software. (#6365852)

Description:

You should install a patch to Mobile Access software.

Solution:

To install patch to Mobile Access software, use the following instructions:

  1. Install Portal Server.

  2. Download the patch 119530-02 from http://sunsolve.sun.com.

  3. Install the patch.

  4. Restart Portal Server and Access Manager.


Manual step to enable Mobile Access functionality in Portal Server 7. (#6312195)

Description:

Manual steps are necessary to enable Mobile Access functionality in Portal Server 7.0.

Solution:

Perform the following steps:

  1. On the psconsole, click Portals.

  2. Click portal1 in the list of portals.

  3. In the Select DN drop-down menu, select DeveloperSample.

    Note –

    If the user creates own organization, then select the user-created organization.

  4. In the Desktop Attributes section, change the default value of parent container to WirelessDesktopDispatcher.

  5. Ensure the value of Edit Container is set to JSPEditContainer.

  6. Ensure the value of Desktop Type is set to developer_sample.

  7. Click Save.


Voice portal does not show unread email messages if user ID and email ID are different. (#6251291)

Description:

When the user accesses email messages through Voice portal and selects the option List Unread Messages Addressed To Me, there is no message indicating the present unread email messages even if unread email messages are available. This happens when the mail server login user ID is different from that of the email ID. For example, the login user ID is JohnDoe and the email ID is John.Doe@Sun.com.


Add MailProvider to access voice portal. (#6335332)

Description:

To enable the Mail channel to be available while accessing Voice portal, you need to do the following;

  1. Create a Mail channel of type MailProvider.

  2. From psconsole, add the channel to the portal desktop (MyFrontPageTabPanelContainter).

  3. From psconsole, add the MailProvider-based channel to VoiceJSPDesktopContainer.


Online help not available for Mobile Mail Preferences. (#6185112)

Description:

From portal desktop select Edit Mail. Click Mobile Mail Preferences link. When you click, the Help window displays an error instead of information on how to use Mobile Mail Preferences.


An error message is displayed when logging onto the Portal using a Nokia WML device. (#6242679)

Description:

While logging in to the Portal through Nokia WML device an error message, File too Large to be Downloaded, is displayed.

Solution:

Change the attribute of the device profile from Cookies Supported to Cookies Not Supported.


Native path fails with too many channels. (#6242641)

Description:

When there are too many channels on the desktop it displays an error message “File too large to be loaded”.

Solution:

To allow many channels on the desktop:

  1. Log in to Portal Server management console.

  2. Click Manage Channels & Containers button.

    A popup window appears.

  3. From Select Location drop-down menu, choose DeveloperSample and click OK.

    You are taken to Manage Containers And Channels page.

  4. From View Type, choose JSPNativeContainer.

    You will see the available channels on the left and Properties on the right.

  5. Change the frontPagesize to approximate size of the desktop after adding n number of channels to desktop.

  6. Uncheck IsChannelsMinimized, so that channel contents are split into multiple pages.


Large html attachment is not fully displayed in email. (#6294635)

Description:

If the email attachment is larger than what the browser can handle, then the contents of the attachments are only partly displayed in the mobile device.


Unix authentication module in cookieless mode displays error message. (#6301733)

Description:

Log in to mobile desktop using Unix authentication module in Cookieless mode displays Serious desktop error message. However, in Cookies Supported mode, the log in succeeds.


Treo device connects only if the default HTTP port is 80. (#6321267)

Description:

Treo mobile device accesses Mobile Access functionality only when the portal server is installed on the default HTTP port 80.


Deleted messages are not removed permanently from voice portal. #(6251934)

Description:

Log in to the voice portal and select Mail option. From the listed messages by the voicelet, delete and confirm the deletion of a message. When you log back into the Mail through the voice portal, the deleted message is marked for deletion and not permanently deleted.

Solution:

Permanently delete the messages that are marked for deletion using a mail client.


Special characters in subject line of unread email exits Voice Mail Channel. (#6301217)

Description:

The Voice Mail Channel abruptly exits if the subject line of an unread email contains the two special characters & and <. You get a message “We have encountered technical difficulties.”


Account inactivated without lockout warning. (#6252408)

Description:

A warning message is not displayed despite enabling lockout warning in the administration console and the account is inactivated due to multiple incorrect login attempts.


Mail views cannot be configured for non-default devices. (#6332781)

Description:

Mail views cannot be configured for devices that are not mentioned in the list of mobile devices under the Portal desktop. When you try to set Device Views, only default devices are displayed.


POP collection settings is not saved. (#6332798)

Description:

When you create a POP collection from the Communication Express Mail channel, only the POP collection name and port number are saved. The server name and user information is not saved.

Solution:

After you create a POP collection and click Finish, Click Edit to verify the settings before exiting the Mobile Mail Preferences. This step saves the POP collection settings correctly.


Command line interface restrictions. (#6312802)

Description:

The Mobile Access software configuration attributes with user-friendly names, sortBy, sortOrder, fromAddress, and sentFolderCopy cannot be maintained through command line interface (CLI). However, you can maintain these attributes by editing them by clicking the Edit link from the mail channel.


Mail menu error makes Mail channel unusable. (#6329170)

Description:

When you click the Mail menu, you see an error instead of the menu items.

Solution:

Configuring the address book enables the Mail channel to work properly.


Self-register feature registers user in top level. (#6330978)

Description:

A new user is created at the top level org despite selecting DeveloperSample as the target place for creating the user. Also, you cannot self-register using the Register option on the authless desktop. The mobile desktop for the newly registered user says that no channels have been configured.

Solution:

Self-register function works when performed from the Membership authentication module and the user is created under the DeveloperSample org.


Edit Content and Edit Layout options do not affect display on Mobile Desktop. (#6332777)

Description:

Despite making changes to these options on portal desktop, the changes are not reflected on mobile desktop and also, once the Mobile desktop is accessed, accessing the portal desktop again causes the changes made in portal desktop to be lost.


Links to three mobile services appear without any configuration. (#6358359)

Description:

Links to MobileMail, MobileCalendar and MobileAddressBook appear in the mobile desktop even when they are not added to JSPRenderingContainer or JSPNativeContainer. The three mobile services should appear only when they are added to JSPRenderingContainer or JSPNativeContainer.


HTML to AML functionality is broken. (#6351027)

Description:

Most mobile devices are supported using the AML-based JSP files. The output of the AML pages is processed by the rendering engine, which translates AML to device-specific markup. This functionality is not functioning.


Accessing nested containers displays error. (#6301735)

Description:

Nesting containers and accessing them using a mobile device displays “Serious Desktop Error” message.

Monitoring


Monitoring does not work on WebSphere 5.1.1.5. (#6376117)

Description:

Monitoring does not work when Portal Server 7 software is installed on WebSphere 5.1.1.5.

Solution:

To enable monitoring, disable the following in MonitoringConfiguration.properties:

com.sun.portal.monitoring.ConnectorContext.sas1.disable=true

com.sun.portal.monitoring.ConnectorContext.ss1.disable=true


Monitoring does not work in a multi portal instance scenario. (#6396046)

Description:

When there are multiple portal instances available, if you bring one or more portal instances down, the Monitoring tab does not work.


Monitoring does not work for portal created using psadmin create-portal. (#6323766)

Description:

Monitoring displays an error message while executing the CLI.

Solution:

Go to /etc/opt/SUNWam/config/AMconfig.properties

Change the value of com.sun.identity.jss.donotInstallAtHighestPriority from false to true. Then restart the web container.


Container mbeans are not listed on psconsole. (#6362460)

Description:

Monitoring information on containers is not available on psconsole, but available through psadmin Monitoring subcommands


Sorting of channel name on monitoring tab not functional. (#6354751)

Description:

Unknown error message is displayed when you click on Channel Name tab to sort.


Monitoring functionality will work only if portal is accessed at least once. (#6365342)

Description:

If the portal server instance is not running or if portal has not been accessed at least once, the Setting tab shows status of the portal server instance as Not Available.

NetFile


Online help content is not displayed for NetFile. (#6375496)

Description:

When you click the Help menu for NetFile Java2, an error is displayed instead of the help content.

Netlet


Netlet does not load when portal is launched from Proxylet. (#6296829)

Description:

Portal sessioncannot be launched through Proxylet after creating a Proxylet rule in the portal and a Netlet rule in amconsole.

Personalized Knowledge Pack


Discussions created by registered users appear as anonymous. (#6363127)

Description:

When a registered portal user creates a new discussions in the community services, the discussion appears as created by an anonymous user.

Solution:

Add Authentication Configuration service to the user.

Portlet


Log files are redirected if the display name is null. (#6319289)

Description:

In case the display name is null in web.xml, the logs from portlet web application will be directed to the default logger for portlet web application.


Templates loaded by shared events and tasks not accessible from psconsole. (#6350620)

Description:

SSOAdapterTemplates added using amadmin do not appear in psconsole.

Solution:

Stop and restart the CACAO server using the following command:

/opt/SUNWcacao/bin/cacaoadm stop; /opt/SUNWcacao/bin/cacaoadm start


Portal desktop does not close the Proxylet console. (#6241355)

Description:

Even after you log out of the portal console, the Proxylet continues to run.


Extend Session attribute in Netlet does not work. (#6252410)

Description:

The portal desktop session times out even though the Netlet session is active.

Solution:

You need to log out of the portal desktop and log in again for the updated value of the Extend Session attribute to be reflected in the session.


Netlet is not loaded when portal is launched through Proxylet. (#6296829)

Description:

Initiate a portal session through Proxylet. The URL of the browser from where the Proxylet is launched is rewritten with portal desktop URL and the portal desktop is launched. When you launch the Netlet, the browser displays “Netlet is loading” message but fails to launch.


Custom portlets do not deploy in WebSphere from psconsole. (#6341228)

Description:

When you deploy a portlet from psconsole, you see a successfully deployed message. But, in the WebSphere administration console the portlet war file is not deployed. In the portal desktop, the Portlet Samples tab displays an error message.

Solution:

To deploy portlets in WebSphere, perform the following steps:

  1. Run deploy portlet command from psconsole or psadmin.

  2. Go to WebSphere administration console http://<machine>:7090/admin and start the deployed portlet.

Portal Server Management Console


Redeploying one web application resets all other web applications in Sun Java System Web Server 6.1. (#6327475)

Description:

The Portal Server management console loses its session whenever a deploy/undeploy is done on any web applications in the web server.


Creating more than one portal instance should not be allowed on one web server instance. (#6326901)

Description:

Creating two portals on the same web server instance tightly couples both the portals. Any operation performed on one portal is automatically reflected on other portal.


The Portal Server instance needs to be restarted on WebLogic server. (#6339379)

Description:

Running the psadmin create-instance and psadmin create portal on a WebLogic starter requires restarting the web container.

Solution:

Restart the WebLogic administration server and managed server.


Download of dp file fails if filename has .xml extension. (#6349031)

Description:

Using Explorer browser, if you download the dp file with the extension .xml, you get an error message that the xml file cannot be displayed.

Solution:

Do not use a filename with .xml extension.


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 ./web-src/common/common-fonfig.xml, which is located at common/common-config.xml inside the psconsole war file.

  2. Set the value of httpPort to a in-secure port (http) that the web container provides.

Example:

The following example demonstrates setting 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 supports 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 to for the changes to take effect.


Admin panel fails to add file URLs as starting points. (#6360469)

Description:

Fails to add file URLs as starting points when editing a file system robot site.

Solution:

Perform the following steps:

  1. Create a local file system site using URLs in the following formats:

    file:///filepath or file:/localhost/filepath

  2. Edit the file filterrules.conf to add starting points for the file system site definition.

Proxylet


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.

Rewriter


When using Microsoft Exchange 2003, GIF files are missing in some of the pages. (#6186547)

Description:

Many interface image files are missing.


In iNotes, under the Contacts tab, the Help page is redirected to the Administration console. (#6186541)

Description:

Clicking the Help button from the Contacts tab in iNotes displays the Administration console page instead of the Help page.


iNotes does not logout correctly. (#6186544)

Description:

Clicking on logout in iNotes displays two options. Neither of these options will log out of iNotes.


Microsoft Exchange 2000 SP3 gives warning messages and action cancelled messages. (#6186535)

Description:

The following actions in Exchange 2000 SP3 it causes security warning messages and Action cancelled messages:

  • Clicking New tab under Mail.

  • Selecting any item in the drop box list.

  • Clicking New tab under Calendar.

  • Clicking on Empty Deleted Items folder.

  • Creating a new task.


When using Microsoft Exchange 2000 SP3, Moving or Copying messages to specific folders doesn’t work. (#6186534)

Description:

If you login to the Portal Server software through the gateway, and you edit the bookmark channel with the Microsoft Exchange machine details, the Move/Copy buttons on the Microsoft Exchange interface produce the error “Operation could not be performed.”


When using Microsoft Exchange 2000 SP3, Clicking on empty deleted items folder displays Action Cancelled. (#6186540)

Description:

If you log in to the Portal Server software through the gateway, and you edit the bookmark channel with the Microsoft Exchange machine details, deleted items can not be emptied in the Microsoft Exchange interface.


URL present in Remote JavaScript not rewritten correctly. (#6364872)

Description:

URL present in Remote JavaScript not rewritten correctly.


Console Help is not provided for Rewriter RuleSets. (#6327431)

Description:

No Help option is available to explain Rewriter RuleSets screen.


Not all colors are used for Mail message composition. (#6308176)

Description:

The color palette only shows violet color irrespective of the color you select.

Secure Remote Access


Secure Remote Access installation fails when installing in different sessions. (#6333367)

Description:

Install Secure Remote Access in the same session as Portal Server.

Search, Subscriptions, and Discussions


The importmgr utility has no documentation. (#6203829)

Description:

Documentation on the new Search subcommands for import agents can be found in the Chapter 9, Search Subcommands - Import Agents, in Sun Java System Portal Server 7 Command-Line Reference.


Google APIs not fully supported. (#6335501)

Description:

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


Radio button malfunction. (#6361116)

Description:

The Radio button malfunctions for robot property extract meta data..

Solution:

To change Extract meta data from “yes” to “no”, modify the following line from filter.conf:

Change Generate enable=true fn="extract-html-meta" type="text/html" to Generate enable=false fn="extract-html-meta" type="text/html"

To change Resolve cname from “yes” to “no”, modify the following line from robot.conf.

Change use-dns-cname=true to use-dns-cname=false.

WSRP


Accessing sample portlets (such as IPC, search, guess) results in OPERATION_FAILED_FAULT error. (#6301203)

Description:

After configuring WSRP producer and/or consumer, unable to access remote portlets.


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


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

Description:

The SSO configuration of 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.


WSSO portlet to accept simple username and passwords. (#6355670)

Description:

The username and password that is presented by the user in the WSSSO portlet needs to be a fully qualified DN of the user.

Solution:

The sample portal's “developer” user should have the username as uid=developer,ou=People,o=DeveloperSample,dc=india,dc=sun,dc=com


No functional registry interface from psconsole. (#6356897)

Description:

Registry search through psconsole does not work.

Solution:

Use psadmin search-registry.


The command create-configured-producer fails during Developer Sample configuration. (#6334366)

Description:

Remote portlets on the WSRP samples tab of the Developer Sample do not appear. The create-configured-producer fails during Developer Sample configuration.

Solution:

The AM7.0patch1 rectifies this issue. Use the following instructions to install the patch:

  1. Install Identity Server from the installer.

  2. Install AM7.0patch1 and follow the install instructions.

  3. Run the JES installer again and select to install Portal Server.

Known Issues and Limitations

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

Redistributable Files

Sun Java System Portal Server 7 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:

So that we can best 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, please 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 819-2347.

Additional Sun Resources

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