Migration considerations

If you are considering migrating to a CAS-based record store data ingest model, the generate-dval-id-mappings task is a required step within a larger migration process.

This task is used to extract Forge-generated dimval IDs and convert them so that they can be loaded into a CAS-based dimension value id manager. If you do not perform this task, then you lose your dval state information, and all of your existing site URLs no longer work. In particular, inbound links, which get cached by external systems like internet search engines, point to the wrong pages.

A larger migration might look like the following:

  1. (Optional) Learn the CAS-based record store merger data ingest model by setting it up in a development environment.

    Although optional, Oracle recommends performing this step. In particular, it helps you to learn the appropriate product interfaces for updating records and updating taxonomies.

    1. Install Oracle Commerce Guided Search in a development environment.

    2. Create a new record store merger application using the /ToolsAndFrameworks/VERSION/reference/discover-data-cas/deploy.xml deployment template.

    3. Take a snapshot of your production Forge output directory.

    4. Execute the transform-forge-output task on the forge output snapshot, and then load the transformed data and configuration.

    5. Execute a baseline update.

  2. Redirect existing data sources to the appropriate record stores.

    This step might require changes to custom integration code that you have written for Forge or CAS/FCM/Forge. If you are using a previous version of the Oracle Commerce Platform/Oracle Commerce Guided Seargh integration, then you should be able to simply reconfigure the Platform-to-Guided Search repository export mechanism.

  3. Deploy changes to staging and production environments.

After you have implemented and tested the changes to your upstream data integration logic, you can then deploy them to their various supported, non-development environments. As part of this step, you must deploy the new data application into each environment and redirect source systems. You must execute the generate-dval-id-mappings task to migrate all Forge-based dval ID mappings into the CAS-based dimension value ID manager.

Copyright © Legal Notices