Setting up WebSphere Commerce Search in the managed configuration

You can initially set up WebSphere Commerce Search in the managed configuration. Or, you can switch an existing search cluster that is managed by a deployment manager from the advanced configuration to the managed configuration.

Before you begin

Review the managed search topologies and map your current cluster to one of the topologies.

About this task

The following list shows the high-level steps that are associated with setting up a search cluster to use the managed configuration:

Update the WebSphere Application Server system JVM properties for all search server nodes. This step uses the deployment manager to update each Solr cluster member to include Solr home and data directories.
Update the cluster member templates so that newly added nodes contain the proper system properties. This step uses the deployment manager to update the cluster member templates to also include the Solr home and data directories.

Procedure

Update the WebSphere Application Server system JVM properties for all search server nodes.
1. In the deployment manager, go to the search cluster members. WebSphere Application Server clusters > search_cluster_name > Cluster members.
2. For each of the Solr cluster members, go to the custom properties. search_server_name > Process definition > Java Virtual Machine > Custom properties.
3. Click the solr.solr.home property and modify it to the following value: ./installedApps/demo_search_cell/Search_demo.ear/managed-solr/slave/solr/home
  - The demo_search_cell and Search_demo.ear values might be different on your system, depending on the names that were given when the search application was installed.
  - The value starts with a dot to indicate that it is a relative path to the server location on the file system. If the server you are updating is a managed repeater, use the following value instead: ./installedApps/demo_search_cell/Search_demo.ear/managed-solr/repeater/solr/home
4. Save the property into the configuration.
5. Click New to create a new property. Enter the following name: solr.data.dir and enter a value that is a location in the file system. For example: /opt/WebSphere/solr/Data
6. Save the property into the configuration.
Update the cluster member templates so that newly added nodes contain the proper system properties.
1. In the deployment manager, go to the search cluster member templates. WebSphere Application Server clusters > search_cluster_name > Cluster members > Cluster member templates.
2. Go to the custom properties. template_name > Process definition > Java Virtual Machine > Custom properties.
3. Click the solr.solr.home property and modify it to the following value: ./installedApps/demo_search_cell/Search_demo.ear/managed-solr/slave/solr/home
  
  Note: The slave path is used because when new nodes are added, they will typically be used as subordinate nodes.
4. Save the property into the configuration.
5. Click New to create a new property. Enter the following name: solr.data.dir and enter a value that is a location in the file system. For example: /opt/WebSphere/solr/Data
6. Save the property into the configuration.