weblogic server (wls) 12c (release 12.1.1) on rhel 5 update 3 · 2013-05-14 · weblogic server...

WebLogic Server (WLS) 12c (Release 12.1.1) on RHEL 5 Update 3

Software – Following software are needed for WebLogic Server (WLS) 12c (Release 12.1.1) on RHEL 5

Update 3.

1. WebLogic Server 12c Release 12.1.1 – Generic Installer

a. http://www.oracle.com/technetwork/middleware/fusion-

middleware/downloads/index.html

i. ii. Login to Oracle E-delivery Cloud

iii. iv. Click on Oracle WLS 12C Media pack

v. 2. JDK (User here is 7u2 Linux64 RPM) – Download it from

a. http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-

1880260.html

Server Set up

• Make sure the ‘/etc/hosts’ file contains the correct entries for local and actual hostname

o

Installation Process

• Install JDK – Login to server as ‘root’ and install the RPM

• User and Group creation

o I created a group called ‘oinstall’

o And added a user ‘wlace’ into that group

• Middleware Home

o There was FS already created - /d01/wlace

o Hence Middleware Home Directory is created inside that -

/d01/wlace/oracle/middleware

• Permission

o Changed the owner of that Middleware Home to that of ‘wlace’

• Login as ‘wlace’ and add following entries to the ‘.bash_profile’ file

o

• Setting up VNC for display

o Login as ‘root’ and issue the command ‘service vncserver start’

o Set the password – Not this password for further reference

• Login as ‘wlace’ – start the VNC. Supply the same password as noted earlier

• Check DISPLAY if properly set – Running ‘xclock’ command (if successful, you will see a Clock

displayed on the VNC on your local desktop)

o I got an error while checking DISPLAY

� This error was due to the fact that my ‘loopback’ address in /etc/hosts file was

not correct. It was still showing “localhost.localdomain localhost”

� Error was resolved by updating the actual hostname against this loopback IP –

127.0.0.1

To Resolve - /etc/hosts file need to be updated for loop back address

After

• Once the DISPLAY is properly set, go to $JAVA_HOME/bin and launch the installer (Using ‘wlace’

user)

o java -Xmx1024m -jar /d01/wlace/software/wls1211_generic.jar � “/d01/wlace/software” is the location where the WLS binaries are downloaded

and kept

• Click on “Getting Started with WLS 12.1.1

Here we have to create “Managed Server” as well. This is used for the application to be deployed.

Normally, port selected is – 7003 (default). 7002 port is not selected as it is SSL port for Admin Server

Pls check if Admin Server is up and running. If not, this needs to be started.

How to check

• $ ps –ef|grep java

o

How to start Admin Server

• $ cd /d01/wlace/oracle/middleware/user_projects/domains/<DOMAIN_NAME>/bin

• $ nohup ./ startWebLogic.sh &

How to start Managed Server

• Check if boot.properties file exist in the location -

/d01/wlace/oracle/middleware/user_projects/domains/wlacedev/servers/ManagedServer1/

security

• If there is no ‘security’ folder inside ‘ManagerServer’ directory, create one

And

Copy the “boot.properties”

From below location

/d01/wlace/oracle/middleware/user_projects/domains/wlacedev/servers/AdminServer/securit

y/

To newly created ‘Security’ folder inside ‘ManagedServer’

• Now start the Manager Server - nohup ./startManagedWebLogic.sh ManagedServer1 http://adc-al-

lnx50:7001 &

• Now to check if ManagedServer is up and running o $ ps –ef|grep java � this will show both Admin and MS are up and running

o

Due to the missing ‘boot.properties’ file, MS was not coming up and log was showing below error.

After following the above mentioned approach, MS came up w/o any issue.