WebLogic software will be
installed on a Linux Box, running under Oracle Enterprise Linux-6.
Step1 [optional]: Create new UNIX group
and user
Altough WebLogic software
could be installed as "root" on a UNIX machine, creating a new group and
user which will serve as WebLogic Administrator will make the administration
tasks easier. Therefore we will start by creating a new group and user on UNIX.
Connect as "root" (or as another
administrator) user and first create "weblogic"
gorup.
[admin@zeus ~]$ sudo groupadd weblogic
Verify if the group "weblogic" has been
created.
[admin@zeus tmp]$ grep weblogic /etc/group
weblogic:x:503:
Next, create "weblogic" user
[admin@zeus ~]$ sudo useradd weblogic
Verify if the user "weblogic" has been created
[admin@zeus tmp]$ grep weblogic /etc/passwd
weblogic:x:502:503:Weblogic Admin
user:/home/weblogic:/bin/bash
Disconnect from "admin"
[admin@zeus ~]$ ^d
Step2 [optional]: install JRockit-JDK
Normally JDK has already
been installed with the first OS installaion as shown below.
[admin@zeus ~]$ java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.7)
(rhel-1.39.1.9.7.el6-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed
mode)
However, based on the
requirements submitted by the development team, JRockit is the perferred JDK to
be used with Weblogic server. Therefore, JRockit will also be installed as
"weblogic" user.
Connect as "weblogic" user and perform
installation of JRockit JDK.
[weblogic@zeus ~]$ ./jrockit-jdk1.6.0_29-R28.2.0-4.1.0-linux-x64.bin
To install JRockit, accept all the default options and press "Next" button until the installation is complete.
Verify the installation
of JRockit
[weblogic@zeus ~]$ $HOME/jrockit-jdk1.6.0_29-R28.2.0-4.1.0/bin/java
-version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build
1.6.0_29-b11)
Oracle JRockit(R) (build
R28.2.0-79-146777-1.6.0_29-20111005-1807-linux-x86_64
Step3: Adjust
your Java environment settings
Set the new JRockit environment
to be the default home for Java
[weblogic@zeus ~]$ vi .bashrc
export
JAVA_HOME="/home/weblogic/jrockit-jdk1.6.0_29-R28.2.0-4.1.0"
PATH=$JAVA_HOME/bin:$PATH
:wq
Activate the new environment settings
[weblogic@zeus ~]$ . .bashrc
Verify the new settings
[weblogic@zeus ~]$ echo $JAVA_HOME
/home/weblogic/jrockit-jdk1.6.0_29-R28.2.0-4.1.0
[weblogic@zeus ~]$ echo $PATH | tr ':' '\n'
Step4 [optional]: Perform installation
of Java ADF Libraries
Java ADF libraries will
aslo be installed based on another requirement submitted by development team:
[weblogic@zeus ~]$ java -jar jdevstudio11114install.jar
Step5: Perform installation of WebLogic
server software
[weblogic@zeus ~]$ java -jar wls1034_generic.jar
Select "Use an existing Oracle
Middleware Home" option to select Oracle Middleware directory, which has
already been created in the previous step when installing Java ADF Libraries.
Do not enter anything for "Register
for Security Updates" section.
Choose the JRockit as JDK that we
previously installed.
Choose the directories that we already
created in the previous steps.
Step6: Create a Weblogic domain
At this stage, after the
installation of WebLogic server software above, we need to create a WebLogic
domain, which is made up of at least one Administration Console and one or more
Managed Servers.
[weblogic@zeus ~]$
./Oracle/Middleware/wlserver_10.3/common/bin/config.sh
Accept the default
options in the first step as shown in the followin screenshot.
Press Next button to create a new domain.
Select either "Development Mode"
or "Production Mode" for server start mode based on your own
requirements. If you select "Development Mode", weblogic does not
require you to provide any user/password at startup. However, if you choose
"Production Mode" then you will have to provide a valid user/password
in a configuration file (boot.properties) when you want to start a WebLogic
server.
Create one "Administration
Server" and one or more "Managed Server" for the domain.
Administration server will be used to manage the managed (start/stop/modify
etc.) servers. Managed servers will be used to deploy the applications.
Accept the default options and press Next
button.
In "Configure Managed Servers"
screen, press on the "Add" button to add a new managed server and
enter name, address and listening port properties.
Press "Next" button in
"Configure Clusters" screen as we do need to have any clusters in our
domain.
Configure a machine to create a Node
Manager, which is a WebLogic component that allows us to administer
"Administration Console" and "Managed Servers" remotely.
Press "->" button to assign
servers displayed on the left pane to the machine on the right.
Verify the configuration summary and then
press "Create" button.
Step7: Start Node Manager and Administration
Console
In order to user
WewbLogic services we need to start "Node Manager" and then
"Administration Console". "Managed Server" will then be
started using "Administration Console".
Start Node Manager first:
[weblogic@zeus ~]$ cd ./Oracle/Middleware/wlserver_10.3/server/bin
[weblogic@zeus ~]$ nohup ./startNodeManager.sh
&
Start WebLogic
Administration Console afterwards:
[weblogic@zeus ~]$ cd ./Oracle/Middleware/user_projects/domains/MTS_DEMO/bin
[weblogic@zeus ~]$ nohup startWebLogic.sh &
Note: There are more than
one way to start "Admnistratin Console" and "Managed
Server". Refer to WebLogic documents for all the possible ways to
start/stop WebLogic services.
Değerli Hüseyin Özpay'a yardımları konusunda teşekkürler.
