weblogic 11g admin

Introduction
Installation of weblogic 11g
Creation and configuration of Admin server with three managed server
Creation of And Configuring Machines in Weblogic Server
Administering Managed Server With Node Manager

Introduction

What is Oracle Weblogic 11g ?

Oracle WebLogic Server 11g is a component of Oracle Fusion Middleware 11g,

which consists of several Oracle products that span

o business intelligence,
o collaboration tools,
o content management,
o and integration services.

The underlying application server supporting these middleware applications

is Oracle WebLogic Server 11g.

Products such as Oracle SOA Suite and Oracle Fusion applications

rely on Oracle WebLogic Server 11g to run their code

3 products as part of the Oracle WebLogic Server 11g family:

Oracle WebLogic Server Standard Edition (SE)

full-featured server, but is mainly intended for developers

to develop enterprise applications quickly.

 WebLogic Server SE implements all the Java EE standards

and offers management capabilities through the Administration Console.

Oracle WebLogic Server Enterprise Edition (EE)

Oracle WebLogic Server EE is designed for mission-critical

applications that require high availability and

advanced diagnostic capabilities.

EE version=SE version+ clustering +various diagnostic tools.

Oracle WebLogic Suite

Oracle WebLogic Suite offers support for dynamic

scale-out applications with features such as

Oracle WebLogic Suite=EE version +

in-memory data grid technology + comprehensive management capabilities.

It consists of the following components

Oracle WebLogic Server EE

Oracle Coherence (provides in-memory caching)
Oracle Top Link (provides persistence functionality)
Oracle JRockit (for low-latency, high-throughput transactions)

Now lets discuss some common termnologies relation to oracle weblogic

WL server
Admin server
Managed Server
Cluster
what is Weblogic Server means?

Note that Weblogic server and Weblogic Server instance is one and the same thing !

WebLogic Server Instance

It is JVM process that runs the Java code.

The instance is the actively working component, receiving client

requests and sending them on to the appropriate components,

and sending the processed requests back to the originating clients.

The server instance manages the resources necessary for applications,

such as the JTA and JDBC services, to function.

In each domain, one instance serves as the Administration Server, which

is your primary means of managing the domain.

The rest of the WebLogic Server instances are called Managed Servers.

If you have a domain with just one WebLogic Server instance,

as is the common case in a development environment,

the single server instance functions as both the managed server and admin server

WebLogic Server Domain

A WL server domain is a set of WebLogic Server instances

that you manage with the Administration Server (Also an WL instance)

Why to create an domain?

Ease of admin

Configuration done on domain applied on each managed server ...no need to

configure managed server separatly...

Each domain has one and only one Admin Server which is

used to configure all the managed server

A domain lets you easily deploy applications across multiple WebLogic

Server instances located on heterogeneous servers and multiple networks,

with varying physical and network descriptions.

Administering a domain makes it easy for you to configure

high availability with the help of multiple WebLogic Server

instances and administer various services spread across heterogeneous host servers

What domain includes?

1 admin server

N managed server

Application components that we deploy

Services required by the all managed server

Domain=1 Admin server

N managed servers(including those configured into WebLogic clusters)

machines (servers)

and all the services necessary to run your applications.

How Admin and Managed server related?

Each Managed Server has local copy of its domain configuration.

Upon startup, it synchronizes its configuration with the Admin Server.

Similarly, when you make domain configuration changes on the Admin Server,

those changes are propagated to the Managed Servers configuration.

Administration Server

Remember server is an instace of WL server that run in its own JVM

Now Admin server is an special instance of WebLogic Server designed

for managing the domain rather than running applications.

There is a one-to-one relationship between domains and the Admin Server

an Admin Server belonging to Domain A cant manage Domain B managed server

Not WE CAN DEPLOY USE APPLICATION ON ADMIN SERVER

IT MUST BE AVOIDED ON PRODUCTION SYSTEM ENVIRONMENT

OK FOR DEVELOPMENT ENVERIONMENT

What is admin consol?

The Admin Server hosts the Administration Console,

which is a web application front end used for configuring, monitoring,

and managing a domain.

You can access the Administration Console with any

supported browser that can access the Admin Server.

All WebLogic system administration tools and

APIs interact with the Admin Server.

Managed Server

A Managed Server hosts your Java EE applications, as well as all related

resources and services such as Java Database Connectivity (JDBC)

connection pools and data sources, Java Transaction API (JTA)

transaction services, and Java Messaging Service (JMS) connection

factories that are necessary to support application deployments.

 *Any additional servers you create after

the creation of the default Admin Server are Managed Servers.

*The Managed Server contacts the Admin Server, only when you start it up,

to get the configuration and deployment settings.

thats why we should always start up the Admin Server

before you start a Managed Server.

Once a Managed Server starts running, it operates

completely independent of the Admin Server.

Note:

In Managed Server Independence (MSI) mode we can

even run an Managed server without starting admin server

WebLogic Server Cluster ?

first need to understand clustering?

WL server cluster?

group of WebLogic Server instances consisting of multiple

Managed Servers that run simultaneously with

same configuration and same application is deployed?

clustered application response to http server through a load balancer

 Load balancer?

third party plugin...

Why?

To increase reliability and scalability through load distribution and high availability.

The load balancer handles the HTTP requests after the requests

pass through a firewall.

Cluster members pass replicated copies of objects such as HTTP

sessions among themselves to provide the failover capability for the cluster.

Each domain consist of own set of resources such as jdbc ,jta, jms that is

not shared among other domains.......

Node Manager?

The Node Manager is an optional process that runs

on a machine and manages the availability of all servers

that run on that machine.

Node Managers help you remotely start, stop,

suspend, and restart Managed Servers.

Machine?

PC

What is the context of machine in world of WL server?

A machine is logical representation of the computer that hosts

one or more WebLogic Server instances (servers).

A machine could be a physical or virtual server

that hosts an Admin or Managed Server that belongs to a domain.

We must define a machine first if you want the Admin Server to

use the Node Manager service to monitor, start,

and stop the Managed Servers running on a server.

In a sense, a machine in a WebLogic Server environment is more or

less equivalent to an instance of a Node Manager

and this is essentially the concept that a machine represents.

WebLogic clusters make use of the machines you define in

order to decide the optimal way to replicate session data on

a different server that is part of a cluster.

Installation of WL 11g

Installation options

1. graphical mode

which is an interactive mode.

2. The console mode

interactive mode, but is run from the command line.

3. The silent mode

noninteractive mode of installation,

where you can use a script or a text file

when you need to install WebLogic Server on many hosts.

We choose option 1 ie. graphical option simple...

*Download Oracle WebLogic Server 11gR1 (10.3.4) + Coherence + OEPE - Package Installer

from oracle site.

Zip installation (small size) but only for development purpose

Need jrocket jdk seperatly

need Derby seperatly

*Double click

*Welcome screen =====> choose middleware directory(keep default)

====>disable registration

======>installation type custom (we want sample example)

 ======>check Server Example from the list

next...next ...next ...

Don't Run Quickstart check Now..

Exploring what has been installed?

*********************************
Exploring the Installation Directories

********************************************
Exploring WebLogic Server Home directory
WebLogic Server Domain Directory

Oracle recommends that you start working with the wl_server domain to
understand the basics of Java EE programming and Oracle WebLogic Server.

its a good idea to check out the Avitek Medical Records and the
Avitek Medical Records (Spring) sample applications.
Both of these present you a realistic example of how to develop
and deploy full-blown Java EE applications.

The two applications also serve as great learning tools for

Java EE developers as well as for WebLogic Server administrators
who wish to understand application deployment concepts

Now starting example server ie admin server for wl_server domain

it start server and dbderby database in seperate console...

check admin console.....

login with UserName: weblogic
Password: welcome1

Stopping admin server

click stopWeblogic.cmd......
Navigating the Administration Console
open weblogic server admin again...
How?
click startweblogic.cmd....
then login..

Now focus highlighted area...

click server to see confugred server, at this moment only one ie exampleServer(admin)
creating /deleting WL server domain

creating wl server domain

We are going to create one admin server and two managed server

1 admin server

N managed server

go to C:\Oracle\Middleware\wlserver_10.3\common\bin

that contain tools/script to create domain

run config.exe

config wizard pops up...

click next...
choose next...

select an suitable domain name and next....

provide name and password
eg name: weblogic
password: welcome1

click next.......

choose production mode....

Say next.....
click ok...it will create domain.
check directory structure where it create domain.

click start WebLogic.cmd

console start up ..provide un and pw used during installation
http://localhost:7001/console/login/LoginForm.jsp

login screen open ..provide un and pw again.

Now how to delete WL domain
--------------------------------------
Just delete directory where it is installed, no need to uninstalled it.

Also change:
One configuration file where i need to delete entery for WL domain

we just need to delete entry form nodemanager.domains

and that's all domain is deleted...

Now we have two managed server ie rg_ms1 and rg_ms2

lets now configure them

managed server actually host jee applications, ws, have confugraiton of jdbc,jms and jta
resources...while admin conf for management only.

Now under rg_domain i am going to configuration of managed server ie rg_ms1 and rg_ms2
different way to configure managed server in WL
Go to home page--->

Now we can set configuration setting for rg_ms1

click lock and edit button, we obtain an lock on the editiable connection of mbean.
changes donot effect immedetly ...
Now do some R&D lets say changing SSL listnen port to 7004, click save.

Do same with rg_ms2

We can also create managed server now

lets say rg_ms3...do same with it...
now click view changes and restart for summery of changes done...
then activate all changes if all is ok

May /May not need to restart server...

How to manages machine in domain?

Now we have one admin server rg_domain
and three managed server rg_ms1,rg_ms2 and rg_ms3
What is machine?
computer that host wl server instance.

Why we must have configuration of machine?

To understand it lets consider following diagram:

As shown in fig we have configure an domain on two machine(two physical machines)

with one admin server and three managed server in an cluster
now if serverA is down then due to machine failure then it is sure that serverB would also be
down
so if serverC is not configred on seperate machine how we ensure avability of application to
our client?

Session migration form serverA to serverB is useless in case of machine1 failure....

What is WL sever...nothing but JVM process running in our system.

Now lets see how to configure machine on WL server

go to home===>choose machine from left pan======>

Now create new machines

create another machine rg_mach2

Now we have created two machines rg_mach1 and rg_mach2

Now we need to configruation of these machines

=========================================
Now we want to assigned managed server lets say rg_ms1 to rg_mach1 and rg_ms2 and
mg_ms3 to rg_mach2

Now start configuration for rg_mach1

Assigning servers to this machine.....click srevers

assigned rg_ms1 to machine1 as planned.

click finished.

SImlarly configure machine 2 with rg_ms1 and rg_ms2

So finally all changes done...
Admin managed server with the help of Node manager
==============================================
What is node manager?
configuration ?
how to use it to configure manged server?

We have 3 managed server with two machines configured in last excercise

Now We will create two node manager for two machines

What is an node manager

====================
seperate process that can be used to remotely start WL server instance ....
It is not associated with any particular domain
Why we need it
-------------------
to use admin console to start servers
Automatic server migration (more latter.....)

Two version of Node manager

-----------------------------------------
Java based
Script based: only available for Unix
Node manager must be configure on each machine for management purpose

Now steps to create node manager for each machine

-----------------------------------------------------------------------------

select rg_mach1 ---> then click node manager....

for second Node manager change port to 5557 to avoid conflict
Activate changes

Now We configure node manager

Go to C:\Oracle\Middleware\wlserver_10.3\common\bin
and run wlst.cmd
So it start WLS in offline mode (two modes: offline and online )
Using this tools i can configure Node manager..........

Now run command

connect('weblogic','welcome','t3//localhost:7001')
Now give command:

nmEnroll('C:/Oracle/Middleware/user_projects/domains/rg_domain',
'C:/Oracle/Middleware/wlserver_10.3/common/nodemanager')

nmEnroll(domain_home, nodeManager_home) where domain_home is the root of your domain

and nodemanager home is where your running the nodemanager from.

Running nmEnroll() ensures that the correct Node Manager user and password token are
supplied to each Managed Server. Once these are available for each Managed Server, you can
use nmConnect() in a production environment.

Now we have successful enrol machine with domain directory

Now we need to add classpath to each managed server.............

CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpa
th\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe172\profiles\default\sys_mani
fest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp360\profiles\defau
lt\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_adfr1111\p
rofiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK
160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\
Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\fe
atures\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server
\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Or
acle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;.;;C:\Oracle\MIDDLE~1\uti
ls\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\
derbynet.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\O
racle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbytools.jar;;

Now we have to start each managed server......

go to ......
C:\Oracle\Middleware\user_projects\domains\rg_domain\bin
and run

startManagedWebLogic.cmd

Now we need to provide requested informations

startManagedWebLogic.cmd rg_ms1 http://localhost:7001

Enter un and pw that used while installation of Admin server..........

managed server started....do similarly for other managed server.

startManagedWebLogic.cmd rg_ms2 http://localhost:7001

startManagedWebLogic.cmd rg_ms3 http://localhost:7001
Now Question is how to use node manager to start managed server from web console

Now force shut down all the managed server , we will start them using node manager.

Now shutting down rg_ms3

Click rg_ms3

Then click control

Choose force shut down

Do it for all managed server one by one..

Now open an new console to start Node manager so that we use it to control managed servers.

Go to
C:\Oracle\Middleware\wlserver_10.3\server\bin

And run startNodeManger.cmd

Now start another node manager for rg_ms2 and rg_ms3

Open new console repeat same procedure

Now try to start managed server from web console.

And finally started message appear.