Publishing multiple store archives of one type per instance
If a composite store archive for a store type is published, you can publish multiple composite store archives of the store type. Similarly, if a corresponding organization structure store archive for a store type is published, you can publish multiple organization structure store archives for the store type.
About this task
- Composite store archives
- A starter store archive that contains the organization structure, predefined user roles, and necessary access control policies to create the appropriate store environment, plus a working starter store or site.
- Component store archives
- A starter store archive that contains assets for each component of a composite store archive.
See Starter store archives for a complete list of all the store archives you can publish.
Procedure
- For the type of store archive you want to publish multiple times, ensure that you first publish an instance of the composite store archive or the organization structure.
-
Determine the name of the organization for the component that you are publishing.
If you are publishing an additional catalog asset store, the organization is important. If you publish an additional catalog asset store and use the default organization (Extended Sites Organization), the catalog asset store is assigned the same MEMBER_ID as the existing catalog asset stores within that parent organization. This behavior effectively bridges the two catalog asset stores into a single "shared" catalog. With the shared catalog, the two stores cannot have duplicate part numbers, and so on. If you want the stores to be separate and distinct, ensure that the additional catalog asset store is published under another organization.
- Follow the steps in Publishing a store archive using the Publish wizard Component store archives are available from the business model views. Enter the name of the organization for the component you are publishing in the Parameters page of the Publish wizard.
- Change at least the store directory and store identifier parameters on the parameters page for the store archive.
- Ensure that you change the store directory name in the cachespec.xml file to match the store directory that you specified in step 4. For more information about the cachespec.xml file, see Publishing a store archive using the Publish wizard.
- In a clustered environment, you must synchronize all cluster members after you publish any store archive.