weblogic 11g system requirements

Oracle Weblogic Server

Weblogic 11g system requirements and planning Installation Of Oracle WebLogic Application Server

Choosing hardware:

Oracle WebLogic is certified for several different hardware architectures;

see the full list of certifications at:


– Minimum CPU required is 1 GHz, but that’s the absolute minimum. It is better to start from 2.5 GHz, with dual- or quad-core architecture. Intel and non-Intel processors are both supported.

– It depends on what you will run on top of your WebLogic, but a good start is 3GB, considering the number of simultaneous users, sessions, and in-memory programs.

– Storage refers to local hard disk or external storage. For just a WebLogic Server, installing 3 GB is enough, but be aware that normally you have to install additional software afterwards and configure your WebLogic domain. Consider around 7 to 11 GB, and then you’re on the safer side.

– Hardware or virtualized? Nowadays most companies use virtualization of hardware to reduce costs. Virtualization can be done on AIX (LPAR), Sun (LDOM), or VMware. For a long time, Oracle did not support virtualization, but now Oracle offers its own virtualization solutions, such as Oracle VM and Virtual Box.

Operating system

Oracle WebLogic is certified on various operating systems, such as:
• Linux versions, including as Redhat, Oracle Linux, and SLES
• Sun Solaris
• Windows 2000-2003-2008 Server, XP

For a complete list of certified operating systems, see the Certification Matrix at


If personally asked which OS to choose I would go for Redhat Enterprise Linux 5.x
Highly scalable and sustainable, we had one machine running very fine for over 2yrs without any restarts.

System and File system level requirements:

File limits should be set in /etc/security/limits.conf

# /etc/security/limits.conf
weblogic hard nofile 4096
weblogic soft nofile 4096

We had limits set to the maximum to avoid “too many open files” error but it depends on the IT policy to choose what as ulimit
file descriptor limits can be checked by “ulimit -aH” command.

[[email protected] ~]$ ulimit -aH
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 90112
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 90112
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
By default its 1024 but can be set higher, you can also temporarily set to higher value without changing the limits.conf by using the command ulimit -n number
but this will set only for that session, so its suggested to put the command in the script which starts the JVM.

On some Linux systems, the /tmp filesystem is of a very small size. If this is the case, ask your OS administrator to increase it or else choose your own directory. This can be accomplished by entering the following option on the command line, when you start the installation program:

Here, tmpdirpath is the full path of the directory that you want to designate as a temporary storage area for the installation program.

Choosing your installaer types:

Depending on your platform, you will have to choose the OS-specific package installer (.bin or .exe file) or a generic package installer (.jar file). For all 64-bit operating system versions, only a generic installer is available.
If asked which one to choose i would go for generic jar(Ex:wls1033_generic.jar) file installer as it fits to all OS where system specific JDk is installed.

JDK installation:

I usually prefer to use Sun JDk as all my applications are tested on Sun JDK but you can also run it on IBM JDk and Jrockit(preferred by Oracle in Production modes) if required.
Download binary file from Sun/Oracle download and install into a folder, jdk*.bin extracts to a folder name with the version of JDk.
Check the JDK version by cd to its bin folder and executing ./java -version

To set the Java environment login as the weblogic admin user which will be used to install weblogic app. server and do the following.

su - wladmin
vi ~/.profile
export JAVA_HOME=/u01/java/jdk1.6.0_18 
export JAVA_VENDOR=Sun
export CLASSPATH=$CLASSPATH:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/jre/lib/rt.jar
export PATH=$JAVA_HOME/bin:$PATH
ulimit -n 10000
ulimit -s 32768

***(Change path accordingly for all above instances)

For large processes using bigger stack size is good and it can be set by using ulimit -s number as given above.

STACK SIZE – Limits the amount of memory a process can allocate on the stack, as in the case of local variables in C, C++ and many other languages. Limiting the stack size stops runaway recursive function calls; however, it is possible to legitimately allocate large arrays of data on the stack without unreasonable recursion. Specified in kilobytes, in the bash shell, as found in Linux and many other systems.

Below is a sample architecture for weblogic environment which is production ready and secured.

Sample Weblogic Deployment Architecture

Now you are ready for Oracle Weblogic Installation.
Please go to this link for Weblogic Installation steps.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.