Ant target: ConfigureDatabase

ConfigureDatabase creates a database with schema, and populates the schema with the WebSphere Commerce bootstrap data.

Important: This Ant target is to be used only as a part of WebSphere Commerce instance creation.

Called by

CreateInstance

Calls

Prerequisites

The createInstance.properties file must exist for this Ant target to work. For information about generating the properties file, see Ant targets.

Required parameters

instance_name
The name of the WebSphere Commerce instance with which you are working (for example, demo).
merchantKey
The WebSphere Commerce site merchant key.
siteAdminPassword
The WebSphere Commerce site administrator's password.
SolarisLinuxWindowsAIXdbaPassword
SolarisLinuxWindowsAIXThe database administrator's password.
dbUserPassword
The WebSphere Commerce database user's password.

Example

  • SolarisLinuxAIXWC_installdir/bin/config_ant.sh -DinstanceName=instance_name -DmerchantKey=merchantKey -DsiteAdminPassword=siteAdminPassword -DdbaPassword=dbaPassword -DdbUserPassword=dbUserPassword ConfigureDatabase
  • For IBM i OS operating systemWC_installdir/bin/config_ant.sh -DinstanceName=instance_name -DmerchantKey=merchantKey -DsiteAdminPassword=siteAdminPassword -DdbUserPassword=dbUserPassword ConfigureDatabase
  • WindowsWC_installdir/bin/config_ant.bat -DinstanceName=instance_name -DmerchantKey=merchantKey -DsiteAdminPassword=siteAdminPassword -DdbaPassword=dbaPassword -DdbUserPassword=dbUserPassword ConfigureDatabase

Recovery

  1. If an error occurs, review the following log files:
    • SolarisLinuxWindowsAIX
      • WC_installdir/instances/instance_name/logs/createInstanceANT.log
      • WC_installdir/instances/instance_name/logs/createInstanceANT.err.log
    • For IBM i OS operating system
      • WC_userdir/instances/instance_name/logs/createInstanceANT.log
      • WC_userdir/instances/instance_name/logs/createInstanceANT.err.log
  2. Identify which Ant target of ConfigureDatabase failed.
  3. Resolve the problem.
  4. Drop the database or cleanup the Oracle Schema.
  5. Run the failed target and the remaining subsequent targets OR run the ConfigureDatabase target again to call all subtargets.