fileprop utility

The fileprop utility sends all new and changed files to the administration node of the federated WAS environment, which later pushes them into the managed nodes, which include the production server.

If there is no federated environment, fileprop puts the names of new and changed files into the log file, so that you can manually copy the files from the
staging server to the production server's file system. The fileprop utility assumes that the manual copy is carried out, and will not handle those files the next time the utility is called.

The function of the fileprop utility can also provided 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 machine that can connect to both the staging or authoring server database and the production server database.

I5/OS: To run shell scripts:

  1. Log on as a user profile that has a CCSID other than 65535.

  2. Open a QSHELL command window by typing the following command on a command line: STRQSH.

  3. Run the utility as follows:

    The user parameters must always be specified.

 

Utility command

The fileprop utility has the following file name:

 

Parameter values

All parameters are required unless indicated.

-dbtype

  • AIX|Linux|Solaris|Windows:

    (DB2) (Optional) Specify DB2. This is the default database type and you can omit the dbtype parameter from the command.

  • I5/OS|(DB2) (Required) Specify one of the following values:

    DB2/OS400

    Specify DB2/OS400 when using the native i5/OS JDBC driver.

    DB2/OS400ToolBox

    Specify DB2/OS400ToolBox when using the IBM Toolbox for Java JDBC driver.

  • (Oracle) (Required) Specify Oracle.

-sourcedb

(Required) The name of the database on the staging server.

I5/OS|

  • If the -dbtype parameter is DB2/OS400, specify the name of the database on the staging server, as displayed in the relational database directory.

  • If the -dbtype parameter is DB2/OS400ToolBox, specify the hostname of the server on which the production-ready data resides.

-sourcedb_user

(Required) The logon ID of the database administrator who has created the source database schema. If not specified, the ID of the user currently invoking the utility is used.

I5/OS: The user profile associated with the commerce instance. This is the same as the source database schema.

-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.

I5/OS|

  • If the -dbtype parameter is DB2/OS400, specify the name of the database on the production server, as displayed in the relational database directory.

  • If the -dbtype parameter is DB2/OS400ToolBox, specify the hostname of the server on which the production database resides.

-destdb_user

(Required) The logon ID of the database administrator who has created the production database schema. If not specified, the ID of the user invoking the utility is used. This parameter is mandatory when using a remote database.

I5/OS: The user profile associated with the commerce instance. This is the same as the production database schema.

-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 using a remote database.

-destdb_locktimeout

-wsadmin_user

(Optional) A WAS administrative user ID.

This parameter is required if WAS global security is enabled. See the Global security topic in the WebSphere Application Server Information Center for more information.

-wsadmin_passwd

(Optional) The password for the user ID specified by the wsadmin_user parameter.

This parameter is required if WAS global security is enabled. See the Global security topic in the WebSphere Application Server Information Center for more information.

-waspath

The full path to the location of the wsadmin.sh or wsadmin.bat file on staging or authoring server. These files are usually located in the following directory:

-profilename

The name of the WAS profile on the production server that contains WebSphere Commerce. By default, the profile name is the same as the WebSphere Commerce instance name.

-appname

The value of WC_enterprise_application on the production server.

-modulename

The name of the application module to which managed files are copied. This is usually Stores.war.

-log

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 called fileprop_ yyyy.mm.dd_hh.mm.ss.zzz.log is created in the following log directory.

Related concepts

Staging server

Authoring server

Managed files


Related Reference

Staging server limitations