Oracle Weblogic Server 11gR1 (10.3.6) ZIP Distribution – Linux
- As root run the following to create the oracle user and orainstall group
groupadd orainstall useradd -g orainstall oracle
- Login as user oracle
- Make sure you got JAVA on your server
type the following to see what version you gotjava -version
You might just have the JRE versus the JDK which is what you want to run weblogic with. So if you don’t have it, get it!
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.htmlPut the file on your server (I put mines in /softwaretmp), and run the following to get that bad boy installed:mkdir -p /u01/jdk cd /u01/jdk tar -zxvf /softwaretmp/jdk-7u51-linux-i586.gz ln -s jdk1.7.0_51 jdk7
- create the MW_HOME and weblogic server directories
mkdir -p /u01/oracle/fmw/wlserver_10.3
- Now let’s download weblogic
Go to: http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html - Put the ZIP file in your weblogic server directory, which (if you’re following) is
/u01/oracle/fmw/wlserver_10.3
- Update the ~/.bash_profile (it’ll make things easier)
MW_HOME=/u01/oracle/fmw/wlserver_10.3; export MW_HOME JAVA_HOME=/u01/jdk/jdk7; export JAVA_HOME PATH=$JAVA_HOME/bin:$PATH; export PATH
- Make sure you pickup the environment variables in your session by sourcing the .bash_profile
cd ~ . ./.bash_profile
Now chiggity check it, if you run java -version it should pick up the JDK you installed (it’ll return the following):java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Client VM (build 24.51-b03, mixed mode)
- unzip the contents of the weblogic zip file
cd /u01/oracle/fmw/wlserver_10.3 unzip wls1036_dev.zip
- Run the configuration
./configure.sh
- Setup the WLS environment in the current shell
. $MW_HOME/wlserver/server/bin/setWLSEnv.sh
- Now lets Create the Weblogic Domain yaahhyuuhh!
create the domains directorymkdir -p /u01/oracle/wlsdomains
- Run the configuration wizard
cd /u01/oracle/fmw/wlserver_10.3/wlserver/common/bin ./config.sh
In the below image, I selected “Production Mode” – one thing I like about production mode is that you have to explicitly redeploy items rather than apps auto-redeploying as soon as you upload a new version. But you can also select Development Mode if you want the auto-deploy and other features of the Deployment Mode… up to you…
The image below shows “All Local Addresses” selected. I actually recommend using the FQDN of the machine you are dealing with so that things like IP changes don’t require you to change any configuration. Additionally, selecting “All Local Addresses” can mess you up if you have multiple IPs assigned to this machine and you need to use the ports you select on the different IPs. But for simplicity, I’m selecting “All Local Addresses”…
Note in the below image, you should be on the “Unix Machine” tab since we are on Linux
Assign the AdminServer and Managed Server to a machine, we’re only dealing with 1 machine so guess what – both just get assigned to the same machine
We’re almost done!
Tada! Finished creating the domain…
- Create the boot.properties file so that you won’t have to input the login you created in the configuration wizard every time you startup
cd /u01/oracle/wlsdomains/devnumbertwo_domain/ mkdir -p servers/AdminServer/security mkdir -p servers/managedServer_1/security vi servers/AdminServer/security/boot.properties vi servers/managedServer_1/security/boot.properties
Put the login you created in the configuration wizard into your boot.properties fileusername=weblogic password=password123
- Let’s Start the Weblogic Admin Server!
cd /u01/oracle/wlsdomains/devnumbertwo_domain/ ./startWebLogic.sh
it will ask you to .
When it’s started, it will show the following lines:<BEA-000365> <Server state changed to RUNNING> <BEA-000360> <Server started in RUNNING mode>
- Let’s Start the Managed Server
cd /u01/oracle/wlsdomains/devnumbertwo_domain/bin ./startManagedWebLogic.sh managedServer_1
same thing here, it will ask you to input the username and password you inputted into the configuration wizard.
When it’s started, it will show the following lines:<BEA-000365> <Server state changed to RUNNING> <BEA-000360> <Server started in RUNNING mode>
- You can also check that your Managed Server is running by Logging to the Weblogic Administration Consoleby going to
http://localhost:7001/console OR http://serverip:7001/console
on the left nav go to Servers –> on the main pane it should show your your servers and in the status it will say RUNNING
No comments:
Post a Comment