If you want to move data from your development database to the database used by your application server, you can do this using the startSQLRepository
script. This script is described in detail in the Repository Guide. To use this script, follow these steps:
Set the
DYNAMO_HOME
environment variable to<ATG11dir>/home
.In the Dynamo Server Admin, create a new Oracle Commerce Platform server that uses data sources that point to the development database. This is the default configuration for a new server.
Use the
startSQLRepository
script to export data from the development database. Include in thestartSQLRepository
command the–s
servername
switch. For example, if the server you created in the previous step is calledserver1
, you can export the data from all of the Oracle Commerce Platform repositories using this command:bin/startSQLRepository -s server1 -exportRepositories all all.xml
Use the
startSQLRepository
script to import data from the XML file (created in the previous step) into the database used by your application server. Use the–s
switch to specify a Oracle Commerce Platform server that is configured to use an Oracle Commerce Platform data source that points to that database. For example:bin/startSQLRepository –s
server_name
-import all.xml
Note that the Oracle Commerce Platform data source must use an Oracle Commerce Platform-supported database driver. To see a list of supported database drivers refer to the Oracle Commerce Supported Environments document in the My Oracle Support knowledge base.
Oracle users: Before importing the demo data, set the useSetCharacterStream
property of all SQL repository components to true
so that non-8859 characters are displayed correctly. You can set this property in your localconfig/GLOBAL.properties
file:
useSetCharacterStream=true
Microsoft SQL users: In order to run the Oracle Commerce Platform demos with a Microsoft SQL database, you must configure the database to be case-sensitive. See your MSSQL documentation for instructions. Note that the Quincy Funds demo is not supported for MSSQL.
Note: Entering passwords as command line arguments entails some security risks. Do not enter passwords as command line arguments in situations where security is a top priority.