Publishing managed files to the WebSphere Commerce EAR on the production server


To publish only managed files to the production server:

  1. Set the PATH environment variables.

  2. Change to the directory to which you want log files written.

  3. Issue the fileprop command.

    The following are examples of the fileprop command for a WebSphere Commerce production server instance called "demo".

    (DB2)

    • AIX|Linux|Solaris|I5/OS| 
      fileprop.sh -dbtype
 db_type
   -sourcedb 
production-ready_database_name -sourcedb_user 
source_user_ID -sourcedb_passwd 
source_password
   -destdb 
production_database_name  -destdb_user 
dest_user_ID -destdb_passwd 
dest_password
   -waspath 
WC_profiledir/bin -profilename demo -appname WC_demo
-modulename Stores.war
   -log fileprop

    • Windows: 
      
fileprop -dbtype 
db_type
   -sourcedb 
production-ready_database_name -sourcedb_user 
source_user_ID -sourcedb_passwd 
source_password
   -destdb 
production_database_name  -destdb_user 
dest_user_ID -destdb_passwd 
dest_password
   -waspath 
WC_profiledir/bin -profilename demo -appname WC_demo
-modulename Stores.war
   -log fileprop

    (Oracle)

    • AIX|Solaris| 
      fileprop.sh -dbtype oracle
   -sourcedb 
production-ready_database_name -sourcedb_user 
source_user_ID -sourcedb_passwd 
source_password
   -destdb 
production_database_name  -destdb_user 
dest_user_ID -destdb_passwd 
dest_password
   -waspath 
WC_profiledir/bin -profilename demo -appname WC_demo
-modulename Stores.war
   -log fileprop

    • Windows: 
      fileprop -dbtype oracle
  -sourcedb 
production-ready_database_name -sourcedb_user 
source_user_ID -sourcedb_passwd 
source_password
   -destdb 
production_database_name  -destdb_user 
dest_user_ID -destdb_passwd 
dest_password
   -waspath 
WC_profiledir/bin -profilename demo -appname WC_demo
-modulename Stores.war
   -log fileprop

  4. Examine the fileprop_ yyyy.mm.dd_hh.mm.ss.zzz.log file.


 

Related Concepts


Staging server

 

Related Reference


fileprop utility