AppMapping support in Shopping

From AppClarity 5.1, the Catalog – which is used to map and correctly identify installed applications – has become a separate component with a new schema. By default, Shopping 5.3.100 and later is configured to be backwards compatible with AppClarity 5.0 and earlier. If you intend to integrate with AppClarity 5.1 or 5.2 (whether through an upgrade or first time installation), you must run the Application Mapping Migration wizard so that application mapping works with the Catalog's new schema.

After running the Application Mapping Migration wizard Shopping will no longer be backwards compatible with previous versions.

Before running the Application Mapping Migration wizard you must configure the Shopping settings that locate the AppClarity database and the AppClarity and Catalog API endpoints. Post-migration, Shopping 5.3.100 will no longer be backwards compatible with previous versions. We recommend you carry out the migration at a time that has the least impact to your business operations.

To migrate to the new catalog using the Application Mapping Migration wizard:

  1. Stop the Shopping central service.
  2. Stop the Shopping receiver service.
  3. Stop the Shopping Web service.
  4. Backup the Shopping database.
  5. Run the wizard by clicking the Application Mapping Migration wizard icon in the Shopping Admin Console.
    The Application Mapping Migration wizard in the Shopping Admin console 
  6. On the Welcome screen, click Next.
  7. On the Prerequisites Check screen, checks are made to ensure that the Catalog and Shopping APIs are accessible when you click Next. If these APIs are not accessible, you are prompted to resolve the issue before you can complete the migration.
    Checks to ensure that the Catalog and Shopping APIs are accessible pre-migration
  8. On the Shopping Application Ref ID Migration screen, review the Vendor, Title, Version and Edition fields. These fields must have mappings against them before you can continue. If pre-populated values for Vendor, Title and Version are incorrect or incomplete, click the down arrow next to it for a list to choose from – they are mandatory fields. The Edition field is mandatory only if it is available for an application.
    Mapping the vendor, title, version and edition fields to the catalog
    Click Next when all the fields are mapped. 
  9. On the OSD Mapping Rule Migration screen, review the Vendor, Title, Version and Edition fields and update them if necessary.
    Mapping the vendor, title, version and edition fields for OS deployments
    Click Next. 
  10. On the Migration screen, read the information about the migration process and confirm that you have backed-up your Shopping database and stopped the Shopping Web. Click Migrate.
    Ready to migrate
    If the Shopping web is still running, you are prompted with:
    Warning that the Shopping web is still running
    You must stop the Shopping Web before you can continue.
  11. On the Finish screen, click Close.
  12. Restart the Shopping Web service, the Shopping receiver service and the Shopping central service.

Reviewing the impact of the migration

The changes that take place after the migration are:

  1. The Application Mapping Migration wizard toolbar in the Shopping Admin console is no longer accessible.
  2.  In the Shopping console under Integration, the value for IntegratioMode is now Catalog (it was AppClarity before the migration).
    Post migration integration mode 
  3. For the applications that were migrated, an Integration tab is now visible in its Properties dialog.
     
  4. Log in to the Shopping Website as the administrator and on the Administration tab, go to OS Migration and review your OS mapping rules.
    OS deployment mapping rules
    For any rule where Vendor, Title, Version and Edition fields are not populated, it is highlighted and classified as invalid and are never used in any OS deployment. To use them, click Edit and update the Vendor, Title, Version and Edition fields.