Putting Oracle Database 11g to Work for Java. Kuassi Mensah Group Product Manager, Java Platform Group db360.blogspot.com

Transcription

1 Putting Oracle Database 11g to Work for Java Kuassi Mensah Group Product Manager, Java Platform Group db360.blogspot.com

2 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 remains at the sole discretion of Oracle.

3 Agenda Putting Oracle JDBC 11g Drivers to Work Putting Universal Connection Pool to Work Putting the Java Runtime in Oracle Database 11g to Work

4 Oracle JDBC 11g <Insert Picture Here>

5 All Java Roads Lead to JDBC Transparent Persistence Do It YourSelf Persistence EJB Object Relational Mapping POJO JDBC SQLJ

6 What Oracle JDBC 11g Brings to Java JavaStandards: JDBC 4.0, RowSet APIs Built-in Advanced Security Encryption: AES, 3DES Checksumming: SHA1 Strong Authentication: Kerberos, Radius,SSL New Performance Capabilities Prefetch in First Roundtrip Faster Native AQ protocol Query Change Notification Client Query Result Cache Connection Services Fast Connection Failover (RAC) Runtime Connection Load Balancing (RAC) New Universal Connection Pool (RAC, Data Guard, XA)

7 Client Query Result Cache Database Server Configuration (init.ora) client_result_cache_size=200m client_result_cache_lag=5000 Client Configuration (sqlnet.ora) OCI_QUERY_CACHE_SIZE=200M OCI_QUERY_CACHE_MAXROWS=20 Application Server Database Hints for Caching the Result Set select /*+ result_cache */ * from employees Alternatively without code change alter table emp result_cache (mode force); The Cache is proactively invalidated upon changes to the Result Set on the server side Available with OCI, PHP, Ruby, ODP.Net, JDBC-OCI, ODBC

8 Fast Connection Fail-Over What The Application Sees Fast Connection Failover Failed Database Connections Inst x New Database Connections Inst y

9 Fast Connection Fail-Over Connection Retry try { conn = getconnection(); // do some work } catch (SQLException e) { handlesqlexception(e) }... handlesqlexception (SQLException e) { if (OracleConnectionCacheManager.isFatalConnectionError(e)) ConnRetry = true; // Fatal Connection error detected, }

10 Runtime Connection Load Balancing How Does It Work? 30% Work RAC Database Application pool I m busy 10% Work I m very busy Instance1 I m idle Instance2 60% Work Instance3

11 Universal Connection Pool <Insert Picture Here>

12 Pool Users ERP BPEL Java EE TopLink ADF POJO JDBC Adapter JCA Adapter JNDI Adapter LDAP Universal Connection Pool Connection Labeling JMX-based Management Advanced Timeouts Statistics Diagnostics and Tracing High Availability Load Balancing Work Load Management Web, XA, & Connection Affinity DataGuard Support Driver / Resource LDAP JDBC JCA Database Oracle SQL Server CICS 2006 Oracle Corporation Proprietary and Confidential

13 Feature Matrix 1/3 UCP Feature JDBC Standard pool properties Improved Pool Timeouts Multiple Pools per JVM Firewall timeout support Dynamic Pool Reconfiguration JMX-based Pool Management Rich set of pool Statistics Enhanced logging and Diagnostics Standalone Applications (JDBC, Tomcat, etc) Java EE Components

14 Feature Matrix 2/3 UCP Feature Standalone Applications (JDBC, Tomcat, etc) Java EE Components Connection Labeling Connection Harvesting RAC Fast Connection Fail-over with Abort Support RAC UP-event Load Balancing of Connections RAC Runtime Connection Load Balancing Application Callbacks Oracle Data Guard Support

15 Feature Matrix 3/3 UCP Feature Pooling of XA Connections Pooling of Proxy Connections Refresh, Recycle, Purge, Start, Stop etc. Support Web Session Based Affinity to RAC instance XA Connection Affinity to RAC Instance End-to-End Workload Management Metrics Standalone Applications (JDBC, Tomcat, etc) Java EE Components

16 Conversational, Web Session, and XA Affinity Conversational Affinity Determines if a Connection Request is Serviced by the same Pool The first connection request uses RCLB to select a connection. Subsequent requests enforce Affinity Pool resorts to RCLB whenever a desired connection is not found Affinity is only a hint Each RAC instance evaluates performance metrics and sends affinity hints per Service to UCP Web Session Affinity Built into OC4J Web Container Based on HTTP Session Determined by either the HTTP Session life cycle or RAC hint UCP enforces Affinity across AS / OC4J instances

17 Conversational, Web Session, and XA Affinity XA Affinity Enables XA and RAC to work together with optimal performance Eliminates current single DTP service limitation for XA/RAC XA affinity is the ability to automatically localize a global transaction to a single RAC instance XA Affinity scope is the life of a global transaction first connection request for a global transaction uses RCLB subsequent requests uses affinity and are routed to the same RAC instance when XA first started

18 Java Runtime in the Database <Insert Picture Here>

19 Java Runtime in the Database Java in Mid-Tier versus Java in the Database Java in the Database: Pros, Cons, What For Java Standards: Java SE 5, RowSet, JMX Performance: JIT Ease of Use & Manageability Database as Web Services Consumer

20 Java in Mid-Tier vs Java in the Database Java SE/EE Java in the Database Java SQL JDBC Calls JDBC Calls Any Language Java SQL Stored Procedure Call Typically 10+ times Faster!

21 Java in the Database Pros Business Logic Runs Directly in the Database and Process Data In Situ, Eliminates Network Roundtrip Code Shipping in Cheap Less Moving Parts Perfect for Data-Intensive Problems Good for Data-and-Compute intensive Cons Databases can scale up to 100s nodes, only!

22 Java in the Database: What For Trigger-based Notification System using RMI Secure Credit-Card Processing using JSSE Custom Alert applications that monitor business data Sending s with attachment from within the database Produce PDF files from Result Set Execute external OS commands and external procedures Implement Md5 CRC Publish Repository Content to Portal Portable Logistic Applications Implement Parsers for various File Formats (txt, zip, xml, binary) Implement Image Transformation and Format Conversion (GIF, PNG, JPEG, etc) Implement database-resident Content Management System HTTP Call-Out JDBC Call-Out RMI Call-Out to SAP Web Services Call-Out Messaging across Tiers Database Resident Lucene* RESTful Database Web Services* *

23 JIT Faster and Transparent Native Compilation 10X Speed up out of the box No dependency on C compiler Automatic Compilation (enabled out of the box) Compiles also dynamically generated Java code Uses a Feedback Mechanism for Detecting Hot Spots Persist Compiled Java in the database Bottom Line: Faster Java Execution

24 Database as Web Services Consumer Oracle Database SQL, PL/SQL UTL_DBWS Table Function Java Dynamic Interface Java WS Stack PL/SQL Wrapper Java WS Proxy SOAP Request Web Service

25 Resources Oracle JDBC and UCP Java Runtime in the Database Oracle Database Programming using Java and Web Services by Kuassi Mensah