Go Live Checklist: Migrating Data

Overview

• This document will describe all the steps necessary to migrate data from one instance to another instance.
• Typically this will be used to migrate the Staging (or UAT) to Production for the initial setup.
• This document will use the terms source and target.
• It is not anticipated that these steps will be used after Go Live.

Pre-Requisite

• The target database should be cleaned of all Product, Category, Content and other data.

Product Catalog

• Whichever strategies were used to initially load the source database should be repeated.
• This will include Category, Product, Associated Products and Image assets.

Learn More: Product Loader

General Data Migration

• This includes the various content that has been setup during testing on the source instance.
• On the Source Instance:
  • Admin Admin Tools BigFish XML Exporter
  • Check all the boxes so that all user content is included in the export
    • Content Library
    • Site Info
    • Home Page
    • Static Pages
    • Page Content Spots
    • General PDP Spots
    • Product Category Content
    • Email Templates
    • Txt Templates
    • Payment Gateway Settings
    • Shipping Charges
    • Sales Taxes
  • This will create an XML file, this should be saved in a location that can be accessed by the Target instance.
• On the target Instance:
  • Use OFBiz OOTB
  • Access Webtools
  • Click on Import/Export
  • Click on XML Data Import
  • Enter the filename in the prompt Absolute Filename or URL
  • Click on Import File

Media Library

UI Labels and Captions

• The Labels and Captions are stored in an XML file.
• The Source values can simply be copied over to the Target with a simple file transfer.
• The file is called OSafeUiLabels.xml.
• The location of the Source is:

[root] \hot-deploy\osafe\config

• Copy the Source file to the equivalent two locations on the Target Server. This is required so that your implementation uses the latest file as well as a master location in the event of a build.

[root] \hot-deploy\osafe\config

[root] \osafe_deployment\ofbiz\hot-deploy\osafe\config

DIV Sequences

• The DIV Sequences are stored in an XML file.
• The Source values can simply be copied over to the Target with a simple file transfer.
• The file is called OSafeUiSequence.xml
• The location of the Source is:

[root] \hot-deploy\osafe\config

• Copy the Source file to the equivalent two locations on the Target Server. This is required so that your implementation uses the latest file as well as a master location in the event of a build.

[root] \hot-deploy\osafe\config

[root] \osafe_deployment\ofbiz\hot-deploy\osafe\config

Custom Party Attributes

• The Custom Party Attributes are stored in an XML file.
• The Source values can simply be copied over to the Target with a simple file transfer.
• The file is called CustomPartyAttributes.xml
• The location of the Source is:

[root] \hot-deploy\osafe\import\data\xml

• Copy the Source file to the equivalent two locations on the Target Server. This is required so that your implementation uses the latest file as well as a master location in the event of a build.

[root] \hot-deploy\osafe\import\data\xml

[root] \osafe_deployment\ofbiz\hot-deploy\osafe\import\data\xml

Lookup Data

• Admin Lookup Data
• These should be manually updated in the Target instance to reflect the live values.
• This includes:
  • Age
  • Credit Card
  • Titles
  • Contact Us Reasons

SOLR Facets and Groups:

• These should be manually updated in the Target instance to reflect the live values.
• Admin Manage SOLR Configuration

System Parameters

• System Parameters should follow the standard OFBiz Export and Import process described below.
• The checkbox for entity xProductStoreParm should be chcked.

OFBiz Export and Import Process

On the Source Instance

• Use OFBiz OOTB
• Access Webtools
• Click on Import/Export
• Click on XML Data Export
  • Enter a valid entry for the Output Directory
  • Enter a valid entry for the Single Filename
  • Click Check the checkbox for the appropriate entity
• Click on Export File

Post Migration Verification

• It is strongly suggested that the Compare tools are used to verify the migration of System Parameters, DIV Sequencing and Labels and Captions
  • Admin Admin Tools Compare Tools

Back to Top