Enabling interim fixes JR47273, JR47089, JR47194, JR43818

Interim fixes for JR47273, JR47089, JR47194, JR46726, and JR46779 include various enhancements and fixes for catalog issues, facet management issues, and search issues.

For example:

Fixes catalog upload issues after you upgrade to Fix Pack 6
Provides facet management support in a workspaces environment, and includes various usability enhancements
Fixes workspaces store preview so that catalog data is accurately displayed
Includes various fixes to setupSearchIndex, buildindex, and preprocess utilities
Fixes search rules in Management Center so that you can use the ampersand character (&) in search terms

Before you begin

Install the cumulative interim fix for Feature Pack 5, JR53048.fep.

For information about how to install an interim fix, see

Procedure

Skip the following steps (1 to 4) if you are not using the Aurora starter store.

Update the Aurora.sar file.
1. Copy the Aurora.sar file from WC_installdir/components/store-enhancements/starterstores/ConsumerDirect/.
2. Paste the file to
  - WC_installdir/instances/instance_name/starterstores/ConsumerDirect/
  - WCDE_installdir/starterstores/ConsumerDirect/
Update the Aurora storefront asset store SAR file.
1. Copy the AuroraStorefrontAssetStore.sar file from
  - WC_installdir/components/store-enhancements/starterstores/ExtendedSites/
  - WCDE_installdir/components/store-enhancements/starterstores/ExtendedSites/
  to
  - WC_installdir/instances/instance_name/starterstores/ExtendedSites/
  - WCDE_installdir/starterstores/ExtendedSites/
Update the Aurora catalog asset store SAR file.
1. Copy the SampleData.sar file from
  - WC_installdir/components/store-enhancements/starterstores/common/samplecatalogs/
  - WCDE_installdir/components/store-enhancements/starterstores/common/samplecatalogs/
2. Paste the file to
  - WC_installdir/instances/instance_name/starterstores/common/samplecatalogs/
  - WCDE_installdir/starterstores/common/samplecatalogs/
Publish the following SAR file according to your store model to apply the updates to your existing store:
Important: For a development environment, the search index is automatically set up and built after you publish a store archive. Ensure that the UpdateSearchIndex job is not scheduled to run around the time that you plan to publish the store archive. If the UpdateSearchIndex job conflicts with the search index set up process, you will encounter errors. For information about how to edit the UpdateSearchIndex job, see Editing the configuration for a scheduled job.
- If your existing store model is Aurora B2C direct, publish the Aurora.sar file.
- If your existing store model is Extended Sites (ExtendedSitesV2), publish the ExtendedSitesV2.sar file. Publish EliteEnhancements.sar again if you published it before.

Skip the following steps (5 to 6) if you do not use the WebSphere Commerce Workspace Management Tool

Update your WebSphere Commerce Management Center definition files to enable facet management to function properly within a workspace environment.
1. If you performed customizations on the following files
  - WC_eardir/LOBTools.war/config/commerce/catalog/listViewDefinitions/AttributeDictionaryAttributeGrid.def
  - WC_eardir/LOBTools.war/config/commerce/catalog/propertiesViews/AttributeDictionaryAttributePropertiesView.def
  - WC_eardir/LOBTools.war/config/commerce/catalog/objectDefinitions/CatalogGroupPrimaryObjectDefinition.def
  - WC_eardir/LOBTools.war/config/commerce/catalog/objectDefinitions/SalesCatalogGroupPrimaryObjectDefinition.def
  - WCDE_installdir/workspaces/LobTools/WebContent/config/commerce/catalog/listViewDefinitions/AttributeDictionaryAttributeGrid.def
  - WCDE_installdir/workspaces/LobTools/WebContent/config/commerce/catalog/propertiesViews/AttributeDictionaryAttributePropertiesView.def
  - WCDE_installdir/workspaces/LobTools/WebContent/config/commerce/catalog/objectDefinitions/CatalogGroupPrimaryObjectDefinition.def
  - WCDE_installdir/workspaces/LobTools/WebContent/config/commerce/catalog/objectDefinitions/SalesCatalogGroupPrimaryObjectDefinition.def
  Merge the changes from the files in the /components/foundation/samples/FacetManagement directory.
2. If you did not perform customizations, then copy the files from the components/foundation/samples/FacetManagement directory to the corresponding directories and build a single compressed file. The structure of the compressed file resembles the following structure:
  - LOBTools.war/config/commerce/catalog/listViewDefinitions/AttributeDictionaryAttributeGrid.def
  - LOBTools.war/config/commerce/catalog/propertiesViews/AttributeDictionaryAttributePropertiesView.def
  - LOBTools.war/config/commerce/catalog/objectDefinitions/CatalogGroupPrimaryObjectDefinition.def
  - LOBTools.war/config/commerce/catalog/objectDefinitions/SalesCatalogGroupPrimaryObjectDefinition.def
3. Deploy the Java EE assets for a partial application.
Update the authoring server runtime to enable facet management by running the following update scripts from the command line as wasuser (not root), once for each of the following tables:
- FACET
- ATTR
- ATTRDICTSRCHCONF
- SRCHATTR
- SRCHATTRPROP
- FACETCATGRP
```
WC_installdir/bin/config_ant.bat 
	-buildfile WC_installdir/components/Workspaces/xml/updateWorkspacesSchemaTable.xml
	-DinstanceName=instance_name 
	-DdbaPassword=administrative_password
	-DtableName=tableName 
	CM_updateWorkspacesTable
	-DresourceXMLLocation=location_of_resource_XML_Files
    
```
```
WC_installdir/bin/config_ant.sh 
	-buildfile WC_installdir/components/Workspaces/xml/updateWorkspacesSchemaTable.xml
	-DinstanceName=instance_name 
	-DdbaPassword=administrative_password
	-DtableName=tableName 
	CM_updateWorkspacesTable
	-DresourceXMLLocation=location_of_resource_XML_Files
    
```
Note: When you run the config_ant scripts, ensure that you meet all of the following conditions:
- Ensure that the WebSphere Commerce Server is not running, as this tool is updating the workspace schema structure.
- Run the config_ant tool under the WC_installdir/bin directory.
- Do not run the config_ant tool under any db2cmd prompt in Windows.
For more information about running the config_ant tool, see Ant target: CM_updateWorkspacesSchema.

Update the command registry using the WebSphere Commerce database user (not DBA user) to run the following query:

insert into cmdreg (storeent_id, interfacename, classname, target) values 
(0, 'com.ibm.commerce.catalog.facade.server.commands.InsertMoreCatalogGroupDataCmd+IBM_Admin_CatalogGroupFacets.0', 
'com.ibm.commerce.foundation.server.command.bod.bom.InsertMoreNounChangeControlMetaDataCmdImpl', 'Local')

If you are using search in a workspaces environment, drop the <READ_SCHEMA>.TI_APGROUP_0 table if it exists.
For example:
```
drop table WCR101.TI_APGROUP_0
```
Recreate the search directory structure for the schema and recreate the search preprocessing templates.
1. Back up your existing search directory if you customized the current search index pre-processing templates.
  The search directory is in the following location:
  - WCDE_installdir/search/
  - For AIX, Linux, Solaris, and Windows operating systems: WC_installdir/instances/instance_name/search
  - For IBM i OS operating system: /search/
2. Ensure that the WebSphere Test Server is stopped.
3. Ensure that the WebSphere Commerce search server is stopped. Delete the pre-processConfig folder under this search directory and the MC_MasterCatalogId folder under the search/solr/home directory.
4. Delete the pre-processConfig folder under this search directory and the MC_MasterCatalogId folder under the search/solr/home directory.
5. Ensure that the WebSphere Commerce search server and WebSphere Commerce instance are running.
6. Re-create the search directory structure with the setupSearchIndex utility. For more information, see Setting up the WebSphere Commerce search index structure for a specific master catalog.
7. Merge your customizations back into these newly created templates, if necessary.
8. Preprocess the WebSphere Commerce search index.
9. Build the WebSphere Commerce search index.