HCL Commerce Version 9.1.8.0 or later

Fileprop utility

The fileprop utility copies all the new and changed files to a mounted drive that is shared with the live environment.

The function of the fileprop utility can be performed by the stagingprop utility if you specify the required parameters. The stagingprop utility publishes production-ready data then publishes managed files. If you only want to publish managed files to the production server, use the fileprop utility.

The fileprop utility runs as a single transaction and is committed only after propagation is successful. If the propagation fails, the transaction rolls back returning your production database to the state before the fileprop utility began.

To run the fileprop utility, issue the following command from a command line on a system that can connect to both the staging or authoring server database and the production server database.

fileprop utility syntax diagram

Utility command

The fileprop utility has the following file name:

  • LinuxAIXFor IBM i OS operating systemfileprop.sh
  • Windowsfileprop.bat

Parameter values

All parameters are required unless indicated.

dbtype
  • Optional: Specify DB2. This value is the default database type and you can omit the dbtype parameter from the command.
  • Required: Specify Oracle.
sourcedb
Required: The name of the database on the staging server.
Note: For DB2 UDB databases, the DB2 Type 4 JDBC driver is used, where the Type 4 database name is prefixed with the database server and port. For example, db_server:db_port/db_name.
sourcedb_user
Required: The logon ID of the database administrator who created the source database schema. If not specified, the ID of the user currently invoking the utility is used.
sourcedb_passwd
Required: The password of the logon ID that is specified by the sourcedb_user parameter.
destdb
Required: The name of the database on the production server.
destdb_user
Required: The logon ID of the database administrator who created the production database schema. If not specified, the ID of the user that starts the utility is used. This parameter is mandatory when you use a remote database.
destdb_passwd
Required: The password of the logon ID that is specified by the destdb_user parameter. If not specified, the system prompts you to enter the password. This parameter is mandatory when you use a remote database.
destdb_locktimeout
Optional: Specifies the number of seconds the fileprop utility connection to the production database waits to obtain a lock on the database it is updating. If the fileprop utility cannot obtain a lock within the specified number of seconds, the database transaction is rolled back.
log
Optional. The path and name of the file in which the fileprop utility records its activities and errors. The timestamp is appended to the file name, for example, myLog_ yyyy.mm.dd_hh.mm.ss.zzz.log. If this parameter is not specified, a log file that is called fileprop_ yyyy.mm.dd_hh.mm.ss.zzz.log is created in the following log directory.
  • LinuxAIXWC_installdir/logs
  • WindowsWC_installdir\logs
assetTargetDirectory
The directory where the managed files from authoring should be copied for the production file mount. (i.e. /SETUP/assets/live)
paramfile
Optional. Specifies the path to the parameter file that includes command-line arguments and values. Each argument and value needs to be in the format argument=value with a single argument and value on each line in the file. Any passwords within this parameter file must be encrypted.