How to Migrate Dimension Value IDs Between Environments in a Forge Implementation
Last updated on AUGUST 31, 2016
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 5.1.5 and later
Information in this document applies to any platform.
We have multiple Endeca environments, for example Development and Staging, which both use Forge to create and map dimension values (we do not use Forge Configuration Manager or Deployment Template for Product Catalog Integration (DTPCI)). We need to ensure that each environment uses the same dimension value ID mappings for internal, auto-generated, and externally managed dimensions. How do we migrate dimension value ID mappings between the two environment's Forge pipeline configurations so that they each use the same dimension value mappings?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms