Before you install components, use the steps in this section to make sure the system on which you are installing is ready.
The performance of your messaging server depends on many factors, including CPU power, available memory, disk space, file system performance, usage patterns, network bandwidth, and so on. For example, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.
Make sure you are the root user for the system.
Have at least 2.2 GB free disk space for the unzipped image.
Have the image already unzipped.
Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
domain comms.beta.com nameserver 192.168.100.22 nameserver 192.168.100.23 nameserver 192.168.100.24 nameserver 192.168.100.25
Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
10.1.82.52 wireless.comms.beta.com wireless loghost
Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:
hosts: files dns nis [NOTFOUND=return]
Or, if NIS is not used:
hosts: files dns
On Solaris 10 platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file.
Otherwise, you'll get an error indicating that your host name is not a fully qualified domain name (FQDN).