This section describes the configuration steps you must take before performing a database copy of your product catalog and price lists data. You must complete this process before performing an initial database copy. However, you don’t need to complete this process before subsequent database copies as long as the source and destination databases remain the same.
Follow these configuration steps to prepare to copy the product catalog and price lists data from one database to another:
Create the destination database and all destination tables.
Most interactions between the Oracle ATG Web Commerce and a database are done through JDBC, but the
DBCopier
in this process instead uses native commands according to the database manufacturer. It executes a new process and uses the vendor’s bulk copy tools to copy the tables from one database to another. This means that theDBCopier
and, therefore, the JVM running Dynamo must have the proper environment set up as specified by the vendor. See your vendor documentation for these specifications. For information on the API for the specificDBCopier
you are using, you can refer to the ATG Platform API Reference.Verify that the environment is set up correctly. Make sure that all the necessary environmental variables are set as specified by the vendor. Verify that all the necessary drivers or client tools are installed.
Create a
DBCopier
component with which to copy the product catalog and price lists data. The class from which you instantiate theDBCopier
depends on the database you are using. The following are subclasses ofatg.adapter.gsa.DBCopier
and are in packageatg.adapter.gsa
:BcpDBCopier
(for Microsoft)DB2DBCopier
OracleDBCopier
For more information on these
DBCopier
classes, refer to the ATG Platform API Reference.Alternatively, you can use one of the preconfigured
DBCopier
components that are included with Oracle ATG Web Commerce. They are:ProductCatalogMsSqlDBCopier
Note: By default, the
ProductCatalogMsSqlDBCopier.maxTextOrImageSize
property is set to a negative value (-1) in order to force the copier not to use the–T
option with thebcp
utility; the–T
option does not work with MS SQL. For more information on themaxTextOrImageSize
property, refer to theBcpDBCopier
class (from whichProductCatalogMsSqlDBCopier
is instantiated) in the ATG Platform API Reference. For more information on thebcp
utility, refer to your database vendor documentation.ProductCatalogOracleDBCopier
ProductCatalogDB2DBCopier
These
DBCopier
components are located in Nucleus at/atg/commerce/jdbc/
.Check that the directory specified in the
directory
property of theDBCopier
component is available in the file system used by ATG.Verify that the
tables
property of theDBCopier
component includes all the necessary tables to copy in the correct order. The tables in the destination database will be updated according to the list of tables in this property.Optionally, to obtain information on the activity of the
DBCopier
, you can set theloggingDebug
property of theDBCopier
component to true.Create an instance of
atg.droplet.sql.DBCopyFormHandler
to handle the database copy. Alternatively, you can use the preconfiguredDBCopyFormHandler
included with Oracle ATG Web Commerce. It is located in Nucleus at/atg/commerce/jdbc/ProductCatalogCopierForm
.Perform the database copy from the Copy Product Catalog and Price Lists page, as described in Performing a Database Copy.