The native SystemWeaver XML format can be used for the exchange of SystemWeaver models and meta models between SystemWeaver databases using the Export to XML and Update from XML views. From a technical point of view, the base requirements for a data exchange between two SystemWeaver servers to be possible are that the source and destination databases share the same metadata structure for the data being exported or that it is possible to convert the exported meta model into the meta model on the receiving side.
It should be noted that converting exported data to fit into a different SystemWeaver installation that does NOT use the same meta model can be complicated and potentially impossible. See Available Data Conversion Solutions for more information on the conversion options.
- Configuration is done in Configure the explorer, therefore, the SW Architect role is required.
To export data from one SystemWeaver server to another, the configurable view XML Export can be used. This view contains a variety of configurable options, but the most important ones for your scenario are IncludeParts and IncludeAttributes. They are used to define what metadata information to include in an export.
Note: The content of an XML export is affected by the exporting user’s access rights. The user must have a minimum of Read rights.
Similarly, for the receiving side there is a configurable view called XML Import, with the same configurable options as XML Export, i.e., IncludeParts and IncludeAttributes. The XML Import view also includes the capability to convert metadata (C) in a received XML to adapt it to the meta model in the receiving database. There are, however, limitations as to how different the exporting and receiving databases can be.
Once configuration is completed, you are ready to use the XML import tool which is available to all users in Explorer. The tool is described in Importing Data Using Import from XML.
Export and Import Frequency
There are several different scenarios that the export and import functionality can support:
One-Time Export and Import
This scenario is rather straight forward and only requires that the exporting and importing databases have compatible meta models. Since the export is a one-off, there are no further requirements.
Continuous Export and Import (One Direction)
Continuous export and import in one direction is normally used when an OEM wants to supply a Tier X with reoccurring updates of information. For this to work properly and transparently, it is recommended that all information that is exported has a Status of 'CS_Released'. This will ensure that change logs on the receiving side can function properly making it easy to analyze information deltas. It is possible to export information with a Status of 'Work', but it is hard to analyze what has changed from one import to another since the changes will not be indicated by new versions. A base assumption in this scenario is that imported data is considered read-only. If the imported information were to be edited in the receiving database, the next import would produce branches. This may not be a problem if the changes can be discarded at the next import. However, unnecessary branches will decrease the readability of the versioning information.
Round-Trip Export and Import
The recommendation in this scenario is to give the Tier X supplier access to the SystemWeaver server so that all parties can collaborate in real time instead. This also shortens the lead time for feedback. If there are limits to what a supplier is authorized to see, the read access control can be enabled and used.
Learn more about XML Export and Import of data in the SystemWeaver Help or in Exporting and Importing.