Copying managed files from a production environment to an authoring environment

When you set up a new authoring environment after you run the stagingcopy utility, or when you are synchronizing managed files from the production system to the authoring system, you must take more steps to copy managed files to the authoring environment.

About this task

Depending on whether the files were loaded directly into the production EAR or loaded with a WebSphere Commerce utility, you must copy them using different steps. If some files were loaded directly, but other using a utility, then take both steps in the order shown.
Note: If you are running the stagingcopy utility to copy files to a remote web server, you must still complete the following procedure. If you do not copy the files to the EAR on your remote web server, Management Center store preview might not work properly because store preview might not be able to retrieve the required files from the EAR and the database.


  1. If the files are managed by the file system, and therefore loaded directly into the production EAR, complete the following steps:
    1. Export data in the CMFILE and CMFILEDIR tables from the production database.
    2. Import the data that you exported in the preceding step into the CMFILE and CMFILEDIR tables in the authoring database.
    3. Copy the files with a file system copy utility, such as FTP, from the production EAR to the authoring EAR.
  2. If you loaded the files with a WebSphere Commerce utility, such as FileLoader, into the production database and the files are not yet copied to the production EAR, follow these steps:
    1. Temporarily set the PUBLISHED column of the CMFILE table in the production database to 0.
    2. Run the fileprop utility. Set the source database to the production database and set the destination database to the authoring database.