Use the Archive File to XML Convertor to convert Archive
File data to XML format. You can identify the data to convert by typing
SQL SELECT statements or using a batch file. You can also create a
file that includes an XML schema describing Archive File data.
The Archive File to XML Convertor requires Java™ JRE release 1.4 or later. To
open the Archive File to XML Convertor, run the atoxml.jar executable
file, located in the ODM\java subdirectory of the Optim™ installation directory.
For
batch and command line documentation, refer to the Archive File to
XML Convertor online help, available from the Help menu.
Interactive Tab
Use
the Interactive tab to type an SQL STATEMENT
that specifies the data to convert.
- Parameters
- Server
- The machine name of the ODM Server, followed by a colon ":" and
the port number. If the default port number (2551) is used, the port
number can be omitted.
- Data Source
- The data source for the Archive File.
- Maximum Rows
- The maximum number of rows to convert to XML.
- Root Name
- The name of the root XML tag.
- Rowset Name
- The name of the XML tag in which the data is placed.
- Generate
- Schema
- Select this check box to include XML schema of the Archive File
data with the output XML.
- XML
- Select this check box to include Archive File data with the output
XML.
- Mode
- Element
- Select this check box to generate an XML tag for each data value.
- Attribute
- Select this check box to generate <row> tag attributes for
each data value.
- Execute
- Click to begin the conversion process.
- SQL Select
- Type an SQL SELECT statement to specify selection
criteria for the data.
- Messages
- Displays messages for the conversion process.
- Output
- Displays the XML output.
Batch Tab
Use
the Batch tab to specify the data to convert
by using a batch file or typing batch parameters.
- Open File
- Click to select a batch input file.
- Messages
- Displays message for the conversion process.
- Execute
- Click to execute the batch process.
- Input
- Type the batch parameters, if a batch input file
is not used.
Conversion Issues
The
following issues arise in the conversion of archived data to XML:
- Characters that are not legal in XML, including
characters less than x'20' (except for carriage return, linefeed,
and tab), are replaced by a '?'. A diagnostic is written when this
occurs.
- CLOBs (character large objects) are written as
single long lines.
- Binary data is encoded as base64 data and written
as single long lines.
- Null columns are omitted in attribute mode and
indicated by xsi:nil="true" in element mode. Note that because of
a limitation in the Attunity interface, null large objects are given
zero length; they are not marked explicitly as null.
- Characters in the first column of the following
table are translated to the entity reference in the second column:
| Character |
Entity Reference |
| “ |
" |
| & |
& |
| ‘ |
' |
| < |
< |
| > |
> |