Migration from Previous Versions

•This version is backward incompatible with release 12.0.

•For versions 12.1, 12.2, 12.3, 12.4 and 12.4, there is automated migration, which ensures that both the server and the agent can be migrated, together with user data

For detailed information about the migration process, refer to the Installation Guide.

Getting Data for USU ITSM Overview

This chapter describes how to get the data for the newly added USU ITSM connector. These steps should be executed after the update of the server instance to the newest version.

1.Start the import wizards "Import > From template..."" in the library view.

2.Select dashboard "USU-ITSM-Overview" under Connectors section and enter the necessary data for a new task:

oUSUVALUEMATION_PNP_MATCHINGTABLE_URL = "http://www.linux-usb.org/usb.ids.gz"

oUSUVALUEMATION_INVENTORY_DATA_TABLESTART = "Inventory"

oUSUVALUEMATION_INVENTORY_DATA_CONNECTION = "Data Source=(local);Initial Catalog=[DataHub];Integrated Security=True

oUSUVALUEMATION_DISPLAYNAME_FQDN = 1

oUSUVALUEMATION_DEVICE_IMPORTID = 1

3.Add the variable USUVALUEMATION_PNP_MATCHINGTABLE_URL with value http://www.linux-usb.org/usb.ids.gz manually, if it is not shown in Wizard

4.Run 5 tasks in "TASKS > USU > ITSM > IMPORT" folder to generate import data.

5.Run all 22 tasks in "TASKS > USU > ITSM > EXPORT" folder to generate export CMP data.

Breaking Changes and Important Notes

•Default RayVentory tasks have now dependency on stored procedures, installed with AsperaConnector version 12.2.0.11458 or later. The version may be installed as a part of RayVentory server installation or separately (as a SQL file). The new version of the connector is required to use the newly added USU ITSM connector tasks.

•Some tasks and reports might need to be re-imported to benefit from changes and fixes brought by this release. This is especially valid for SQL-based tasks, where the logic is encapsulated as a SQL script in the Task Configuration.

•The server should be always installed with the matching version of the agent. Mixing versions (for example 12.6 Data Hub and 12.1 Data Hub Agent) is not recommended and may lead to unexpected issues.

•Important changes for users migrating from version 12.2 (without Service Packs)

oWe have changed the way the report table name resolution works. The previously used separator (dot) is not used anymore in favor of a minus sign.

oThis means that the tables created by 12.2 extraction tasks followed the following naming convention dataset.tablename, whereas the new one puts out dataset-tablename. The migration script included in this build should be able to convert your existing reports to the new format, but the data will only be available once all tasks are restarted. You may also do the renaming on your own.Important changes for users migrating from version 12.2 (without Service Packs)