Thes Release Notes contains important information available at the time of release of Sun JavaTM SystemPortal Server 7.1(“Portal Server”). New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Portal Server 7.1.
The most up-to-date version of these release notes can be found at the Sun documentation web site at 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.
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.
The following table lists the hardware and operating system requirements for Portal Server.
Table 1–1 Hardware and Operating System Requirements
Component |
Platform Requirement |
---|---|
Supported Platforms |
Sun Blade comparable or better workstation or server |
Operating System |
Windows XP Professional SP2 Windows 2000 Advanced Server SP4 Windows 2003 Enterprise Server SP1 (32 bit) Windows 2003 Enterprise Server SP1 (64 bit) |
RAM |
1.5 Gbytes of RAM for regular deployment on Sun Java System Web Server 2.0 Gbytes of RAM for regular deployment on Sun Java System Application Server |
Disk Space |
1 Gbyte of disk space for Portal Server and associated applications |
The Portal Server software requires the following stack components:
Sun Java System Directory Server 6
Sun Java System Access Manager 7 installed in legacy mode.
Portal Server requires Access Manager, Directory Server, and a web container for its installation and configuration. If you are performing a fresh installation, Access Manager and Directory Server do not have to be pre-installed. Access Manager, Directory Server, and Portal Server can all be installed at the same time. If you have Access Manager and Directory Server installed already, point the portal installation and configuration to the existing Directory Server and Access Manager servers.
Sun Java System Web Server 7 or Sun Java System Application Server 8.2.
Sun Java System Portal Server 7.1 software does not support Sun Java System Access Manager 7 installed in realm mode. Access Manager must be installed in legacy mode before installing Portal Server 7.1 software. By default, Java ES 5 installer configures Access Manager in legacy mode in Configure Automatically During Installation mode.
For detailed instructions for installing the stack components, see the Sun Java Enterprise System 5 Installation Reference for UNIX.
The Sun Java System Portal Server 7.1 product gives end users a portal desktop that 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, Portal Server 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.
The following new features are available in Portal Server 7.1:
Administration Portlets and Tag Library
New Management Console
Command-line tools for administration
Communities and collaboration
Logging
Administration audit logging
Monitoring
RSS Portlet
New samples
Support for interportlet Communication
Support for JSF application
Support for multiple portals
Support for Struts application
User behavior tracking
Federated search
Rewriter proxy available in http mode
Administration console option to control all aspects of the checking and authorization on the rewriter proxy
Support for Oracle database
Support for Red Hat Enterprise Linux 4.0
Support for Web Server 7.0 including 64-bit support on the SolarisTM platform
Support for Communications Express 6.3
Portal Server administration console and portal supported on Internet Explorer 7.0.
The following is a list of features deprecated in Portal Server 7.1:
Lotus Address Book and Calendar does not work with old NCSO.jar
In future, Microsoft Exchange and OWA ruleset for Rewriter will not be packaged along with the product.
The following is a list of features removed in Portal Server 7.1:
Secure Remote Access Java 1 Netfile is removed from Portal Server 7.1.
Java 2 version of NetFile is not removed from Portal Server 7.1.
The following are known bugs in the Portal Server 7.1 release:
Admin Tab Not Visible For Users Having OrgAdmin Role (6464910)
Accessing psconsole Through Gateway Redirects Proxylet Page to Portal Home Page (6471845)
deploy-portlet-cli Not Working With Modified Web Server 7 Instances (6472297)
Many bugs for Portal Server are cross-platform, which can affect Windows as well. For more information on these bugs, see Sun Java System Portal Server 7.1 Release Notes.
The help option does not exist for the get-sra-status command. The get-sra-status command retrieves the SRA status on a portal server machine.
Workaround: None.
The Admin tab is not visible for users with OrgAdmin role.
Admin tab is visible if the user is assigned OrgAdmin role through the Access Manager admin console.
Workaround: None.
When a user accesses psconsole through gateway the proxylet page redirects the user to the portal home page.
Workaround: None.
If a user has manually modified the Web Server configuration, the deployment configuration fails for these modified instances.
Workaround: follow these steps:
Invoke web server admin console.
Click on the instance configuration to reset and redeploy all web applications.
While using the IP address in the netlet, if the reverse lookup entry for a particular host is not configured in the DHCP server then the operation associated with that host does not work.
For example, if nslookup.exe ipaddress fails to return host name then the netlet operations do not work for these IP addresses.
Workaround: Follow these steps:
Start a command prompt: Start -> Run ->, type "cmd" then click Ok button.
Run cacaoadm.bat stop.
Exit from the cmd prompt.
Adding portal_install_directory\lib into the path from Control Panel->System->Advanced Tab->Environment Variablesbutton.
Start a new command prompt: cacaoadm.bat start.
Now you can run autoclassify on both psadmin cli and psconsole.
On Windows platform, you must configure Access Manager SDK with container before using create-portal or create-instance . Similarly on a Portal Server or Access Manager separated installation before configuring portal server, Access Manager SDK must be configured.
Sun Java System Portal Server 7.1 does not contain any files which you can redistribute.
If you have problems with Sun Java System Portal Server, contact Sun customer support using one of the following mechanisms:
Sun Software Support services online at http:\\www.sun.com\service\sunone\software
This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.
The telephone dispatch number associated with your maintenance contract
To assist you in resolving problems, please have the following information available when you contact support:
Description of the problem, including the situation where the problem occurs and its affect on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps
If you have problems with Sun Java System Portal Server, Mobile Access, please have the following information available when you contact support:
Description of the problem, including the situation where the problem occurs and its affect on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
What patches (with patch numbers) are installed
Whether the problem is seen on the phone, the emulator, or Mobile Access server
Whether the problem is specific to any particular type of device (for example, Sony Ericsson P800 or Nokia 3650)
Whether problem occurred on default installation of Mobile Access software (if applicable)
When the problem was first seen
Whether the problem occurs all the time or randomly
What changes, if any, were made just before the problem started
How many users are affected by the problem
The number instances of Mobile Access software and how they are linked to Portal Server software and Access Manager software
The number of machines and how they are set up with regard to Mobile Access software
What error messages or exceptions are reported in the log files under <Install_dir>\portal\data\logs , <Install_dir>\portal\data\portals\<portalid>\logs, <Install_dir>\identity\debug
What error messages are reported in the information window for emulators
What the web server port is where Mobile Access is installed
If your problems seem to be associated with a client, please have the following information available:
What client types are new
What default client type settings have changed and how
What errors or exceptions are reported in the <Install_dir>\identity\debug\render.debug file or the <Install_dir>\identity\debug\MAPFilterConfig file
What exceptions are reported in the tag libs log file <Install_dir>\portal\identity\debug\mapJsp
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-4986.
Useful Sun Java System information can be found at the following Internet locations:
Sun Java System Documentation: http://docs.sun.com/prod/java.sys
Sun Java System Professional Services: http://www.sun.com/service/sunjavasystem/sjsservicessuite.html
Sun Java System Software Products and Service http://www.sun.com/software
Sun Java System Software Support Services: http://www.sun.com/service/serviceplans/software/
Sun Java System Support and Knowledge Base http://www.sun.com/service/serviceplans/software/
Sun Support and Training Services: http://www.sun.com/training/
Sun Java System Consulting and Professional Services: http://www.sun.com/service/sunjavasystem/sjsservicessuite.html
Sun Java System Developer Information: http://developers.sun.com/
Sun Developer Support Services: http://developers.sun.com/prodtech/support/
Sun Java System Software Training http://www.sun.com/training
Sun Software Data Sheets: http://www.sun.com/software