Stage server utilities
The staging server uses three utilities: stagingcopy, stagingprop, and fileprop.
- stagingcopy utility
The stagingcopy utility copies data from the production database to the production-ready data on a staging or authoring server. You cannot use this command if RFQs are on the production system.
- stagingprop utility
The stagingprop utility copies data and managed files from the production-ready data to the production server. You cannot create or update RFQ objects on the staging server. The stagingprop utility uses the STAGLOG table to identify changed records in the production-ready data and update the corresponding tables in the production database.
- fileprop utility
The fileprop utility sends all new and changed files to the administration node of the federated WebSphere Application Server environment, which later pushes them into the managed nodes, which includes the production server. The staging server needs to be federated using the same deployment manager as the production server. Otherwise, the managed files will not be propagated into the production EAR because the deployment manager is not aware of the production node.
- Customized database table requirements
If you have customized the database schema by creating new tables, meet the several requirements to use the staging server.
- Enable custom tables for staging
If you have customized the database schema by creating new tables and to stage these custom tables, do the following for each custom table to stage.
Related tasks
Test the site on a staging server
Related reference