You can specify the -scope parameter
of the stagingprop utility so that only data from selected tables
is published to the production server. The -scope parameter
accepts three predefined table sets - all tables, site data tables
only, and merchant data only. You can also specify a custom list of
database tables with the -scope and -configfile
parameters.
The
file that is specified by the -configfile
parameter
contains a list or multiple lists of database tables while the -scope parameter
specifies which list or lists in the file to use.
The stagingprop
utility follows the order of the database tables in the list or lists
provided. When you are creating your database table lists, ensure
that any referenced tables appear in the list before the referencing
tables.
Procedure
- Create an XML file that uses the following format:
<?xml version="1.0" encoding="UTF-8"?>
<StagingConfig>
<TableList name="list_name">
<Table name="table1"/>
<Table name="table2"/>
...
<Table name="tableX"/>
</TableList>
</StagingConfig>
Where:
- list_name
- The name of the list of database tables. Specify this name with
the -scope parameter to limit the data that is
published to the production server to the tables in the list.
- table1, table2, tableX
- The database table names from which data is published.
You can add more lists by adding a <TableList>
tag
within the <StagingConfig>
tag. You can repeat
table names in different lists. The same table name cannot appear
more than one time in a list.
The following file contains two
lists:
<?xml version="1.0" encoding="UTF-8"?>
<StagingConfig>
<TableList name="list_name1">
<Table name="table1"/>
<Table name="table2"/>
...
<Table name="tableX"/>
</TableList>
<TableList name="list_name2">
<Table name="tableA"/>
<Table name="tableB"/>
...
<Table name="tableZ"/>
</TableList>
</StagingConfig>
You can also create multiple database filter files.
- Save your changes and take note of the full path to the
database filter list file.