Catalog and search index deployment from staging to production
Key Takeaway
Rebuild search indexes on staging, then replicate the "Catalogs" and "Search Indexes" tasks to production at the same time. Availability and active data indexes aren't included, because they depend on inventory data that exists only on production.
In B2C Commerce, merchandisers build and change catalogs on the staging instance. Data replication then copies that data to development for testing and to production. Storefront search reads from search indexes, so the indexes are rebuilt on staging and replicated together with the catalogs, which keeps search in step with the catalog data shoppers see.
Where catalog work happens
Replication moves code, configuration settings, and data from a source instance to a target instance. Staging is the source. Development and production are the targets. Replication runs only on the PIG.
Catalog work happens on staging. Merchandisers create and maintain catalogs there. Data replication then copies the catalogs to development for testing, and after that to production.