WebLogic Suite & Exalogic Deep Dive Oracle Partner iDay Jeffrey West Application Grid Product Management Oracle Strategy Hardware and Software Engineered to work Together • Deliver a complete, open, integrated stack of hardware, infrastructure, database, middleware, and business applications • Exploit processor, systems, storage, and networking trends to deliver breakthrough innovations by combining Oracle software with Sun hardware • Integrate components of Oracle‟s software stack to provide unique value to customers 2 2 Middleware and Java in Oracle’s Strategy • Comprehensive foundation for building and running custom and packaged applications – Extremely well integrated – Industry-leading reliability and performance – Unified development and management – Basis for Oracle Fusion Applications • Built with and for Java technology 3 Application Server Platform at Oracle Strategically Centered Around WebLogic Server Custom Packaged SOA Cloud FMW App App Service Service Service Cloud Application Foundation GlassFish Coherence Developer WebLogic Enterprise Tools Server Management Java SE Most complete Best integration platform for #1 in Performance AND with Oracle cloud time-to-market stack 4 WebLogic Areas of Focus Lifecycle • Seamless install, upgrade, patching, provisioning, diagnostics across Fusion Management Middleware and Fusion Applications Enterprise • Mission critical database, messaging, security, Web, services, caching, Runtime Services transactional middleware infrastructure Platform • Formalized large scale, HA operations, Operations virtualization, Exalogic and Cloud solutions Lightweight • Standards based, highly productive Java Application development with Java EE 6 Development 5 WLS 11g Innovations 6 WebLogic Suite Product Update Rolling Updates in 11g R1 Patchsets Spring/ Java EE 6 • Developer Experience Jan 2011 WebLogic RAC Integration • Active GridLink for RAC Jan 2011 Partitioned Distributed • Messaging Jan 2011 Topics 3 Coherence 2 1 • ActiveCache April 2010 Integration April 2010 Assembly • Virtualization Builder • Operations April 2010 Flight Recorder, EM 11g • Exalogic Elastic Cloud Dec 2010 Hardware/ Software Optimized 7 WebLogic Unique Features 8 WebLogic Suite Unique Features Features available on WebLogic Messaging Persistence Diagnostics Development • WebLogic JMS • TopLink & EclipseLink • WebLogic Diagnostic • Fast Swap Extensions • Transaction Manager Frameworks • OEPE • JMS Performance • High Performance • JRMC & JRFR • Netbeans • Foundation for FMW • EM 11g Java Advanced • Web Services Interoperability Monitoring Advanced: Buffered, • JMS C/Net Client Asynchronous, Conversational, JMS transport • Assembly Builder • ZIP Distribution • Mac OS Support High Availability Operations Leveraging Performance Open Source • SPECjAppServer • Web Tier & HW LB • WebLogic Console Benchmarks • Side by Side • WLST & Recording • Spring Integration • SPECJBB Benchmarks Deployments • WebLogic Templates • JPA Integration • Multiple Vendors & • Whole Server Migration • WebLogic Configuration • Active Cache for JPA Topologies Supported • Service Migration Wizards (2nd level cache) • Jrockit Real Time • Rolling Upgrade • Vertical & Horizontal • ExaLogic • Data Guard • Self Tuning (WebLogic Optimizations Certification & Jrockit) • RMAN Certification • OVF Deployer/Control • Cloud Management Pack 9 Messaging 10 Messaging Infrastructure Foundation JMS for Java EE, SOA and Applications Java EE/ISV SOA Applications C, .NET Apps Suite Clients WebLogic Server JMS WebLogic Server File Database Store and Bridging Oracle AQ Persistence Persistence Forward (OFM 11) File Database SAF Bridge AQ 11 Messaging Infrastructure Designed to Scale to the Most Complex SOA Integrations • Unit of Order Messages red and grey have separate UOO – Messages tagged with same Unit of Order (UOO) 1 2 3 4 5 6 7 8 9 are processed in order – Stronger ordering semantics than the JMS MDB 1 MDB 2 MDB 3 specification Message 3/4 not processed until 1/2 processed • Unit of Work – Messages are grouped with a group identifier 1 MDB 1 – Messages at final destination become available Producer MDB 3 only when entire group arrives 2 3 2 1 3 MDB 2 • Store and Forward Messaging WebLogic WebLogic – Store messages on local server and forward to Forward when remote server when available JMS Server Target Available JMS Server – Store and forward for clients to server and server to server • Distributed Destinations – All queues and topics in a cluster appear as a JMS Server JMS Server single logical destination to clients Client – Provides high availability and scalability; parallel JMS Server JMS Server processing and load balancing Logical Destination WebLogic Cluster 12 Messaging Infrastructure Performance: Meets the Most Rigorous Throughput Req Persistent Queuing • WebLogic 10 JMS is fast 7000 6000 – Up to 10X faster than previous WLS 5000 releases 4000 – Re-written file store and disk scheduling 3000 2000 extremely fast 1000 – Database integration optimized with JDBC 0 and batching optimizations 1 2 4 8 16 32 64 WL 100byte EMS 100byte WL 4K EMS 4K • WebLogic JMS consistently beats 1400 pure plays 1200 1000 – Synchronous writes 3X-6X faster than 800 competitors 600 – Message size 25%-4X faster for messages 400 between 1K->512K than competitors 200 0 0001K 0002K 0004K 0008K 0016K 0032K 0064K 0128K 0256K 0512K 1024K WL Persist EMS Persist Persistent Message Versus Size Oracle Confidential 13 Messaging WebLogic Partitioned Distributed Destinations 3 • Distributed 2 Destination is 1 created with physical members Publish on each server and Connection accessed with a Factory global JNDI Name JNDI: jms/MyApp/Queue1 DT Member DT Member DT Member • Messages sent to 1 2 3 an individual Member topic are jms-server-1 jms-server-2 jms-server-3 NOT forwarded to other members Subscription Subscription Subscription MDB / MDB / MDB / • Each MDB pool on Consumer Consumer Consumer a single server receives a copy of Server 1 Server 2 Server 3 the message Cluster 14 Messaging Oracle AQ JMS Integration • Enables migration and interop with AQ JMS apps • Leverages new JNDI provider in AQ JMS client • Uses standard WebLogic integration features – Foreign JMS Servers, JDBC Data Sources, MDBs • Fully supports JTA transactions Oracle FMW 10gR3 Oracle FMW 11gR1 OC4J/OAS, BPEL PM, SOA Suite… WLS, BPEL PM, SOA Suite… AQ client Foreign AQ AQ JMS MDB MDB JNDI provider Server OC4J JDBC WLS JDBC Oracle AQ DBMS Store 15 Persistence & RAC Connectivity 16 Persistence Services High Performance Transaction Manager Java Java EE SCA Spring Ships WLS TX Clients Applications Applications Integration Transaction Coordinator Transaction Recovery Manager Global Transaction HA Local Transactions Transaction Service/Server Migration Inter Domain Server Interposed Logging Last Tx Log Administrative Transactions Transaction Manager Resource Transaction (Shared Operations (JMX) Operations Storage) WebLogic Transaction Service (JTA/JTS) WebLogic Server DB Resource 3rd Party (JMS, DB…) 3rd Party (Vitria BW…) Other WLS Instances Manager Resource Manager Transaction Manager (Global, Local & Tx Propagation) (Global, Local Tx) (Global, Local Tx ) (JTS Tx Interoperability ) 17 Persistence Services Infrastructure Integrated with Eclipse Java Persistence Platform - TopLink OSGI Java Spring Applications ORM OXM EIS SDO XML Database (JPA) (JAXB) Relational Web Services JDBC Coherence JCA Eclipse Java Persistence Platform WebLogic Server Databases Data Hub XML Data Packaged Apps Legacy Systems 18 WebLogic and RAC Highest Availability and Performance • Long History, Wide Adoption WebLogic Cluster • Highest Availability – For Mission Critical Applications – Transaction Recovery – Fast Connection Failover OracleORACLE RAC RAC ClusterCluster • Highest Performance – Load Balancing – Connection Affinity RAC 1 RAC 2 RAC 3 • GridLink Data Source – Easier Configuration for RAC RAC Instances 19 Complete Resiliency with WebLogic Server Active GridLink for RAC WebLogic Domain WebLogic Cluster Managed Managed Server1 Server 2 Datasource No Service Interruption! Active GridLink Connection Data Source Pool RAC Node Taken Offline! What will happen with WebLogic applications when a RAC Node is taken Oracle RAC Database offline? RAC Node 1 RAC Node 2 • No user downtime • Zero wait time for WebLogic connection recovery • Connect pool automatically and rapidly rebalances • No application changes required RAC Node 3 RAC Node 4 20 Active GridLink: Runtime Connection Load Balancing Oracle Oracle Oracle Oracle WebLogic RAC WebLogic RAC Server Server Server Server RAC 1 RAC 1 Connections 90% Connections for RAC Node 1 for RAC Node 1 35% Connections RAC 2 Connections RAC 2 for RAC Node 2 for RAC Node 2 Thin Thin 40% JDBC 5% High JDBC Utilization Connections on RAC Connections Node 1 for RAC Node 3 RAC 3 for RAC Node 3 RAC 3 Oracle WebLogic Workload Oracle WebLogic 5% Balanced 25% Data Source Across Data Source Connection Pool RAC Instance Cluster Connection Pool RAC Instance Notification Notification Notification Notification Service Service Service Service Channel for RAC Node Status Notifications Channel for RAC Node Status Notifications 21 Active GridLink: Fast Connection Failover Connecting WebLogic Server to Oracle RAC Oracle Oracle Oracle Oracle WebLogic RAC WebLogic RAC Server Server Server Server RAC 1 RAC 1 Invalid Entries Invalid Entries for RAC Node 1 for RAC Node 1 X Pool Entries RAC 2 Pool Entries RAC 2 for RAC Node 2 Thin for RAC Node 2 Thin JDBC RAC JDBC Node 1 Pool Entries failure Pool Entries causes for RAC Node 3 for RAC Node 3