Before you can install IBM® WebSphere® Application Server products on Solaris operating systems, you must take steps to prepare the operating system.
The installation uses Installation Manager. You can use the graphical interface, the command line, or a response file.
If you want to install 32-bit WebSphere Application Server on a 64-bit operating system, you must install the appropriate 32-bit libraries on your system.
Preparing the operating system involves such changes as allocating disk space and installing patches to the operating system. IBM tests WebSphere Application Server products on each operating system platform. Such tests verify whether an operating system change is required for WebSphere Application Server products to run correctly. Without the required changes, WebSphere Application Server products do not run correctly.
You can log on as root or as a nonroot installer.
umask
umask 022
Export the location of the supported browser using a command that identifies the actual location of the browser.
export BROWSER=/opt/bin/firefox
Font changes occur when using the Hummingbird Exceed package and invoke the Profile Management Tool. When you use the Hummingbird Exceed package to connect to a machine running the Solaris operating system, and then invoke the Profile Management Tool, some font sizes and styles display differently than when doing the same operation from the native Solaris display.
The font sizes and style changes are based on the font selections in the bundled Java SE Runtime Environment 6 (JRE 6).
To prevent the various font changes, configure Hummingbird Exceed to disable Automatic Font Substitution:
The amount of disk space required varies with the number of features or products installed. If you are installing the product using Installation Manager, the installation summary panel indicates the approximate amount of disk space required based on the features and products you have selected.
Installing all features and products requires approximately 2 GB of disk space. This estimate includes the following products, components, and features:If you plan to migrate applications and the configuration from a previous version, verify that the application objects have enough disk space. As a rough guideline, plan for space equal to 110 percent of the size of the applications.
The instructions in this step apply to the Solaris SPARC (32-bit and 64-bit) operating system only. For Solaris x64 processor-based systems, see How to Get Started with IBM WebSphere Application Server on Solaris 10 and Zones. The article was written for Solaris 10 on SPARC but the principles apply equally to x64.
sysdef -i
The kernel values are set in the /etc/system file (for Solaris 8 or 9) or /etc/project file (for Solaris 10).
The resource controls are set in the /etc/system project file (for Solaris 10. Resource controls are new for Solaris 10 and are replacing the use of some kernel values. Resource controls do not apply to Solaris 8 or 9.
set shmsys:shminfo_shmmax = 4294967295 (a resource control in Solaris 10)
set shmsys:shminfo_shmseg = 1024 (obsolete in Solaris 9 and 10)
set shmsys:shminfo_shmmni = 1024 (obsolete in Solaris 9 and 10
set semsys:seminfo_semaem = 16384 (obsolete in Solaris 10)
set semsys:seminfo_semmni = 1024 (a resource control in Solaris 10)
set semsys:seminfo_semmap = 1026 (obsolete in Solaris 10)
set semsys:seminfo_semmns = 16384 (removed in Solaris 10)
set semsys:seminfo_semmsl = 100 (a resource control in Solaris 10)
set semsys:seminfo_semopm = 100 (a resource control in Solaris 10)
set semsys:seminfo_semmnu = 2048 (removed in Solaris 10)
set semsys:seminfo_semume = 256 (obsolete in Solaris 10)
set msgsys:msginfo_msgmap = 1026 (obsolete in Solaris 10)
set msgsys:msginfo_msgmax = 65535 (obsolete in Solaris 10)
set rlim_fd_cur=1024
Old Old New New
Resource control tunable default Max default
Value
---------------------- ------------- ------- --------- -----
process.max-msg-qbytes msginfo_msgmnb 4096 ULONG_MAX 65536
process.max-msg-messages msginfo_msgtql 40 UINT_MAX 8192
process.max-sem-ops seminfo_semopm 10 INT_MAX 512
process.max-sem-nsems seminfo_semmsl 25 SHRT_MAX 512
project.max-shm-memory shminfo_shmmax 0x800000 UINT64_MAX 1/4*
* (New default is 1/4 of physical memory)
project.max-shm-ids shminfo_shmmni 100 2**24 128
project.max-msg-ids msginfo_msgmni 50 2**24 128
project.max-sem-ids seminfo_semmni 10 2**24 128
Shared Memory Semaphores Message-Queue
-------------- -------------- ---------------
shminfo_shmseg seminfo_semmns msginfo_msgmax
shminfo_shmmin seminfo_semvmx msginfo_msgssz
shminfo_shmmax* seminfo_semmnu msginfo_msgmni*
shminfo_shmmni* seminfo_semaem msginfo_msgtql*
seminfo_semume msginfo_msgmnb*
seminfo_semusz msginfo_msgmap
seminfo_semmap msginfo_msgseg
seminfo_semmsl*
seminfo_semopm*
seminfo_semmni*
values ending in * are technically obsolete, but if they are present
in the /etc/system file then at system boot, the kernel will translate the
values into global resource controls.
*project.max-shm-ids: Maximum shared memory IDs for a project.
Replaces shmmni
*project.max-sem-ids: Maximum semaphore IDs for a project.
Replaces semmni
*project.max-msg-ids: Maximum message queue IDs for a project.
Replaces msgmni
*project.max-shm-memory: Total amount of shared memory allowed for a project.
Replaces shmmax
*process.max-sem-nsems: Maximum number of semaphores allowed persemaphore set.
Replaces semmsl
*process.max-sem-ops: Maximum number of semaphore operations allowed persemop.
Replaces semopm
*process.max-msg-qbytes: Maximum number of bytes of messages on a message queue.
Replaces msgmnb
*process.max-msg-messages: Maximum number of messages on a message queue.
Replaces msgtql
You can change kernel values by editing the /etc/system file (for Solaris 8 or 9) or /etc/project file (for Solaris 10) then rebooting the operating system. For more information about setting up the Solaris system, see the Sun Microsystems documentation. For example, the Solaris Tunable Parameters Reference Manual.
Although Installation Manager checks for prerequisite operating system patches, review the prerequisites on the Supported hardware and software website if you have not done so already. Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
java.io.IOException: Cannot run program "sh": error=12, Not enough space
at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
at java.lang.Runtime.exec(Runtime.java:593)
at java.lang.Runtime.exec(Runtime.java:466)
Free up additional memory on the machine and retry the
installation.which cp
If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in the app_server_root/java directory.
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, you can install the application server product successfully.
For example, you might have downloaded an installation image from Passport Advantage®, or you might have copied an installation image onto a backup disk. In either case, perform the following steps to verify that the disk contains a valid Java software development kit (SDK).
cd /JDK/jre.pak/repository/package.java.jre/java/jre/bin
./java -version
The command completes successfully with no errors when the SDK is intact.
This procedure results in preparing the operating system for installing the product.
After verifying prerequisites, verifying the product disk, and setting your installation goals, you can start installing. Use one of the following links to open the installation procedure that you require.
See Installing the product on distributed operating systems using the GUI.
See Installing the product on distributed operating systems using response files.
See Installing and removing features on distributed operating systems.