For easy parsing, the rules & format of the hidden options in configuration 
XML files should conform to the following:

1. DMU client parameters can be classified into the following three groups based
on the scope to which each parameter applies.
A. Global configuration parameters, which are in the file global-config.xml.
   Parameters in this group apply to any connections created in any DMU client 
   instances launched from the DMU home directory. 
B. User level parameters, which are in the <options> node under the 
   <connections> node directly. Parameters in this group apply to any 
   connections created in a DMU instance launched by a user.
C. Connection level parameters, which are in the special <connection> node.
   Parameters in this group apply only to the connection.
D. Connection level parameters can override user level hidden options.
   User level parameters can override the global level hidden options .
   Global level parameters can override the default value of hidden options.
E. The <update-center> option is a default tag in the file global-config.xml 
   as below:
 
   <update-center name="DMU Update Center">http://www.oracle.com/ocom/groups
    /public/@otn/documents/webcontent/1664996.xml</update-center>

This option is used to indicate the internet URL of the DMU upgrade center.

2. Currently we have the following hidden parameters, developers can add these 
   hidden options based on their requirements:
-  <!--Whether or not to stop the conversion execution when an error occurs --> 
   <stop-at-exception value="true" /> 
-  <!--Whether or not to stop SQL generation when an error occurs-->
   <stop-at-sql-generation value="true" /> 
-  <!--The threshold value of a table which is split for scanning. If the 
       used_size of table > this value, the table will be split into chunks. 
       If this value is zero, it will calculate the threshold in code. -->
   <scan-threshold value="0" /> 
-  <!--Whether or not to alter the db character set after conversion is 
       finished-->
   <skip-altercs value="false" /> 
-  <!-- is debug or not -->
   <is-debug value="false" /> 
-  <!-- Whether or not to do force conversion--> 
   <force-conversion value="false" /> 
- <!--It is in test model or not, added for QA team --> 
  <is-test value="false" /> 
- <!-- The time interval (in minutes) of printing memory usage to the log.
       Set to 0 to disable memory trace --> 
  <trace-memory-interval value="0" /> 
- <!-- If used_size of a table > this value (for example 500M), parallel 
       execution enabled --> 
  <parallel-execution-threshold value="500000000" /> 
- <!--  If used_size of a table < this value (for example 100M), regarded as a 
        small table --> 
  <small-table-threshold value="100000000" /> 
- <!--  The threshold of update convertible for large tables--> 
  <lt-update-convertible-threshold value="0.01" /> 
- <!--  The threshold of update convertible for small tables--> 
  <st-update-convertible-threshold value="0.03" /> 
- <!--  The threshold of update all method for tables--> 
  <update-all-threshold value="0.3" /> 
- <!--Bypass CDB test or not. If the value is false it will do CDB test--> 
  <bypass-cdb-test value="false" /> 
- <!-- Enable diagnostic serve side trace -->
  <diagnostic-trace enabled="true">
    <trace schema="SCOTT" level="15" /> 
    <trace schema="APPLSYS" table="WF_ITEM_ATTRIBUTE_VALUES" level="12288" />
  </diagnostic-trace>
  <!-- how many rows to be loaded in cleansing editor -->
  <cleansing-editor-pagesize value="500" />
