The Stage Propagate utility copies data from the staging database to the production database. Note that you cannot create or update RFQ objects on the staging server. The Stage Propagate utility uses the STAGLOG table to identify changed records in the staging database and update the corresponding tables in the production database.
The Stage Propagate 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 Stage Propagate utility began.
To run the Stage Propagate utility, type the following from a command line on a machine that can connect to both the staging server and the production server database. Type the entire script on one line. It is shown here on more than one line for presentation purposes only.
Working with databases other than DB2 for z/OS
Note: You must include the optional parameters, logon user ID and password in the utility even if you are currently running this utility with the same user ID.
- Log on as a user profile that has a CCSID other than 65535.
- Open a QSHELL command window by typing the following command on an OS/400 command line: STRQSH.
- Run the utility as follows:
/QIBM/ProdData/CommerceServer56/bin/stagingProp.sh (parameters . . .)
Note: The user parameters must always be specified.
Parameter values
- scope
- The scope level for the propagation to the production server. Specify one of the following:
- _all_
- Type _all_ to propagate both record related to site and to all merchants.
- _site_
- Type _site_ to propagate only site-related record.
- _merchant_
- Type _merchant_ to propagate only records related to all merchants.
- sourcedb
- The name of the database on the staging server.
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 staging database resides.
- destdb
- The name of the database on the production server.
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.
- dbtable
- (Optional) The name of any specific table to be propagated. All changed records in this table will be propagated, provided the records are within the scope specified by the scope parameter; otherwise, no records will be propagated.
- sourcedb_user
- (Optional) 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.
(Required) The user profile associated with the commerce instance. This is the same as the source database schema.
- sourcedb_passwd
- (Optional) The password of the logon ID that is specified by the sourcedb_user parameter.
- destdb_user
- (Optional) The logon ID of the database administrator who has created the destination database schema. If not specified, the ID of the user invoking the utility is used. This parameter is mandatory when using a remote database.
(Required) The user profile associated with the commerce instance. This is the same as the destination database schema.
- destdb_passwd
- (Optional) 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.
- log
- (Optional) The path and name of the file in which the Stage Propagate 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 stagingprop_yyyy.mm.dd_hh.mm.ss.zzz.log is created in the following log directory.
WC_installdir/logs
WC_userdir/instances
WC_installdir\logs
- dbtype
- (Optional)
The database type (DB2 or Oracle). The default is DB2.
Specify one of the following:
- DB2/OS400
- Type DB2/OS400 when using the native JDBC driver. This is the default value if no dbtype is specified.
- DB2/OS400ToolBox
- Type DB2/OS400ToolBox when using the toolbox JDBC driver.
Note: Both users (specified by -sourcedb_user and -destdb_user) need to have the DBADM privilege on the database objects created by each other
Parameter values
- scope
- The scope level for the propagation to the production server. Specify one of the following:
- _all_
- Type _all_ to propagate both record related to site and to all merchants.
- _site_
- Type _site_ to propagate only site-related record.
- _merchant_
- Type _merchant_ to propagate only records related to all merchants.
- sourcedb
- The name of the database on the staging server.
- destdb
- The name of the database on the production server.
- dbtable
- (Optional) The name of any specific table to be propagated. All changed records in this table will be propagated, provided the records are within the scope specified by the scope parameter; otherwise, no records will be propagated.
- sourcedb_user
- (Required) The logon ID of the database administrator who has created the source database schema.
- sourcedb_passwd
- (Required) The password of the logon ID that is specified by the sourcedb_user parameter.
- sourcedb_schema
- (Required) The schema for the source database
- destdb_user
- (Required) The logon ID of the database administrator who has created the destination database schema.
- destdb_passwd
- (Required) The password of the logon ID that is specified by the destdb_user parameter.
- destdb_schema
- (Required) The schema for the destination database.
- log
- (Optional) The path and name of the file in which the Stage Propagate 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 stagingprop_yyyy.mm.dd_hh.mm.ss.zzz.log is created in the WC_installdir/logs directory.
- dbtype
- (Required) The database type must be DB2/390.