Publishing to the production server
Publish production-ready data from the authoring server to the production server to propagate changes to your site.
Before you begin
Tip: An
authoring server is a staging server that has workspaces enabled.
About this task
- Quick publish
- If quick publish is enabled when a task group is created in a
workspace, the files and data in that task group are published to
the production server as soon as all tasks in that task group are
marked complete and all approvals are satisfied. When all tasks in
a task group marked as quick publish are completed and, if necessary,
approved, the task group files and data are committed to the production-ready
data. When the task group commit completes successfully, the task
group files and data are published to the production server.
If the task group commit fails, the files and data from the task group remain committed to the production-ready data and are not published to the production server. You can use the stagingprop utility to immediately correct errors and publish the production-ready data to the production server.
Quick publish is not supported in
WebSphere Commerce Developer. - Global publish
- Use one of the following staging server utilities to publish production-ready
data to the production server:
- stagingprop utility
- Use to publish changes from the production-ready data on the authoring server to the production database. The information in the STAGLOG database table identifies the records in the production-ready data to insert, update, or delete in the production database. Processed records are indicated in the STAGLOG table by a 1 in the STGPROCESSED column. These processed records are not deleted and can be used for future analysis or troubleshooting.
- fileprop utility
- Use to propagate managed files from the production-ready data on the authoring server to the WebSphere Commerce EAR file on the production server.