Xoom 2.1 has been released

A new version of Xoom, 2.1, has just been released. The version builds functionality on top of version 2.0 which marked the transition to the major new version of .NET, 4.0. We summarise the new features and bug fixes below.


  • Scheme, infrastructure and data-entry matching support have been finalised for Service Optimization 8 (or newer). The majority of core interpretations has also been added. This makes this release the first Xoom version that is practically usable for Service Optimization 8.
  • Settings Migration Tool now displays the representation of the selected setting in the Export tab. This is particularly useful when quickly browsing through various settings of the same kind to understand how they are configured.
  • Xoom Explorer’s XPath text box now changes background colour depending on whether the result is zero (white) or more (green) hits, or whether the XPath is invalid (red).
  • XoomToolkit now supports a number of additional features:
    • Xoom messages can now be sent to remote servers.
    • Writing the result to an output file instead of the console is now supported in order to avoid the mangling of Unicode characters in some cases.
    • XSLT transformation (running a report) of the result of a Xoom call is now supported.
  • A report to remove transactional information from the Xoom file has been added. The main purpose of the new report is to ease the configuration versioning use case.

Improvements / changes

  • Detailed interpretation for a number of additional settings of both Service Optimization 7.5 and 8 has been added.
  • Consistency of formatting of Xoom files obtained via different client tools has been improved.
  • Xoom Console now imports scheme changes by default.
  • Automatic data-entry matching (for rule, objective and BVF interpretation) has been improved in its reliability. The Booleans are now also interpreted as Booleans, not as numbers.
  • The robustness of the installer has been greatly improved.

Bug Fixes

  • Corrected incorrectly reported maximum optimisation time in the BGO report.