Ant target: RemoveInstance

RemoveInstance removes the WebSphere Commerce instance configuration completely such as the site data, bootstrap data, schema, application, Web server configuration (IBM HTTP server only), and instance configuration files.

The following sub-targets are run to completely remove the WebSphere Commerce instance.

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).

Example

  • For IBM i OS operating systemAIXLinuxWC_installdir/bin/config_ant.sh -DinstanceName=instance_name RemoveInstance
  • WindowsWC_installdir/bin/config_ant.bat -DinstanceName=instance_name RemoveInstance

Recovery

  1. Review the output of the Ant command.
  2. Identify which step (Ant target) failed.
  3. Resolve the problem.
  4. Follow the recovery instructions in the failed target.
  5. Run the remaining targets.
Note: The following type of error may be encountered when removing the WebSphere Commerce instance using the config_ant.sh script:
 WASX7017E: Exception received while running file
 "/opt/WebSphere/CommerceServer80/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
 "/opt/WebSphere/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 (com.ibm.SOAP.requestTimeout=6000).
  3. Stop and restart your WebSphere Application Server profile.
  4. Follow the recovery instructions in the failed target.
  5. Execute the rest of the targets.