XML Extender

8 8 8

Decomposing documents larger than 1 MB

8

You do not need to drop and recreate the stored procedure dxxShredXML to decompose documents that are larger than 1 MB. To decompose documents 8that are larger than 1 MB, invoke the stored procedure dxxShredXML100MB, which can shred documents up to 100 MB. Although dxxShredXML100MB can handle large documents, you might need to increase other resources 8for the stored procedure to complete successfully. To invoke the stored procedure 8 through the sample program dxxshrd, use the new flag "-large". For example:

8
dxxshrd -large mydb xxx.xml
8

If your version of DB2 Universal Database is earlier than Version 88 FixPak 6, you must run dxxMigv to migrate XML Extender to the 8current level to run the new stored procedure.

7 7 7

Configuring MQ XML UDFs with XML Extender

7

You must configure and enable MQ XML user-defined functions (UDFs) 7before you can use them.

7
7Prerequisites 7

Install the UDFs by following the procedure in the "Installing DB2 WebSphere MQ functions" 7topic, which is found either in the Information Center or the IBM DB2 Information 7Integrator Application Developer's Guide.

7
7Procedure 7

To configure and enable MQ XML UDFs with XML Extender:

7
    7
  1. Open a DB2 command prompt window.
    2. 7
  2. Connect to the database that will use the MQ XML UDFs by entering the 7following command: 7
    db2 connect to <database>
    3. 7
  3. Change to the bnd directory within the path where you installed DB2 Universal Database, such as: 7
      7
    • SQLLIB/bnd (Linux and UNIX)
      • 7
    • C:\Program Files\IBM\SQLLIB\bnd (Windows)
    4. 7
  4. Bind the database to XML Extender using the following command: 7
    db2 bind @dbxxbind.lst
    5. 7
  5. Bind the database for XML Extender to use the MQ XML UDFs using the following 7command: 7
    db2 bind mqxml.bnd
    6. 7
  6. Bind the database to the CLI using the following command: 7
    db2 bind @db2cli.lst
7 7 7

XML Extender environment variable DB2DXX_MIN_TMPFILE_SIZE

7

DB2 XML Extender can place large documents in temporary files to avoid 7using a great amount of memory during processing. On systems with large amounts 7of physical memory, you can avoid moving documents to temporary files, reducing 7the amount of Input/Output activity. The environment variable DB2DXX_MIN_TMPFILE_SIZE 7instructs XML Extender to use memory buffers, instead of temporary files, 7 for processing documents smaller than the specified value. The variable 7is applicable only on the server. If multiple physical nodes participate 7in a partitioned environment, the variable can be set differently on each 7node, accurately reflecting the amount of memory installed on each computer. 7If the environment variable is not set, documents larger than 128 KB will 7automatically be placed into temporary files during processing. Documents 7smaller than 128 KB will be processed in memory.

7 7 7

DB2XML.XMLVarchar UDT redefinition

7

You can redefine the user-defined type (UDT) DB2XML.XMLVarchar up to 32 7KB. To change the size of an XMLVarchar UDT, create the UDT before you enable 7the database for XML Extender.

7

For more information, see DB2 XML Extender Administration and Programming.

[ Top of Page |Previous Page | Next Page | Contents ]