Slide1: XML and Storage Michael Hawkins General Manager Business Development Japan, Asia, China, Australia Who is Software AG? XML Adoption Where‘s the pain? The pain relief! XML Server Examples XQuery


37 Years Heritage of Technology Leadership: 37 Years Heritage of Technology Leadership 2000 2002 …


Software AG has more than 600 Customers in Financial Services: Software AG has more than 600 Customers in Financial Services


…and more than 3,000 Customers across all Industries worldwide: …and more than 3,000 Customers across all Industries worldwide


XML ADOPTION: XML ADOPTION Hype Cycle XML adoption curve XML – Here To Stay "XML will continue to be a hot story, though it is unlikely to hit the front pages as much as it has in the past. In some ways, that may be a good thing, as XML makes the transition from topic for debate to forgone conclusion.“ Christopher Lindquist / Ed Dumbill - Jan 2002 Issue of CIO Magazine


GARTNER - XML hype cycle 2003: GARTNER - XML hype cycle 2003 Source: Gartner Group - 05/2003


XML Adoption Curve: XML Adoption Curve Impact Adoption time line (mainstream usage) Today 2-3 years Minimal Intermediate High


WHERE'S THE PAIN?: WHERE'S THE PAIN? Business drivers The pain - reality check


Business Drivers for XML: Business Drivers for XML Issues: I Application integration Respond faster - improve efficiency - provide better service II Content integration Unified view - effective location of content III Content management Single source / multi channel publishing - workflow IV Device communication Common content format - offline access - synchronization V Other issues Cost reduction - investment risk reduction - customer loyalty


Business Drivers (I): Business Drivers (I) Application integration issues Respond faster to changing business needs and competitive pressure Reduce efforts to adhere to regulatory requirements Mergers & acquisitions require consolidation of services Logistics managemt. – minimize inventory/optimize resource usage Offer new business services (e.g. Web services) Improve Business Efficiency Improve operational productivity of employees Increase efficiency of business processes (e.g. increase automation, manage exceptions) Provide better service to customers, partners and employees Customer self-service over the Web & call center solutions Reduce process cycle time


The need for integration: The need for integration Overwhelming number of data producers and consumers in organizations XML provides way to exchange data Point-to-point integrations have limitations No records, auditing No versioning No cross-application processes Increased complexity


Business Drivers (II) : Business Drivers (II) Content integration issues Provide unified view and access to enterprise content Central content repository to serve hundreds/thousands of users Access to data in productive external sources and applications Allow effective location of pre-existing content Querying structured content - minor problem today Querying unstructured content - inefficient today Unstructured content proliferates Content not yet encoded w/ descriptive metadata Query content in repository and external sources Metadata aggregation & storage required for efficient enterprise-wide searching on unstructured content


Business Drivers (III) : Business Drivers (III) Content management issues Single source publishing - to leverage existing assets Create and store content for maximum reusability and self-service Store XML + associated layout information + other types of data Avoid inconsistencies and redundancies Assemble on demand Repurpose many times in different formats (Web, print, mobile ...) Personalized access to information relevant to a specific subject Workflow Streamline processes for higher efficiency (short response-times ..) Keep enterprise-wide processing of data in sync (log, versioning ...) Access control / authentication


Business Drivers (IV): Business Drivers (IV) Device communication issues Mobile access Common format to transmit content/applications to ext. devices Common internal representation format => XML!!! Content storage and indexing On central server -and- at point of consumption (mobile device) Online searches / cost-effective offline searches (everywhere) Synchronization Between central (staging) server and back end infrastructure Between mobile devices and central server


Business Drivers (V): Business Drivers (V) Other issues Reduce "update"/"administration"/"development" cost Web browser-based administration and access Use standard Web technologies and best-of-breed tools Keep storage efforts for XML documents as low as possible Drive down technology and investment risks IT solutions to be based on open standards No platform lock-in or vendor lock-in Improve customer loyalty With fast, comprehensive and accurate search capabilities Access to up-to-date planning / status data Delivery as promised


The pain - reality check: The pain - reality check Large investment in existing systems that already provide optimum performance for mission critical functions IT infrastructures are and will remain heterogeneous Not ready for Web services - often not even Web-enabled No central point of access / querying to enterprise data They are not connected 85% of application projects do not use integration software Less than 10% of business processes connected to other systems Lack of real-time access and information flow Content inconsistencies - the "cut & paste dilemma" Re-use of existing content is ineffective & yields to inconsistencies Insufficient versioning / revision management Low budgets Tactical, project-based funding but desire long term strategic value Projects are critical to business viability - must show rapid ROI!


THE PAIN RELIEF: THE PAIN RELIEF Value of XML storage in the enterprise Where do we store it? Native versus Enabled


XML storage in the enterprise: XML storage in the enterprise Persistent storage for applications that rely upon business documents A repository for an Enterprise Service Bus integrating multiple enterprise applications A repository for XML content-oriented applications including XML content management A staging server and a repository for all portal-centric content A registry of web services, taxonomies, or other directories (e.g. UDDI registry, metadata repository, ...) A database to manage Web service states, long-term cache, or intermediary between specialized repositories Source: Gilbane Report - June 2003


Where do we store it?: Where do we store it? File system Text files Utilise existing infrastructure (backup/restore, security, etc) No query/reporting, etc Existing Database Structures Usually an existing RDBMS Utilise the facilities of a database for management/processing, etc XML-based storage Native XML Database/Server


RDBMS vs XDMBS: RDBMS vs XDMBS By design a RDBMS is good to handle normalised table structures XML documents have a kind of hierarchical nested table structure that does not fit into the RDBMS database unless you use features that help to automate this mapping process.


XML Document Structure: XML Document Structure Blues Eric Clapton Uni/Polydor 24.97 22.47 2.50 10 Markup content


The Logical Structure of XML Documents : The Logical Structure of XML Documents


Relational Database Views: Relational Database Views


XML in a Tamino native XML Server: XML in a Tamino native XML Server No mapping required: quick development results in short time-to market Native storage: keeping the original structure eg. for legal & auditing purposes High performance: no delay of converting layers in between Scalable: support for 1 to 100000… and more users


Native vs Enabled: Native vs Enabled You’ve got to admit that my storage is clear and organised!


Why is XML difficult to handle by RDBMS?: Why is XML difficult to handle by RDBMS? An RDBMS is primarily designed to handle table oriented data structure and format of data is known prior to storage names and types of data components are fixed and unchanging column descriptions are used for indexing and retrieval without column descriptions we do not know the meaning of the content


How to store XML in MS SQL Server? : How to store XML in MS SQL Server? 1044 Paul Astoria 123 Cherry Lane Best CA 94132 create table customer ( customerid number(10), firstname varchar(20), lastname varchar(20), street varchar(40), city varchar(20), state varchar(10), zip varchar(10) ); Flatten the xml file: Create the stored procedure Pass xml to stored procedure then parse & insert into the table


Value of XML for XML repositories: Value of XML for XML repositories XML document is the basis XML documents can be stored as is - without further conversion Associated open XML standards provide for effective access to document parts or the document as a whole (e.g. XQuery, XPath) Content validation prior to storage (XML Schema) XML-DBs promote automation of document exchange by providing persistent message storage for logging, auditing and tracking of business documents XML provides context to stored information so it can be queried and presented most effectively for intelligent re-formatting –> flexible re-use in multi-channel publishing services XML makes stored content flexible to change Changes in the document structure mainly require a change in the associated schema - little or no data remodeling


Caching / staging server: Caching / staging server XML Database is frequently used as caching server, for example, for online catalogs Ensures performance requirements of business solutions (good response times) Reduces direct load on back-end applications Storing information in XML format makes it easier to create or generate different "skins" (user interfaces / layout) or personalized views on the data Manage multiple languages A Caching Server Enterprise Transaction System Web


XML-DB in a service oriented architecture: XML-DB in a service oriented architecture System of Record Completed Documents: relational - Permanent, long-term storage - System of record - Rigid schema - Normalized and highly typed Operational Data Store Documents in Progress: XML - State data and payload data - Managed for the duration of the process - Shared, updated, audited – iterative extensions - Dynamic (variable) schema XML as an intermediate data representation or middleware layer and storage format to effectively facilitate inter-system communication


TAMINO: TAMINO What is Tamino? Tamino in the enterprise


Tamino XML Server Architecture: Tamino XML Server Architecture Core Services Security Service Tokenizer (opt.) Chin.,Jap.,Kor. Administration Services Query / Text- Retrieval Service XML Parser + Query Interpreter Obj. Processor & Obj. Composer X-Tension Service Tamino Manager Data Map XML Schema Service Native XML Data Store Internet File System


Facts and features: Full XML Support XQuery Facts and features Interfaces & APIs Integration Adapters XPath DTDs XML Schema XML Namespaces XML Signatures .NET Java EJB JavaScript C, C++, VB SOAP XML:DB WebDAV XSL(T) Platforms Windows2000 & XP Compatibility AIX HP-UX SuSe Linux (Intel) Bea WebLogic SunOne HP JBoss IBM WebSphere Sun Solaris Suse Linux (OS/390) RedHat Linux PHP HTTPS HTTP ERP (SAP, Peoplesoft, etc.) DBMSs (ebXML, XBRL, SWIFT etc.) Application servers XML Industry Standards Heritage systems Application Servers Apache Microsoft IIS Web Servers Sun StarOffice Microsoft Office Office Packages Altova XML Spy & Authentic Tools … (more than 200) & many more SunOne SAX DOM


Selection of customers (1): Selection of customers (1) Finance Government


Selection of customers (2): Selection of customers (2) Pharma & Healthcare Media & Technology


Selection of customers (3): Selection of customers (3) Manufacturing & Transport Retail


XML-Based Content Management: XML-Based Content Management Problem: Statutory obligation to preserve holdings for future generations Protect against “Corporate Alzheimer’s”!! This includes Books, journals and other publications, plus Papers, manuscripts, photographs, oral history readings, architectural plans, maps and other artefacts relating to SA History. Solution: Based on research, concluded XML required and native storage required Terabytes of content will be available to the public thru the web and their CM Systems Project SA Memory – a collaboration outside SA Library


UK Ordnance Survey OfficeSVG and GML: UK Ordnance Survey Office SVG and GML


Objectives: Objectives Build and manage a high-performance web directory of European businesses with information on approx 500,000 companies in 33 countries. Fast response times. Powerful query capabilities. Support for multiple languages (including Eastern European languages). Move from an SGML based system to XML.


Solution: Solution Information is stored and managed in the form of XML documents. The customer referred to this as a “natural choice”. Solution is built on Tamino XML Server. The internet site has good performance and powerful search mechanisms. Currently 24 languages are supported. The solution also contains a thesaurus with some 300,000 entries in the area of B2B. Site has been live for approximately 2 years.


Slide42: Snapshot


Workflow-based XML document management for complex testand diagnostic data: Workflow-based XML document management for complex test and diagnostic data


Objectives: Objectives Use XML as the standard for consistent management of all testing and diagnostics information related to electronic control devices in Mercedes-Benz vehicles. Establish an intranet-based portal for a standardized horizontal workflow of documents through the development, production and service departments. Mission of ASAM www.asam.net Reduction of effort and expense to maintain and adapt automation and test systems in the areas of development, production and service.


Slide45: Questions??? Thank you! ....