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

You can publish managed files to the WebSphere Commerce EAR on the production server using the fileprop command.

Before you begin

Set the PATH environment variables.

Procedure

  1. Change to the directory to which you want log files written.
  2. Issue the fileprop command.

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

    DB2
    • LinuxAIXFor IBM i OS operating system 
      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 
      
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
  3. Examine the fileprop_yyyy.mm.dd_hh.mm.ss.zzz.log file.