Using the Altova Tools with IBM DB2 purexml

Transcription

1 Information On Demand Using the Altova Tools with IBM DB2 purexml Irina Kogan December 6, 2007

2 Using the Altova Tools with DB2 purexml... 2 TABLE OF CONTENTS Acknowledgements Introduction About this article Target audience Software versions used in this tutorial Background purexml in DB2 9 and Altova Tools: DatabaseSpy, XMLSpy, MapForce, StyleVision Creating a database, tables with XML columns and XML indexes (DatabaseSpy) Creating the SAMPLE database with XML extensions Knowing the location of the XML samples for the DB2 SAMPLE database Creating a working directory and a DatabaseSpy Project Connecting to the database from the Altova tools Understanding the database contents using the visual representation of its structure Creating XML indexes Creating new tables in the Design Editor Understanding the graphical representation of the relationships between the existing tables Refreshing the database state Creating, validating, running and debugging XQueries (XMLSpy) Creating an XMLSpy Project Creating a new XQuery document / file Validating an XQuery and executing it on DB Using the XQuery Debugger Executing SQL or SQL/XML statements and editing XML data (XMLSpy) Running an SQL/XML query and viewing its results displayed in a table Viewing XML retrieved by an SQL query in an XML editor, modifying it and saving it to DB2 / in a file Executing updates with or without XML schema validation Running XQupdate statements (sub-document level updates) Deleting rows from a table using a GUI... 38

3 Using the Altova Tools with DB2 purexml Inserting new rows into a table containing XML fields using a GUI Accessing Query Database window from different Altova tools Working with XML schemas from the database Viewing and validating XML schemas in XMLSpy Deleting schemas from the DB2 XML Schema Registry Registering new schemas to the DB2 XML Schema Registry Using XML schemas to validate the documents to be inserted to DB Accessing XML Schema Management from different Altova tools Saving XML data from the database to a CSV file (MapForce) Creating and validating a simple mapping without any filtering Saving the output of the mapping and the mapping itself in the files Creating a mapping using the Nodes/Rows filtering Editing the database data using MapForce GUIs Transforming XML from the database to an HTML table (StyleVision) Conclusion... 69

4 Using the Altova Tools with DB2 purexml... 4 LIST OF FIGURES Figure 1. Cataloging the database as an ODBC data source... 9 Figure 2. Directory containing XML samples Figure 3. DatabaseSpy interface Figure 4. DatabaseSpy Project menu Figure 5. Creating a new project in DatabaseSpy Figure 6. Naming the project Figure 7. Using Quick Connect Window to connect to the database Figure 8. Saving the password for the database connection Figure 9. Confirming the unique identifier for the database Figure 10. Adding data sources to the project Figure 11. View of the database objects Figure 12. Properties details Figure 13. Select statement created for the table automatically Figure 14. Data Inspector window Figure 15. Creating an XML index Figure 16. Adding an SQL file to the project Figure 17. Default table in the Design Editor Figure 18. Creating a table in the Design Editor Figure 19. Adding a file to the Design folder Figure 20. Graphical representation of the table relationships Figure 21. XMLSpy interface Figure 22. Creating a new project in XMLSpy Figure 23. The defined XMLSpy project Figure 24. Creating an XQuery file Figure 25. Setting the options for the XQuery file Figure 26. XQuery open in XMLSpy Figure 27. Specifying the database and the DB2-specific options Figure 28. XQuery validation Figure 29. XQuery output Figure 30. XQuery Debugger Figure 31. Result of the XQuery debugging Figure 32. Messages window with the errors produced by the XQuery Debugger Figure 33. Adding an XQuery file to the project Figure 34. Running an SQL/XML query from the Database Query window Figure 35. Output in the Messages tab Figure 36. Adding a file to the SQL Files folder Figure 37. Adding more queries to the project Figure 38. Running an SQL query from the Database Query window Figure 39. Options for XML retrieved from the database Figure 40. Editing an XML file in the Grid perspective Figure 41. Indications of the data being modified Figure 42. XML document opened in the Text perspective... 36

5 Using the Altova Tools with DB2 purexml... 5 Figure 43. Adding the XML file to the project Figure 44. Adding an XQupdate file to the project Figure 45. Execution of the XQupdate statement Figure 46. Deleting a row Figure 47. Appending a row Figure 48. Specifying the data the new row is to contain (including XML) Figure 49. Database Query window access from MapForce Figure 50. Database Query window access from StyleVision Figure 51. Managing XML Schemas from DB2 in XMLSpy Figure 52. XML Schema Management for Databases window Figure 53. Viewing an XML schema in the Schema/WSDL perspective Figure 54. XML schema validation Figure 55. Preparing to delete an XML schema Figure 56. Deleting the schema from the DB2 XML Schema Repository Figure 57. Output in Report tab Figure 58. Adding an XML schema to the project Figure 59. Adding an XML schema to the DB2 XML Schema Repository Figure 60. Accessing XML Schema Management for Databases from DatabaseSpy Figure 61. MapForce interface Figure 62. Specifying a database table as the source of the mapping Figure 63. Assigning an XML schema to an XML column Figure 64. Using the schema from the database in the mapping Figure 65. Zoom-in view of the schema Figure 66. Specifying a CSV file as a target of the mapping Figure 67. Text/CSV file properties window Figure 68. Specifying the CSV file fields and their types Figure 69. Completing the mapping Figure 70. Mapping validation Figure 71. Mapping output Figure 72. Insert a filter Figure 73. The "equal" function Figure 74. Inserting a constant Figure 75. Mapping using data filtering Figure 76. Mapping output Figure 77. Option to supply a sample XML file for the schema Figure 78. Schema from the file system as the source of the mapping Figure 79. Adding a database table with an XML column as the target of the mapping Figure 80. Connecting the source schema to the target schema Figure 81. Database Table Actions Figure 82. Default database table action: Insert All Figure 83. Changing the database table action to be Update if Figure 84. Finalizing and validating the mapping Figure 85. Mapping output Figure 86. Successful execution of the mapping against DB

6 Using the Altova Tools with DB2 purexml... 6 Figure 87. Examples of functions Figure 88. StyleVision interface Figure 89. Specifying that an XML column from DB2 is to be used in the transformation Figure 90. Selecting the database table Figure 91. Specifying the XML document from the database Figure 92. Using the filter when selecting a document Figure 93. Specifying the schema from the database Figure 94. Simple design/tranformation for the XML document from the database Figure 95. View menu Figure 96. Preview HTML result for a simple design Figure 97. Schema Sources window showing a schema from DB Figure 98. Modifying the Main Template Figure 99. Creating a dynamic table from the schema Figure 100. Specifying the attributes and elements to be present in the table Figure 101. Updated Main Template Figure 102. Specifying the style Figure 103. Final template Figure 104. Final output: customer profile in an html table... 69

7 Using the Altova Tools with DB2 purexml... 7 Acknowledgements I would like to thank Nick Nagel from Altova for reviewing this tutorial and for his feedback. 1 Introduction IBM and Altova provide deep integration between the world's first multi-structured data server with the industry's premier XML tools. Through this integration, users can query, exchange, transform, and edit their XML artifacts more quickly, easily, and accurately. The first release of the integrated solution took place in May The version 2007 release 3 of the Altova tools was integrated with DB2 9: More detailed information about the integration in each tool can be found here: About this article This article shows a variety of purexml features in DB2 and how the Altova tools can help the user to work with them. In particular, it demonstrates how to do the following: Visualize the database structure and work with the database objects using the GUIs Easily query the database tables using SQL, SQL/XML, and XQuery statements or run other database transactions such as the one creating an XML index Edit and debug XQuery statements with a graphical editor Edit the XML data retrieved from the database, validate it and save it back using a GUI Manage XML Schemas stored in the DB2 Schema Repository Transform the XML data to different formats and use data filtering Even though this article is quite detailed, it is not meant to cover all functionality available in the Altova tools for DB2. Only the most important new functionality related to purexml is demonstrated (using the SAMPLE database with XML extensions that comes with DB2). The material presented is not basic XML. Some knowledge of XML itself and purexml in DB2 is assumed. The actual support of DB2 purexml is much richer than what is shown in this article. 1.2 Target audience Database developers, administrators and users; data integration specialists; software developers People who know DB2 purexml but lack knowledge of the Altova tools, or vice versa. People new to XML technologies, purexml in DB2 and to Altova tools and willing to do a little pre-work to get an understanding of how they can benefit from the IBM/Altova integrated solution when learning these technologies. 1.3 Software versions used in this tutorial DB2 9.5 All examples work with DB2 9 as well, unless otherwise specified. MissionKit 2008 The four Altova tools that are integrated with DB2 are: DatabaseSpy XMLSpy MapForce StyleVision

8 Using the Altova Tools with DB2 purexml... 8 All four are demonstrated in this tutorial. The MissionKit contains four additional tools. 2 Background This section provides the reader with very basic information about DB2 purexml and the Altova tools. 2.1 purexml in DB2 9 and 9.5 In contrast to previous DB2 implementations where XML data was stored as a CLOB or shredded to relational tables, DB2 9's purexml feature has provided support for XML data -- handling XML as a new data type that is stored in a natural hierarchy -- different from relational data. purexml's seamless integration of XML with relational data speeds application development, improves search performance with highly optimized XML indexes, and is flexible because both SQL and XQuery can be used to query XML data. It also includes sophisticated XML schema handling. DB2 9.5, released in October 2007, has many enhancements (both functionality- and performance-wise) over previous versions. One of the new features is the implementation of the XQupdates that follow the w3c standard the updates that modify parts of the XML document. The following website discusses what is new in DB2 9.5: The New features and functionality link takes you to a second page with links to descriptions of various enhancements. There is one specific to purexml. Database applications involving XML are very diverse and include publishing relational data as XML, content and document management with XML full-text search, consolidation of diverse data sources, managing highly variable data, forms processing, backend support for web-services and SOA, as well as message-based transaction processing and XML-based OLTP. For more information and learning materials, please see: (actually about DB2 9.5 rather than DB2 9) es&product_by=db2 (DB2 Express-C -- free edition of DB2 with purexml) 2.2 Altova Tools: DatabaseSpy, XMLSpy, MapForce, StyleVision This section simply lists the Altova products that have been enhanced by the integration with IBM DB2 purexml. The examples demonstrating this integration will be shown throughout this article. XMLSpy the industry-leading XML editor and IDE for working with XML documents, XML Schema, XQuery, XSLT, XPath, and more. MapForce a data mapping and conversion tool that builds and maintains relationships between XML, databases, flat files, EDI, and Web services.

9 Using the Altova Tools with DB2 purexml... 9 StyleVision a visual stylesheet creation tool for delivery of XML and relational data through HTML, PDF, Word/RTF, and electronic forms. DatabaseSpy an end-to-end development tool for database query and design. These four products are a part of the Altova MissionKit (that currently consists of eight products). For more info and learning materials, please see: (the links to each product separately are provided on the left) Creating a database, tables with XML columns and XML indexes (DatabaseSpy) In order for the reader of this article to be easily able to reproduce all steps discussed,, the SAMPLE database with XML extensions that comes with DB2 is used in all examples. 3.1 Creating the SAMPLE database with XML extensions The database can be created from the DB2 CLP (command-line processor). Then it can be declared as the ODBC source so that the Altova tools can connect to it and use it. From the Windows Start menu, go to Run and type cmd. On the window that appears, type db2cmd to obtain the DB2 Command Window. Then enter the following commands, as shown in Figure 1: db2sampl -xml db2 catalog odbc data source SAMPLE Figure 1. Cataloging the database as an ODBC data source

10 Using the Altova Tools with DB2 purexml Now the SAMPLE database can be used by any of the Altova tools that have database support. 3.2 Knowing the location of the XML samples for the DB2 SAMPLE database The XML samples for DB2 installed on Windows can be found in the following location: <DB2 install_path>\sqllib\samples\xml (where <DB2 install_path> is the location of DB2 9 or DB2 9.5 on your hard drive). The default location for <DB2 install_path> is C:\Program Files\IBM. Please note that if you have multiple installations of DB2 on your computer, the SQLLIB directories are named as follows: SQLLIB for the first installation (e.g. DB2 9), SQLLIB_01 for the second (e.g. DB2 9.5), and so on.. This is the reason why in the examples that follow you see SQLLIB_01 rather than SQLLIB: Figure 2. Directory containing XML samples 3.3 Creating a working directory and a DatabaseSpy Project Let our working directory for all tasks discussed in this tutorial be C:\XML_2007_Demo. Please create this folder. The great thing about the Altova tools is that they allow us to organize our work in a Project. First, we will be working with DatabaseSpy:

11 Using the Altova Tools with DB2 purexml Figure 3. DatabaseSpy interface This is what the DatabaseSpy Project menu looks like: Figure 4. DatabaseSpy Project menu If we create a new project, we give it a name and specify its Data Sources, SQL scripts, and so on:

12 Using the Altova Tools with DB2 purexml Figure 5. Creating a new project in DatabaseSpy Right-clicking on New Project allows us to name our project (use Save As ). Let s call it XML_2007_Demo_DatabaseSpy.qprj and save it in our working directory. This file name extension is always used for the DatabaseSpy projects. Currently, our project has a name but nothing else specified for it: Figure 6. Naming the project 3.4 Connecting to the database from the Altova tools Whenever DatabaseSpy is launched, a Quick Connect window appears and allows us to select the database to which we would like to connect. (At any later point, the Quick Connect button can be used to obtain this window. This window is available from XMLSpy, MapForce and StyleVision as well.) At first, we could just close this window since we wanted to create our project before doing anything else. But now let s right-click on the Data Sources in our project and choose Add a New Data Source. The Quick Connect window appears again. We need to select ODBC Connections and scroll down the menu listing the Data Sources. We see the SAMPLE database at the bottom of the list showing the User DSNs:

13 Using the Altova Tools with DB2 purexml Figure 7. Using Quick Connect Window to connect to the database In the scroll-down menu that allows us to add a new DSN or to edit an existing one (below the one for the Data Sources and Drivers), we can edit the existing DSN to save the password for the SAMPLE database. We choose IBM DB2 ODBC DRIVER - DB2COPY2 (DB2 version must be the one on which the SAMPLE database was created) instead of the SQL Server (which is a default): Then we press the Settings button have to re-type it each time: to save the password for the SAMPLE database in order not to

14 Using the Altova Tools with DB2 purexml Figure 8. Saving the password for the database connection When the pop-up window appears, we just need to confirm that the password can be saved in the db2cli.ini file. Next time we try to use the database we just confirm its unique identifier and are not asked for the password anymore: Figure 9. Confirming the unique identifier for the database So now our project lists the SAMPLE database as its only Data Source:

15 Using the Altova Tools with DB2 purexml Figure 10. Adding data sources to the project Right-clicking on the SAMPLE database allows us to disconnect from it. Then we can connect to it in the same way (for example, if we close and re-open our project). 3.5 Understanding the database contents using the visual representation of its structure When we connect to the database, we can choose the Online Browser tab (the one right next to the Project tab) and see which objects exist in our database:

16 Using the Altova Tools with DB2 purexml Figure 11. View of the database objects We see that there are seven tables created in the database and four XML schemas registered in the DB2 schema repository (the PRODUCT and the SUPPLIER schemas can be seen when scrolling down further). The Properties tab describes what is in the database. If a database object s name is typed in [type search string here], that object is described instead (for example, for a table, we see its number of columns, number of indexes, and so on). The same happens when one of the objects is rightclicked on.

17 Using the Altova Tools with DB2 purexml Figure 12. Properties details (The Properties window now shows the overview of the CUSTOMER table rather than the database itself.) We can see the SELECT statement appearing in an SQL Editor. It selects all three columns from the CUSTOMER table. (The INFO and HISTORY columns are of the XML type.) There is really no need to save this script in a file, as it can be obtained by just a couple of clicks. If we press on the Execute button denoted by, we see that the result set contains six rows (since there were no predicates used in the SQL statement, this means that the whole table contains only six rows):

18 Using the Altova Tools with DB2 purexml Figure 13. Select statement created for the table automatically (A similar button that looks like is called Execute for Data Editing. Its use for editing of the XML data and storing it back to the database will be demonstrated later. XMLSpy rather than DatabaseSpy will be used for this purpose.) Now let s take a look at the table with the result set from the query. We can right-click on one of the XML documents and choose Show in Data Inspector Window. It looks like this (with Wrap being selected):

19 Using the Altova Tools with DB2 purexml Figure 14. Data Inspector window Each of the XML schemas can be viewed in XMLSpy (right-click on it and choose the corresponding option), but let s not do this just yet. We will work with XMLSpy later on. 3.6 Creating XML indexes We can see in the Online Browser that some XML indexes already exist on the table CUSTOMER. If we try to create the same index once again, the CREATE INDEX statement fails and the error message fetched from DB2 is returned. If we try to create a new XML index (say, on the customer zip code), the statement succeeds. Let us use a new SQL Editor (obtained by clicking on the corresponding menu) to demonstrate this: button or from the

20 Using the Altova Tools with DB2 purexml Figure 15. Creating an XML index If you would like to create the CUSTOMER_ZIPCODE_XMLIDX on your system, please note that this statement was used: CREATE INDEX CUSTOMER_ZIPCODE_XMLIDX ON CUSTOMER(INFO) GENERATE KEY USING XMLPATTERN 'declare default element namespace " AS SQL VARCHAR(7); Also note that the Options on the left specify that the semicolons are used as the statement delimiters (this is default in DB2). 1 This is done so that a single SQL script created to be run on DB2 can contain several statements. Such a script can be saved in a file (traditionally, having a name with an.sql extension) using File -> Save As It can contain any semicolon-terminated SQL statements such as ALTER TABLE <table name> (to modify the table) or INSERT INTO <table name> (to insert a single row or to even populate the whole table). Let s call our script create_xml_index.sql and save it in the working directory. Then we can right-click on the SQL folder of our project, choose Add Files to Project and add this file: 1 When XML namespace declarations are present in a statement, a statement terminator other than a semicolon is used on DB2 (as the namespace declaration already contains a semicolon). However, when a statement is to be run from the Altova tools, the statement terminator is removed before the statement is sent to DB2, so the semicolon can be safely used.

21 Using the Altova Tools with DB2 purexml Figure 16. Adding an SQL file to the project 3.7 Creating new tables in the Design Editor New tables (as well as some other database objects) can also be created / dropped from the SQL Editor. However, DatabaseSpy also provides us with a nice graphical Design Editor that can be accessed from either File -> New Design Editor or by pressing this button. Once we get the new Design Editor, we can right-click on it and select Create New Table from the menu. We see this default table appearing: Figure 17. Default table in the Design Editor For simplicity, let us create a table called TEST with a single column called TDOC of type XML. The table and column names need to be double-clicked in order to change them. To make the TDOC column not nullable, we just uncheck the corresponding check box. Then we run the Database Structure Change Script created by DatabaseSpy on DB2 by pressing the Execute button :

22 Using the Altova Tools with DB2 purexml Figure 18. Creating a table in the Design Editor The message notifying us that the Database Structure Change Script was executed successfully appears on the screen. The database structure is re-loaded and the Online Browser starts showing the TEST table. (It is left up to the reader of this tutorial to verify this.) While we are in a Design Editor, we can go the File -> Save As menu and save our design under a name with the.qdes extension. Then we can always use an existing design to obtain a sql script we are interested in and to run it against the database. Let s call it create_test_table.qdes. If we add this file to the Design folder of our project, we end up with this:

23 Using the Altova Tools with DB2 purexml Figure 19. Adding a file to the Design folder We won t be adding anything else to this project. This project is now listed in our Recent Projects and can be easily open again. It is a very simple one. However, some projects are very complex and this structure that the Altova tools provide us with is very helpful. 3.8 Understanding the graphical representation of the relationships between the existing tables The Design Editor can also be used to see the relationships between different tables. For example, if we drag and drop the CUSTOMER and the PURCHASERORDER tables into a new Design Editor, we see how the primary keys and foreign keys are defined; that is, how these two tables are related to each other via the referential integrity constraints: Figure 20. Graphical representation of the table relationships The arrow next to the Keys was clicked on, whereas the arrow next to the Indexes was not. If it were, then we would see 20 indexes for the CUSTOMER table and 9 indexes for the PURCHASEORDER table. The dropping and editing of the tables, columns, keys, indexes and check constraints can also be done right in the Design Editor providing us with a nice GUI.

24 Using the Altova Tools with DB2 purexml Refreshing the database state The Online Browser has the Refresh button that allows us to refresh the database state. The database could have been modified not only by the transactions ran from the DatabaseSpy, but also from the DB2 CLP or some other application, so it is important to use the database in its current/most recent state. 4 Creating, validating, running and debugging XQueries (XMLSpy) Let s start up XMLSpy in order to work with XQueries. This is what the XMLSpy window looks like: Figure 21. XMLSpy interface 4.1 Creating an XMLSpy Project We will use the same working directory as for the DatabaseSpy project: C:\XML_2007_Demo. Selecting Project -> New Project creates a new XMLSpy project for us:

25 Using the Altova Tools with DB2 purexml Figure 22. Creating a new project in XMLSpy Project -> Save Project allows us to save this project. We will use this project for all tasks discussed in this chapter. Let s give the project a name with an.spp extension and save it in our working directory. Also, let s remove XSL Files, HTML Files, and Entities folders, since we won t need them (right-click and choose Delete). Also, let s right-click on the DTD/Schemas folder, open the Properties window and change the folder s name to XML Schemas. We also need to remove all File Extensions in this Properties window, except for xsd (as this is the only one associated with XML schemas). Additionally, let s right-click on the project s name and choose Add Project Folder We call it SQL Files and specify sql in the File Extensions part of the form. This is what we have at this point: Figure 23. The defined XMLSpy project 4.2 Creating a new XQuery document / file We go to File -> New to create a new XQuery file (that is, one for the XML Query Language):

26 Using the Altova Tools with DB2 purexml Figure 24. Creating an XQuery file Either of the four extensions for it can be chosen. Let s chose.xq (the first one). Then we need to choose Generic XQuery Transformation: Figure 25. Setting the options for the XQuery file Remove xquery version "1.0"; from the new document that appears and paste the first XQuery from <install path>\sqllib[_01]\samples\xml\xquery\clp\flwor.db2 2 without the statement terminator denoted This XQuery lists the customers who live in Canada in alphabetical order: 2 Here and later, SQLLIB[_01] means that unless there are multiple installations of DB2 on the same machine, SQLLIB rather than SQLLIB_01 is used.

27 Using the Altova Tools with DB2 purexml Figure 26. XQuery open in XMLSpy 4.3 Validating an XQuery and executing it on DB2 The Enable Database Support check box in the Info panel needs to be checked in. Then the Quick Connect window pops up asking us which database to connect to. We choose the SAMPLE database again. We also need to check in the Support for DB2 extensions and the Execute XQuery directly in DB2:

28 Using the Altova Tools with DB2 purexml Figure 27. Specifying the database and the DB2-specific options Then if we press the Validate button denoted by statement is valid:. We see on the Validation window that the Figure 28. XQuery validation Please note that the statement contains db2-fn:xmlcolumn(), which means it would not be valid if the Support for DB2 extensions were not enabled (the corresponding check box checked in). The Altova tools have been extended to understand the DB2 functions db2-fn:xmlcolumn() and db2- fn:sqlquery() used inside of the XQueries. Let us look at the XQuery execution next. We can use the XQuery Execution button. Once we execute our xquery, we see the following output in a file XQuery Output.xml created by XMLSpy: Figure 29. XQuery output

29 Using the Altova Tools with DB2 purexml From running a SELECT * statement against the CUSTOMER table in the previous section, we know that there were six customers in total. Now we know that all of them are from Canada. 4.4 Using the XQuery Debugger Now let us try to debug this query with the XQuery Debugger built into XMLSpy. We need to start the debugger from the XSL/XQuery menu (unless we have already placed the Start Debugger/Go button on the toolbar): This is what we see: Figure 30. XQuery Debugger When we press on the Start Debugger button, we see that the debugging finishes without any errors being found and the XQuery output is being displayed:

30 Using the Altova Tools with DB2 purexml Figure 31. Result of the XQuery debugging On the other hand, if we remove the leading keyword XQUERY, the debugger detects an error and opens the Messages window to display it: Figure 32. Messages window with the errors produced by the XQuery Debugger Please note that an XQuery can be valid, but the debugger can still complain about it. A simple example is if we change CUSTOMER.INFO to CUSTOMERS.INFO. The validation will succeed. However, the debugger will catch an error from DB2 that the table CUSTOMERS does not exist in the SAMPLE database (making this XQuery fail on DB2). Then the debugger displays this error in the Messages window. You need to know the difference between the following two buttons: and. The former stops the debugger, which can at any point be re-started by using the button. The latter ends the debugging session and returns to the regular XQuery window/perspective. Let s save our XQuery under the xquery_customer_list.xqr name and add it to the XQuery Files of the project:

31 Using the Altova Tools with DB2 purexml Figure 33. Adding an XQuery file to the project 5 Executing SQL or SQL/XML statements and editing XML data (XMLSpy) Let us list the names of all customers who live in Canada using SQL/XML rather than XQuery, as SQL/XML is also supported by DB2 (and it can be executed on DB2 from the Altova tools). In contrast to what we did in Section 4, let s print the names in the order they appear in the database rather than in the alphabetical order. 5.1 Running an SQL/XML query and viewing its results displayed in a table This is what our query looks like: SELECT XMLQUERY ( 'declare default element namespace " for $custinfo in $custdoc/customerinfo return $custinfo/name' PASSING info AS "custdoc" ) FROM customer WHERE XMLEXISTS ( 'declare default element namespace " $custdoc/custinfo/addr/@country="canada" ' PASSING info AS "custdoc" ) We can run this query from either the SQL Editor in DatabaseSpy or the Query Database window that is now available from XMLSpy, MapForce and StyleVision. (The way how the Query Database window is accessed from each of these three tools is different. This is shown at the end of this section.) Let us use XMLSpy in our example. If we choose DB -> Query Database, a new window pops up and we are asked to connect to the database. Let s use the SAMPLE database again. We can paste the query into the editor (or alternatively save it in the file first and then use the Import SQL file button to open the file in the editor). Then we can just execute the query and see its results:

32 Using the Altova Tools with DB2 purexml Figure 34. Running an SQL/XML query from the Database Query window The output in the Messages tab shows that the execution of the statement was successful and took only seconds: Figure 35. Output in the Messages tab We can view each retrieved document in XMLSpy as well as to save it in a file on the file system. Let s not do this just yet though. However, let s save the query itself as sqlxml_customer_list.xqr and add it to the SQL Files folder of the project:

33 Using the Altova Tools with DB2 purexml Figure 36. Adding a file to the SQL Files folder SQL/XML is different from SQL (and so is XQUpdate discussed later). However, we can still save this file in the SQL Files folder, as it has the.sql extension. 5.2 Viewing XML retrieved by an SQL query in an XML editor, modifying it and saving it to DB2 / in a file Let us write an SQL query that will retrieve the info document together with the primary key cid. Then we will be able to edit the retrieved data. The query is very simple: SELECT cid, info FROM customer Let s call this query sql_customer_list.sql, save it in the working directory (by using the Export SQL file button on the DB Query Window) and add it to the SQL Files in our project: Figure 37. Adding more queries to the project Now let us run this query by clicking on the Execute for Data Editing button :

34 Using the Altova Tools with DB2 purexml Figure 38. Running an SQL query from the Database Query window This time we see the following choices when we click on the button for either of the XML documents: Figure 39. Options for XML retrieved from the database Let s open the first XML document and look at it in the Grid perspective (do not forget to open up the addr and phone elements):

35 Using the Altova Tools with DB2 purexml Figure 40. Editing an XML file in the Grid perspective We can change the phone number by typing directly in its cell. If we choose on DB -> Query Database again, we can see that the for the first document appears in red (indicating that the document was open in the XMLSpy editor and was possibly modified). The Commit button now appears enabled: Figure 41. Indications of the data being modified If we press on the Commit button, the changes are saved to the database. However, if the modification we made is not allowed (for example, it makes the XML document to be not well-formed), then keeps appearing in red and the Messages tab shows an error returned by DB2. This is not the case in our example though.

36 Using the Altova Tools with DB2 purexml If we execute the same query again, we see that the phone number for the customer with the cid = 1000 was indeed changed (that is, the update on DB2 was successful). Let s open this document in the Text perspective this time: Figure 42. XML document opened in the Text perspective Let s use File -> Save As to save the Table_SAMPLE.IKOGAN.CUSTOMER_Column_INFO document in C:\XML_2007_Demo\customer_1000.xml, as we will need it later. (Saving XML files retrieved from DB2 on a file system is a very convenient option XMLSpy provides us with.) We can now add this XML file to our project:

37 Using the Altova Tools with DB2 purexml Figure 43. Adding the XML file to the project Please note that Edit -> Pretty Print XML Text properly aligns all tags in the XML document. XML -> Check well-formedness ( ) checks whether XML is well formed. XML -> Validate XML ( ) validates the document against the schema if one is assigned to it. 5.3 Executing updates with or without XML schema validation Please note that if we assigned a schema to the INFO column (in our case it would be customer.xsd from <DB2 install path>\sqllib[_01]\samples\xml\data) by right-clicking on the document of interest and choosing Assign XML Schema, the update on DB2 would be with the schema validation. Otherwise, it is not. An XML schema in DB2 is assigned on a per-document rather than on a per-column basis; that is, different XML documents in the same column might be conforming to different schemas and some might have no schema associated with them. The XQupdate shown next could also use the schema validation by containing XMLVALIDATE( ) according to a certain schema, but this is beyond the scope of this tutorial. 5.4 Running XQupdate statements (sub-document level updates) If DB2 9.5 is used, another way to update the phone number of this customer would be to run a subdocument level update from the Query Database Window. (Please note that this feature is not supported in DB2 9.) This is what the XQupdate statement would look like: UPDATE customer SET info = XMLQUERY('declare default element namespace " transform copy $custinfo := $info modify do replace value of $custinfo/customerinfo/phone[1] with " " return $custinfo' PASSING info AS "info") WHERE XMLEXISTS ('declare default element namespace " $info/customerinfo[@cid=1000]' PASSING info AS "info") Let s call it xqupdate_customer_phone.sql and add it to our project:

38 Using the Altova Tools with DB2 purexml Figure 44. Adding an XQupdate file to the project Basically, we are just replacing the phone number back to what it was. The following snapshot shows that the statement is executed successfully on DB2. (It is left up to the reader of this tutorial to select this document again to verify that the phone number for this customer was indeed changed.) Figure 45. Execution of the XQupdate statement 5.5 Deleting rows from a table using a GUI If we take a look at the output of our query, we can see that two first rows (with cid = 1000 and cid = 1001) are for Kathy Smith. Let s delete the first one of them. If we select the corresponding row and press on the Delete Row button, the row appears in pink:

39 Using the Altova Tools with DB2 purexml Figure 46. Deleting a row Pressing the Commit button commits the changes to the database (and the output starts showing five rows instead of six). 5.6 Inserting new rows into a table containing XML fields using a GUI Now let s try to insert a new row. To do that, we need to press on the Append a New Row button. Then a new row appears at the bottom of the output: Figure 47. Appending a row We can now re-use the cid of 1000, as it does not exist in the table anymore after the deletion (duplicates would not be allowed due to a primary key constraint on cid and a unique XML index Figure 48. Specifying the data the new row is to contain (including XML) In order to produce the value (XML document) for the INFO column, we can either create the document from scratch (by choosing the Open for editing option) or load an XML document from a file. Let s use the latter option and load C:\XML_2007_Demo\customer_1000.xml that we saved in Section 5.2. Committing the changes to the database is executed successfully. The CUSTOMER table now has six rows again. Please note that once you start making the changes to the database data, you can always undo them (clearly only before committing them) by pressing the button that undoes all changes done to the

40 Using the Altova Tools with DB2 purexml result grid. After the changes are committed to the database, this button is disabled so as not to confuse you. 5.7 Accessing Query Database window from different Altova tools It was noted earlier that the Query Database window is available from different Altova tools through different interfaces. In MapForce (see Section 7 for more detail on MapForce), there is a Database Query button that we can use: Figure 49. Database Query window access from MapForce This is how the Database Query window can be accessed from StyleVision (see Section 9 for more detail on StyleVision): Figure 50. Database Query window access from StyleVision 6 Working with XML schemas from the database Several Altova tools (DatabaseSpy, XMLSpy, MapForce and StyleVision) provide us with the capabilities to work with the XML schemas from a DB2 database. The interface is different from within different tools. Let us use XMLSpy in our demo below. We go to DB2 -> IBM DB2 -> Manage XML Schemas (Please make sure that you are still connected to the SAMPLE database.) Figure 51. Managing XML Schemas from DB2 in XMLSpy If we check the show details box on the window that pops us, this is what we see:

41 Using the Altova Tools with DB2 purexml Figure 52. XML Schema Management for Databases window Basically, we see all four schemas registered in the DB2 XML Schema Registry for the SAMPLE database. These are the same schemas as we saw in the Online Browser in Section Viewing and validating XML schemas in XMLSpy When we select the CUSTOMER schema in the table, we can click on the button (followed by the button) to see what the schema looks like. Let s use the Schema/WSDL perspective to see what this schema obtained from the database looks like:

42 Using the Altova Tools with DB2 purexml Figure 53. Viewing an XML schema in the Schema/WSDL perspective We can also use the validation button to make sure the schema is valid:

43 Using the Altova Tools with DB2 purexml Figure 54. XML schema validation 6.2 Deleting schemas from the DB2 XML Schema Registry Let s drop the CUSTOMER schema. We select the schema by clicking on it. Then we press the button: This is what we see at this point: Figure 55. Preparing to delete an XML schema In order to actually delete the schema from the database, we need to use the button. Then the CUSTOMER schema actually disappears from the list of the available schemas: Figure 56. Deleting the schema from the DB2 XML Schema Repository The Report tab shows that the DROP XSROBJECT statement has been executed successfully on the database:

44 Using the Altova Tools with DB2 purexml Figure 57. Output in Report tab 6.3 Registering new schemas to the DB2 XML Schema Registry Now let us add the CUSTOMER schema back. This customer.xsd schema can be found in the directory containing the XML samples for DB2 on the file system: <DB2 install path>\sqllib[_01]\samples\xml. Let s copy this schema to C:\XML_2007_Demo\customer.xsd and add it to the XML Schemas in our project: Figure 58. Adding an XML schema to the project (Once we save the project by selecting Project -> Save Project, the * right next to the project name disappears indicating that it has not been modified since it was last saved). In order to register a new schema in the DB2 XML Schema Registry, we need to press the button. Then a Select File window pops up and allows the user to either choose the customer.xsd schema from our project (the only one available there) or browse the file system to choose an.xsd file containing the schema to be registered. We choose our customer.xsd from the project:

45 Using the Altova Tools with DB2 purexml Figure 59. Adding an XML schema to the DB2 XML Schema Repository Once we press on the XML Schema Repository. button, the CUSTOMER schema is registered in the DB2 If DB2 returns any error during the schema registration, XMLSpy will catch and display that error and the schema won t be registered. 6.4 Using XML schemas to validate the documents to be inserted to DB2 When an XML document is to be inserted into the database, it can be assigned an XML schema in XMLSpy first (from the DTD/Schema menu) and then validated against that schema in XMLSpy. In this case, an insert without validation can be performed on DB2 (e.g., from the Query Database window), as we already know that the document we are inserting is valid: INSERT INTO CUSTOMER VALUES (XMLPARSE (DOCUMENT ' the actual xml document here ')) Alternatively, the XML document is not validated by XMLSpy, but an insert with validation is performed on DB2: INSERT INTO CUSTOMER VALUES (XMLVALIDATE (XMLPARSE (DOCUMENT ' the actual xml document here ') ACCORDING TO XMLSCHEMA ID IKOGAN.CUSTOMER)) 6.5 Accessing XML Schema Management from different Altova tools As it was discussed earlier, the interface for working with XML schemas from DB2 is different in different Altova tools. This is the menu we would need to use when working with DatabaseSpy rather than XMLSpy:

46 Using the Altova Tools with DB2 purexml Figure 60. Accessing XML Schema Management for Databases from DatabaseSpy In MapForce and StyleVision, the XML column/document is usually right-clicked on and the Assign XML Schema option is used to assign a schema to it. Then the list of the schemas the user can choose from also includes the schema from the database to which the user of MapForce/StyleVision is connected. 7 Saving XML data from the database to a CSV file (MapForce) CSV output is a comma separated value output that can be easily saved in a text file or in a special.csv file that can be open in Excel. XML data from a DB2 database table can be transformed to such a CSV output by performing a mapping in MapForce. The first object for the mapping is a DB2 database, whereas the second one is a CSV file. This is what the MapForce window looks like:

47 Using the Altova Tools with DB2 purexml Figure 61. MapForce interface MapForce mappings can be organized into projects, but this is beyond the scope of this tutorial. 7.1 Creating and validating a simple mapping without any filtering Let us add the database to the New Design1 Mapping panel by pressing the Insert Database button and then selecting the database and connecting to it using the Quick Connect window such as the one we already saw. Once we do that, we are asked to select a table which we want to work with. (Pressing the Preview button shows the data in the table.) Let us work with the CUSTOMER table again:

48 Using the Altova Tools with DB2 purexml Figure 62. Specifying a database table as the source of the mapping Once we press OK, the SAMPLE database containing only the CUSTOMER table appears on the New Design1 window. We need to assign an XML schema to the XML column we want to work with (the INFO column in our case):

49 Using the Altova Tools with DB2 purexml Figure 63. Assigning an XML schema to an XML column We can either choose a schema from the database or from the file system. IKOGAN.CUSTOMER from the database: Let s choose Figure 64. Using the schema from the database in the mapping After the OK button is pressed, the INFO column in the New Design1 window appears with the schema assigned to it (that is, restricting which values can appear in each document of this column). Once we press on all the + signs next to the elements that have them (to zoom in), this is what we end up with:

50 Using the Altova Tools with DB2 purexml Figure 65. Zoom-in view of the schema The left object of the mapping is ready for use. Which fields of the customerinfo would we like to have in a CSV file? Let s choose Cid, name, country and the phone (the phone number would be whichever one is specified first, no matter of which type ; that is, no matter whether it is a work, home or cell phone). The namespace ( denoted by n1: is irrelevant to us in this mapping. Now we need to create the right object of the mapping. We press on the Insert Text File button choose a CSV file: and Figure 66. Specifying a CSV file as a target of the mapping The following window appears in which we specify C:\XML_2007_Demo\customer_info.txt as our Output File:

51 Using the Altova Tools with DB2 purexml Figure 67. Text/CSV file properties window We need to specify the correct fields instead of Field1 by editing the cells and using more fields: to add Figure 68. Specifying the CSV file fields and their types We choose the types that correspond to the types in the CUSTOMER schema for the corresponding elements/attributes. The types are chosen from the scroll-down menu that lists all types allowed to be in a text file. When we press OK to add this CSV file to the New Design1 window, it appears on the right side of the mapping. We join the arrows to connect the fields between the two objects used in the mapping. It is also very important not to forget to join the n1:customerinfo on the left with the Rows on the right, since we are doing a many-to-many mapping (obtaining info for all customers):

52 Using the Altova Tools with DB2 purexml Figure 69. Completing the mapping We can validate our mapping using the Validate Mapping button and see that it is valid: Figure 70. Mapping validation If we press on the Output button, this is what we see:

53 Using the Altova Tools with DB2 purexml Figure 71. Mapping output (Actually just pressing on the Output button performs the mapping validation as well. If a mapping is not valid, the errors are produced in the Messages window.) 7.2 Saving the output of the mapping and the mapping itself in the files The Save Generated Output button saves the output to C:\XML_2007_Demo\customer_info.txt (unless you choose a different file during the prompt), since this file was specified as the Output File in the Text import/export window above. The regular Save button saves the MapForce mapping (with an.mfd extension) in the specified directory on the file system. But first we need to use File -> Save As to give the file with our mapping a name. Let s call it customer_table_to_csv_file.mfd. Now we can just open it and work with it again later. MapForce can auto-generate the software program code in Java, C++ or C# for the mapping such as the one we just created (as well as for a much more complex one or for a project containing multiple mappings). This code can be easily used in any software application. The discussion of this nice feature is beyond the scope of this tutorial. The same applies to the mapping of the XML data from a database into EDI, Web services, modified XML, and so on. 7.3 Creating a mapping using the Nodes/Rows filtering Now let us take a look at how filters can be used in MapForce to select only a specific document from the table. To do that, let s copy customer_table_to_csv_file.mfd to customer_table_to_csv_file_filter.mfd and work with this new file. In this exercise, we would like to select the customer document (from the CUSTOMER table from the SAMPLE database) that has the attribute Cid equal to 1001 and map it to a CSV file. As compared to our previous mapping in which we mapped n1:customerinfo to Rows, now we need to include a filter between them that would only select a row (document) where Cid equals to Let s

54 Using the Altova Tools with DB2 purexml remove our old link connecting the two. If we click on the Insert Filter button on top of our previous mapping:, the following appears Figure 72. Insert a filter (Alternatively, we can right-click on our old link between n1:customerinfo and Rows instead of removing it and choose from the menu. Then the filter is inserted on that link.) We will need to connect n1:customerinfo to node/row. This is our first input to the filter. What is the second one ( bool ) going to be? It is going to be the result of the function checking whether Cid of the customer is equal to the specified value. The function we need can be obtained from the Libraries menu on the left. It is a logical function called equal : Figure 73. The "equal" function Once we click on it, the following is being added to our mapping: We will need to connect the result (output from the equal function) to the bool input of the filter. What are our input parameters a and b to the equal function? a is the Cid attribute. b is a constant equal to We use the Insert Constant button and specify what we need in the form: Figure 74. Inserting a constant

55 Using the Altova Tools with DB2 purexml The following appears on the mapping: This is exactly our b input parameter for the equal function. The last thing that remains is to connect the on-true output parameter of the filter we inserted earlier to the Rows in the CSV file; i.e., we are only interested in the document for which the condition Cid = 1001 is true. This is what our whole new mapping looks like: Figure 75. Mapping using data filtering We can see that now the output only contains a single line which is the info for the customer with the Cid = 1001: Figure 76. Mapping output 8 Editing the database data using MapForce GUIs When the database is on the right side of the mapping (i.e., it is a mapping target rather than a source in contrast to what we saw in the previous chapter), we can use MapForce to modify the data in the database. The following actions can be performed: INSERT, UPDATE, and DELETE. The left side of the mapping will contain an XML schema with a document assigned to it. Let s modify the XML document (INFO column) of the customer with the Cid = We already have customer1000.xml saved in our

56 Using the Altova Tools with DB2 purexml working directory. Let s edit this document in XMLSpy to change, say, the address of the customer. This step is skipped, but the assumption is that the document has been modified. Let s use the Insert XML Schema/File button directory. The following window pops up: to insert the customer.xsd schema from our working Figure 77. Option to supply a sample XML file for the schema We choose Yes and supply our modified customer1000.xml file. Then the schema appears in the mapping: Figure 78. Schema from the file system as the source of the mapping Next we insert our SAMPLE database and choose the CUSTOMER table when asked. We also assign the IKOGAN.CUSTOMER schema to the INFO table. This is all exactly the same as in the previous chapter. Now we have the following:

57 Using the Altova Tools with DB2 purexml Figure 79. Adding a database table with an XML column as the target of the mapping Once we connect n1:customerinfo on the left to n1:customerinfo on the right, we see that actually all descendants are connected too: Figure 80. Connecting the source schema to the target schema This is exactly what we need. When this is not the case, we can use the following button that toggles auto connect of children:. We also need an arrow going from n1:customerinfo on the left to the customer table (IKOGAN.CUSTOMER) on the right in order to perform any changes to that table. Additionally, we need to right-click on the table and specify the Database Table Actions; i.e. what kind of operation(s) we are interested in:

58 Using the Altova Tools with DB2 purexml Figure 81. Database Table Actions The default action is INSERT, but it can be changed to DELETE or UPDATE (or several actions can be specified at the same time): Figure 82. Default database table action: Insert All We specify Update If instead of Insert All and the condition for update is when a Cid is equal to the specified value:

59 Using the Altova Tools with DB2 purexml Figure 83. Changing the database table action to be Update if Now we need to press OK and then specify what the Cid is equal to using a constant (1000). The mapping is validated successfully: Figure 84. Finalizing and validating the mapping This is what the output (with the password removed) looks like:

60 Using the Altova Tools with DB2 purexml Figure 85. Mapping output So it is an SQL statement in which we update the INFO column of the customer with the Cid = We replace the original XML document by the binary data in the XML file provided on the left side of the mapping. Now we need to run this script by pressing the Run-SQL-script button Once we do that, we see that the update was successful (1 row was updated): from the toolbar. Figure 86. Successful execution of the mapping against DB2 We could write similar mapping for insert and delete. We could also have mappings that affect more than one row in the table. For insert, there are all kinds of functions that we could use to populate non-xml columns. Here are just some examples: Figure 87. Examples of functions Even though some data modifications that are easier to do in the Database Query Window, the important advantage of using MapForce is that the mapping can be saved and the software program code in Java, C++ or C# can be auto-generated for it and saved as well.

61 Using the Altova Tools with DB2 purexml Transforming XML from the database to an HTML table (StyleVision) In order to transform an XML document from the database to an HTML table, we need to use StyleVision. This is what the StyleVision window looks like: Figure 88. StyleVision interface (StyleVision transformations can be organized into projects, but this is beyond the scope of this tutorial.) First, we need to insert an XML schema/document from DB2 as an object to be used in the transformation:

62 Using the Altova Tools with DB2 purexml Figure 89. Specifying that an XML column from DB2 is to be used in the transformation Once again, we connect to the SAMPLE database and choose the CUSTOMER table: Figure 90. Selecting the database table Now we need to specify which document we would like to work on. Let it be the customer with the Cid equal to 1000 (not 1001 used in the previous example/section):

63 Using the Altova Tools with DB2 purexml Figure 91. Specifying the XML document from the database Please note that our CUSTOMER table is very small and, therefore, we can just easily click on the document we need and this document is being selected. In case of a large table we would need to use Filter (Where clause) and the Update button to limit our selection to a single document: Figure 92. Using the filter when selecting a document Once we press on the Next button, we are offered to select an XML schema for our document. We choose the CUSTOMER schema from the database:

64 Using the Altova Tools with DB2 purexml Figure 93. Specifying the schema from the database When we press the Finish button, we see that the CUSTOMER schema is open in the StyleVision window and the window itself starts looking like this: Figure 94. Simple design/tranformation for the XML document from the database Discussing the Design Tree (on the left) and Styles and Properties (on the right) is beyond the scope of this tutorial (the Styles will actually be briefly discussed later in this section). The only thing that is important to notice here is that the Design Tree window shows that n1 is our XML namespace. Let s now concentrate on the Main Template and the Schema Sources.

65 Using the Altova Tools with DB2 purexml The View menu allows the user to easily specify which windows and toolbars should be shown and which should be invisible: Figure 95. View menu So if we accidently closed, say, Style Repository we can re-open it by going to the View menu. If we click on the Preview HTML for the Main Template looking as-is now, the output is very simple: Figure 96. Preview HTML result for a simple design All info about the customer with the Cid = 1000 is just shown in one line, without any spaces added. In order to make it more interesting, let us look at the CUSTOMER schema that was open in the Schema Sources window (MapForce makes it very clear that the schema is from the DB2 database):

66 Using the Altova Tools with DB2 purexml Figure 97. Schema Sources window showing a schema from DB2 As in Section 7, we are only interested Cid, name, country and the phone. We would like these four fields to be displayed in an html table. Let s remove (content) from the Main Template: Figure 98. Modifying the Main Template Let s drug-and-drop n1:customerinfo to the place where the (content) was. We see the following options:

67 Using the Altova Tools with DB2 purexml Figure 99. Creating a dynamic table from the schema We need to create a dynamic table and, therefore, we choose Create Table We need to specify which attributes and elements should be present. Let s deselect n1:assistant by clicking on it and then pressing OK: Figure 100. Specifying the attributes and elements to be present in the table

68 Using the Altova Tools with DB2 purexml Our Main Template now looks like this: Figure 101. Updated Main Template The column names were added automatically (based on the attribute/element name the column contains). They are displayed in bold by default. In general, in order to make a word in a table appear in bold, we need to choose the following style (by highlighting that word, going to the Styles menu and choosing bold for the font-weight): Figure 102. Specifying the style Are we done with our Main Template? Not really, because the second column shows the whole address instead of the country. We change the column name (first row) from the addr to the country (by doing simple editing in the cell) and erase the contents of the second row in that column. Then we drug-anddrop attribute from the schema on the left into the empty cell. We choose the first option - Create Contents. Now we have our final template:

69 Using the Altova Tools with DB2 purexml Figure 103. Final template For example, what we see for the Cid corresponds to for the selected document, where n1 is our XML namespace. This is exactly what we need. We can see that the country, name and phone are also what we would expect them to be. (content) means the actual content of the element/attribute selected. That is why we removed it in the beginning, as we did not want the content of the whole n1:customerinfo element to be present in the output. Now when we Preview HTML again, we see a nice tabular output: Figure 104. Final output: customer profile in an html table We can save it in an.html file by going to File -> Save Generated Files -> Save Generated HTML File For example, let s call it C:\XML_2007_Demo\customer_profile.html. Then we can save the whole project by using the File -> Save As and calling it customer_profile.sps, where the.sps extension stands for the StyleVision Power Stylesheets. Please note that StyleVision can easily render XML database data in HTML, PDF, Word/RTF simultaneously (for publishing and communication). We only looked at the transformation to HTML. The rest is beyond the scope of this tutorial. The same applies to the new feature to create the XSLT and XSL:FO stylesheets to publish the XML data from the database. 10 Conclusion In this tutorial, you have learned how to work with the following DB2 purexml features using the graphical interfaces from the DatabaseSpy, XMLSpy, MapForce and StyleVision developed by Altova: Create the SAMPLE database (with XML extensions) that comes with DB2 Connect to the database, visualize its structure, work with the database objects using the GUIs and understand the relationships between these objects Create tables with XML columns and XML indexes Create, validate, run and debug XQuery statements Execute SQL/XML statements, obtain and view the results