For IBM i OS operating systemWindowsAIXLinuxSolaris Ant target: CreateInstance

CreateInstance runs all instance creation actions such as database configuration, WebSphere Application Server configuration, Web server configuration, Content Management configuration, generating WebSphere Commerce instance-specific files and file permission settings.

Prerequisites

The createInstance.properties file must exist for this Ant target to work.

Important: Before you run this Ant target, complete the steps in Generating the createInstance.properties file.
Note: The Ant targets are individually documented to help you easily recover from a failed instance creation.

Calls

If you want to skip any of the instance creation actions, you should not run CreateInstance but run the subtargets selectively.

Required parameters

instance_name
The name of the WebSphere Commerce instance with which you are working (for example, demo).
SolarisLinuxWindowsAIXdbaPassword
SolarisLinuxWindowsAIXThe database administrator's password. This parameter is required when:
  • DB2A database is created for the new WebSphere Commerce instance
  • OracleA user schema is created for the new WebSphere Commerce instance.
This parameter is not required when you use an existing database or schema for your new WebSphere Commerce instance.
dbUserPassword
The WebSphere Commerce database user's password.
siteAdminPassword
The WebSphere Commerce site administrator's password.
merchantKey
The WebSphere Commerce site merchant key.
cmDBUserPwd
(required if workspaces are enabled) The authoring server's workspace database user password.
ftpUserPwd
(required if you configure remote webserver via FTP option) The user password of the FTP account being used to configure the web server.

Example

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

Recovery

  1. If an error occurs, review the following log files:
    • SolarisLinuxWindowsAIXWC_installdir/instances/instance_name/logs/createInstanceANT.log
    • SolarisLinuxWindowsAIXWC_installdir/instances/instance_name/logs/createInstanceANT.err.log
    • For IBM i OS operating systemWC_userdir/instances/instance_name/logs/createInstanceANT.log
    • For IBM i OS operating systemWC_userdir/instances/instance_name/logs/createInstanceANT.err.log
  2. Identify which step (Ant target) failed.
  3. Resolve the problem.
  4. Follow the recovery instructions in the failed target.
  5. Run the rest of the targets.
Note: When you create the WebSphere Commerce instance using the config_ant.sh script, you can encounter an error similar to the following sample:
WASX7017E: Exception received while running file "/QIBM/ProdData/
CommerceServer60/config/deployment/scripts/uninstallEar.jacl";
exception information: com.ibm.websphere.management.exception.
ConfigServiceExceptioncom.ibm.websphere.management.exception.
ConnectorException org.apache.soap.SOAPException:[SOAPException: 
faultCode=SOAP-ENV:Client; msg=READ TIMED UT; targetException=
java.net.SocketTime outException: READ TIMED OUT]

WASX7309W: No "save" was performed before the script
"/QIBM/ProdData
/CommerceServer60/Config/deployment/scripts/uninstallEar.jacl"exited;

configuration changes will not be saved.

If this error is encountered, complete the following steps:

  1. Open the following file in a text editor: WC_profiledir/properties/soap.client.props
  2. Search for the com.ibm.SOAP.requestTimeout entry, and set the value to 6000. For example, com.ibm.SOAP.requestTimeout=6000
  3. Follow the recovery instructions in the failed target.
  4. Run the rest of the targets.