Server Day 2009: Oracle/Bea Fusion Middleware by Paolo Ramasso
5 likes727 views
The document discusses Oracle WebLogic Server and Oracle WebLogic Suite, highlighting the application grid and its components such as administration servers, node managers, and lightweight installations. It explains features like self-tuning, workload management, high availability, and integration with Oracle RAC, emphasizing scalability, reliability, and performance benefits. Additionally, it covers deployment options, diagnostics, and lifecycle management for enterprise applications.
Server Day 2009: Oracle/Bea Fusion Middleware by Paolo Ramasso
- 3. Application Grid with Oracle Fusion Middleware
- 4. A New Approach: Application Grid Grid computing at the middleware layer Custom Packaged C/C++/ SOA Svc Legacy App App COBOL Application Grid Flexible High Quality Efficiency Scaling of Service 06/17/09 ©2008 Oracle Corporation 4
- 5. Elements of the Application Grid Comprehensive, hotpluggable, preintegrated Enterprise Manager WebLogic Tuxedo Server WebLogic Operations Control Coherence + AD4J JRockit 06/17/09 ©2008 Oracle Corporation 5
- 6. JRockit Managing GC Latency Traditional Java 120 JRockit Real Time 105 90 75 60 45 30 15 0 0 2000 4000 6000 8000 10000 12000 14000 16000 18000 During Low Load: GC spikes and occasional timeouts visible 120 105 90 75 60 45 30 JRRT Makes garbage collection deterministic. 15 0 Allowing for the guarantee of SLAs. 0 2000 4000 6000 8000 10000 12000 14000 16000 18000 During High Load: GC pauses can result in unacceptable response times
- 7. Oracle Weblogic Server
- 8. WebLogic Server 10.3 • Hardened release of the WebLogic 10.x release cycle • Recommended WLS 8.1 and WLS 9.2 upgrade path • Upgrade to mature release, fully compliant with Oracle requirements • Foundation release of Fusion Middleware 11 R1 • Fusion Middleware 11 R1 will do small incremental maintenance changes to core WebLogic Server
- 9. Architectural View: Domain • What is it? • a logically related group of WebLogic Server instances that you manage from a single set of configuration artifacts. • What’s in a domain? • Servers • Clusters of servers • Rules: • All WebLogic Server instances within the same domain must be at the same major and minor version. • Servers within a domain can be at different Maintenance Pack levels as config.xml long as the Administration Server is at the same Maintenance Pack Level or higher than its Managed Servers.
- 10. Architectural View: Administration Server • What is it? • Central configuration controller for the entire Managed Servers domain • What else does it do? • Hosts the Administration Console • Enables you to start and stop servers from a Admin Server central location • Enables you to migrate servers and services within the domain config.xml • Enables you to deploy applications within the domain • Guidelines: • There must be exactly one* Administration Server in domain • An Administration Server controls only one domain. • For production use, we recommend not hosting application logic or resources on the Administration Server Admin Console *The Administration Server does not need to run at all times, but is required for making configuration and deployment changes to a running domain.
- 11. Architectural View: Node Manager • Utility/process running on a physical server that enables you to start, stop, suspend, and restart WebLogic Server instances remotely • Must run on each physical server that hosts WebLogic Server instances that you want to control with Node Manager • Not associated with a domain. Can start any server instance that resides on the same physical server. • Optional, but required to start/stop servers using the Administration Console • Required for Whole Server Migration and for some configurations of Automatic Service Migration Admin Server Managed Server Node Manager
- 13. Lightweight WebLogic Server • Lightweight installers • “Core” WLS install option, addons (JDKs, etc) optional • Reduce download and install time, installation footprint • Optional service startup • Start WebApp container without starting EJB, JMS, JCA services • Provide developer flexibility
- 14. Production Redeployment Side by Side Deployment • Multiple application versions can co exist • New client requests are routed to active version; Existing client requests can finish up with existing version • Automatic Retirement Policy: Graceful, Timeout • Test application version before opening up for business • Rollback to previous application version • Two versions of the application can be active at any given point of time
- 15. Integration with Oracle RAC Oracle RAC Support Use WLS MultiDataSources • Fast failover upon node failure • Loadbalancing or Failover algorithm • Periodic health check of connections
- 16. HighValue and Unique features BestofBreed Messaging (JMS) Engine • Unit of Order/Unit of Work • Strict Ordering of Message processing • Distributed Destinations • Highly Available JMS Destinations across a Cluster • StoreandForward (SAF)/Client SAF • Asynchronous Reliable Messaging across WAN • Integrated JTA (XA) Transaction Management
- 17. SelfTuning and Work Managers WebLogic's SelfTuning Thread Pool Network Socket Handlers (“Muxers”) Self Tuning • Active Thread Pool • Standby • Stuck • Hogging Request Queue Asynchronously dispatched work 1. Monitor rate of from WebLogic kernel, subsystem request processing or application 2. Adjust thread pool size accordingly
- 18. SelfTuning and Work Managers Configurable Work Managers • Every application has its own Work Manager • based on the 'global' 'fairshare' work manager by default • Can explicitly configure a new Work Manager • apply to one or more specific applications and even individual resources • Each work manager can have a mix of the following configuration elements.... REQUEST CLASS ELEMENT CONSTRAINT ELEMENT TRIGGER ELEMENT • Fair Share (default) • Minimum Threads (active) • Shutdown Trigger • Response Time (goal) • Maximum Threads • Context based (per • Capacity (threshold for user/group) rejection)
- 19. Clustering and High Availability Transparent Load Balancing and Failover HTTP, EJB, JNDI and JMS clients • HTTP requires Hardware Load Balancer or Web Server Proxy • EJB/JNDI/JMS client 'stubs' are automatically cluster aware
- 20. Quality of Service Meet the Most Demanding Requirements for “RASP” • Reliability • Proven quality in enterprise environments – “it just works” • Transactional integrity, reliable messaging, Oracle RAC • Availability • Maintain app/service availability to end users • Tolerate planned and unplanned events • Scalability • Expand and add system resources as required • Millions of users and thousands of systems • Performance • Aggregate throughput of apps/services • Low, predictable latency
- 21. Oracle Coherence Distributed Data Grid
- 22. Oracle Coherence Data Grid Distributed in Memory Data Management Enterprise Real Time Web Applications Clients Services • Provides a reliable data tier Data Services with a single, consistent view of data Oracle Coherence • Enables dynamic data Data Grid partitioning including fault tolerance and load balancing • Ensures that data capacity scales with processing Databases Mainframes Web Services capacity
- 23. The Coherence Approach… • Traditional scaleout approaches limit • Scalability, Availability, Reliability and Performance • In Coherence… • Servers share responsibilities (health, services, data…) • No SPoB • No SPoF • Massively scalable by design • Logically servers form a “mesh” • No Masters / Slaves etc. • Members work together as a team
- 24. Coherence*Web: Session State Management Web Application Coherence Web Java EE or Servlet Application Container State Router Web Application Coherence Web Web Load Java EE or Servlet Application Tier Balanced Container State Clustered Oracle, WebLogic, WebSphere, JBoss, Tomcat In Memory Coherence Data Grid for Session State
- 26. WebLogic Operations Control Centralized Governance and Control Define services and operational policies, rules, & Deploy & SLAs manage apps & services in resource Manually or pools autoadjust resource Actively allocations monitor all across apps deployments against policy
- 28. Competitive Advantage indepth Application view Diagnose & Root Cause Monitor The Platform 24X7 Memory Analysis AD4J Console DB Activity JVM Activity Diagnose & Memory Leak Monitoring Monitoring Root Cause Analysis AD4J AD4J Console AD4J Console Repository Java Classes JSPs NOC App Support & QA DEV
- 30. WebLogic Suite | Reducing Lifecycle Costs Deployment and Configuration Monitoring and • WLST Diagnostics • Enterprise Manager Configuration Packs • WebLogic Diagnostic Developer Productivity Framework • Sidebyside deployment • FastSwap • Application testing • Split developer directory • Componentized installer • Enterprise Manager Diagnostics Pack • Support for Spring • JRockit Mission Control WebLogic Server Troubleshooting and Tuning • WebLogic Diagnostic Framework • Enterprise Manger Capacity Diagnostics Packs Management, • JRockit Mission Disaster Recovery Control • Server / service migration • Policydriven Ongoing Administration overload protection • MAN, WAN session replication • Enterprise Manager Provisioning Pack • Policydriven resource management • Multidomain, multiversion management • Future: appliance builders