This section contains the requirements for installing Sun Java System Portal Server 7.1.
The installation instructions are specific to the Solaris platform. Refer to the Installation guide for Windows if you are installing Portal Server on the Windows.
The following table lists hardware and operating system requirements:
Table 1–1 Hardware and Operating System Requirements
Component |
Platform Requirement |
---|---|
Supported platforms |
Sun BladeTM or comparable workstation or server |
Operating system |
SolarisTM 9 or Solaris 10 on SPARC Solaris 9 or Solaris 10 on x86 Red Hat Enterprise Linux 3.0 Update 3 or 4.0 on x86 Windows Note: Portal Server 7.1 on Windows can only be used as a developer platform or an evaluation platform. It can not be used as a deployment platform. |
RAM |
1.5 Gbytes for regular deployment on Sun Java System Web Server 2.0 Gbytes for regular deployment on Sun Java System Application Server |
Disk space |
1 Gbyte for Portal Server and associated applications |
Swap space |
Twice the amount of physical memory, for example, 2.0 Gbytes RAM and 4.0 Gbytes swap space. |
Remove the link /usr/share/bdb/db.jar before installation, if it exists.
Check ant already exists on the system by running the following command:
rpm -qa | grep ant
If a version of ant below 1.6 is installed, remove it by running the following command:
rpm -e ant-older-version ant-libs-older-version
You need to use the version of ant sun-ant-1.6.5-2 to install or deploy Portal Server. When you run the installer, it is automatically installed at /opt/sun/bin/ant.
Portal Server requires the following stack components:
Sun Java System Directory Server 6
Sun Java System Access Manager 7 installed in legacy mode not in realm mode.
Portal Server requires Access Manager, Directory Server, and a web container for its installation and configuration. If you are performing a fresh install, Access Manager and Directory Server do not have to be installed before Portal Server is installed. Access Manager, Directory Server, and Portal Server can be installed at the same time. If Access Manager and Directory Server are installed already, point the Portal Server installation and configuration to the existing Directory Server and Access Manager servers.
Sun Java System Web Server 6.x or Sun Java System Application Server 8.x.
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.
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.
Execute the command prtconf | grep Memory to check RAM.
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.