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.

Task info

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:

1. The fileprop utility moves records associated with managed files from the authoring database to the production database

2. 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.

In some cases, we might not want the WebSphere Commerce application to restart. Use one of the following sets of steps to prevent the application from restarting.

Procedure

• If you start the fileprop utility directly:

  1. Do not specify the following parameters:

     • -profilename

     • -waspath

     • -appname

     • -modulename

     When you leave these parameters unspecified, the fileprop utility does not update the production environment EAR for managed files with content that exists in the authoring database.

  2. Manually copy any file assets on the authoring environment to have on the production environment. Copy the assets using a file system or equivalent utility, such as FTP. To determine the list of files to copy, see the output in the fileprop utility log file.

• If you call the fileprop utility indirectly using the stagingprop utility:

  1. Do not specify the following parameters:

     • -profilename

     • -waspath

     • -appname

     • -modulename

     When you leave these parameters unspecified, the fileprop utility does not update the production environment EAR for managed files with content that exists in the authoring database.

  2. Include this additional parameter and specify its value when you run the stagingprop utility:

     • -forcefileprop true

     Setting this parameter to true ensures that the stagingprop utility calls the fileprop utility, but still prevents updates to the production environment EAR.

  3. Manually copy any file assets on the authoring environment to have on the production environment. Copy the assets using a file system or equivalent utility, such as FTP. To determine the list of files to copy, see the output in the stagingprop utility log file.