DB2 9 XML Data Server Francis Arnaudiès IT/Specialist Information Management. Jeudi 24 Mai 2007

Transcription

1 DB2 9 Data Server Francis Arnaudiès IT/Specialist Information Management Jeudi 24 Mai 2007

2 Agenda Part I: Usage and DB2 9 pure Overview Database Usage Scenarios DB2 9 pure Part II: Storebrand s Experience with DB2 9 Business Environment and Challenges Solution based on DB2 9 Early results and benefits

3 Click to edit Master title style Part I: pure Solutions

4 What is? extensible Markup Language Self-describing data structures tags describe each element and their attributes Benefits Flexible No fixed format or data types Structure can be easily changed Platform Independent Not tied to any operating system, language or software vendor can be easily exchanged Fully Unicode compliant!"#$% &' () *+),-),.) /%)/ ) )

5 Importance of data? More and more data generated everyday is pervasive in all kinds of organizations Almost every sector has based standards

6 You will store! Resistance is Futile.

7 pure Usage Scenarios

8 1. Industry standards and data exchange applications IFX, OFX, SWIFT, SPARCS, MISMO +++ HL7, DICOM, SNOMED, LOINC, SCRIPT +++ ACORD for P&C, Life +++ MIAME, MAGE, LSID, HL7, DICOM, CDIS, LAB, ADaM +++ IXRetail, UCCNET, EAN-UCC epc Network +++ PIPs, RNIF, Business Directory, Open Access Standards +++ etom, NGOSS, etc. Parlay Specification +++ #! PDES/STEPml SMPI Standards RFID, DOD +++ FI, MDDL, RI, FpML +++ eb, other B2B Stds. Chemical estandards CyberSecurity PDX Standard+++!" IEC Working Group 14 Multiple Standards CIM, Multispeak

9 Industry Standard Example: FI Old FIX Protocol Buying 1000 Shares of IBM Stock.. 8=FIX.4.2^9=251^35=D^49=AFUNDMGR^56=ABROKER^34=2 ^52= :14:49^11=12345^1=111111^63=0^64= ^21=3^110=1000^111=50000^55=IBM^48= ^22= 1^54=1^60= :14:4938=5000^40=1^44=15.75^15=USD ^59=0^10=127 New FI Protocol extensible lower appl development & maintenance cost

10 2. - the foundation for SOA and Web Services is the transport for messages and data in SOA DBs can provide SOA data services SOA messages/data often need to be persisted Temporary Cache Audit Logs Compliance Records Insight Service Requestor Service Provider <xml>

11 2. Mapping for relational applications Shredding may be ok if: Simple data / Schema not complicated is merely a transport i.e. structure not relevant Existing SQL Apps have only relational APIs E.g. BI apps, reporting tools %!) %%) ) ID 129 DB2 9 Name Acme Price DB2 9 Annotated Schema Shredding Insight

12 3. as a better data model provides a better data model for many new apps Flexibility, schema versatility, hierarchical nature Semi-structured or unstructured data E.g. healthcare records, biological data, contracts, insurance claims, etc. Inherently hierarchical, nested or complex data E.g. manuals, books, catalogs, bills of materials, land records, etc. Data with changing or evolving schemas E.g. Forms, changing industry standard documents, new product versions, etc. Data with Null, Multiple or Unknown values E.g., Phone numbers (home, office, mobile), in patient records, etc. pure database a natural choice for data

13 DB2 9 pure

14 Data Needs Relational Maturity Data Needs Protection Backup and recovery features to ensure continuity Data is protected using database security Simplified Data Access Centrally store and access difficult to retrieve data SQL or XQuery can be used to retrieve data Join data with it s related relational data Search Speed Search documents quickly and efficiently using proven search optimization engine of mature database Optimize Existing Investments Use existing technology infrastructure and skills to store and manage both relational and

15 DB2 9: Hybrid Data Server pure and Relational Storage Relational and data are stored differently, but closely linked Seamlessly Join Relational and data DB2 9 SERVER CLIENT DB2 Client / Client Application SQL/ XQuery Relational Interface Interface Hybrid DB2 Engine DB2 Storage: Relational

16 XQuery: The FLWOR Expression FOR: iterates through a sequence, bind variable to items LET: binds a variable to a sequence WHERE: eliminates items of the iteration ORDER: reorders items of the iteration RETURN: constructs query results create table dept(deptid char(8),deptdoc xml); xquery for $d in db2-fn:xmlcolumn('dept.deptdoc')/dept let $emp := $d//employee/name where $d/@bldg > 95 order by $d/@bldg return <EmpList> {$d/@bldg, $emp} </EmpList> Input: <dept bldg=101> <employee id=901> <name>john Doe</name> <phone> </phone> <office>344</office> </employee> <employee id=902> <name>peter Pan</name> <phone> </phone> <office>216</office> </employee> </dept>

17 DB2 9 Summary of pure Support as a native data type Pure storage and indexing XQuery and SQL/ support Schema Repository Schema validation Application Support Java, C/C++,.NET, PHP, etc. Visual Tooling, Control Center Enhancements Annotated schema shredding DB2 Utilities: Import/Export, HADR, etc. and more 9

18 Click to edit Master title style Part II: Storebrand s experiences with DB2 9

19 Storebrand ASA The Storebrand Group is a leading player in the Norwegian markets for pensions, life- and health insurance, banking and asset management. The Group s activities are carried out through three main business areas: Life Insurance, Storebrand Investments, and Storebrand Bank. Storebrand has roots back to Throughout all these years the basis for value creation in Storebrand has been the readiness and ability to meet the challenges of new situations.

20 Storebrand challenges Background Traditionally a product oriented organisation. Each product has its own IT solutions supporting it. Business processes based on many manual steps and little integration between business areas Our system portfolio is the result of many mergers resulting in great complexity Our main systems are on mainframe and started their life years ago

21 Why use? I have often been asked: I understand as a technology but does any organization use and what problems does it solve? This is what we use it for: WebServices: B2B integration Integration of systems Reuse and continuous change

22 B2B Web Services Customers For company pensions, keeping up to date information on employees and their salaries has traditionally been a manual task. Now we get this information automatically from the customers ERP systems. Business partners Several Business Partners want to use their CRM system with our sales application. The integration is done through Web Services Business Partners also want to integrate our services into their portals Outsourced services Some Business Processes has been outsourced to external partners. Web services is the interface Government registers We are discussing with different governmental registers about automatic access. Today this is done by phone or mail Partner CRM System Web Services Web Services Government registers Customer ERP System Web Services Our Pension System Web Services Outsorced ERP

23 as an integration tool *!1 0 (( 2

24 Reuse and continuous change How do you change a service that is used by many internal and external applications? Services are regularly changed to accommodate new applications When a service is updated it is impossible to change all applications using it. We need to handle different versions of the same service. technology allows us to handle this in an elegant way also allows us to handle different data in a homogenous way For example all internet orders for all products are stored in one database. All orders have a common set of header information but the product data is very different depending on the product ordered. We have applications giving an overview over all orders

25 Business Processes Customer Orders Insurance system Investment system Agent Challenges Traditionally a product oriented organization, with each product containing their own IT solutions. Business processes based on many manual steps and little integration between business areas Portfolio is the result of many mergers resulting in great complexity Main systems are on mainframe and started their life years ago

26 New Solution based on Service Oriented Architecture (SOA) SOA Integration Architecture DB2 v 9 Integration Database Integration Document Header Customer Product A Shredded Key Info.!" # Product B Product C! $! % &'&$ (&$

27 Challenges that DB2 9 with pure Solved Data Query Need the ability to query any element in the document Need to quickly retrieve sets of data Shredding Need to remove the complexity around shredding Standard Technology XQuery And XPath Flexibility Need the ability to change any data element at any time Native storage defines each field SQL or XQuery to retrieve sets of data No more shredding Easy to learn Use same technology for application and database Schema evolution allows multiple schemas

28 Early Results with DB2 9 The complexity of the database code in the application is significantly reduced 20-65% reduction in code No need for deep SQL experience Reduced development time for search and retrieval business processes ( from 2-8 hours to 30 minutes) More flexibility Changing the schema typically took a week. We can now do it in 1 day Improved reporting In one case we reduced the time it took to produce a report from 24 hours to 10 minutes

29 Business Results Significantly Reduce Processing Time Order time reduced from 1-3 weeks to less than 5 minutes First week in June we processed more orders than the whole of 2005 Implemented significant changes in product and business processes in 4 weeks Fast, easy access to richer product & client information Most satisfied customers in 2006

30