Importing and deploying previous search assets to the new version

Your previous search customizations are required to perform some migration tasks in WebSphere Commerce Version 8. Therefore, you must move your search customizations from WebSphere Commerce Version 7 into source control in WebSphere Commerce Version 8.

Procedure

Check in your previous customizations into source control and extract them into your WebSphere Commerce Version 8 development environment, including them in the WCBD package during builds. For more information about this process, see Deploying Java EE assets for a partial application.

Back up and import the search directory, so that you can successfully run the search index migration utility:
- WC_installdir/instances/instance_name/search
Ensure that you do not overwrite the following directories in WebSphere Commerce Version 8:
- WC_installdir/instances/instance_name/search/commerce
- WC_installdir/instances/instance_name/search/solr/home/htdocs
- WC_installdir/instances/instance_name/search/solr/home/httpconf
- WC_installdir/instances/instance_name/search/solr/home/httplogs
Back up the search configuration files from WebSphere Commerce Version 7 and import it to WebSphere Commerce Version 8, so that you can successfully rebuild the search index:
- WC_eardir/xml/config/com.ibm.commerce.catalog-ext/wc-search.xml
- Search_eardir/xml/config/com.ibm.commerce.catalog-ext/wc-search.xml
Note: You can skip this step if your WebSphere Commerce Version 7 version does not contain this file.

Before you import the file to WebSphere Commerce Version 8, update the _config:server section of the file if your search web server uses a different host name in WebSphere Commerce Version 8.
For example:
```
<_config:server name="AdvancedConfiguration_1">
<_config:common-http URL="http://hostname:3737/solr/"
allowCompression="true" connectionTimeout="15000"
defaultMaxConnectionsPerHost="600" followRedirects="false"
maxRetries="1" maxTotalConnections="600"
reference="com.ibm.commerce.foundation.server.services.search.url"
retryTimeInterval="1000" soTimeout="15000"/>
</_config:server>
```
If you are migrating from WebSphere Commerce Version 7 Feature Pack 2 - 8, work with the search configuration files to ensure that the search configuration can successfully be migrated:
1. Back up the following file in WebSphere Commerce Version 7:
  - WC_eardir/xml/config/com.ibm.commerce.catalog-fep/wc-search.xml
2. Rename the file to wc-search-copy.xml.
3. Update the _config:server section of the file if your search web server uses a different host name in WebSphere Commerce Version 8.
  For example:
```
<_config:server name="AdvancedConfiguration_1">
<_config:common-http URL="http://hostname:3737/solr/"
allowCompression="true" connectionTimeout="15000"
defaultMaxConnectionsPerHost="600" followRedirects="false"
maxRetries="1" maxTotalConnections="600"
reference="com.ibm.commerce.foundation.server.services.search.url"
retryTimeInterval="1000" soTimeout="15000"/>
</_config:server>
```
4. Import the file to the following location in WebSphere Commerce Version 8:
  - WC_eardir/xml/config/com.ibm.commerce.catalog-ext/wc-search-copy.xml
If you have customized files within the Search or Search-Rest projects in WebSphere Commerce Version 7, you must deploy those customizations to the same locations in WebSphere Commerce Version 8.
For example, but not limited to, the following files:
- Search_eardir/xml/config/com.ibm.commerce.catalog-ext/wc-component.xml
- Search_eardir/xml/config/com.ibm.commerce.catalog-ext/wc-search.xml
- Search_eardir/Search-Rest.war/WEB-INF/config/com.ibm.commerce.rest-ext/wc-rest-resourceconfig.xml