D80149GC20 Les02

2
Unauthorized reproduction or distribution prohibited Copyright 2016, Oracle and/or its affiliates
WebLogic Server: Overview

a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
Copyright 2016, Oracle and/or its affiliates. All rights reserved.
B
i n da ferab
a ch ans
M n-tr
no
Objectives
After completing this lesson, you should be able to:

Define WebLogic Server termsdomain, server, and cluster
Describe the difference between the administration server and

managed servers
List WebLogic Server tools
Describe Paas, IaaS, and Java Cloud Service
Enumerate the features and functions of Java Cloud Service
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch ans
M n-tr
no
Oracle WebLogic Server 12c: Administration I 2 - 2

Distributed Systems
Distributed systems divide their work across similar modules.

As demand increases, more modules can be added to the
system. This makes the system more scalable.

The failure of a single module has less impact on the overall
system,
t which
hi h makes
k th the system
t more available.
il bl
s a
)h a
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a
The main
h of andistributed
cgoal s system is to better manage the complexity and resulting cost of
M t r a
n o n- available and scalable systems.
providing highly
Scalability is how well a system can adapt to increased demands. When a distributed
systems capacity is reached, new equipment can be added fairly easily. These new modules
should handle the increased demand. Distributed systems have the added advantage of
lowering the initial costs of a new system, because additional equipment can be purchased as
needed.
Availability is a measure of a systems ability to process client requests without down time.
High availability requires that a system is up and running as close to 24/7/365 as possible.
Thi iis achieved
This hi dbby using
i lloaddbbalancing
l i and d ffailover
il ttechniques.
h i

Java Platform Enterprise Edition
Java Platform Enterprise Edition (Java EE) is the Java

standard for distributed, enterprise computing.
The Java EE platform consists of:

A Java Virtual Machine (JVM)
Java Platform Standard Edition (Java SE)
A Java EE application server
Java EE Application Programming Interfaces (APIs)
s a
)h a
m
co uide
Java i l
Application
SE/EE g ma nt G
Server
APIs
d a @ tude
n
a chi this S
Java Virtual Machine
Back-end
Clients
c o m
Hardware
s e Systems
s
la e t o u
( b
s c o
c e ns
la le li
B
i n da ferab
The JVMa cisha software
a n s machine that converts compiled Java code into the machine code of
M non
the platform r
-t which the virtual machine runs. Because Java source code is compiled into
o
n that runs on the virtual machine, that compiled code is portable.
the code
Java Platform Standard Edition (SE) is a platform for developing portable, object-oriented
applications. It includes a compiler, a debugger, and a JVM. It also includes thousands of
already created classes (templates for kinds of objects) to make development easier. Java
Platform Enterprise Edition is built on top of Java Platform Standard Edition.
An application server is software that handles application operations from the end user to the
back-end business processes and databases. A Java EE application server complies with all
th JJava EE standards.
the t d d It contains
t i ttwo maini parts:
t
The Web Container that processes Java web application components like Servlets and
JSPs
The EJB Container that processes the Java system components called an Enterprise
JavaBeans
Java EE Application Programming Interfaces (APIs) define standards and provide callable
code that can perform many server
server-side
side tasks from controlling transactions (Java Transaction
API or JTA) to managing resources (Java Management Extensions or JMX).

Oracle WebLogic Server
Oracle WebLogic Server (WLS):

Is a Java EE application server hosting Java EE applications
Is a completely compliant with Java EE 7

Provides clustering for load balancing and high availability
Offers an extensible security realm for authentication,
authorization, and so on
Runs the Java components of Oracle Fusion Middleware
(FMW). These include Oracle SOA Suite, Oracle Service sBus, a
a
Oracle WebCenter Suite,, and some Oracle Identityym) h
Management components l c o ide
m ai t Gu
Runs System components of FMW, such @ g as en
Oracle HTTP Server (OHS) i n d a
S tud
h ac e this
o m
l as c
t o us
o (b nse
l a sc lice Copyright 2016, Oracle and/or its affiliates. All rights reserved.
a B ble
h i n sfera
d
Oracle a c anServer is a scalable, enterprise-ready, Java Enterprise Edition application
WebLogic
M - tr Server enables enterprises to deploy mission-critical applications in a
server. WebLogic
n
robust,n o highly available, and scalable environment. These features enable enterprises
secure,
to configure clusters of WebLogic Server instances to balance workload, provide extra
capacity, and failover in case of hardware or other failures.
Extensive security features protect access to services and keep enterprise data secure.
Oracle Fusion Middleware is a collection of standards-based products that spans a range of
tools and services: from Java EE, to integration services, business intelligence, and
collaboration. Fusion Middleware products are organized into two general categories: Java
components t andd system
t components.
t Java
J components t generally
ll are deployed
d l d tto W
WebLogic
bL i
Server as one or more Java Enterprise Edition applications and a set of resources. FMW 11g
system components are not deployed as Java applications. Instead, system components are
managed by the OPMN server. FMW 12c system components are deployed as part of a
specialized WebLogic Server domain. OHS 12c runs as a WebLogic-managed system
component either within a regular WebLogic domain or within a standalone domain that is
dedicated to running OHS.

JVM
WebLogic Server, as Java code itself, runs within a JVM.

The JVM and its settings can significantly affect WebLogic
Server performance.
For example, the memory available to WebLogic Server and its
applications is contained within the memory assigned to the
JVM.
Oracle provides the Oracle Hotspot JVM.
JVM configuration options are set when the JVM starts. a
This can be done by updating the scripts used to a s
m )h
start
t t WebLogic
W bL i Server.S
i l co uide
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a
The JVM cisha virtual
a n scomputer that executes the bytecode in compiled Java class files on a
M machine.
physical n r
-t How you tune your JVM affects the performance of WebLogic Server and
n o
the applications on it. Use only production JVMs on which WebLogic Server has been
certified. Check the documentation for the latest list of JVMs and operating systems. The
current release of WebLogic Server supports only those JVMs that are Java Platform
Standard Edition 1.6 and higher.
Tuning the JVM to achieve optimal application performance is one of the most critical aspects
of WebLogic Server performance. A poorly tuned JVM can result in slow transactions, long
latencies, system freezes, and even system crashes. Ideally, tuning should occur as part of
the system startup
startup, by employing various combinations of the startup options.
options

System Architecture
Machine
Cluster
WebLogic
Server
Back-end
Systems
and
Machine
Load WebLogic Databases
Balancer Server a
Web h a s
m )
Cli t
Clients
l c o i d e
WebLogic
m ai t Gu
Server
@ g en
Firewall n
Machine
i d a
S tud
a ch this Company Network
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a chsystem
A possible a n s
architecture might contain:
M t r
on-using the World Wide Web to access your applications
Clients
n
A firewall (hardware or software designed to prevent unauthorized access to or from a
private network by using filtering or blocking ports)
A cluster proxy of either a hardware load balancer or a web server like OHS
A cluster of WebLogic Servers on various machines (each one running applications)
Various back-end systems or databases accessed by the applications running on
WebLogic Server
Other common architectural elements not shown:
Additional firewalls (for example, between the Load Balancer and WebLogic Server or
between WebLogic Server and the database)
Multiple load balancers, or perhaps hardware load balancers in front of multiple web
servers
Multiple WebLogic Server clusters

WebLogic Server Domain
A domain is a collection of WebLogic Server resources.

How many domains there are and how they are organized is
completely up to you.
Machine Machine Machine
Domain A Domain A Domain B Domain B

Admin
Server Server Serveras
a
Admin
Server m )h
Server i l co Server
u ide
a
m nt G
g
@ tude Product
Product
n d a
chi this S
Installation Product Installation Installation
a
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a
A domain cisha collection
a n s of WebLogic Server resources. There are different kinds of resources
in a M
domain,n t r
-including WebLogic Servers, deployed applications, clusters, security providers,
o
n Message Service and Java Database Connectivity elements.
and Java
How many domains you have and how you organize them is completely left to you. For
example, domains may be organized by a logical division of types of applications, by physical
location of hardware, by size and number of administrators, and so on.
All domains contain a special server called the administration server. You use the
administration server to configure and manage all of the domain resources. Any other
WebLogic Servers in the domain are called managed servers.
In most domains, the applications are deployed to the managed servers. The administration
server is only used for domain configuration and management.
A single WebLogic Server product installation can be used to create and run multiple
domains, or multiple product installations can be used to run a single domain. How domains
are defined is up to you. You can define multiple domains based on different system
administrators responsibilities, application boundaries, or geographical locations of the
machines on which servers run run.

Administration Server
A domain must have exactly one instance of WebLogic Server

acting as the administration server. An administration server is
part of exactly one domain.

The administration server is:
Th
The central
t l point
i t th
through
h which
hi h you configure
fi andd manage allll
domain resources
Solely in charge of the domains configuration. It distributes
configuration changes to other servers in the domain.
An instance of WebLogic Server and, therefore, a fully as
a
h
functional Java Enterprise Edition application serverm) co uide
i
a tGl
g m n
Domain A
a @ d e
h i nd is Stu
m ac e th
s o Server
Admin
c us
l a t o
o (b nse
a B ble
h i n sfera
d
M ac contain
All domains
t r a n a special server called the administration server. You use the
- server to configure and manage all of the domain resources. Any other
administration
non
WebLogic Servers in the domain are called managed servers.
In most domains, the applications are deployed to the managed servers. The administration
server is only used for domain configuration and management.
Because an administration server is an instance of WebLogic Server, it can perform any task
of a Java Enterprise Edition application server. Applications can be deployed and run on the
administration server. For simplicity, often a development-time domain will only contain the
administration server and no others. Developers deploy and test their applications on the
administration
d i i t ti server.

Managed Servers
A domain can have zero or more managed servers.

A managed server:
Is managed by the administration server

Is an instance of WebLogic Server and, therefore, a fully
f
functional
ti l Java
J Enterprise
E t i Edition
Editi application
li ti server
Is where your Java Enterprise Edition applications run
Web applications, EJBs, web services, enterprise applications
Can be clustered with other cooperating managed servers for
s a
availability, scalability, and automatic failover h a )
o m
a i lc uide
Domain A
g m nt G
d a @ tude
Managed Managed
c in is S Managed
hManaged
Server Server m a th
Server
e Server
s c o u s
b l a t o
o ( nse
a s c l i ce Copyright 2016, Oracle and/or its affiliates. All rights reserved.
l
B ble
a
n sfera
d
h i
M acall domains,
In almost
t r a n the administration server is not the only server defined in the domain.
Other servers- are also defined. These others are called managed servers, because they are
managednobyn the administration server.
A companys web applications, EJBs, web services, and other resources are deployed and
run on the managed servers. That leaves the administration server free for configuration and
management purposes.
For scalability, availability, and failover (when one server fails, requests are automatically sent
to another server), managed servers can be placed together in a cluster.

Node Manager
Is a separate process that accepts remote commands to start,

stop, or suspend servers on its machine
Monitors server availability and can restart failed servers

Can be used to migrate servers on a failed machine to
another
th machine
hi
Machine
s a
a
)h Server
Node Start/stopp m
Manager Monitor/ i l co uide
restart g ma Server n t G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Server a ch ainnsa WebLogic Server production environment are often distributed across
instances
M domains,
multiple n - tr machines, and geographic locations. Node Manager is a WebLogic Server
noenables you to start, shut down, and restart both administration server and
utility that
managed server instances from a remote location. Although Node Manager is optional, it is
recommended if your WebLogic Server environment hosts applications with high-availability
requirements. A Node Manager process runs on a particular machine.
There are two versions of Node Manager: the Java-based one that runs on any platform on
which WebLogic Server runs and the script-based one that only runs on *nix operating
systems. The Java-based Node Manager is recommended.
If Node
N d M Manager starts
t t a server and d that
th t server later
l t fails,
f il Node
N d M Manager can bbe sett tto
automatically restart it. If Node Manager fails or is explicitly shut down, upon restart, it
determines the servers that were under its control when it exited. Node Manager can restart
any failed servers as needed.
The WebLogic Server administration console can be used to issue commands to Node
Managers running on remote machines. The WebLogic Scripting Tool (WLST) (in offline
mode)) also serves as a Node Manager
g command-line interface.

Machines and Clusters
A machine:
Is defined within a domain to represent physical hardware
Is required by Node Manager and used by clusters

Has managed servers assigned to it
A cluster:
Has multiple managed servers running cooperatively in it,
which provides for failover
s a
With HTTP clients requires a cluster proxy that providesaload
balancing m )h
o
Proxy
a ilc Guide
@ gm ent
i n da Stud Server
ch this
Cluster Server Server
a
Machine
s c om Machine
u se Machine
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a chdefinition
A machine a n sis used to associate a computer with the managed servers that it hosts.
MManager
Node n r
-t is always defined within the context of a machine. Machine definitions, and
n o
which servers are assigned to them, are also used by a clustered managed server in selecting
the best location for storing replicated session data.
A cluster is a collection of multiple managed servers within a single domain running
simultaneously and cooperatively to provide increased scalability and reliability. Resources
and services are deployed identically to each server in a cluster, allowing for failover and load
balancing. The session state of one clustered server is replicated on another server in the
cluster. When a server fails, another server in the cluster takes over for it and retrieves the
replicated data.
data No information is lost and customers do not realize that a different server is
now fulfilling their requests. Clustered servers communicate with one another in two main
ways: sending updates to their backup server when session state changes, and through
cluster heartbeats. Each clustered server sends out a signal periodically to indicate that it is
still viable. If a member of the cluster misses too many heartbeats, that server has failed.
A cluster with HTTP clients (a cluster with web applications) is always fronted by a proxy,
which could be a web server, a hardware load balancer, or an instance of WebLogic Server.
Th proxy provides
The id lload
dbbalancing
l i and d enables
bl ffailover
il b
by avoiding
idi ffailed
il d servers. Cl
Clusters
t
that provide EJB or JMS applications do not require a cluster proxy.

WebLogic Server Application Services
Java Database Connectivity (JDBC)

The API for accessing relational databases
Data source objects are configured to provide database

access.
Java
J Message
M Service
S i (JMS)
The API for and implementation of an enterprise messaging
system
Multiple resources must be configured in WebLogic Server for
a
JMS. as ) h
Java Transaction API (JTA) c m
o ide
i l
aWebLogic u Server
When transactions need to span resources,
g m n t G
can act as the transaction manager.a@ ude
h i nd is St
m ac e th
s c o us
l a t o
o (b nse
a B ble
h i n sfera
d
c
Ma n-tran
no

WebLogic Server Application: Example
1
Web
Application
2 3
EJB
Application
Persistence
4
Web Service s a
Application WebLogic) h
a
Message Queue
XML
l c om ide
Server
5 WebLogic Server
m ai t Gu
@ g en
Otheri n d a
SystemsS tud
a h his
orcApplications
c o m se t
l as t o u
o b
( nse
a s c l i ce Copyright 2016, Oracle and/or its affiliates. All rights reserved.
l
B ble
a
n sfera
d
h i
ac interact
1. Users
Mresponsible
t r a n with a web application by using a browser. The web application is
- for rendering the website and for capturing user input through buttons,
nonlinks, and so on. It is possible that the web application contains all of the
forms,
necessary business logic to perform the tasks that users request.
2. In this example, however, the web application accesses Enterprise JavaBeans (EJBs) to
perform the business logic. These EJBs can be located on the same server as the web
application or on a different server, as shown in this example.
3. Some of the EJBs shown include a persistence mechanism. They are writing newly
placed orders to a relational database.
4
4. Aft the
After th order
d isi written
itt tot the
th database,
d t b an EJB uses the
th Java
J Message
M Service
S i (JMS)
to asynchronously communicate with other applications so that those applications can
also process the order.
5. To expose the business logic of this application in a standard way to other applications,
both within your organization and beyond, a web service is used. XML-based web
services can be accessed by both Java and non-Java applications and are a
cornerstone of service-oriented architecture.

WebLogic Server Administrative Tools
WebLogic Server can be administered and monitored by using:

The WebLogic Server administration console
Fusion Middleware Control

The WebLogic Scripting Tool (WLST)
The WebLogic Diagnostic Framework (WLDF) and Monitoring
Dashboard
Enterprise Manager Cloud Control
RESTful Management Services s a
a
)h
Java Management Extentions (JMX) o m e
a ilc Guid
@ gm ent
i n da Stud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a
WebLogic chServeransystem
s administration includes a wide range of tasks which can be handled
by using r
M a nvariety
-t of tools, including:
n o
eb og c Se
WebLogic Server
e Administration
d st at o CoConsole:
so e A full-featured
u eatu ed console
co so e which
c suppo
supportsts bot
both
administration and monitoring capabilities, but is focused purely on WebLogic Server
Fusion Middleware Control: A web-based management system for administering
Oracle Fusion Middleware products. Fusion Middleware Control enables you to manage
services in your enterprise, including hosts, databases, listeners, application servers,
HTTP Servers, and web applications, as one cohesive unit.
WebLogic Scripting Tool (WLST): A command-line scripting environment that you can
use to
t create,
t manage, and d monitor
it WebLogic
W bL i domains.
d i It is
i bbased
d on th
the JJava scripting
i ti
interpreter, Jython.
WebLogic Diagnostic Framework (WLDF): A monitoring and diagnostic framework
that defines and implements a set of services that run within WebLogic Server
processes and participate in the standard server life cycle. Using WLDF, you can create,
collect, analyze, archive, and access diagnostic data.
Enterprise Manager Cloud Control (EMCC): A suite of integrated enterprise
information technology management products, which provides comprehensive solutions
for testing, deploying, operating, monitoring, diagnosing, and resolving problems in
todays complex IT environments.

RESTFul Management Services: A comprehensive public interface for configuring,
monitoring, and administering the Oracle WebLogic Server platform in all supported
environments.
Java Management
g Extensions: A technology
gy for managing
g g applications,
pp objects,
j
devices, and other resources that are known as managed beans (MBeans). A MBean is
a Java bean that provides a Java Management Extensions (JMX) interface. JMX is the
J2EE solution for monitoring and managing resources on a network. Like SNMP and
other management standards, JMX is a public specification and many vendors of

commonly used monitoring products support it. WebLogic Server provides a set of
MBeans that you can use to configure, monitor, and manage WebLogic Server
g JMX.
resources through
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
B la le li
i n da ferab
a ch ans
M n-tr
no

WebLogic Server Administration Console
The Oracle WebLogic Server administration console is a web

browserbased tool for configuring, administering, and
monitoring the resources of a domain.

The console application runs on the administration server.
It is
i partt off the
th normall installation
i t ll ti off W
WebLogic
bL i S Server.
s a
a
)h
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a chWebLogic
The Oracle a n s Server administration console (admin console) is a
webM -t r
browserbased,
n graphical user interface that can be used to manage a WebLogic Server
o
nThe admin console application runs on the administration server. The admin console
domain.
can be used to:
Configure, start, and stop instances of WebLogic Server
Configure clusters
Configure database connectivity (JDBC)
Configure messaging (JMS)
g
Configure WebLogic
g Server securityy
Deploy applications
Monitor server and application performance
View server and domain log files

Fusion Middleware Control
Fusion Middleware Control includes

support for:
Oracle Traffic Director: Create and

manage OTD MT configurations.
WebLogic
W bL i Server:
S C t and
Create d
manage WLS and Coherence MT,
including domains, partitions,
applications, caches, and more.
s a
Health: Monitor WebLogic Domains, a
)h
C h
Coherence Cl
Clusters,
t Oracle
O l Traffic
T ffi m
co uide
i l
directory, and other tools to examine
g ma nt G
e
health and performance. da@ tud n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Fusiona ch ansControl (FMW) is a web browser-based, graphical user interface that you
Middleware
can M
use to n - tr and administer your domain. It can manage an Oracle WebLogic Server
monitor
no
domain with its Administration Server, one or more Managed Servers, clusters, the Oracle
Fusion Middleware components that are installed, configured, and running in the domain, and
the applications you deploy. Fusion Middleware Control organizes a wide variety of
performance data and administrative functions into distinct, web-based home pages for the
domain, servers, components, and applications. The Fusion Middleware Control home pages
make it easy to locate the most important monitoring data and the most commonly used
administrative functionsall from a web browser.
g functionality
The following y is available in Fusion Middleware Control:
Create WebLogic Server clusters, server instances, domains, machines, and server
templates
Configure applications and libraries
Create and configure UCP and proxy data sources

Create and configure JMS servers, Store-and-Forward agents, JMS modules, JMS
resources, path services, messaging bridges, and messaging bridge destinations
Create and configure security realms
Manage WebLogic Server diagnostics
Configure elasticity for dynamic clusters
Manage WebLogic Server in a multi-tenant environment
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
B la le li
i n da ferab
a ch ans
M n-tr
no

WebLogic Scripting Tool
The WebLogic Scripting Tool (WLST) is:

A scripting tool for creating, configuring, administering, and
monitoring the resources of a WebLogic Server domain

Included with the installation of WebLogic Server
Capable of performing all the tasks available in the
administration console, and more
$> . . . s a
$> java weblogic.WLST
)h a
I iti li i
Initializing W
WebLogic
bL i S Scripting
i ti T
Tool
l (WLST) ... m
co uide
i l
ma nt G
wls:offline> connect('username', 'password', 'localhost:7001')
. . . g
@ tude
n d a
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch Scripting
The WebLogic a n s Tool (WLST) is a command-line scripting interface that system
r
M n-t and operators use to monitor and manage WebLogic Server instances and
administrators
noWLST is based on the Java scripting interpreter, Jython. In addition to supporting
domains.
standard Jython features such as local variables, conditional execution, and flow control
statements, WLST provides a set of commands that are specific to WebLogic Server. WLST
can be run interactively (one command at a time) or in script mode (running a file of
commands). It also can be run online (connected to an administration server that allows it to
manage an active domain) or offline (accessing the configuration files of an inactive domain).
WebLogic Server developers and administrators can extend the WebLogic scripting language
to suit their environmental needs byy following
g the Jython
y language
g g syntax.
y
To call WLST with a script, simply append the fully qualified path to the script to the WLST
command.
$> java weblogic.WLST myscript.py
Calling WLST without a script, as shown in the slide, puts WLST into interactive mode.

WebLogic Diagnostic Framework
Is a monitoring and diagnostic framework

Creates, collects, analyzes, and archives diagnostic data
Runs within WebLogic Server processes

Participates in the standard server life cycle
Installed with WebLogic Server WLDF is configured and used
through the administration
WLDF supports: console or WLST!
Diagnostic images: Create snapshots of the
servers configuration and runtime metrics. s a
a
)h
Harvesters: Periodically collect and record m
co uide
i l
metric data.
g ma nt G
Policies and Actions: Compare data d a @
to sett u de
conditions and send notification in met.
chwhen i s S
a
m se t h
More s c o u
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a
The WLDF chprovides
a n sfeatures for generating, gathering, analyzing, and persisting diagnostic
dataM -t r
from WebLogic
n Server instances and from applications deployed to them. Some WLDF
o
nare configured as part of the configuration for a server in a domain. Other features
features
are configured as system resources (diagnostic modules) that can be targeted to servers (or
clusters).
You use the diagnostic image capture component of WLDF to create a diagnostic snapshot of
a servers internal runtime state at the time of the capture. This information can help Oracle
support personnel analyze the cause of a server failure. You can capture an image manually
by using the WebLogic Server administration console or WLST, or you can generate one
automatically as part of a watch notification
notification. A diagnostic image zip file includes the servers
server s
configuration, log cache, JVM state, work manager state, JNDI tree, and most recent
harvested data.

WebLogic Diagnostics Framework Dashboard
Is accessed from the WLS Administration Console

Graphically presents the current and historical state of
WebLogic Server, and hosted applications and resources

Includes information gathered by the built-in diagnostic system
modules
d l
Includes tools for organizing and displaying diagnostic data
s a
)h a
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch Dashboard
The Monitoring a n s displays the current and historical operating state of WebLogic
M t r
- applications by providing visualizations of metric runtime MBean attributes,
Server andnhosted
no some of the more critical runtime performance metrics and the change in those
which surface
metrics over time. Historical operating state is represented by collected metrics that have
been persisted into the Archive. To view collected metrics from the Archive, you must
configure the Harvester to capture the data you want to monitor.
The Monitoring Dashboard displays metric information in a series of views. A view is a
collection of one or more charts that display metrics. The Monitoring Dashboard includes a
predefined set of built-in views of available runtime metrics for all running WebLogic Server
instances in the domain
domain. Built-in
Built in views surface some of the more critical runtime WebLogic
Server performance metrics and serve as examples of the Monitoring Dashboard's graphic
capabilities.

Enterprise Manager Cloud Control
Provides a comprehensive IT management infrastructure for

both Oracle and non-Oracle hardware and software
Offers insight into the health of all the components in your

enterprise or private cloud
Supports
S t private
i t cloud
l d managementt and d self-service
lf i (I(IaaS,
S
PaaS, DBaaS, and MWaaS)
Is designed for flexibility and customization
Runs on WebLogic Server but requires a relational database sa
) ha
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Oracle a ch anManager
Enterprise s Cloud Control is Oracles integrated, enterprise information
M t r
- management product line, which provides the industrys only complete,
technologyn(IT)
no
integrated, and business-driven enterprise cloud management solution. Oracle Enterprise
Manager creates business value for IT by leveraging the built-in management capabilities of
the Oracle stack for traditional and cloud environments, thus enabling customers to achieve
unprecedented efficiency gains while dramatically increasing service levels.
Enterprise Manager Cloud Control (EMCC) also provides on-demand access to servers and
storage in a self-serviced, elastically scalable, and metered manner. The EMCC private cloud
models can be divided into two primary categories:
Infrastructure as a Service (IaaS),
(IaaS) which allows users to request virtualized compute
compute,
storage, and network resources to run applications
Platform as a Service (PaaS), which provides the specific database (DBaaS) and
middleware (MWaaS) components required by applications
Oracle Cloud Management Pack for Oracle Middleware delivers MWaaS capabilities that
span the entire middleware cloud life cycle. It enables cloud administrators to identify pooled
resources,, configure
g role-based access,, define the service catalog,
g, and define the related
chargeback plans. It enables cloud users to request middleware services and consume them
on demand.

WebLogic Server and RESTful Management
WebLogic RESTful management services:

Provide a public interface for configuring, monitoring,
deploying, and administering WebLogic Server

Are supported in all environments
Are based on WebLogic MBeans and descriptor interfaces
Support configuration, management, and reporting of:
Domains, Partitions, Servers,
and other environments
s a
REST API
Multitenant environments )h a WebLogic
Domain
m
co uide
And others GET
i l
a tG
g m
POST
n
a @ PUT de
i nd DELETE
S tu
h
ac e this
o m
l as c
t o us
o (b nse
a B ble
h i n sfera
d
M ac RESTful
WebLogic
t r a n management services provide a comprehensive public interface for
-
configuring,nmonitoring, deploying, and administering WebLogic Server in all supported
no This lesson describes the RESTful management services supported by
environments.
WebLogic Server.
The 12.2.1 release of RESTful management services provides comprehensive support for
WebLogic Server administration through the dynamic generation of REST resources based
on WLS MBeans and descriptor interfaces. There are resources to support the configuration
and monitoring of partitioned and nonpartitioned environments, life cycle management
resources, and legacy resources from 12.1.3.
There are two main bean types:

Configuration: Used to configure WebLogic Server
Runtime: Used to monitor WebLogic Server and for some operations, control WebLogic
Server (for example, starting and stopping servers, and shrinking data source
connection pools).
For more information,, see Oracle Fusion Middleware Administering
g Oracle WebLogic
g
Server with RESTful Management Services.

Cloud Computing
Delivers software functionality as remote services

Relies on a shared infrastructure whose location and
implementation are transparent to users

Consolidates IT resources for multiple business units or
organizations
i ti
Strives to optimize resource utilization and reduce power
consumption
May also provide integrated metering and billing s a
)h a
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch level,
At the highest a n sa cloud approach decouples the users of applications from the
applications t r
M n-themselves. In other words, users no longer install software in their local
o
n and have no idea where their applications are really running. The concept of
environment
cloud computing has been around for many decades, and it gained momentum with the
success of the Internet.
Now, however, the right hardware and software are available to implement a high-
performance and scalable cloud infrastructure. Smaller organizations can eliminate their IT
infrastructure by leveraging a public cloud to run their applications. Alternatively, public clouds
may not be able to meet the capacity and security requirements of larger organizations,
which therefore
which, therefore, create and use their own private cloud infrastructure instead.
instead
It is critical for both public and private clouds to track the resource utilization of the services
that they host. Public clouds may need to bill customers, and private clouds may need to
cross-charge expenses to different business units. Both types of clouds may implement
service-level agreements that limit the resource utilization of certain services.

Self Service
Is a core pillar of any good cloud platform

Provides a simple, intuitive web interface
Avoids creating IT tickets to provision resources

Hides the underlying details of the infrastructure
Limits the rights or resource usage of different organizational
units or applications
Automates complex setup tasks
s a
)h a
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
ch anplatform
A cloudacomputing s should offer a unified, intelligent interface for interacting with the
M
platform ton - t r
configure, use, and optimize infrastructure resources. Administrative self-service
no be able to manage and monitor resource supply, configuration, and utilization of
users should
the cloud. Other users should be able to quickly provision, manage, and monitor their own
resources in the cloud.

Infrastructure as a Service (IaaS)
IaaS focuses on server, storage, and network virtualization

technologies.
Users of an IaaS cloud service:

Provision new servers (VMs), storage, and networks as needed
Are responsible for configuring and maintaining the VM guest
operating system, including the installation of other required
software
s a
)h a
m
co uide
i l
g ma nt G
d a @ tude
n
a chi this S
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
An IaaSa ch agives
service n s users direct access to the virtualized hardware infrastructure on which
yourM r
t Users can provision virtual machines (VMs) and deploy to them any
is-built.
cloud n
o
n of their choice. This also means that users are responsible for maintaining the entire
software
software stack within their VMs. To deploy their applications, users must install, configure,
and patch all the appropriate software, including the operating system. IaaS users also control
the networks and storage devices to which their VMs are connected.

Platform as a Service (PaaS)
PaaS services:
Provide a complete platform to build, test, and deploy custom
applications
May or may not expose the underlying VMs and server
software to users
May target developers or business users
A PaaS provider:
Provisions the OS and server software for users
a
Often includes supporting services like databases
) has
Offers
Off high-availability,
hi h il bilit security,
it andd
l c om ide
maintenance features m ai t Gu
g n
a@ ude
May include various development tools
nd is St
h i
m ac e th
s c o us
l a t o
o (b nse
a B ble
h i n sfera
d
ac trhide
PaaS services
M a n more of the cloud infrastructure from users. They expose a particular
- on which to deploy custom applications. A database service would provide
software platform
nonthe ability to create tables, import data, and so on. PaaS eliminates many of the
users with
installation and maintenance tasks associated with the platform and its underlying operating
system.

Java Cloud Service
Is a self-service platform for Oracle middleware

Enables users to rapidly:
Provision WebLogic Server, Coherence, and Traffic Director on

multiple VMs
Scale
S l in i or outt off their
th i WebLogic
W bL i or Coherence
C h clusters
l t
Back up or restore their environment
Apply or roll back a patch
Provides full access to the underlying guest OS and a
middleware configuration a s
m )h
Requires a relational database i l co uide
Offers a web UI and REST API g ma nt G
@ e
i n da Stud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Oracle a ch Cloud
Java a n s
Service is a complete platform and infrastructure cloud solution for
M - t r
building, deploying, and managing Java EE applications. Use Java Cloud Service to rapidly
noann application environment with Oracle WebLogic Server as the application
provision
container, Oracle Coherence as a caching and data grid tier, and Oracle Traffic Director as
the software load balancer. All of these service components run on top of infrastructure
provided by Oracle Compute Cloud Service.
When provisioning a Java Cloud Service instance, you can choose the WebLogic Server
software edition and version, the CPU and memory capacity of the VMs, and the initial size of
your cluster. Also, with a single click in the JCS web interface, you can perform common
lifecycle operations on demand like starting and stopping the instance,
instance backing it up
up, and
scaling it out to meet new capacity requirements.
JCS provides users with full access and control over the underlying components that
comprise a service instance, including the VMs, the WebLogic domain, and the Traffic
Director load balancer configuration. You can administer the instance with familiar tools like
the WebLogic Server Administration Console, the Fusion Middleware Control, and the
WebLogic Scripting Tool.

JCS Instance
Public
Network
JCS Instance
VM WebLogic WebLogic WebLogic

Admin Server WebLogic WebLogic
Coherence
Traffic Director WebLogic
(optional) VM VM
(optional)
VM WebLogic VM VM
VM VM
a
) h as
DBCS m
Private
l c o ide
Instance
Network
m ai t Gu
@ g en
i n d a
S tudMDS schema
a ch this (required)
o m e
l asc to us
o (b nse
a B ble
h i n sfera
d
c
Ma n-tran
no

Creating a JCS Instance
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch ans
M n-tr
no

Java Cloud Service: Default Ports
Admin JCS Instance

VM
HTTPS:7002 WebLogic Admin 7001
Server
8001 WebLogic
WebLogic
W bL i 8001 WebLogic
HTTPS:8989 M
Managed
dSServer
8002 Managed Server
Private Network
Managed Server
8002 VM
VM
HTTPS:443
Load Balancer
Public Network
VM s a
End User
)h a
m
co uideDBCS
i l
a t G Instance
g m1521 n
a @ d e
h i nd is Stu
m ac e th
s c o us
l a t o
o (b nse
a B ble
h i n sfera
d
M ac channels
The network
t r a n available to administrators and end users will vary depending on the
topology you-selected when you created the JCS instance. In this first scenario, lets say that
nona brand new JCS instance with multiple managed servers and with the load
you created
balancer option. As an administrator, you have remote access to the administration consoles
by using HTTPS. To access the WebLogic or Fusion Middleware console, use port 7002, and
to access the load balancer console, use port 8989. End users access your applications by
using the default HTTPS port of the load balancer. After you have connected to one of these
public endpoints via SSH or HTTPS, you can access the remaining components of the
instance by using a private network. Managed servers listen on ports 8001 and 8002, with the
q g SSL.
latter requiring

Java Cloud Service: Default Domain Configuration
cluster
server_1 server_2 server_3
Data Sources Server Template

p JRF/ADF Deployments
p y
adminserver Node Manager Node Manager
Data Sources machine_2 machine_3

MDS
Schema Embedded LDAP
s a
) h a
Node Manager
c m
o ide
l
ai t Gudomain
machine_1 m
g en
d a @ tud
i n S
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Each VMa cinhyouraJCS
n s instance that hosts servers in this WebLogic domain is represented in
r
M nas-t a machine. The first machine in a JCS domain always hosts the administration
the domain
server n o the first managed server. The security realm for the domain uses an LDAP server
and
that is embedded within the administration server. As you scale out the JCS instance,
additional machines and managed servers are added to the domain. These managed servers
are grouped together as a cluster and also inherit attributes from a shared server template. All
of the servers in the domain, including the administration server, connect to your database in
the Oracle cloud. This database connectivity is defined as a set of WebLogic data sources.

Quiz
Q
Which of the following statements are true about Node Manager?
a. Node manager is a separate process that accepts remote
commands to start, stop, or suspend servers on its machine.

b. It monitors server availability and can restart failed servers.
c. It can be used to submit remote command to a WebLogic
Server administrative server to modify domain configuration.
d. It can be used to migrate servers on a failed machine to
another machine. sa
) ha
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
ch ans
Answer:aa,b,d
M n-tr
noScripting Tool (WLST) can be used to submit remote commands to modify domain
WebLogic
configuration All others are true
configuration. true.

Quiz
Q
What is the minimum number of administrative servers in a
WebLogic domain?
a. 0
b. 1
c. 2
d. 3
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Answer:ab ch ans
M n-tr
There is o
nonly one administrative server in a WebLogic domain.

Quiz
Q
What are the minimum requirements for using Fusion
Middleware Control?
a. An administration server must be defined.

b. An administration server and a managed server must be
d fi d
defined.
c. The domain must be configured to support Fusion Middleware
Control when created.
d. All of the above sa
) ha
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
Answer:acc
h ns
M n-tra
no the domain, the Fusion Middleware Control must be enabled.
When creating

Summary
In this lesson, you should have learned how to:

Define WebLogic Server termsdomain, server, and cluster
Describe the difference between the administration server and

managed servers
List WebLogic Server tools
Describe Paas, IaaS, and Java Cloud Service
Enumerate the features and functions of Java Cloud Service
a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
la le li
B
i n da ferab
a ch ans
M n-tr
no

a
) has
l c om ide
m ai t Gu
@ g en
i n d a
S tud
a ch this
s c om use
( b la e to
s c o
c e ns
B la le li
i n da ferab
a ch ans
M n-tr
no

D80149GC20 Les02

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

D80149GC20 Les02

Transféré par

Droits d'auteur :

Formats disponibles

2

WebLogic Server: Overview

After completing this lesson, you should be able to:

Describe the difference between the administration server and

Oracle WebLogic Server 12c: Administration I 2 - 2

Distributed systems divide their work across similar modules.

system. This makes the system more scalable.

Oracle WebLogic Server 12c: Administration I 2 - 3

Java Platform Enterprise Edition (Java EE) is the Java

The Java EE platform consists of:

Oracle WebLogic Server 12c: Administration I 2 - 4

Oracle WebLogic Server (WLS):

Is a completely compliant with Java EE 7

Oracle WebLogic Server 12c: Administration I 2 - 5

WebLogic Server, as Java code itself, runs within a JVM.

Oracle WebLogic Server 12c: Administration I 2 - 6

Oracle WebLogic Server 12c: Administration I 2 - 7

A domain is a collection of WebLogic Server resources.

Machine Machine Machine

Domain A Domain A Domain B Domain B

Oracle WebLogic Server 12c: Administration I 2 - 8

A domain must have exactly one instance of WebLogic Server

part of exactly one domain.

Oracle WebLogic Server 12c: Administration I 2 - 9

A domain can have zero or more managed servers.

Is managed by the administration server

Oracle WebLogic Server 12c: Administration I 2 - 10

Is a separate process that accepts remote commands to start,

Monitors server availability and can restart failed servers

Oracle WebLogic Server 12c: Administration I 2 - 11

Is required by Node Manager and used by clusters

Oracle WebLogic Server 12c: Administration I 2 - 12

Java Database Connectivity (JDBC)

Data source objects are configured to provide database

Oracle WebLogic Server 12c: Administration I 2 - 13

Oracle WebLogic Server 12c: Administration I 2 - 14

WebLogic Server can be administered and monitored by using:

Fusion Middleware Control

Oracle WebLogic Server 12c: Administration I 2 - 15

other management standards, JMX is a public specification and many vendors of

Oracle WebLogic Server 12c: Administration I 2 - 16

The Oracle WebLogic Server administration console is a web

monitoring the resources of a domain.

Oracle WebLogic Server 12c: Administration I 2 - 17

Fusion Middleware Control includes

Oracle Traffic Director: Create and

Oracle WebLogic Server 12c: Administration I 2 - 18

Oracle WebLogic Server 12c: Administration I 2 - 19

The WebLogic Scripting Tool (WLST) is:

monitoring the resources of a WebLogic Server domain

Oracle WebLogic Server 12c: Administration I 2 - 20

Is a monitoring and diagnostic framework

Runs within WebLogic Server processes

Oracle WebLogic Server 12c: Administration I 2 - 21

Is accessed from the WLS Administration Console

WebLogic Server, and hosted applications and resources

Oracle WebLogic Server 12c: Administration I 2 - 22

Provides a comprehensive IT management infrastructure for

Offers insight into the health of all the components in your

Oracle WebLogic Server 12c: Administration I 2 - 23

WebLogic RESTful management services:

deploying, and administering WebLogic Server

There are two main bean types: