Software Requirements (Sun Java System Portal Server 7.2 Installation and Configuration Guide)

Sun Java System Portal Server 7.2 Installation and Configuration Guide

Software Requirements

Before you begin installing Portal Server 7.2, you need to have the following requirements:

You need to have Java SE^TM 5 or Java SE 6 Update 5 or above pre-installed, before installing Portal Server 7.2.

The installer checks for the available Java SE version and prompts you to install the required version.
If you are using Solaris 5.9, you need to download and install the following patches from http://www.sunsolve.sun.com/, before installing Portal Server 7.2.
- Patch id — 114677-05
- Patch id — 114678-05
Note –
The above patches are required for Solaris 5.9 version on SPARC and x86 systems. There is no need to install these patches, if you use Solaris 10 or Red Hat Enterprise Linux.
You need an installed web container. You can use Sun Java System Application Server 9.1 as the web container for installing Portal Server 7.2. The web container must be installed and running, before you run Portal Server 7.2 installer.

Note –
You can also use GlassFish^TM V2 as a web container only for evaluation purpose.

Note –
If you are using Application Server 9.1 as the web container, you can have the Application Server 9.1 installer install a JDK^TM for you. For GlassFish V2 installation, you must manually install a JDK. Moreover, the installed JDK has to be package based. Otherwise, the Common Agent Container will not start.
Portal Server 7.2 requires Sun Java System Access Manager 7.1 and Sun Java System Directory Server 6. These need to be pre-installed and running. It is recommended that these components are installed from the Java ES 5 Update 1 distribution.

Note –
If you are installing Portal Server 7.2 in a multi-node environment and using Directory Server 6.2, you must first upgrade to Directory Server 6.3 before installing Portal Server 7.2. For more information, refer the Portal Server 7.2 Bugs in this Release in Sun Java System Portal Server 7.2 Release Notes.
If you are using the Java ES 5 Update 1 installer, install Access Manager 7.1 and Directory Server 6 on Application Server 9.1 in the Configure Now mode. Whereas, if you are using the Java ES 5 installer, install Access Manager 7.1 and Directory Server 6 in the Configure Later mode on Application Server 9.1.

Note –
If you are using the Java ES 5 Update 1 installer with Portal Server 7.2 on a single machine, do the following:
1. Install Application Server 9.1.
  
  Note –
  If you are installing Portal Server 7.2 with GlassFish V2, then you should set the Master Password to match the Administrator Password, using the command asadmin change-master-password.
2. Start Application Server 9.1. The command to start Application Server 9.1 is /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
3. Invoke the Java ES 5 Update 1 installer and install Access Manager 7.1 and Directory Server 6 in the Configure Now mode.
4. Ensure that you select Application Server 9.1 instance in the Access Manager web container panel and provide appropriate values.
  
  Note –
  If you are running the Java ES 5 Update 1 installer in text mode, choose Option 2 (Application Server Enterprise Edition 8.2 Patch 2). Though it is mentioned as Application Server Enterprise Edition 8.2, the Java ES 5 Update 1 installer will pick the values of Application Server 9.1 that you have installed.
5. Ensure that the instance directory and DocRoot values are correct. The default values are /opt/SUNWappserver/appserver/domains/domain1 and /opt/SUNWappserver/appserver/domains/domain1/docroot.
6. Ensure that the administration port is correct. The default value is 4848.
7. Start Directory Server after the installation is complete. The command to start Directory Server is /opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1
8. Stop and restart Application Server 9.1 after the Access Manager configuration is complete. The command to start Application Server 9.1 is /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
Note –
If you are using Java ES 5 installer with Portal Server 7.2 on a single machine, do the following:
1. Invoke the Java ES 5 installer and install Directory Server 6 in the Configure Now mode. Do not select any of the shared components. Select the run time user for Directory Server as root.
2. Start Directory Server.
3. Install Access Manager 7.1 in the Configure Later mode.
4. Install Application Server 9.1.
5. Start Application Server 9.1. The command to start Application Server 9.1 is /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
6. Modify the /opt/SUNWam/bin/amsamplesilent file (Access Manager silent installation file) with appropriate values. Use Application Server 9.1 as the web container property value.
7. Run the ./amconfig -s amsamplesilent command to configure Access Manager.
8. Start Application Server 9.1 after the Access Manager configuration is complete.
  
  Note –
  You can also install Sun Java System Access Manager 7.1 in realm mode with Sun Java System Directory Server 6 as datastore.

Miscellaneous Checks

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 Application Server 9.1, 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>
```
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.
For Linux, you can check the memory and swap size form the meminfo file. Use the vi /proc/meminfo command to view the meminfo file.
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.
To increase the swap size on Linux, use the following instructions:
1. Create a swap file by using the mkswap /directory-name/swap-filename command.
  
  Note –
  You can create the swap file on any directory, where the disk space is available.
2. Mention the swap file name where you need to increase the swap size by using the swapon /directory-name/swap-filename command.
3. Increase the swap size by using the /directory-name/dd if=/dev/zero of=/directory-name/swap-filename bs=1024 count=x command.
  
  where x is a variable that depends on the amount of swap you need to increase. The variable can be in the multiples of blocksize (bs), which is 1024.
4. Remove the swap file by using the rm —rf /directory-name/swap-filename, since the swap file consumes huge disk space.
5. The amconfig script and other configure later utilities, require the JDK to be installed and linked to /usr/jdk/entsys-j2se. This looks like the following:
  
  lrwxrwxrwx 1 root root 27 Jan 17 09:28 entsys-j2se -> /usr/jdk/instances/jdk1.5.0