Deprecated feature

Deleting a WebSphere Commerce Payments instance

You can delete a WebSphere Commerce Payments instance.

Procedure

Ensure that WebSphere Commerce Payments is stopped.
Note: The WebSphere Commerce Information Center does not need to be stopped when deleting a WebSphere Commerce Payments instance.
Delete the WebSphere Commerce Payments instance from Configuration Manager by doing the following steps:
1. Start Configuration Manager.
2. In Configuration Manager, under WebSphere Commerce expand hostname > Payments > Instance List.
3. Right-click the instance you want to delete and select Delete Payments Instance. A dialog displays confirming that you want to delete the instance. When the instance is deleted, a message displays. Click OK.
4. Exit Configuration Manager. This step also deletes the enterprise application and virtual hosts.
Do one of the following sets of steps, depending on the database you are using for WebSphere Commerce Payments:
- Drop the WebSphere Commerce Payments database associated with the WebSphere Commerce Payments instance you want to delete.
  To drop a local WebSphere Commerce Payments database, issue the following commands from a DB2 command window:
```
db2 drop db db_name where db_name is the name of the WebSphere Commerce Payments database.
```
  To drop a remote WebSphere Commerce Payments database, issue the following commands from a DB2 command session on the WebSphere Commerce Payments machine:
```
db2 attach to remote_db_node_name user db_admin_ID using db_admin_password 
db2 drop db db_name db2 uncatalog db db_alias
```
  Where:
  
  remote_db_node_name
  
  The database node name that was specified when the WebSphere Commerce Payments instance was created.
  
  db_admin_ID
  
  The database administrator ID that was specified when the WebSphere Commerce Payments instance was created.
  
  db_admin_password
  
  The password for the database administrator
  
  db_name
  
  The name of the WebSphere Commerce Payments database.
  
  db_alias
  
  This is the alias under which the remote WebSphere Commerce Payments database is cataloged on the WebSphere Commerce Payments machine.
- Drop the WebSphere Commerce Payments tablespace and delete the Oracle user associated with the WebSphere Commerce Payments instance you want to delete. For instructions on dropping a tablespace and deleting an Oracle user, refer to the Oracle documentation.
Delete the following directories if they exist:
- WC_installdir/payments/instances/instance_name
- WC_profiledir/installedApps/hostname/instance_name_Commerce_Payments_App.ear
- WAS_installdir/profiles/WAS_WPM_profile_name/logs/instance_name/
- WAS_installdir/logs/instance_name_Commerce_Payments_Server
- where instance_name is the name of the WebSphere Commerce Payments instance you want to delete, and node_name is the node under which your payments application is installed. By default, the node_name is the hostname of the machine.

Do the following steps, depending on your Web server:


Web server	Actions
IBM HTTP Server	No additional steps need to be performed when using IBM HTTP Server.
Microsoft IIS	No additional steps need to be performed when using Microsoft IIS.
Sun Java System Web Server	No additional steps need to be performed when using Sun ONE Web Server.

If you plan to use another WebSphere Application Server after deleting the WebSphere Commerce Payments instance, you must regenerate the WebSphere Application Server plug-in configuration file.

What to do next

Deleting your WebSphere Commerce Payments instance does not delete the corresponding WebSphere Application Server profile. To remove your WebSphere Application Server profile, see the Deleting a profile topic.