Introduction
Introduction
Weblogic Concepts:
a. Installation:
Any software requires installation. Installation of a software to your computer so that you can use the software from your HD D frequently.
For any JAVA based application we need a software called JAVA installed first.
Linux has its own directory structure, when you install weblogic/java it would be in this directory structure.
/<Installation Path>/
bin folder -> contains binary files
Config -> where all configuration files would reside
Log -> where all log files would be there
Modules -> where all modules would be present
Lib -> library files
Installation of JAVA
Installation of weblogic
Post Installation
b. Home Path:
JAVA_HOME=/u01/apps/java/
MW_Home = /u01/apps/Oracle/Middlware/
Oracle_Home =/u01/apps/Middlware/Oracle_Home/
WLS_HOME = /u01/apps/Middlware/Oracle_Home/wlserver/
Domain_Home = /u01/apps/<name of the domain>
c. Domain:
What is a domain:
If your creating two websites on prod env or pre prod env or stage env or DR env,
www.google.com
www.facebook.com
We will create one domain only for www.google.com. This will isolate the configuration, logs, executable or bin files, deployed content from
www.facebook.com.
Because both these websites would have their own HOME directory.
Domain is nothing but folder where you store you website's content individually so that you can personalise things you want.
Domain Creation:
We use templates to create domains, while creating a domain you can find the option to select which type of template you need base this domain on.
You can also customize or create your own template by domain template builder tool
WLS L2 Page 1
d. JVM:
What is a JVM ?
In weblogic:
f. Admin Server:
Once you have created a domain, the first thing you want to do is to start the Admin Server in that domain you have created.
i) Admin server is a JVM process, which gets created by default when you create a domain.
ii) Admin Server is where you can perform any modification to your configuration & control(stop / start) your entire domain.
iii) You cannot access the Admin Server directly but you have tools to do so.
One. Admin Console -> Web Based interface.
Two. WLST (weblogic scripting tool) -> A command line tool to do everything what was said earlier
iv) To access the Admin Console or to connect from WLST to the Admin Server, you need your Admin Server to be up and running
The conclusion is Admin Server is default in every domain, where it is the first thing we start in the domain, and once you start you will have to way of
accessing the admin server using admin console or WLST.
Admin Server
g. Managed Server:
Managed Servers are JVM process which runs under an Admin Server's control or independently when Admin Server is unavailable ( but it will resume
connection once Admin Server is available).
First. The Code which is designed by the developers would be archived Into .war or .ear, we deploy them from the Admin Console or WL ST. When
you do so, it would ask you for a target, target means what is going to process these codes, you would assigning either an Ma naged Server or
a Cluster ( a group of managed servers) to process these codes and display the result on the website.
Second. We can have multiple number of ear or war on one JVM or Managed Server. It can handle any number of request based on the RAM usage &
CPU Usage.
h. Deployments:
This is where your content will be deployed, where you have the option of installing a new ear file or war file or update the existing war or ear or deleting
the war or ear file.
When you deploy you set targets, security, and staging of your content
i. Clusters:
WLS L2 Page 2
Load Balancing Feature:
Failover Feature:
j. Web Server:
JDBC:
Provider:
On further classes
Datasource:
On further classes
Connection Pool:
On further classes
JMS:
On further classes
SSL:
On further classes
RAM:
On further classes
On further classes
WLS L2 Page 3