How To Migrate Dimension Value ID Mapping From Forge-Based to CAS-Based Applications
(Doc ID 2086838.1)
Last updated on DECEMBER 09, 2024
Applies to:
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.2 and laterOracle Commerce Platform - Version 11.2 and later
Oracle Commerce Cloud Service - Version 24.08 and later
Information in this document applies to any platform.
Goal
Is there a module or a guide that gives instruction on how to migrate dimension value ID mapping from a Forge-based application environment to a CAS-based 11.2 environment?
Oracle Commerce Platform + Oracle Commerce Guided Search integrations prior to release 11.0 would, by default, utilize a Forge-based deployment template out-of-the-box.
However, as of Oracle Commerce 11.1, the CAS-based, or "Forgeless" deployment template is used in the out-of-the-box integration configuration.
A conversion process would therefore be required to maintain the existing dimension value ID mapping, to prevent a change in any existing URL "N-parameters".
As an example, if a URL exists in the current, Forge-based application:
http://www.discoverapp.com/en/browse/brands/sony/_/N-12497
Ideally, this URL will remain the same after upgrading the application to 11.2.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |