WLS 12c IS - WLS 12c Fundamentals

For Oracle employees and authorized partners only. Do not distribute to third parties.
© 2012 Oracle Corporation – Proprietary and Confidential

Safe Harbor Statement
The following is intended to outline our general product

direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions.
The development, release, and timing of any features or
functionality described for Oracle’s products remains at the
sole discretion of Oracle.
Oracle Training Materials – Usage
Agreement
Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:
1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and copy the information,
documents, and the online training courses (collectively, “Materials") found on this Site. The use of the Materials is
restricted to the non-commercial, internal training of the Partner’s employees only. The Materials may not be used for
training, promotion, or sales to customers or other partners or third parties.
2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other third party at no time
has any right to resell, redistribute or create derivative works from the Materials.
3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials. Materials are
provided "as is" without warranty of any kind, either express or implied, including without limitation warranties of
merchantability, fitness for a particular purpose, and non-infringement.
4. Under no circumstances shall Oracle or the Oracle Authorized Boot Camp Training Partner be liable for any loss,
damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site of Materials. As a
condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses,
damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.
5. Reference materials including but not limited to those identified in the Boot Camp manifest can not be redistributed in any
format without Oracle written consent.
<Insert Picture Here>
Oracle WebLogic Server 12c

Implementation Boot Camp
WebLogic Server 12c Fundamentals
WLS Basics
WebLogic Server Introduction
For the “Heavy Lifting” in the Enterprise
Reliability
• Overload protection (work managers, message size and persistence limits)
• Rock-solid 2PC transaction management (Tuxedo development heritage)
• Fault tolerant JMS - combined with 2PC for message loss avoidance
Availability
• Features for tolerance of planned and unplanned events
• Automatic failover of services
Scalability
• Increasing cluster doesn't exponentially increase HA management overhead
• Customer deployments with hundreds of servers and thousands of CPUs
Performance
• T3 fast network protocol, Native Network I/O, Self-tuning kernel and user tunables; caching, load
balancing
• Predictable fast response times - JRockit Deterministic GC for maximum pause targets of < 10 ms
Key Concepts
WebLogic Terminology
• Domain - group of instances and clusters under
unified control
• Administration Server - central configuration

controller for the domain
• Managed Server - Instance that hosts

applications and required resources
• Cluster - group of managed servers to provide

increased scalability and reliability
• Node Manager - per-machine process used to

start, stop and auto-restart instances
Administration Console
• Graphical interface to configure, manage, monitor a domain
• The Administration Server hosts the Administration Console
• Open the Administration Console with the following URL:

• http://host:port/console
• Typically: http://localhost:7001/console
• Sample domains use weblogic/weblogic or weblogic/welcome1 as the user
name and password
• The Administration Console application deploys lazily

Administration Server
Managed Servers
• What is it?
• Central configuration controller for a domain
• What else does it do?
Admin Server
• Hosts the Administration Console
• Enables you to start and stop servers from a central config.xml
location
• Enables you to deploy applications within the
domain
• Guidelines
• There must be exactly one Administration Server in
domain
• An Administration Server controls a single domain. Admin Console
• For production use, we recommend not hosting

application logic or resources on the Administration
Server
*The Administration Server does not need to run at all times, but is required for making
configuration and deployment changes to a running domain.
Managed Server
• What is it?
• A running instance that hosts applications JNDI
and resources needed by those JMS Queue
applications - The real work horses in a JDBC Pool

WebLogic domain
• Each Managed Server is independent of
all other Managed Servers in the domain
(unless they are in a cluster, defined later)
• You can have as many Managed Servers
in a domain as you need
• Individual Managed Servers are typically
added for capacity and application
isolation
Administration Server to Managed Server
Interaction
• The Administration Server stores the master copy of the
domain configuration, including the configuration for all
managed servers in the domain
• Each Managed Server stores a local copy of its configuration.
• When a Managed Server starts, it connects to the
Administration Server to synchronize the configuration
• When configuration is changed, the Administration Server
sends changed configuration to Managed Servers
Key Concepts
Single Administration Server for a Domain
WLS Distributions
NEED SLIDE FOR PACKAGES /
INSTALLERS
WebLogic Server SE, Server EE, Suite
Packaging and Licensing
WebLogic Server WebLogic Server
WebLogic Suite
Standard Edition Enterprise Edition
WebLogic Server = WebLogic Server Standard = WebLogic Server
+ Edition Enterprise Edition
Kodo Enterprise + +
+ Clustering Coherence EE
TopLink and ADF + +
+ Enterprise Manager JRockit Real Time
JDeveloper Diagnostics Pack +
+ Management Pack
Enterprise Pack for Eclipse for Coherence
+ +
Oracle HTTP Server iAS EE
+
WL Operations Control
Installation
Installation
WLS 11g Platform Support
http://www.oracle.com/technetwork/middleware/fusion-middleware/documentation/index.html
*Always check the up-to-date information on OTN
Operating Systems Web Server Plugins
• Linux: OL 4/5, RHEL 4/5, SLES 10/11 (x86, x86-64) 1.0 Plugins
• Solaris: 9/10 (SPARC, x86, x86-64) • iPlanet: 7.x (64-bit)
• Windows: 2003/XP/Vista/2008 (x86, x86-64) • Apache: 2.0/2.2 (32-bit and 64-bit)
• HP-UX: 11i v2/v3 (Itanium, PA-RISC)
• Microsoft IIS: 6/7 (32-bit and 64-bit)
• AIX: 5.3/6.1/7.1 (POWER)
• Sun Java System Web Server (iPlanet):
6.1/7.0 (32-bit only)
Java Virtual Machines (JVMs) • Oracle HTTP Server (OHS) – 11g (64-bit)
• JDK 1.6 (plus 1.5 for clients) 1.1 Plugins
• JRockit: Linux & Windows (32-bit, 64-bit), Solaris • Apache: 2.2 (64-bit)
SPARC (64-bit)
• Microsoft IIS: 6/7 (64-bit)
• Sun Hotspot: Linux, Windows & Solaris (32-bit and
64-bit) • Oracle HTTP Server (OHS) – 11g (64-bit)
Installation
WLS 12.1.1 - Current Platform Support
• Operating Systems
• Linux: OL 5/6, RHEL 5, SLES 10/11 (x86-64)
Web Server Plugins
• Solaris: 10/11 (SPARC, x86-64) 1.0 Plugins
• Windows: 7 / Server 2008 (x86-64) • iPlanet: 7.x (64-bit)
• HP-UX: 11i v2/v3 (Itanium, PA-RISC) • Apache: 2.0/2.2 (32-bit and 64-bit)
• AIX: 6.1/7.1 (POWER) • Microsoft IIS: 6/7 (32-bit and 64-bit)
• Max OS X for development only • Oracle HTTP Server (OHS) – 11g (64-bit)
• Java Virtual Machines (JVMs) 1.1 Plugins

• Apache: 2.2 (64-bit)
• Java 6 and 7
• Microsoft IIS: 6/7 (64-bit)
• JRockit
• Oracle HTTP Server (OHS) – 11g (64-bit)
• Sun Hotspot
64-bit only for production
Installation
Install Specifics
• Middleware Home
• To store one or more installed products (e.g. WLS, SOA Suite)
• Examples: c:\Oracle\Middleware or /u01/Oracle/Middleware
• Recommendation: Use separate MW homes for separate products
• Recommendation: Use separate MW homes for different versions
• WebLogic Home
• To store installed WebLogic product, containing all the WebLogic library JARs, executables,
tools, licence info, examples and scripts
• Usually a directory underneath MW home, eg.: c:\Oracle\middleware\wlserver_12.1
/opt/Oracle/middleware/wlserver_12.1
• Neither Middleware nor WebLogic Home should be used to store
configuration of Domains
• A machine can be used to host more than one WebLogic server or domain
• Domains are physically separate from the product installation on a file-system
Installation
Installer
• Different installers
• Package native installer, Generic (jar, Unix) installer, Zip (~160Mb for development only, supports Mac)
One installer - different install modes
• Graphical mode, Character mode, Silent (scripted) mode
Custom/Selective Installation
• Can choose installation of core
application server only
• Optionally add Admin Console,
Drivers, Examples, UDDI server, and
others
• Web Server plug-ins are now
versioned and distributed separately
Domains
Key Concepts
Installation distinct from Domain configuration
Configuration Wizard
• Wizard that walks you through domain creation off-line
• Cannot be used against a running domain
• Requires a template
• Templates can either be a domain template, an extension template, or a
managed server template
• WLS ships with default template, templates for samples domains, and a
extension template for enabling support for advanced web services
• Customers and layered products can create their own templates

• Created with the domain template builder, or pack command
• Scriptable
• Not well documented or supported, use WLST offline instead
Domain Configuration
Distribution
• If a WebLogic domain spans multiple physical machines, the
configuration needs to be distributed so that managed
servers can be started on these machines
• Utilities are provided with WebLogic to help with this:

• Pack – creates an template archive from a domain directory
• Unpack – creates a domain directory from a template archive
WebLogic Domain Structure
Domain Configuration Wizard
• Graphical or Character mode
• Silent mode no longer supported – use
WLST instead (far more flexible)
• Configure, servers, clusters, addresses,
ports, machines, data-sources, JMS
modules and many others
• Default templates provided (eg. Basic
WLS Domain Template) or choose own
custom template
RUN: <wlhome>/common/bin/config.sh (or .cmd)
Domain Directory
Domain name
Start and stop
scripts
Root configuration for
the domain
Configuration files for

WLDF, JDBC, JMS, and
Security
Pending configuration
changes
Subdirectory for each Managed
Server in the domain
Server Start
Many Options
• Supplied Command Line Scripts
• Admin Server: <domain>/bin/startWebLogic.sh
• Managed Server: <domain>/bin/startManagedWebLogic.sh MngdSrvr t3://admin-
host:adminport
• Server/JVM start-up parameters sourced from 'setDomainEnv.sh
• Java Node Manager
• Use Admin Console | Control | Server Start tools (except for Admin Server)
• Use WLST based Node Manager nmStart() function
• Server/JVM start-up parameters obtained from Domain Config (config.xml)
• Operating System Service
• A 'Windows Service' configured using the WebLogic 'beasvc' tool
• Custom start/start/restart init.d script on Unix/Linux
• Custom Scripts
• To run: 'java weblogic.Server .....' with appropriate classpath and start params
Clustering & Node Manager
Key Concepts Cluster 1
Clusters
• A cluster is a group of Managed Admin Svr

Servers working together to provide
increased scalability and reliability
• Scalability: through parallelism
• Reliability/Availability: through
replication and redundancy
• A cluster appears as a single Cluster 2

instance to most clients
Key Concepts
Clusters
• Can have zero or more clusters in a domain
• Clusters can have one or more servers
• Some servers in a domain may not belong to any cluster
Example domain: 2 clusters - 1 for hosting “UI” part of a distributed app,1 for “Business Logic”
Key Concepts
Node Manager
• Two choices
• Java Node Manager (more established)
• Script (SSH) Node Manager (introduced in WLS 9) • Start/Stop servers remotely
• Small 'agent' process running on
host machine (Java NM)
• Looks after one or more WLS
instances on the physical
machine
• Server health monitoring
• Automatic server re-start upon
failure
• Required for server and service
migration (see later)
Node Manager
• Optional process running on a physical server that enables

you to start, stop, suspend, and restart WebLogic Server
instances remotely
• Runs on each physical server that hosts WebLogic Server
instances that you want to control with Node Manager
• Registered with many domains. Can start any server instance
that resides on the same physical server
• Required to start/stop servers using the Administration
Console
Node Manager & WebLogic
Start/Stop WebLogic Managed Servers Remotely
•Two choices
• Start/Stop servers remotely via:
•Java Node Manager (more established)
• Admin Console
•Script (SSH) Node Manager • JMX
• Command Shell
• ANT / WLST
• Small 'agent' process running on
host machine (Java NM)
• Supports multiple domains
• Looks after one or more WLS
instances on the physical
machine
• Server health monitoring
• Automatic server re-start upon
failure
Node Manager & Coherence (New in 11gR1!)
Start/Stop Coherence Servers Remotely
• Easily configure and

start Coherence
servers and clusters
remotely
• One cohesive strategy

for managing
WebLogic and
Coherence server
uptime
Work Managers
WebLogic Server Work Managers
Core Principles
• Work Prioritization
• Applications define resource requirements via meta-data they can relate to, rather than low-level
technical constructs (thread counts)
• User-specific SLAs can be defined
• Thread Pool Management

• Applications should not have to configure and maintain thread pools
• WLS manages this internally and automatically
• Without necessarily requiring Administrator configuration and sizing input
• Overload Protection
• Standardized mechanism to respond to overload conditions
WLS Work Management
Key Components
• New Thread Pool Implementation
• Single internally managed thread pool and priority-based request queue service all application requests
• Request “Priority” dynamic and internally computed to meet application-defined goals
• Thread Count Self-Tuning

• Self-tuning thread pool monitors overall throughput every two seconds
• Present thread count, measured throughput, and past history determines if thread count needs to
change
• New threads automatically added/removed as needed
• Benefits Administrators and Operators - no need to conduct tedious performance testing or
guesswork just to pick a static thread pool size that does not adapt to changing workloads
WLS Work Management
Key Components
• Work Managers
• Runtime abstraction used by applications to define resource requirements
• Work Manager Components
• Request Class
• Fair-Share – desired share of server resources for app
• Response Time –desired app response time
• Context Based – user-specific SLAs
• Minimum Thread Constraint
• Maximum Thread Constraint
• Capacity
• Specified in application descriptor (weblogic.xml, weblogic-ejb.xml, weblogic-application.xml)
• Can be accessed programmatically via CommonJ API – JSR-237
Fair Share
Work Manager Examples
• Desired share of server resources
• Thread usage become higher as fair share number increases
• Fair shares are relative to other fair shares defined in the system
<work-manager>
<name>highfairshare_workmanager</name>
<fair-share-request-class>
<name>high_fairshare</name>
<fair-share>80</fair-share>
</fair-share-request-class>
</work-manager>
Response Time Goal
• Desired response-time goal in milliseconds
• Response-time goals relative to other response goals and fair shares
• Workload is distributed to applications based on the ratio of their Fair Share.
• Two applications each set at 80 would result in each getting ~50% of the CPU
<work-manager>
<name>highfairshare_workmanager</name>
<fair-share-request-class>
<name>high_fairshare</name>
<fair-share>80</fair-share>
</fair-share-request-class>
</work-manager>
Context Based
• Currently look at security name and group of user submitting the request
<work-manager> <name>context_workmanager</name>
<context-request-class>
<name>test_context</name>
<context-case>
<user-name>platinum_user</user-name>
<request-class-name>high_fairshare</request-class-name>
</context-case>
<context-case>
<user-name>evaluation_user</user-name>
<request-class-name>low_fairshare</request-class-name>
</context-case>
</context-request-class>
</work-manager>
How to use Work Managers
• Coarse Grained
• Target at the entire server (“default” Work Manager)
• Target entire applications or modules - e.g. weblogic.xml
<wl-dispatch-policy>myAppWorkManager</wl-dispatch-policy>
• Fine Grained
• Target individual JSPs, Servlets, EJBs, MDBs
<servlet> ...
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>myCustomWorkManager</param-value> ...
• Programmatically via JNDI lookup

InitialContext ic = new InitialContext();
commonj.work.WorkManager wm =
(commonj.work.WorkManager)ic.lookup("java:comp/env/wm/myWM");
Basic JDBC
JDBC Overview
 The Java Database Connectivity (JDBC) specification:

– Is a platform and vendor-independent mechanism for accessing and updating a
database
– Provides transparency from proprietary vendor issues
– Requires the use of a driver
 JDBC drivers are supplied by WebLogic Server or by your database vendor.
JDBC Data Sources
 Enable database connectivity to be managed by the application server
 Are obtained by applications from the server’s JNDI tree
 Use a dynamic pool of reusable database connections
Data Source Scope
 Each data source configuration or “module” is persisted as a separate XML

document.
 The system modules that are created with the console or WLST are:
– Stored in the domain’s config/jdbc directory
– Available to all applications in the domain
 Application-specific modules are:

– Deployed as part of Java Platform, Enterprise Edition (Java
EE) enterprise applications
– Accessible only by the containing application
Multi-Tier Architecture
 In the multi-tier model, commands are

sent to a “middle tier” of services,
which then sends the commands to
the DBMS.
 The DBMS processes the commands

and sends the results back to the
middle tier, which then sends them to
the client.
WebLogic JDBC Drivers
 Oracle and third-party drivers are included in the WLS installation for many
popular database products:
– Oracle 9i, 10g, 11g and 12c
– Sybase Adaptive Server
– Microsoft SQL Server
– IBM DB2
– Informix
– MySQL
– PointBase
 By default, these drivers are added to the server’s classpath.
What Is a Connection Pool?
 A connection pool is a group of ready-to-use database connections associated

with a data source.
 Connection pools:
– Are created at Oracle WebLogic Server startup
– Can be administered using the Administration Console
– Can be dynamically resized to accommodate increasing or decreasing load
JDBC Connection Pooling
Benefits of Connection Pools
 The following are some advantages of connection pooling:

– Connection time and overhead are saved by using an existing database
connection.
– It facilitates easier management because connection information is managed in

one location.
– The number of connections to a database can be controlled.
– The DBMS can be changed without the application developer having to modify
the underlying code.
 A connection pool allows an application to “borrow” a DBMS connection.
Modular Configuration and Deployment of
JDBC Resources
 The JDBC configurations in WebLogic Server are stored in XML documents:
– All JDBC configurations must conform to the new weblogic-jdbc.xsd schema.
– IDEs and other tools can validate the JDBC modules based on the schema.
 You create and manage JDBC resources either as system modules or as

application modules.
 The JDBC application modules are a WLS-specific extension of Java EE

modules and can be deployed either within a Java EE application or as stand-
alone modules.
How Data Source Connection Pools Are Used
 A client retrieves a data source through a JNDI lookup and uses it to obtain a
database connection.
Creating a Data Source Using the Administration Console
Data Source Connection Properties
Test Configuration
Connection Pool Configuration
Connection Pool Advanced
Targeting a Data Source
JDBC URLs
Database locations are specified using a JDBC Uniform

Resource Locator (URL).
 Example 1:
– This URL specifies that the oracle:thin subprotocol
should be used to connect to an Oracle Database:
 Example 2:
– This URL can be used to access a PointBase database:
Monitoring and Testing a Data Source
Connection Pooling
 Connection creation is expensive.
 For applications that consistently involve heavy database traffic:

– Determine the optimal Maximum Capacity of a data source
experimentally
– Set the Initial Capacity and Maximum Capacity to the same value
 For applications whose peak database load is periodic or intermittent:

– Use different values for initial and maximum sizes.
– Tune the Capacity Increment and Shrink Frequency based on the speed at
which the load changes.
The preceding is intended to outline our general product
direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions.
The development, release, and timing of any features or
functionality described for Oracle’s products remains at the
sole discretion of Oracle.

WLS 12c IS - WLS 12c Fundamentals

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WLS 12c IS - WLS 12c Fundamentals

Uploaded by

Copyright:

Available Formats

For Oracle employees and authorized partners only. Do not distribute to third parties.

© 2012 Oracle Corporation – Proprietary and Confidential

The following is intended to outline our general product

Oracle WebLogic Server 12c

• Administration Server - central configuration

• Managed Server - Instance that hosts

• Cluster - group of managed servers to provide

• Node Manager - per-machine process used to

• Graphical interface to configure, manage, monitor a domain

• The Administration Server hosts the Administration Console

• Open the Administration Console with the following URL:

• The Administration Console application deploys lazily

• For production use, we recommend not hosting

and resources needed by those JMS Queue

applications - The real work horses in a JDBC Pool

• Java Virtual Machines (JVMs) 1.1 Plugins

64-bit only for production

• Customers and layered products can create their own templates

• Utilities are provided with WebLogic to help with this:

RUN: <wlhome>/common/bin/config.sh (or .cmd)

Configuration files for

• A cluster is a group of Managed Admin Svr

• A cluster appears as a single Cluster 2

• Optional process running on a physical server that enables

• Easily configure and

• One cohesive strategy

• Thread Pool Management

• Thread Count Self-Tuning

• Runtime abstraction used by applications to define resource requirements

• Work Manager Components

• Fair-Share – desired share of server resources for app

• Response Time –desired app response time

• Context Based – user-specific SLAs

• Minimum Thread Constraint

• Maximum Thread Constraint

• Specified in application descriptor (weblogic.xml, weblogic-ejb.xml, weblogic-application.xml)

• Can be accessed programmatically via CommonJ API – JSR-237

• Thread usage become higher as fair share number increases

• Response-time goals relative to other response goals and fair shares

• Workload is distributed to applications based on the ratio of their Fair Share.

• Programmatically via JNDI lookup

 The Java Database Connectivity (JDBC) specification:

 Enable database connectivity to be managed by the application server

 Are obtained by applications from the server’s JNDI tree

 Use a dynamic pool of reusable database connections

 Each data source configuration or “module” is persisted as a separate XML

 Application-specific modules are:

 In the multi-tier model, commands are

 The DBMS processes the commands

 By default, these drivers are added to the server’s classpath.

 A connection pool is a group of ready-to-use database connections associated

 The following are some advantages of connection pooling:

– It facilitates easier management because connection information is managed in

– The number of connections to a database can be controlled.

 A connection pool allows an application to “borrow” a DBMS connection.

 You create and manage JDBC resources either as system modules or as

 The JDBC application modules are a WLS-specific extension of Java EE

Database locations are specified using a JDBC Uniform

 Connection creation is expensive.

 For applications that consistently involve heavy database traffic:

 For applications whose peak database load is periodic or intermittent:

You might also like