Company deployment
Company deployment reduces your content modeling activities and improves administration productivity. You can deploy a company from your test instance to your production instance of Product Master or you can propagate your company data model from one production instance to another.
You typically create a company and test it, and then deploy the company from a test instance to production. You deploy a company by exporting it from the test instance to a compressed file and then importing the compressed file to the production instance.
You deploy your company through both the export and the import environments. You extract data model objects from your test instance of Product Master with the export environment, which exports a compressed file into the document store. You can extract all objects of your data model or only the objects and object dependants that you specify.
To deploy your company on the production instance of Product Master, you use the import environment to import your compressed file.
The compressed file that you export for deployment can contain either the XML, comma-separated value (CSV), or both file formats depending on the object types that you export. You can perform your company deployment from the user interface or from the command-line.
If you are deploying your company from one production instance to another production instance for data model propagation, see Propagate a company to review the propagation restrictions.
Restrictions
- You cannot export or import data models as a means to migrate between different release versions of Product Master because the data model varies between each release version. Company deployment is supported only between instances of the same release version.
- Manual modification to the content in a compressed file is not supported and if you attempt to import a compressed file that was modified, the import might fail.
- If you can stop an import that you initiated, you might cause inconsistencies and you need to manually remove any elements that were imported.
- The export or import environments do not have transaction management to ensure that the objects in your data model were committed or not so if your export or import operation is interrupted, your target instance might become inconsistent and unusable.
- During an import, all rules on catalogs and hierarchies are disabled, including: required fields, length validation, validation rules, value rules, and pre/post processing script.
- See the troubleshooting checklists for workaround details for importing hierarchy content with categories that have a relationship attribute set and opening compressed files that appear empty.