Preventing the WebSphere Commerce application from restarting during the propagation of managed file data
Both the stagingprop and fileprop utilities provide capability of propagating managed file data from the Authoring environment to the Production environment.
About this task
The fileprop utility propagates managed
file data from the Authoring environment to the Production environment
directly. The stagingprop utility accomplishes
the same operation by calling the fileprop utility.
The fileprop utility follows these steps to propagate
the data:
- The fileprop utility moves records that are associated with managed files from the authoring database to the production database
- For any managed files with content that exists in the authoring database, the fileprop utility updates the production environment EAR. It updates the EAR using the WebSphere Application Server wsadmin script to write the content directly into the EAR. As part of this step, the fileprop utility calls for a restart of the WebSphere Commerce application on the production environment.
Procedure
- If you start the fileprop utility directly:
- If you call the fileprop utility indirectly using
the stagingprop utility: