Page 0 Oracle Corporation 2013 DO NOT DISTRIBUTE

Transcription

1 Page 0 Oracle Corporation 2013 DO NOT DISTRIBUTE

2 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 remain at the sole discretion of Oracle. Page 1 Oracle Corporation 2013 DO NOT DISTRIBUTE

3 WebLogic Server Technical Overview & Architecture Venkata Anil Kumar Motamarry CAF Product Management Page 2 Oracle Corporation 2013 DO NOT DISTRIBUTE

4 Cloud Application Foundation

5 Cloud Application Foundation Products WebLogic Server Traffic Director / Web Tier Coherence Virtual Assembly Builder Tuxedo Cloud Application Foundation Deployment Choices Fusion CRM Database Service Private Cloud Fusion HCM Java Service Fusion Talent Data Service Social Network Security Service Public Cloud Page 4 Oracle Corporation 2013 DO NOT DISTRIBUTE

6 Cloud Application Foundation Java Cloud Services & Upcoming Services Developer Services Caching Services Mobile Services Messaging Services Storage Services Identity Services Page 5 Oracle Corporation 2013 DO NOT DISTRIBUTE

7 WebLogic Domain Architecture

8 WebLogic Domain Architecture Overview Load Balancer Load Balancer Domains Machines Admin Server Managed Servers Clusters Node Manager Page 7 Oracle Corporation 2013 DO NOT DISTRIBUTE

9 WebLogic Domain Architecture Single Administration Server for a Domain Page 8 Oracle Corporation 2013 DO NOT DISTRIBUTE

10 WebLogic Domain Architecture Node Manager Small daemon process Start/Stop servers Can kill/restart failed servers Required for Whole Server Migration Java node manager with StartScriptEnabled=true most popular option Relies on domain start scripts to start the server Less configuration required Page 9 Oracle Corporation 2013 DO NOT DISTRIBUTE

11 WebLogic Clustering Architecture

12 WebLogic Clustering Principles Deploy applications and services homogeneously Minimise singletons - every service everywhere Load distribution, not load balancing Expect many service requests No features for grid / partitioning of large problems Minimal interaction between cluster members. Cluster members know their peers' availability through health monitoring No built-in, cluster-wide cache Oracle Coherence HTTP, SOAP Web Services, REST, EJB, JNDI, and JMS clients HTTP and SOAP require Hardware Load Balancer or Web Server Proxy EJB/JNDI/JMS Page 11 Oracle Corporation 2013 DO NOT DISTRIBUTE

13 WebLogic Clustering Protocols WebLogic Server supports 2 clustering protocols Multicast (WLS 4.0+) uses UDP Multicast Unicast (WLS 10.0+) uses TCP Unicast is the default for ease-of-use reasons Works out of the box with virtually any network No extra configuration for clusters that span subnets Easier to troubleshoot TCP issues at the network level Multicast is more scalable Requires a network that supports UDP multicast Requires additional router and WLS configuration for clusters that span subnets Page 12 Oracle Corporation 2013 DO NOT DISTRIBUTE

14 WebLogic Clustering Base Clustering Features Cluster Membership Change Detection Each server maintains its own view of the cluster Server heartbeats Sent by every server every 10 seconds Missing 3 heartbeats in a row will remove the server from the cluster until the next heartbeat is received Peer-to-peer sockets monitored to detect server death JNDI Replication Objects added to a cluster member s JNDI tree are replicated to all servers If the server hosting the object leaves the cluster, the replicated JNDI binding is removed from all servers Special cluster-aware objects (such as EJB stubs) can be bound to the same location on multiple servers Page 13 Oracle Corporation 2013 DO NOT DISTRIBUTE

15 HTTP clustering with a load balancer Http Routing & Session replication HTTP Session-aware routing Relies on load balancer's sticky routing Session replication In-memory replication Alternatives: JDBC, file system, cookie based Page 14 Oracle Corporation 2013 DO NOT DISTRIBUTE

16 HTTP clustering with a web server tier Http Routing & Session replication Web server plug-in advantages: Dynamically adjusts to servers joining and leaving the cluster Good candidate for fire-walled DMZ Page 15 Oracle Corporation 2013 DO NOT DISTRIBUTE

17 JMS Distributed Destinations JMS Routing Logical, cluster wide destinations Implemented using physical queues or topics Service is available everywhere Very easy to configure Basic rules Consumers pinned to queues Queue senders typically round-robin to distribute load Topics broadcast to a subscriber in each server DDs are integral to WebLogic JMS Page 19 Oracle Corporation 2013 DO NOT DISTRIBUTE

18 WebLogic JMS Unit of Order WebLogic JMS Innovation State 1 Msg 1 consumed by MDB 1 Other UOO Red messages unavailable Msg 2 consumed by MDB 2 Other UOO Blue messages unavailable Problem Description Certain apps require strictly ordered processing of messages How this feature works Messages tagged with same Unit of Order (UOO) are processed in order Applies across a cluster, too: messages routed to DD member Concurrency through Multiple UOOs Reduces or eliminates DB lock contention MDB 1 MDB 2 MDB 3 State 2 MDB 1 completes processing message 1 Next UOO Red message becomes available Msg 3 consumed by MDB 3 Other UOO Red messages unavailable MDB 1 MDB 2 MDB 3 Page 20 Oracle Corporation 2013 DO NOT DISTRIBUTE

19 WebLogic JMS Unit of Work WebLogic JMS Innovation Messages are grouped with a group identifier At the final destination, messages become available only when all messages in the group have arrived Messages are reordered as specified by the UOW producer, regardless of the order in which they arrived Messages are received by a single consumer with no gaps between messages in the group Producer 3 2 MDB MDB MDB Page 21 Oracle Corporation 2013 DO NOT DISTRIBUTE

20 WebLogic JMS Store-and-Forward WebLogic Highly Available JMS JMS producers look up a remote destination using a local JNDI reference Messages are stored on the local server and are forwarded to the remote server when the endpoint is available Increases reliability of communication Forwarding between domains, clusters, and servers Preserves message ordering Improvement over Messaging Bridge SAF is faster and more scalable for WLS-WLS connectivity Clusterable Page 22 Oracle Corporation 2013 DO NOT DISTRIBUTE

21 WebLogic JMS Store-and-Forward WebLogic Highly Available JMS The SAF Service should be used when forwarding JMS or WSRM messages between WebLogic Server 9.x or later domains. The SAF service can deliver messages: Between two stand-alone server instances. Between server instances in a cluster. Across two clusters in a domain. Across separate domains. When not to use the SAF service: Forwarding messages to prior releases of WebLogic Server** Interoperating with third-party JMS products (for example, MQSeries) When using temporary destinations with the JMSReplyTo field to return a response to a request. Page 23 Oracle Corporation 2013 DO NOT DISTRIBUTE

22 WebLogic High Availability

23 WebLogic High Availability Administration Server Availability Not part of cluster No automatic failover if host machine dies Not a single point of failure Only needed for monitoring or changing configuration on the fly Managed Servers can continue and even start without it MSI mode (Managed Server Independence) Uses locally cached configuration when Administration Server unavailable Can use a back-up or 'cold' stand-by on another machine Manually re-start Administration Server on new machine No need to migrate old IP address Page 25 Oracle Corporation 2013 DO NOT DISTRIBUTE

24 WebLogic High Availability Cluster Services Replicated services deployed homogeneously to all servers in cluster, enabling transparent fail-over, with state replication where appropriate Pinned services" run on an individual server in the cluster, requiring service migration REPLICATED SERVICES Web Applications EJBs JNDI Tree Distributed JMS Queues and Topics PINNED SERVICES Transaction Manager (one for each server) JMS Stores with persisted queue/topic messages Application Singleton Services Cluster Job Scheduler (cluster wide timer) Page 26 Oracle Corporation 2013 DO NOT DISTRIBUTE

25 WebLogic High Availability Migration Pinned services require migration for recovery In-flight XA transactions (transaction logs) JMS Servers (persisted JMS messages in JMS stores) Cluster aware singletons and job schedulers (typically no local state) Network storage (SAN, dual ported disk) required Migration Strategies Before WLS 9.0, only OOTB migration was manual. Automation required expensive third-party solution (eg. Veritas, Sun Cluster) Now two choices exist, with different pros/cons Service-level Migration Server-level Migration Page 27 Oracle Corporation 2013 DO NOT DISTRIBUTE

26 WebLogic High Availability Automated Whole Server Migration Managed Server 1 Machine 1 Managed Server 2 Machine 2 Automated failure recovery of pinned services using migration, as opposed to fail-over Failed server is re-started on a different machine Requires transition of IP address to new machine Key for maintaining transactional integrity for JMS services WLS 10 also provides automated service-level migration for some services JTA XA Transactions, Singleton Services and Job Scheduler are automated Automation for JMS introduced in 11g Before version 10.3, must always use Whole Server Migration for JMS mixed with XA. Page 28 Oracle Corporation 2013 DO NOT DISTRIBUTE

27 WebLogic High Availability Automated Server Migration Process Migration of IP-Address and Logical Server Admin Server Mngd Server 1 Mngd Server 2 Mngd Server 1 Mngd Server 3 Machine 0 Machine 1 Cluster Detect Failure and Initiate Node M Node M Node M Migration Machine 2 Machine 3 Machine 4 Lease DB Table Current Cluster Master Storage Area Network ( SAN ) Page 29 Oracle Corporation 2013 DO NOT DISTRIBUTE

28 WebLogic High Availability Server Migration Requirements Spare capacity Excess RAM and CPU on existing server host machines, or redundant 'idling' hardware Java or SSH Node Manager Starts servers during migration Migrates floating IP addresses to new physical network devices, Mounts and unmounts shared disks Highly Available Shared Storage (e.g. SAN) Provides access to JMS and JTA persistent stores from other machines Can't use NFS or SMB/CIFS due to atomic write issues * August 2010 update limited NFS supported available with caveats SAN still strongly recommended Network Time Protocol (NTP) WebLogic hosts must be time synchronised Page 30 Oracle Corporation 2013 DO NOT DISTRIBUTE

29 Load Balancer WebLogic State Replication Surviving to a Data Center Failure Domain State Replication Domain Cluster Managed Server 1 State 1 Managed Server 2 State 2 In Memory or Database Backed Asynch or Synch Global Load Balancer MAN State Replication Local Load Balancer Local Load Balancer In Memory Domain Cluster 1 State 1 State 2 Domain Cluster 2 State 3 State 4 Global Load Balancer WAN State Replication Local Load Balancer Local Load Balancer Domain Cluster 1 State 1 State 2 Domain Cluster 2 State 3 State 4 Database Backed Asynch Page 32 Oracle Corporation 2013 DO NOT DISTRIBUTE

30 Oracle Database Service Oracle Notification Service Node Manager Active GridLink for RAC in and 12c Extreme performance and transparent failover Simpler Configuration: single data source Event-Based Model (ONS and FAN) for Adaptive Pool Management SCAN Support Fast Connection Failover Runtime Connection Load Balancing Affinities for Connection Routing (XA, Session, Data) Data Guard Support RAC One Node Support WebLogic Domain WebLogic Cluster Managed Server1 Managed Server2 Oracle Database RAC Node 1 Datasource GridLink Data Source RAC Aware Connection Pool RAC Node 2 RAC Node 3 RAC Node 4 Page 33 Oracle Corporation 2013 DO NOT DISTRIBUTE

31 Cluster with Moving Average (ms) AGL4R Web Session Affinity Performance 250 Cluster Wait Time - Random Workload 25 Threads - 20ms think time 100 Total Connections Affinity Enabled Affinity Disabled second interval Page 34 Oracle Corporation 2013 DO NOT DISTRIBUTE

32 WebLogic Production Redeployment Side by Side Deployment Multiple application versions can coexist 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 Page 35 Oracle Corporation 2013 DO NOT DISTRIBUTE

33 WebLogic Server Performance

34 WebLogic Performance T3 Protocol WebLogic Protocol High-speed binary streaming 'over-the-wire' protocol Insecure (T3) or SSL Secured (T3S) transport Provider URL: t3://ip-address:port Protocol for communication between Java programs WebLogic server to server, client to server A server instance keeps track of each JVM it connects to and maintains that single long-lived T3 connection to carry all traffic to the JVM Continued connection availability monitored via periodic heartbeats A peer Server/JVM is called a 'RJVM' Used by default for RMI and thus EJB can be switched to IIOP instead for CORBA clients - no code changes required Page 37 Oracle Corporation 2013 DO NOT DISTRIBUTE

35 WebLogic Performance Muxers WebLogic can multiplex requests of different protocols over same server socket (ie HTTP and T3 both over port 7001) Inspects first few bytes of input stream before dispatching internally Socket / Muxer Layer RJVM Layer Transport / Connection Management IIOP Layer RMI Layer Application ( T3(S ( IIOP(S ( HTTP(S Code Flow for a Simple RMI Request. Page 38 Oracle Corporation 2013 DO NOT DISTRIBUTE

36 WebLogic Performance Native I/O Muxers On most platforms Native IO Server Sockets are used Written in C using OS native libraries Superior performance and scalability due to native implementations' non-blocking thread model Servers can be configured to use Java I/O instead very rarely required mainly for O.S.s with no native implementations Specific Native I/O Muxer for each platform Windows: NTSocketMuxer (completion ports) Unix: PosixSocketMuxer (poll sockets) Linux: EPollSocketMuxer (poll sockets) Page 39 Oracle Corporation 2013 DO NOT DISTRIBUTE

37 WebLogic Performance Java I/O Muxers Non-Native options: If no native libraries found in path (sometimes 32bit vs 64bit can cause issues here), WLS reverts to Java Sockets, which have lower performance than Native typically Option used in spec.org performance test submissions and Exalogic for optimum performance: Java NIO: NIOSocketMuxer (no native code) This may become a default in the future to not use native code at all -Dweblogic.MuxerClass=weblogic.socket.NIOSocketMuxer Page 40 Oracle Corporation 2013 DO NOT DISTRIBUTE

38 WebLogic Performance WebLogic's Self-Tuning Thread Pool Network Socket Handlers ( Muxers ) Priority Based Request Queue Self Tuning Thread Pool Active Standby Stuck Hogging Asynchronously dispatched work from WebLogic kernel, subsystem, or application 1. Monitor rate of request processing 2. Adjust thread pool size accordingly Page 41 Oracle Corporation 2013 DO NOT DISTRIBUTE

39 WebLogic Performance Partitioning of Work Why partition work? Fair share between applications Dead-lock avoidance Strict ordering Prioritisation of classes of work Throttling Priority Request Queue Not FIFO Single kernel thread pool Kernel schedules priority requests to threads Work Managers define the partitions Every request is associated with a Work Manager Dispatch Policy Statistics Page 42 Oracle Corporation 2013 DO NOT DISTRIBUTE

40 WebLogic Performance Work Managers Every application has its own Work Manager based on the 'global' 'fair-share' work manager by default Can explicitly configure a new Work Manager apply to one or more specific applications and even individual resources (eg. a Servlet) Each work manager can have a mix of the following configuration elements... REQUEST CLASS ELEMENT Fair Share (default) Response Time (goal) Context based (per user/group) CONSTRAINT ELEMENT Minimum Threads (active) Maximum Threads Capacity (threshold for rejection) TRIGGER ELEMENT Shut-down Trigger Page 43 Oracle Corporation 2013 DO NOT DISTRIBUTE

41 WebLogic Performance Tuning work Managers The default fair share balancing of Work Mangers is good Occasionally need to bind some of an application's processing to a custom Work Manager Rarely any need for other tuning Sometimes bottlenecks can cause WebLogic to start many threads, up to the built in limit of 400 threads The self-tuning thread pool is doing the right thing to optimize throughput However, the high number of threads can cause memory issues Set a maximum threads constraint Page 44 Oracle Corporation 2013 DO NOT DISTRIBUTE

42 WebLogic Roadmap

43 WebLogic Current Releases and Roadmap Released Dec 2011 Released Feb 2012 CY2013 CY2013+ WebLogic Server 12c (12.1.1) + Coherence WebLogic Server 11g PS5 (10.3.6) + Coherence WebLogic Server 12c (12.1.2) + Coherence 12c (12.1.2) Java EE 7, Java SE 8, Cloud (12.1.3/12.1.4) Pre-Fusion Middleware 12c Java EE 6 Java SE 6 and 7 Maven integration updates Glassfish to WebLogic OEPE, NetBeans Active GridLink for RAC Session Affinity Transaction logs in DB JMS Distributed Topics EM Cloud Control Coherence Exalogic optimizations Seamless upgrade Fusion Middleware 11g PS5 ( ) Java SE 6 and 7 JDev, OEPE, NetBeans Active GridLink for RAC Session Affinity Transaction logs in DB JMS Distributed Topics Update Java Cloud Service (EE 5 with some EE 6) EM Cloud Control Coherence Exalogic Optimizations FMW Infrastructure w/adf OUI/Opatch Java SE 7 JDev, Eclipse, NetBeans Maven updates OSGi in WLS applications WebSockets/HTML5 TopLink Data Services Managed Coherence Servers Dynamic Clusters Database 12c Integration JMS Resource Adapter JMS - JAX-WS WSDL Exalogic Optimizations SOA, ODI, WebCenter Java EE 7 Reference Implementation and Standard Approval GlassFish 4.0 Java SE 7 and 8 Java Cache, Web Sockets standardized in Java EE JMS improvements Fusion Middleware 12c updates Oracle Cloud and Java Service updates Exalogic optimizations Page 46 Oracle Corporation 2013 DO NOT DISTRIBUTE

44 WebLogic Server Install, Patch, Upgrade Simplified provisioning across FMW Common install, patch, upgrade WLS, Coherence, OHS, ADF, FMWC 5-digit version: New minor version, not a patchset WebLogic and Coherence Distributions OUI installers WLS zip distro dev only, not patchable Simplified FMW packaging FMW Infrastructure in one installer Opatch for WebLogic Smart Update for prior WLS releases BEA Installer Smart Update Upgrade Wizard Oracle Installer Oracle Patch Reconfiguration Wizard Page 47 Oracle Corporation 2013 DO NOT DISTRIBUTE

45 WebLogic Dynamic Clusters Scale Clusters by Changing one Parameter How it works Create cluster with dynamic servers based on server template Servers inherit attributes from template Rules for calculating server-specific attributes Server name, listen ports, machines.. N servers available in the configuration Configuration changes are dynamic Start /stop servers to scale cluster Supported with Console, WLST, Enterprise Manager Elastic JMS, Managed Coherence Servers Server 1 Dynamic Cluster 1 Server Template Server 2 Server 3 Server 4 Server 5 Server 6 Server 7 Server 8 Scale to N Managed Servers Page 48 Oracle Corporation 2013 DO NOT DISTRIBUTE

46 Managed Coherence Servers Streamlined development and management environment for distributed applications Introduces the Grid Archive (GAR) Follows the Java EE model Consolidates config into a single distributable entity Provides Application Isolation & Lifecycle Events Coherence remains available standalone including support for GARs Leverages WebLogic infrastructure to provide: A Coherence container similar to EJB, JMS and JCA Management through Configuration Wizard, WebLogic admin console, WLST, JMX, FMWC Deployment of Coherence applications (GARs) Node Manager for lifecycle management Release and install Coherence libraries on the system classpath (no need to package in your application) Machine Node Manager Coherence App Managed Server WebLogic Domain Machine Node Manager Admin Server Cluster Machine Node Manager Coherence App Managed Server Managed Coherence Servers Page 49 Oracle Corporation 2013 DO NOT DISTRIBUTE

47 Disaster Recovery - TLOGs on file system Active Site Global Load Balancer Standby Site Data in file system replicated using file replication technology. Difficult to synchronize replicated TLogs and JMS, application data. Web Server Tier Web Server 1 WebLogic Cluster File Store Managed Servers Machine Machine 2 Machines 2 GridLink Data Source Web Binaries Server 2 Configuration Binaries Configuration Transaction Logs File Replication Technology Binaries Web Server 1 Configuration Web Server Tier Web Server 2 WebLogic Cluster File Store Binaries Configuration Transaction Logs Managed Servers Machine Machine 2 Machines 2 GridLink Data Source Database replication for JMS and application data. RAC Node 1 Machine 1 RAC Node 2 Machine 2 RAC Node 3 JMS Messages Application Machine 3 Data Golden Gate or DataGuard RAC JMS Messages Node 1 Application Machine Data 1 RAC Node 2 Machine 2 RAC Node 3 Machine 3 RAC Cluster RAC Cluster Page 50 Oracle Corporation 2013 DO NOT DISTRIBUTE

48 Disaster Recovery TLOGs on DB Active Site Global Load Balancer Standby Site Static files replicated separately from dynamic data. Web Server Tier Web Server 1 Web Binaries Server 2 Configuration WebLogic Cluster File Store File Replication Technology Binaries Web Server 1 Configuration Web Server Tier Web Server 2 WebLogic Cluster File Store No need to struggle to synchronize file and data replication Managed Servers Machine Machine 2 Machines 2 GridLink Data Source Binaries Configuration Binaries Configuration Managed Servers Machine Machine 2 Machines 2 GridLink Data Source Dynamic data stored, managed, and replicated together Reliable replication and high performance RAC Node 1 Machine 1 RAC Node 2 Machine 2 RAC Cluster Transaction Logs RAC Node 3 JMS Messages Application Machine 3 Data New Faster Golden Gate or DataGuard Transaction Logs RAC JMS Messages Node 1 Application Machine Data 1 RAC Node 2 Machine 2 RAC Cluster RAC Node 3 Machine 3 Page 51 Oracle Corporation 2013 DO NOT DISTRIBUTE

49 TopLink Grid TopLink Grid allows Java developers to transparently leverage the power of the Coherence data grid TopLink Grid combines: the simplicity of application development using the Java standard Java Persistence API (JPA) with the scalability and distributed processing power of Oracle s Coherence Data Grid. Supports 'JPA on the Grid' Architecture EclipseLink JPA applications using Coherence as a shared (L2) cache replacement along with configuration for more advanced usage Uses data grid to process queries to avoid database access and decrease database load Application EntityManager L1 Cache EntityManagerFactory Shared Cache Coherence Application EntityManager L1 Cache EntityManagerFactory Shared Cache Page 53 Oracle Corporation 2013 DO NOT DISTRIBUTE

50 Modern Development Platform Maven Updates in WebLogic Server Run Sync Plugin Populates a local or shared repository with WebLogic jars, POMs, archetypes Patch/resync to maintain repository Use WebLogic Maven Plugin All goals, plus Web Services goals Leverage repository(s) where possible Archetypes provided Standard approaches Use Maven as designed Consistency across Fusion Middleware More coming in FMW Developer Build Manager Sync plugin WebLogic plugin Sync plugin Product JARs Product JARs POMs <project> <groupid>com.oracle.weblogic</groupid> <artifactid>webservices</artifactid> <version>12.1.2</version> <packaging>jar</packaging> </project> Local Repository POMs <project> <groupid>com.oracle.weblogic</groupid> <artifactid>webservices</artifactid> <version>12.1.2</version> <packaging>jar</packaging> </project> Archetypes Archetypes Shared Private Repository Page 54 Oracle Corporation 2013 DO NOT DISTRIBUTE

51 WebLogic Server WebSocket and WebLogic Server WebLogic Server supports the WebSocket Protocol API to develop applications that use WebSockets Deploy WAR file containing the WebSocketListener implementation and application Client applications (e.g. Javascript) access server applications Proxy support Apache 2.4 with Web Server plug-in (post-ga) Oracle Traffic Director 11g Oracle HTTP Server (planned) Update to JSR 356 (Java EE 7) planned for WebSocket {JSON} Page 55 Oracle Corporation 2013 DO NOT DISTRIBUTE

52 TopLink Data Services in Easy to configure JSON/XML access via REST to enterprise data sources Declarative: No Java SE/EE development required Existing JPA apps Add TopLink Data Services web fragment to app Upon deployment, REST interfaces to entities generated using JAX-RS Can also generate mapping file from DB, and expose interfaces based on that Supports Oracle DB Notifications Multiple Data Sources: Relational, NoSQL, Coherence Multiple Clients: HTML5/JS, mobile devices, ADF Mobile Leverage all of TopLink s features including TopLink Grid, etc. Page 56 Oracle Corporation 2013 DO NOT DISTRIBUTE

53 OSGi Support WebLogic Server will enable use of OSGi in WebLogic applications Makes WebLogic more attractive for OSGi users Configure OSGi Framework from Admin tools Apache Felix 4.03 is bundled with WebLogic EAR/WAR Bundle Bundle Bundle osgi-lib Bundle Deploy/undeploy bundles From inside EAR/WARs, referencing framework By placing bundle in osgi-lib directory and starting framework WebLogic Server Runtime Integrated logging, use of filtering classloader Page 57 Oracle Corporation 2013 DO NOT DISTRIBUTE

54 Seamless Upgrade From WebLogic, ias and Others Simple Upgrade Automated Tooling Redeployment Migration Services WebLogic Server 11g Internet Application Server GlassFish JBoss WebSphere Page 58 Oracle Corporation 2013 DO NOT DISTRIBUTE

55 Java SE Roadmap

56 Java SE Roadmap 7u21 Java Client Security Enhancements App Store Packaging tools 7u40 Java Flight Recorder Java Mission Control 5.2 Java Discovery Protocol Native memory tracking Local Security Policy JDK 8 (Q1 2014) Lambda JVM Convergence JavaScript Interop JavaFX 8 3D API Java SE Embedded support Enhanced HTML5 support JDK 8u40 JDK 9 Modularity Jigsaw Interoperability Cloud Ease of Use JavaFX JSR Optimizations NetBeans IDE 7.3 New hints and refactoring Scene Builder Support Scene Builder 1.1 Linux support NetBeans IDE 8 JDK 8 support Scene Builder 2.0 support Scene Builder 2.0 JavaFX 8 support Enhanced Java IDE support JDK 8u20 Deterministic G1 Java Mission Control 6.0 Improved JRE installer App bundling enhancements NetBeans IDE 9 JDK 9 support Scene Builder 3.0 support SceneBuilder 3.0 JavaFX 9 support Page 60 Oracle Corporation 2013 DO NOT DISTRIBUTE

57 Oracle JDK 7 Java Mission Control Support Capability Host JRMC/JMC GUI Oracle JRockit JDK6 (R28+) Oracle JDK 6 Oracle JDK 7u4+ Oracle JDK 7u40 (CY2013) Y - JRMC Y JRMC Y - JMC Y - JMC Binaries with JMC GUI Default Download None Special binary on MOS Default Download WLDF JFR events and analysis JFR, JMC convergence JVM events Y N Y Y Y N N Y Page 61 Oracle Corporation 2013 DO NOT DISTRIBUTE

58 Page 62 Oracle Corporation 2013 DO NOT DISTRIBUTE

59 Page 63 Oracle Corporation 2013 DO NOT DISTRIBUTE