On Microsoft Windows, Portal Server can only be used as an evaluation platform or as a development platform. It cannot be used as a deployment platform.
If you use the Java ES installer to install Portal Server on Microsoft Windows, the resulting installuation does not function correctly.
Solution Do not use the Java ES installer to install Portal Server on Windows. Instead, download Portal Server 7.1 Update 1 from the Sun Download Center at http://www.sun.com/download/products.xml?id=465e130d. Follow the instructions in the ReadMe file that accompanies the download to produce a functioning installation of Portal Server.
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 the host name then the netlet operations will not work for these IP addresses.
Solution Use host names instead of IP addresses.
The problem occurs because the filter entry for the AMLControllerFilter filter is commented in the web.xml file of the Access Manager web application.
Solution In the web.xml file of the Access Manager web application, uncomment the AMLControllerFilter filter entry.
Clicking on the help icon from the SampleIFrame Channel produces “HTTP Status 404 — /portal/docs/en/desktop/iframechann.htm” is not available.
Solution None. No help is provided with iFrame provider.
During installation and uninstallation of Portal Server, the installer and uninstaller appear to hang.
Solution Ignore the apparent inactivity and wait for the Portal Server installation or uninstallation process, which can take up to 45 minutes on a low-end system, to complete.
If you install Portal Server in one installer session, and then install Portal Server Secure Remote Access in a subsequent installer session, the installer does not validate the Access Host value you provide on the Portal Server: Secure Remote Access: Configure Access to Portal page in the subsequent session.
Solution None.
If you install Portal Server in one installer session, and then install Portal Server Secure Remote Access in a subsequent installer session, the installer does not validate the Log User Password value you provide on the Portal Server: Secure Remote Access: Configure Access to Portal page in the subsequent session.
As a consequence, the portal.fabric logs include errors such as PSFB_CSPFCO312: Incorrect LogUserPassword Entered and PSFB_CSPFCO189: Validation of gateway Data Failed.
Solution None.