Publishing data to the production database
To publish data from the staging or authoring database to the production database:
Before you begin
Procedure
-
Use the staging propagation (stagingprop) utility to publish data from the staging or authoring database to the production database:
stagingprop.sh
stagingprop.bat
-
If you are publishing a store at the staging server, insert the following access control
policies into the Production database:
- For consumer direct (B2C) extended sites
stores:
Whereinsert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='ManagementAndAdministrationPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='CommonShoppingPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='B2CPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='storeIdentifier PolicyGroup', select member_id from storeent where identifier='storeIdentifier');
storeIdentifier
is the identifier for your store, such as Aurora or Madisons. This identifier is stored in the IDENTIFIER column of the STOREENT database table. - For B2B extended sites
stores:
Whereinsert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='ManagementAndAdministrationPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='CommonShoppingPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='B2BPolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='storeIdentifier PolicyGroup', select member_id from storeent where identifier='storeIdentifier'); insert into ACPLGPSUBS (ACPOLGRP_ID, ORGENTITY_ID) values(select acpolgrp_id from acpolgrp where name='storeIdentifier GuestCatalogEnabledPolicyGroup', select member_id from storeent where identifier='storeIdentifier');
storeIdentifier
is the identifier for your store, such as Aurora or Madisons. This identifier is stored in the IDENTIFIER column of the STOREENT database table.
Note: Any custom policies must also be manually inserted. - For consumer direct (B2C) extended sites
stores:
- Optional:
If you published marketing activities, update the marketing registry.
- Provide database triggers that you can add to automatically update the
marketing registry (
CampaignInitiativeCache
) after you run the stagingprop command. If you added the database triggers that are provided in WebSphere Commerce Fix Pack 2, you do not need to manually update the marketing registry. For more information, see Adding database triggers to automatically update registries after data propagation. - If you do not have the database triggers that are provided in WebSphere Commerce Fix Pack 2 added, you must manually update the marketing registry. For more information, see Updating registry components. When you are updating the registry, select the CampaignInitiativeCache component.
- Provide database triggers that you can add to automatically update the
marketing registry (
- Optional:
If you published promotions data, update the promotions registry.
- Provide database triggers that you can add to automatically update the
promotions registries (
PromotionRegistry, PromotionPolicyRegistry, and PromotionGroupRegistry
) after you run the staging propagation utility command. If you added the database triggers that are provided in WebSphere Commerce Fix Pack 3, you do not need to manually update the promotions registry. For more information, see Adding database triggers to automatically update registries after data propagation. - If you do not have the database triggers that are provided in WebSphere Commerce Fix Pack 3 added, you must manually update the promotions registries. For more information, see Updating registry components. When you are updating the registry, select the PromotionRegistry, PromotionPolicyRegistry, and PromotionGroupRegistry components.
- Provide database triggers that you can add to automatically update the
promotions registries (