Deleting WebSphere Commerce search

Delete WebSphere Commerce search when you delete a WebSphere Commerce instance and you no longer need any of the search resources and services. You can also choose to delete the WebSphere Application Server profile and server that is associated with search. Deleting WebSphere Commerce search can free up a significant amount of system resources and can make the resources available for other purposes.

If your WebSphere Commerce search application contains resources or customizations that you might need to reuse in another instance, back up the content before deletion.

Important:

Deleting WebSphere Commerce search cannot be undone.
Do not delete WebSphere Commerce search for any existing instances that you will continue to use. Installing maintenance on an instance requires WebSphere Commerce search to exist for that instance.

Procedure

To delete WebSphere Commerce search:
1. Optional: Export the WebSphere Commerce search application from the WebSphere Application Server Administrative Console to save any WebSphere Commerce search customizations.
  Your search application name is WC_instance_name_solr.
2. Delete WebSphere Commerce search:
  1. If you have a federated or cloned environment, if needed, you can remove the cluster members from your cluster and remove the cluster by using the WebSphere Application Server Deployment Manager administrative console. See Removing a cluster member.
  2. If you are deleting WebSphere Commerce search from a deployment manager cell, if needed, you can remove the WebSphere Commerce node from the deployment manager cell. For more information, see Taking your first steps after a WebSphere Commerce installation.
  3. Ensure that you are logged on as the WebSphere Commerce non-root user.
  4. Ensure that the default WebSphere Application Server search server (solrServer) and WebSphere Commerce server (server1) is started.
    In a federated or cloned environment, ensure that the WebSphere Application Server deployment manager is started. For information about starting the deployment manager, see Starting or stopping WebSphere Application Server.
  5. Start a command prompt session or command line session.
  6. In the command prompt session or command line session, change directories to WC_installdir/bin/.
  7. Issue the following command:
    - ./config_ant.sh -buildfile WC_installdir/components/foundation/subcomponents/search/deploy/deploySearch.xml -DinstanceName=instance_name -DdbUserPassword=dbpassword -DdbaPassword=dbapassword disableSearch
    - config_ant.bat -buildfile WC_installdir/components/foundation/subcomponents/search/deploy/deploySearch.xml -DinstanceName=instance_name -DdbUserPassword=dbpassword -DdbaPassword=dbapassword disableSearch
    Important:
    Ensure that you run the command as the non-root user that was created for WebSphere Commerce.
    The disableSearch command does the following actions:
    
    Backs up the WC_profiledir/instance_name_solr/installedApps/instance_name_search_cell/Search_demo.ear/xml/config/com.ibm.commerce.catalog/wc-search.xml file.
    
    Removes the WebSphere Commerce Search data source from WebSphere Application Server.
    
    Removes the WebSphere Commerce Search virtual hosts from WebSphere Application Server.
    
    Removes JAAS authentication data alias for the WebSphere Commerce database.
    
    Removes the WebSphere Commerce Search JDBC Provider.
    
    Uninstalls the WebSphere Commerce Search EAR from WebSphere Application Server.
    
    Removes search bindings.
    
    Deletes search object caches.
    
    Removes the Windows service.
    
    Deletes the WebSphere Commerce Search directory.
    
    Regenerates the WebSphere Application Server Web server plug-in configuration file.
3. Log on to the WebSphere Application Server Administrative Console
4. Expand Servers > Server Types > Web server
5. Delete solrWebserver.
Optional: You can clean up and remove the WebSphere Application Server search profile and WebSphere Application Server search server that WebSphere Commerce created. Do not complete this step if other applications are using the profile.
If you choose to remove the profile, the following steps remove the following components
- The search server (solrServer)
- Any other servers that might exist in the profile
- related WebSphere Application Server configuration information
- All of the applications that were installed on the mentioned servers
1. Ensure that all of the WebSphere Application Server servers that belong to the profile are stopped. By default you have one application server named server1. For more information, see Starting and stopping quick reference.
2. Use the tools that are provided by WebSphere Application Server to delete the WebSphere Application Server profile that WebSphere Commerce search created. The profile name is the same as your WebSphere Commerce search instance name.
  To remove your WebSphere Application Server profile, see step 7 in Creating a profile on a local WebSphere Application Server V8.5, V8.0, or V7.0
3. Remove the WebSphere Application Server profile service from the Services panel. Run the following commands from a command prompt:
```
cd WAS_installdir/bin
WASService.exe -remove WC_instance_name_solr
```
4. Optional: If you want to re-enable WebSphere Commerce search, then delete or rename the WebSphere Application Server search profile directory from your file system.
  
  The directory to remove or rename is WAS_installdir\profiles\instance_name_solr.