1. Introduction to WebLogic
-by Vishal Srivastava

2. Administration Tools
Tuning Parameters and Best Practices
WebLogicand Its Architecture
Basic Concepts of WebLogic
1
2
3
4
Agenda vertical

3. WebLogic& Its Architecture

4. •WebLogicTengah: 1st version of weblogicwas released in 1997
•In 1998 Weblogicgot name as “webLogicServer” when WebLogicwas acquired by BEA. Weblogic4.0 –10.0 was release by BEA
•Oracle acquired BEA in 2008 and released WebLogic10.3 in 2008. [WebLogic= Bea weblogicand Oracle application Server]
WebLogic
WebLogicis 1stapplication server that was developed by WebLogicand currently hold nearly 43% market hold in Application server industry.

5. Architecture of WebLogic

6. Basic Concepts of WebLogic
Domains
Server/ Admin Server
Managed Server
Cluster
Node manager

7. •Domain
Domain is logical grouping of resources and services and consist ofAdministration Server,Managed Serverandcluster.There can only be one administration Server in domain andzero to NManaged Server.
•Common domain types
•Domain with Managed Servers
•Standalone Server Domain
•Administration Server (Admin server)
Each WebLogicServer domain must have one server instance that acts as the Administration Server. Admin server can be seensas central command and control unit that help Sys Admin to configure new resources, or make chagesand monitor resources within a domain.
•Managed Instance
All other instances within a domain (other than Admin instance) are called Managed Server. Managed Servers host the components and associated resources that constitute your applications

8. •Cluster
Group of WebLogicManaged Server Instances that work together to provide high availability and scalability for applications is called cluster.
•Benefits of Clustering
•Scalability
•High-Availability
•Key Capabilities of Clusters
•Load Balancing
•Application Failover
•Node Manager
Node Manager is a Java utility that runs as separate process from WebLogicServer.

9. Administration tools

10. Administration Console
•Admin console
-Browser-based tool for configuring and
monitoring domains,
Services,settingsecurity,deployingapplications and controlling servers**

11. Dashboard

12. WLST (WebLogicScripting Tool)
Jythonbased command-line scripting environment that one can use to n number of different task
•Creating Domains Using WLST Offline
•Managing the Server Life Cycle
•Configuring Existing Domains
•Getting Runtime Information

13. Tuning Parameters and Best Practices

14. Top Tuning Recommendations for WebLogicServer
•Understand Your Performance Objectives
•Tune the Operating System
•Optimize Your Database
•Identify the Best JVM Settings
•Tune WebLogicServer Performance Parameters
•Monitor Disk and CPU Utilization
•Monitor Data Transfers Across the Network
•Check For Frequent Standard I/O or Logging
•Locate Bottlenecks in Your Applications
•Tune Your Application

15. Top Tuning Recommendations for WebLogicServer
•Tune Pool Sizes
Provide pool sizes (such as pools for JDBC connections, Stateless Session EJBs, and MDBs) that maximize concurrency for the expected thread utilization
•Use the Prepared Statement Cache
The prepared statement cache keeps compiled SQL statements in memory, thus avoiding a round-trip to the database when the same statement is used later.
•Tune Connection Backlog Buffering
Tune the number of connection requests that a WebLogicServer instance accepts before refusing additional requests.
•Tune the Chunk Size
A chunk is a unit of memory that the WebLogicServer network layer, both on the client and server side, uses to read data from and write data to sockets. A server instance maintains a pool of these chunks. For applications that handle large amounts of data per request, increasing the value on both the client and server sides can boost performance

16. •Use Local Interfaces
Use local-interfaces or use call-by-reference semantics to avoid the overhead of serialization when one EJB calls another or an EJB is called by a servlet/JSP in the same application.
•Use eager-relationship-caching
This feature allows the EJB container to load related beans using a single SQL statement. It improves performance by reducingthe number of database calls to load related beans in transactions when a bean and it's related beans are expected to be used in that transaction.
•Tune HTTP Sessions
•Tune Messaging Applications

17. Tools for Performance Analysis
•JProbeProfiler
Provide the capability to detect performance bottlenecks, find and fix memory leaks, perform code coverage, and other metrics.
•Borland OptimizeitProfiler
a performance debugging tool

18. Thanks