Sun Java System Portal Server 7.1 Configuration Guide

Software Requirements

Portal Server requires the following stack components:


Note –

Access Manager must be installed in legacy mode before installing Portal Server 7.1.


For detailed instructions for installing the stack components, see the Sun Java Enterprise System 5 Installation Reference for UNIX.

Miscellaneous Checks

  1. If the system on which you installed Portal Server does not have direct connectivity to the internet, an HTTP proxy needs to be specified. For example, for Sun Java System Application Server, specify the following in the domain.xml file:

    <jvm-options>-Dhttp.proxyHost=proxy-host</jvm-options>
    <jvm-options>-Dhttp.proxyPort=proxy-port</jvm-options>
    <jvm-options>-Dhttp.nonProxyHosts="portalserver-host"</jvm-options>

    For Web Server 7.0, add this options to server.xml of the configuration in which portal is deployed. For IBM WebSphere, add this to the server.xml of the node in which portal is deployed. For WebLogic, add this to startWeblogic.sh/startManagedWeblogic.sh depending on whether the portal is to be installed on administrator server or managed server.

    Where, proxy-host is the fully qualified domain name of the proxy host, proxy-port is the port on which the proxy is run, and portalserver-host is the fully qualified domain name of the Portal Server software host.

  2. Execute the command prtconf | grep Memory to check RAM.

  3. Use the command swap -l to see how much swap space your machine has. To temporarily increase your swap space by 4 Gbytes, you can use the following instructions:

     mkfile 4g /swap-filename
     swap -a /swap-filename
    

where swap-filename is an empty file to be used as a swap area.