The process of installing Xoom is simple. It constitutes of running an installer supplied by Zany Ants and answering a handful of questions in order to allow Xoom to connect to the local installation of Service Optimization. The installer does the rest by checking the prerequisites, installing Xoom and, if necessary, registering custom components that are needed on Service Optimization side for Xoom to fully function.
Example business case for Xoom
This presentation presents a detailed business case for Xoom for a large Service Optimization customer. The business case is an example of the sort of savings that can be made when Xoom is used in a fairly simple way for configuration transportation and configuration versioning.
Upgrading with Xoom
Upgrading Service Optimization from 7.5.x to 8.1.x can be a complex, largely manual process that is subject to a lot of uncertainty and risk, and lacking a suitable tool chain. Xoom addresses many of these problems by supporting a fast, automated, customisable and repeatable upgrade process and a painless and well-tested production deployment.
Configuration versioning using Xoom (technical)
In this tutorial, we describe the steps to set up a scheduled task that at regular intervals acquires a configuration snapshot using Xoom and stores the resulting Xoom file into a Subversion repository. This results in the ability to see what changes, intended or not, were made to the configuration of the system at what time, and allows the user to effectively revert back to the configuration at any point in the past. Continue reading Configuration versioning using Xoom (technical)
Xoom 3.0 has been released
Xoom version 3.0 has been released. This release is built on top of the Windows Communication Foundation infrastructure, and exposes deeper Xoom functionality to client tools and scripts through web services. The release also features major performance and stability improvements, a new tool for implementing renames of settings in the context of a configuration clean-up, and a number of other enhancements. We summarise the new features and bug fixes below. Continue reading Xoom 3.0 has been released
Xoom 2.2.1 has been released
This is a hotfix release addressing Xoom 2.2. It fixes the version detection for the recent builds of Service Optimization 7.5 (which were erroneously identified as version 8 due to the use of the same kind of installer), and fixes a bug where an XML directive within an interpreted XML string caused Xoom to throw an exception.
Xoom 2.2 has been released
Xoom version 2.2 has just been released. This release improves the support for Service Optimization 8+, introduces a generic concept of configuration stages, hierarchical parameterisation for Xoom, and Zany Script, a language for expressing configuration conditions with contextual awareness. Detailed documentation will be provided later, but we summarise the new features and bug fixes below. Continue reading Xoom 2.2 has been released
Xoom Demo Video (2010)
This is the demo video we used for some time now in order to introduce Xoom’s capabilities on a semi-technical level. The video was made in March 2010 and is somewhat dated now as the tools’ UIs have evolved, but the basic behaviour is still the same. The video doesn’t have a narrator and explains everything in captions, which makes it handy for demo sessions with spoken explanation and discussions.
The video covers the following:
- Export using Settings Migration Tool.
- Reporting using Xoom Explorer.
- Import using Settings Migration Tool.
We recommend watching the video in full-screen mode in order to make the text on screen (not just the captions) readable.
Xoom Glossary
Certain terminology is used consistently throughout the Xoom documentation and tools to refer to concepts that have a well-defined meaning in the context of Xoom. Here, we define the most important of those terms in a logical order (not alphabetically). Continue reading Xoom Glossary
Changing ClickSofware username and password used by Xoom (technical)
In order to connect to Service Optimization, Xoom is provided with a username and password during its installation. We recommend that a dedicated user is created for Xoom which doesn’t have any other rights, including the right of remote access to the server on which Xoom is installed, and with a password that doesn’t expire. When that is not possible and there is a policy that all passwords need to expire after a certain amount of time, we provide a way to set this password for Xoom through the command line tool called XoomToolkit. Continue reading Changing ClickSofware username and password used by Xoom (technical)