In the event of having a large XML layout to be loaded as a source or destination while creating a mapping, it may take a lot more time than required. In this case, you may need to optimize the loading of the layout.
| Info |
|---|
| By default, the loading of an XML layout is configured to be optimized in Web Mapper. However, you can modify the configured settings based on your requirements while you are creating a mapping. |
When you optimize the loading of the layout, it means it processes only the root level element; not the complete XSD, if the XSD is complex. When you expand the hierarchy elements, it processes child elements and loads them into memory. The hierarchy elements expansion is now displayed in the Web Mapper. With default settings, it optimizes the processing of XML layouts and loads the XSD elements up to 3 levels in the source and destination panels. You need to click a hierarchy element to load its child elements.
| Tip |
|---|
| Optimization of layout loading is only applicable on XML layouts. |
- Ensure that all the source and destination layout are loaded and all their elements are listed under their respective nodes.
Go to Open > Preferences.
- On the Preferences screen, click XML Layout from the left pane.
This displays the optimize layout loading configuration properties.
On demand (optimized) loading of XML Schema tree | Process only the root level element; not the complete XSD, if the XSD is complex. When you expand the hierarchy elements, it processes child elements and loads them into memory. The hierarchy elements expansion is now displayed in the applet. This option is applicable only on XML schemas. It optimizes the processing of XML schemas and loads the XSD elements only up to 2 levels in the source and target panels. You need to click a hierarchy element to load its further child elements. |
Cache Included Schemas | Set whether or not to cache the included XML schemas instead of inlining them as specified by the XML schema specification. This is applicable to all XML Schema which uses XSD. |
Tree Expand Level for Optimized Loading | Defines the hierarchy level up to which the source and target files will be displayed for the schema loaded in Data Mapper. Hierarchy level is defined in the Tree Expand Level Dialog, which is opened when a user clicks this menu option. By default, its value is 3, that is, Data Mapper will display the hierarchy of source and target files for the respective schema up to level 3. |
Easy Schema Parser Configuration | Defines the hierarchy level up to which the source and target files will process the schema to load it into the Data Mapper. You can define the hierarchy level in the Tree Expand Level Dialog box, it appears when you click on this menu option. The default value in the Tree Expand Level Dialog box is 10. This means that the Data Mapper will display the hierarchy of source and target files for the respective schema up to level 10. |
Another way of splitting source data is to enable the quick splitting feature. This splits the source and sets the Splitter Xpath.
...