RSM archives are zip files containing Rule Scenario Manager executable elements (scenarios, scenario suites, simulations) and their dependent data (input data, tests, baseline reports). They must also contain a file called archive-desciptor.xml, which defines the root executable element in the archive.

Archives must be a complete set of elements ready to execute. For example, an archive containing a scenario suite definition must also contain the definitions, input data, tests, and baseline reports of each member scenario of the suite.

When you select an archive to load, you first view its contents in a hierarchical tree format, with an option to confirm or cancel the loading:

An archive can be created manually by developers and imported into the Console, and they can be downloaded directly from the Console. As all elements in an archive are available within the Console after it is loaded, archives are useful for transferring file-based elements into the Console.

Adding an RSM archive into the Console more than once imports all of its elements each time. The Scenario Browser, for example, will show loaded scenarios in the table as many times as it was loaded via the archive. You can avoid this behavior when reloading RSM archives that were originally created by downloading them from the Console. Clicking Update instead of Add forces the newer versions of artifacts in the archive to replace any other versions with the same ID, thus avoiding duplicates.

Load an RSM archive

The artifacts in the archive are loaded, and can be viewed in the other pages of the Console.

See Also