Xoom 3.8.4 has been released

This is a minor patch release fixing a single bug that caused a misconfiguration to be reported and the interpretation stopped in some rare cases where the situation wasn’t actually an error but a arose from different XML representations in different versions of Service Optimization. The warning with a descriptive message is now issued instead, and the interpretation continues.

Xoom 3.8.3 has been released

This is a patch release implementing the following changes:

  • Convenience types “Action Type” and “Roster Get Candidates Policy” were added to knowledge base, References Report and Bad References Report.
  • The interpretation of ClickRoster configuration, generic events and reports were improved.
  • Corpus capture functionality was also improved. Among other things, Xoom Corpus Generator now captures more relevant information, which decreases the probability of missing the information required for the creation of custom Xoom installers.

Xoom 3.8.2 has been released

This is a minor patch release that fixes a bug in the Service Optimization scheme implementation that previously required newly created collection’s ProductName to be globally unique. On the Service Optimization side, this requirement is only true for top-level collections, while for child collections (such as multi-values) ProductName only needs to be unique within the scope of their parent collection. The fix takes this into account and corrects the behaviour.

Xoom 3.8.1 has been released

Xoom 3.8.1 is a patch release that contains the following changes:

  • Added a new report called Bad References Report. This report lists all bad references in the provided XoomXML. The references are sorted by their originating item and reference type, and each entry also specifies the reference path within the item and their current value, making it very easy to determine which bad references are most urgent to fix, such as for example when a reference is to a non-existent key.
  • Objectives Report now lists objective types as well as categories, making it more informative and easier to navigate.
  • Custom installers that require post-installation actions that require Xoom to be running now take into account the value of DISABLESERVICESTART installer parameter before attempting to perform those actions.

Xoom 3.8 has been released

We are proud to announce the release of Xoom 3.8. This major new release introduces first-class support for Windows PowerShell scripting to Xoom, and with it a new product, Service Optimization Tuning Toolkit. This exciting development brings a host of new scripting and automation capabilities to configuration management, as well as major improvements to the way ClickSchedule configuration can be tuned and maintained, with direct operational impact.

Continue reading Xoom 3.8 has been released

Xoom 3.7.7 has been released

Xoom 3.7.7 is a patch release that contains the following changes:

  • Added support for scheme changes introduced in Service Optimization 8.2 and 8.3.
  • Improved the handling of many-server environments. Service Optimization code that was previously used by Xoom wasn’t robust in handling the parallel access to multiple servers, resulting in unexpected errors and sometimes failure to start the Xoom service in many-server environments. Xoom now uses its own code that suitably addresses this case.
  • Xoom installer now accepts an optional parameter DISABLESERVICESTART. The parameter enables the installation to complete successfully without attempting to start the Xoom service. The purpose of the new parameter is to make it easier to diagnose the problems and find the solution in rare cases where Xoom service can’t be started for whatever reason.

Xoom 3.7.6 has been released

Xoom 3.7.6 is a patch release that includes the updated SXP Extensions for Service Optimization containing significantly improved look-up capabilities for SXPXoomGetObjects. The change won’t affect most users of Xoom, and has been introduced in order to enable more advanced customised use cases, in particular transactional data migration.

Xoom 3.7.5 has been released

Xoom 3.7.5 is a patch release that includes the following changes:

  • Object References are no longer sorted by object name. The decision to make this change was made due to the fact that we encountered a single case where the sorting resulted in a functional error. The sorting was previously considered (and still is, according to ClickSoftware’s product documentation) to be an entirely safe convenience feature making it easier to look up object references using Xoom tools, XoomXML files and Service Optimization Administration tool.
  • Both the readability and usability of Bad References Report have been improved. By displaying the value of the element that contains the actual bad reference, the report now makes it easier to decide whether the remedy for each particular bad reference is in the configuration or in the knowledge base (i.e. in the erroneous interpretation of the configuration).

Xoom 3.7.4 has been released

Xoom 3.7.4 is a patch release that includes the following changes:

  • The installer now allows users to specify the installation directory, both from command line and via the user interface. This is the directory where both Xoom and Xoom W6 directories will be created. The default directory is: “C:Program Files (x86)Zany Ants”.
  • Settings Migration Tool no longer excludes the deployment of Agents Manager and Mapper settings due to the introduction of suitable keep-target instructions that will prevent server names from being overwritten by default.

Xoom 3.7.3 has been released

Xoom 3.7.3 is a patch release that includes the following changes:

  • It introduces a new standard query called Structure, which includes scheme and object reference setting. This query is very useful for automated analysis of the compatibility of different environments and the capability of transferring data between them.
  • Xoom Processor now implements a built-in custom command called GetCustomQuery. The command takes a skeleton structure as its input, and fills in the details using Xoom, exactly as though the skeleton were the body of a named query. This means that ad hoc queries can be used with Xoom without the need to define corresponding named queries.