Use this dialog to change default settings when unmarshalling XML data to database tables.
Input File Tab
XML Content Tab
Database Options Tab
Other Files Tab
|
XML Input File |
Displays a default path name for XML input files. This path will be provided
You can override the path for individual projects using the Unmarshal tab in the Project Properties. Edit this field to provide a directory of your choice.
|
|
Encoding |
Allows you to select the encoding used in the input file from a drop-down
list. |
|
Skip references to the following entities |
This option allows you to ignore references in your input file to external files. Check the option if you want to ignore certain references, then click Add to specify the reference you want to ignore. For example, with a sample input file like the one below ***Sample Input File***** <?xml version="1.0"?> <!DOCTYPE Customer SYSTEM "http://my.com/entity1.dtd" [ <!ENTITY entity SYSTEM "customer1.xml"> ]> <xml> ... </xml> To skip the entities "Customer" and "entity", add the following in the To skip the entity "Customer", click Add, then type "http://my.com/entity1.dtd" in the Unmarshal Input File Entity dialog. To skip the entity "entity", click Add, then type ".*customer1.xml",
where the ".*" shows that the pathname is relative. |
|
Expand XML Nodes Method |
In most cases, you should leave this field with the default value. This field value is considered only if you also set values in the XML Structure tab that determine how to expand combined nodes in the XML input file. For more information, see Interpreting Nodes Using One-to-Many Relations and Interpreting Nodes Using Many-to-Many Relations. |
|
Ignore XML schema data types |
This option applies to both marshal and unmarshal settings. If you change the setting here, it will also be changed for marshal settings. By default, this option is unchecked so that XML schema data types (displayed in the Data Type column of the XML Structure tab) are used in converting XML input node values to database column values. This ensures the most accurate representation of data types based on the XML schema. For example, if you check this option to ignore XML Schema data types, types defined as date-time in the XML schema will be interpreted as strings during the unmarshal operation. |
|
Validate against XML schema of project |
Check Validate against XML schema of project to validate XML input using the XML schema that was specified when you created the project. |
|
Transaction Isolation Level |
Either leave the default or select a different
transaction isolation level. |
|
If tables do not exist in database, create |
This option allows you to control which database structures will be created during unmarshalling if the tables in your mapping file do not exist in the database. The settings here depend on your database user ID (whether you have permissions to create tables etc.) If you are connecting to a FoxPro database, you should also enter a directory to use in creating tables because each table is created in a separate file. If you do not enter a directory, tables are created in a Tables directory in your Allora project directory. For limitations on creating tables with FoxPro, see http://www.hitsw.com/support/kbase/allora/Allora-JDBCDrivers.htm.
|
|
Override settings from the Table Properties tab |
Typically, settings that you have made in the Table Properties tab and the default settings in this dialog are sufficient for most cases of unmarshalling so you do not need to check this option. However, if you have tried the default options and your data does not appear in the database as needed, you can set the options below to for additional control over the unmarshalling operation. |
|
Auto-Incremental Columns |
An auto-increment column is a column with a numeric value that is set automatically to provide a unique value for each record. If you know that your database does not support auto-increment columns, or you specifically want to override the automatic values set by the database, check the option to "Ignore auto-incremental property settings for columns". |
|
If a record's unique cols match an existing record |
By default, if you have set the Update On insert table property on the Table Properties tab, existing records will be updated during the unmarshalling process. Existing records are determined buy comparing the values of columns that you have set as Unique in the Table Properties tab. You can override this setting so that existing records are inserted as new records (Insert new record) or existing records are neither inserted nor updated (Skip record).
|
|
Dynamic Parameter File |
If you have added a predicate that requires parameter values, you need
to specify a file name that contains the parameter values. If no file
is displayed, click Browse to
open the Dynamic Parameter Values File dialog. Locate
a directory, type a file name and click Select.
If you have created dynamic parameters but no file for them, use the Project Explorer Dynamic Parameter
Files node to create a new file and add your dynamic parameter values.
|
|
Lookup File |
If you create Lookup Rules associated with your mappings, you must supply the lookup file and ruleset to use during unmarshalling. If no file is displayed, click Browse to open the Lookup File dialog. Locate a directory, type a file name and click Select. If you have created lookup rules but no file for them, use the Project Explorer Lookup Files node to create a new file and add your lookup rules and values. |
|
Script File |
This field allows you to select an existing script file to use during the unmarshalling operation. Click Browse to located the file. When you have selected the file, the Script Type field will be filled in with one of the following values: Javascript, Jython or Java class. If you supply a Java class, the class name appears in the Java Class Name field.
|
How to Access the Unmarshal Settings Dialog
Choose Project then Unmarshal Settings..., or, in the main toolbar, click Unmarshal Settings.