Welcome to www.freeoraclehelp.com Got questions? Post comments Like the facebook page to get instant updates. Thank you!!!
Total Pageviews
Search this blog

Oracle WebLogic Server 11g R1 10.3.5 Installation

Step by Step instructions to download, install Oracle WebLogic Server 11gR1 10.3.5, and create a sample domain are described in this article. Well, What is WebLogic? WebLogic Server is a powerful Application Server to run J2EE Applications. This is pretty much equivalent to Oracle 10gAS OC4J server, but WebLogic is known for its rich features and great functionality. Since Oracle has acquired BEA, there has been a strategic shift in the Application Server technologies from OC4J to Weblogic Server. Oracle has moved most of the OC4J Applications to Weblogic in Fusion Middleware releases. If you see the tag, Fusion, you can guess that it is Weblogic Application. Other than directory structures, installation procedure, here are few key differences between OC4J and WebLogic Server.

OC4J uses AJP protocol between OHS and OC4J. OHS in front of OC4J is a must (as OC4J itself does not have a HTTP listener, so it cannot answer HTTP requests). This is quite different in WebLogic, as WebLogic has got a HTTP listener, users can directly access WebLogic port from the browser. Of course, it is recommended to front end WebLogic by a web server but it is not mandatory. Web Server is mandatory for OC4J.

OC4J is completely managed by OPMN. A couple of interesting features by OPMN, such as increasing no# of JVMs (numprocs in opmn.xml) for the OC4J are available. WebLogic is not managed by OPMN. So, WebLogic always runs out of only one JVM.

OC4J runs on wide range of ports whereas WebLogic runs everything on a single port by default, i.e. 7001. Here is an example of OC4J Port ranges:

ajp range=12501-12600
rmi range=12401-12500
jms range=12601-12700

Here is a quick installation of 10.3.5 WebLogic Server. I would create a quick Domain to demonstrate the config.sh:

  1. Download Weblogic
  2. Preinstall tasks
  3. Installation
  4. Post Installation
  5. Troubleshooting

Download Weblogic

Download Oracle WebLogic Server: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
Download 64bit JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u29-download-513648.html

wls1035_generic.jar: This is a generic file that can be used on any platform. It includes WebLogic Server and Coherence but NOT JDK. In most of the 64bit WebLogic Installations, I had to use this one instead of direct executable.

wls1035_linux32.bin: Linux x86 32-bit executable. It includes WebLogic Server, Coherence, Sun SDK 1.6.0, and Oracle JRockit 1.6.0.

wls1035_linux64.bin: Linux x86 64-bit executable, it includes WebLogic Server, Coherence, and Oracle JRockit 1.6.0. If you prefer to use Sun JDK for development servers, you got to install JDK first and then run wls1035_generic.jar instead.

If it’s a executable, you can simply execute as:

$ ./wls1035_linux32.bin 

But if you need to run with different JDK, run:

$JAVA_HOME/bin/java -jar wls1035_generic.jar

There is no straight 64bit JDK on HP-PA, HPIA, and Solaris64 platforms and rather it’s a Hybrid JDK. In this case:

$JAVA_HOME/bin/java -d64 -jar wls1035_generic.jar

Preinstall tasks

We need to make a choice for JRockit or Sun JDK. JRockit is more meant to be for Production usage. It takes longer to start, needs more memory and runs faster during the runtime. Sun JDK starts faster, needs less memory heap, and is little slow during the run time. If you have a cap on Memory, better go with Sun JDK. I would prefer Sun JDK in non-production environments. I have already installed 64bit JDK on this Linux Server and called wls1035_generic.jar. Coherence is another new component that is supposed to speed things up using the cache. It’s an optional component.

Here are basic requirements to install the WebLogic Server.

  • Processor: 1-GHz CPU
  • Memory : A minimum of 1 GB RAM, although recommends 2 GB is recommended.
  • Lot of temp space is required as the installer extracts first and then starts the installation.
  • JDK is shipped with a few 32bit WebLogic installers but we have to manually install the JDK for 64bit.


Oracle Weblogic 10.3.5 Installation 001

Oracle Weblogic 10.3.5 Installation 002

Oracle Weblogic 10.3.5 Installation 003

Oracle Weblogic 10.3.5 Installation 004

Oracle Weblogic 10.3.5 Installation 005

Oracle Weblogic 10.3.5 Installation 006

Oracle Weblogic 10.3.5 Installation 007

Oracle Weblogic 10.3.5 Installation 008

Oracle Weblogic 10.3.5 Installation 009

Oracle Weblogic 10.3.5 Installation 010

Oracle Weblogic 10.3.5 Installation 011

Post Installation

Create a new WebLogic domain using the Configuration Wizard:

$ /oracle/middleware/oracle_common/common/bin/config.sh 

Oracle WebLogic 10.3.5 Create Domain 078 

Oracle WebLogic 10.3.5 Create Domain 079 

Oracle WebLogic 10.3.5 Create Domain 080 

Oracle WebLogic 10.3.5 Create Domain 081 

Oracle WebLogic 10.3.5 Create Domain 082

Development Mode: Weblogic User and passwords are stored in boot.properties in Development Mode. Again, I have selected SUN JDK for Development mode.
Production Mode: It does not store the user name and passwords in boot.properties by default. You can manually create boot.properties after the Domain Creation.  You may want to select JRockit for Production. The user name and password will be read and encrypted by WebLogic Server during the startup.

$ cat /oracle/middleware/user_projects/domains/IDMDomain/servers/AdminServer/security/boot.properties 
Oracle WebLogic 10.3.5 Create Domain 083

Oracle WebLogic 10.3.5 Create Domain 084
This is a place to change the default Admin Server Port from 7001 to something else. If you have got multiple domains, you would need to change this port for all domains after the first domain. Unlike Oracle Installers, Configuration Wizard does not check for the Active Port. So we got to check that ourselves.
Oracle WebLogic 10.3.5 Create Domain 087

Oracle WebLogic 10.3.5 Create Domain 088

Oracle WebLogic 10.3.5 Create Domain 089

Oracle WebLogic 10.3.5 Create Domain 090

Oracle WebLogic 10.3.5 Create Domain 091

Oracle WebLogic 10.3.5 Create Domain 092 
Config.sh does not start the services. Start the Admin Server manually.
$ /oracle/middleware/user_projects/domains/IDMDomain/bin/startWebLogic.sh 


Problem: WebLogic server does not start as the port is occupied by other WebLogic Server.

Solution: If you did not change the port during the installation, there is a way to change the port from Admin Console. However, this does not even start the server to go to the Console. So, we need to change $DOMAIN_NAME/config/config.xml

. /oracle/middleware/user_projects/domains/IDMDomain/bin/setDomainEnv.sh 

setDomainEnv.sh sets up all the environment variables and Java options for the entire domain including AdminServer and all Managed Servers. If you need to change JVM Heap Size,  setDomainEnv.sh is the right place for you.

Related Posts


Anonymous said...

Hey Raj

Good article on differences between OC4J and WebLogic Server we are looking forward more on Domains , clustered managed servers.

your articles on RAC are easy to digest
" you rock "

Anonymous said...

Hello Raj,
I wonder how can I find out what size binary 32 or 64 bit WLS installed in a MW HOME? from which conf files ? I am new to a site and found no doc on that. I can tell the domain uses the 64 bit java and wls is 10.3.5. But cannot find what bit of WLS.


yakub pasha said...

Hi Sean,
please look into to below steps.You will find whether WLS is installed 32 bit or 64 bit.

# set the environment by using setWLSEnv.sh (located in the ${WL_HOME}/server/bin directory).
# start WLST by using: java weblogic.WLST

# connect to the adminserver

# change to the serverruntime environment

# show the attributes
# Here an attribute is shown called WebLogicVersion that shows the version of WebLogic
-r-- WeblogicVersion WebLogic Server Fri Apr 1 20:20:06 PDT 2011 1398638
# Note that this does not show if is 32 bits or 64 bits to retrieve this information you have obtain the JVM version

# change the directory

# show the attributes

-r-- Version R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64
# when you have something like x86 at the you are running a 32 bit version, if you have something like x86_64 you are running a 64 bits version


Raj Mareddi said...


I believe WebLogic is built on a generic jar files that can be run on either 32bit or 64bit JVMs out of either Sun JDK or WebLogic JRockit or IBM JDK.

However, some installation package included JDK and WebLogic and its got Bit version as JDK has bit version. but there are generic Weblogic dumps ( for ex: wls1035_generic.jar). This generic version can be run by any JDK of customer's interest.

Raj Mareddi

Anonymous said...

I cannot get that:
wls:/oim_domain/serverRuntime/JVMRuntime/AdminServer> ls();

-r-- HeapFreeCurrent 447741456
-r-- HeapFreePercent 78
-r-- HeapSizeCurrent 778502144
-r-- HeapSizeMax 1556938752
-r-- JavaVMVendor Sun Microsystems Inc.
-r-- JavaVendor Sun Microsystems Inc.
-r-- JavaVersion 1.6.0_30
-r-- Name AdminServer
-r-- OSName Linux
-r-- OSVersion 2.6.32-200.13.1.el5uek
-r-- Type JVMRuntime
-r-- Uptime 18281058

-r-x preDeregister Void :



yakub pasha said...

Hi Sean

WebLogic runs in 32 bit or 64 bit mode depending on the JVM in which WebLogic runs. A few native files are operating system
specific and are used by WebLogic to interact with the operating system such as IO etcetera. These files are located in the
${WL_HOME}/server/native directory. The native files are selected by the file commEnv.sh (${WL_HOME}/common/bin)
based on operating system specific commands. For example, when using Linux the script will use 'uname -m' to retrieve
if the operating system is x86_64.

When you know the version in which the JVM runs (java -version) and the operating system (uname -m) you can
say how WebLogic is running in either 32 or 64 bit mode.


Anonymous said...

Hi Raj,

Very nice article.

i have installed oracle weblogic 11gR1. I could open the console, but unable to open the wliconsole to configure xmlcache, event generators, etc.

I was working on weblogic 8.1 and trying to map to 11g.

can you please help on this?


Raj Mareddi said...


I guess you need to configure xmlcache from EM Console now, I guess.

For example: http://myserver:7001/em if your console URL is http://myserver:7001/console

Raj Mareddi

Anonymous said...

Hi Raj

Thanks for the article. Well documented.

In the former Oracle Application Server (OAS), an Oracle metadata db is required when OAS is installed. Does WebLogic 10.3.5 require a metadata db as well?


Raj Mareddi said...


No, WebLogic 10.3.5 does not require a metadata database repository(RDBMS database). Again, WebLogic simply replaces Oracle J2EE Server (OC4J).

~Raj Mareddi

Anonymous said...

An easy-to-digest document for WebLogic installation that i've ever found. Thanks for your contribution to help the dummy world.

karthickkathiravan said...

I have installed weblogic server, after installing i am not able to find "oracle_common" direoctory like this below

I am have directory like below

not getting source domain
oracle enterprise manager
oracle JRF

Thanks & Regards
Karthick K

Raj Mareddi said...


config.sh can be located here as well: $MW_HOME/wlserver_10.3/common/bin/config.sh

Anonymous said...

Hi Raj,

Thanks for reply,

I got $WEBLOGIC_HOME/oracle_common directory after installing OID software then i have executed config.sh file from
$WEBLOGIC_HOME/oracle_common/common/bin/config.sh after that i got "oracle enterprise manager" "oracle JRF" source domains

Anonymous said...

Hi Raj
can you please tell licensing requirements for a production environment? Is it based on number of CPU/cores etc?

Ravi Kumar said...

I am using wls 10.3.0 running with sun jdk 1.5 ,
I am planing to run my wls with sun JDK 1.6 what are required changes at wls, Please suugest for the same.

BHRT JSWL said...

can we do EJB3.0 unit testing since embedded container is not provided by weblogic 10.3.5

Post a Comment