Many of the views used in SystemWeaver are configurable and the definitions are saved as XML. There are two types of views that can be configured: 

  • Item views available via Configure the explorer
  • Configurable items (also known as Config Items) in the form of reports, grids, graphs, charts, etc.

To help Architects keep track of the XML configurations for both configured item views and Config Items, SystemWeaver provides a number of different options/tools for exporting XML definitions. This article outlines the options that are available.

Summary of Export Options

This table summarizes the export options by tool. 

ToolItem View ConfigurationsConfig Items
swExplorer clientYes, as separate, readable XML filesYes, as binary that can be imported into SystemWeaver
swArchitect clientNo, but you can view themYes, as binary that can be imported into SystemWeaver
SystemWeaver APIYes, as separate, readable XML filesYes, as binary that can be imported into SystemWeaver


  • Assignment of the SW Architect role in the database
  • An installation of the SystemWeaver Architect client (swArchitect)
  • An installation of the SystemWeaver Explorer client (swExplorer)

Item View Configurations

There are two ways to export item view configurations.

Using the Export Configurations Option

You can export the Explorer item view configurations which are defined in Configure the explorer by using an Export configurations tool in the swExplorer client.  The resulting output are the readable XML definition files. See Exporting Explorer View Configurations for how to do this.

Note: This export does not include configured reports, grids, graphs, XMLs and Charts. See Config Items below.

Using the API to Export

It is also possible to get all XML definitions using the SystemWeaver API. The output is separate, readable XML files.

Config Items - Reports, Grids, Graphs, XMLs and Charts

There are a number of ways to export Config Item XML definitions depending on whether or not you would like to export the meta model for Config Items as well. 

Exporting the XML Definitions Together with the Server Meta Model

At some point, a situation may arise where you want to export a server's meta model including the meta data of all Config Item types as well as the Config Item definition items themselves, e.g., to migrate to a new database, create a database copy for testing purposes or share your meta model with a supplier or customer. This can be done using the swArchitect client and the resulting output is one XML file. The Config Item definitions are in binary format. 

Select XML Export..., check the Include config-items box, and click OK. See Exporting an Entire Meta Model for more information.

Tip: If you have already done a meta model export without the Include config-items option selected, you can simply do the export again with the box checked.

Note: This export does not include item view configurations. See Item View Configurations above.

Using XML Export in swExplorer

You can also export the Config Items, with or without the meta model, using the swExplorer client. To do this, you will first need to create a work area for the config items. This is explained in Viewing Config Item Definitions. Once the structure is in place, load the XML Export view. Note that this view must be set up to allow the export of your work area top item. Make your selections and click Export. The resulting output will be one XML file. The config item definitions are in binary format and can be imported into SystemWeaver. 

In the below example, a WorkArea called "All Config items" contains a number of grid and graph definitions. Only referenced meta data will be included with the Config Items in the export. See XML Export: Exporting Models from SystemWeaver for more information on export settings.

Export Grid to Excel

Another option is to configure a grid view to provide you with the XML definitions. The grid content can then be exported to Excel if needed.

Using the API to Export

It is also possible to get all XML definitions using the SystemWeaver API. The resulting XML contains the config item definitions in binary format.

What's Next?

If needed, you can import the Config Item definition items themselves, use the XML Import view in the swExplorer client.