1. Introduction to WebLogic-by Vishal Srivastava

2. Administration ToolsTuning Parameters and Best PracticesWebLogicand Its ArchitectureBasic Concepts of WebLogic1234Agenda vertical 3. WebLogic& Its Architecture 4. WebLogicTengah: 1st version of weblogicwas released in 1997In 1998 Weblogicgot name as webLogicServer when WebLogicwas acquired by BEA. Weblogic4.0 10.0 was release by BEAOracle acquired BEA in 2008 and released WebLogic10.3 in 2008. [WebLogic= Bea weblogicand Oracle application Server]WebLogicWebLogicis 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 WebLogicDomainsServer/ Admin ServerManaged ServerClusterNode manager 7. DomainDomain 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 typesDomain with Managed ServersStandalone Server DomainAdministration 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 InstanceAll 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. ClusterGroup of WebLogicManaged Server Instances that work together to provide high availability and scalability for applications is called cluster.Benefits of ClusteringScalabilityHigh-AvailabilityKey Capabilities of ClustersLoad BalancingApplication FailoverNode ManagerNode Manager is a Java utility that runs as separate process from WebLogicServer. 9. Administration tools 10. Administration ConsoleAdmin console-Browser-based tool for configuring andmonitoring 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 taskCreating Domains Using WLST OfflineManaging the Server Life CycleConfiguring Existing DomainsGetting Runtime Information 13. Tuning Parameters and Best Practices 14. Top Tuning Recommendations for WebLogicServerUnderstand Your Performance ObjectivesTune the Operating SystemOptimize Your DatabaseIdentify the Best JVM SettingsTune WebLogicServer Performance ParametersMonitor Disk and CPU UtilizationMonitor Data Transfers Across the NetworkCheck For Frequent Standard I/O or LoggingLocate Bottlenecks in Your ApplicationsTune Your Application 15. Top Tuning Recommendations for WebLogicServerTune Pool SizesProvide pool sizes (such as pools for JDBC connections, Stateless Session EJBs, and MDBs) that maximize concurrency for the expected thread utilizationUse the Prepared Statement CacheThe 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 BufferingTune the number of connection requests that a WebLogicServer instance accepts before refusing additional requests.Tune the Chunk SizeA 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 InterfacesUse 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-cachingThis 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 SessionsTune Messaging Applications 17. Tools for Performance AnalysisJProbeProfilerProvide the capability to detect performance bottlenecks, find and fix memory leaks, perform code coverage, and other metrics.Borland OptimizeitProfilera performance debugging tool 18. Thanks