Setting up the WebSphere Commerce search index structure for
a specific master catalog locally
You can deploy your search index
structure on your WebSphere Commerce server (embedded configuration
or standard configuration). Then, you can configure WebSphere Commerce
to use the Solr index by running the search index setup utility. This
utility ensures that your index is built successfully by using your
WebSphere Commerce master catalog data.
You can reset the
search cores on the WebSphere Commerce and Solr machines by running the search
index setup utility, after a search index has already been previously setup. For
more information and usage, see the action parameter values
defined in this task.
Before you begin
Ensure that the test server is stopped.
Ensure that your administrative server is started. For example:
If WebSphere Commerce is managed by WebSphere Application Server
Deployment manager (dmgr), start the deployment
manager and all node agents. Your cluster can also be started.
If WebSphere Commerce is not managed by WebSphere Application
Server Deployment manager (dmgr), start the WebSphere
Application Server server1.
Deploying the search server That is, ensure
that the search Server and WebSphere Commerce instance server are
working and running, or the task fails to export the wc-search.xml from
the application EAR.
Note: You
can skip setting up the search index structure (setupSearchIndex utility)
on the repeater, as you can copy the Solr home directory from the
master search server to the repeater. The default Solr home is in
the following location: working_dir/search/instance_name/search/solr/home.
Ensure
that the QEJBSVR user profile has WRITE authority for the following
directory: QIBM/UserData/CommerceServer70/instances/instance_name/temp
Procedure
Use this procedure to set up a catalog entry
index for your master catalog.
Use this procedure to set up both a catalog
entry index and a category index for your master catalog.
Complete one of the following tasks:
Log on as a WebSphere Commerce non-root
user.
Log on with a user profile that has *SECOFR
authority.
Log on with a user ID that is a member of the
Windows Administration group.
Optional: Prepares the search index for certain scenarios, such
as resetting search cores.
Action names that end with Update as
its suffix indicate that the action applies to an existing core, instead
of setting up a new core.
The following actions are supported:
configWCforReset
When used with the configSolrCoresReset parameter, resets search cores on
the WebSphere Commerce server after a previous search index is already setup. When search cores are
reset, all core-related information, such as XML configuration files and database information is
deleted.
To reset all Solr cores, set the masterCatalogId parameter to
all when using this action.
configSolrCoresReset
Resets search cores on the Solr machine.
When search cores are reset, all core-related information, such as XML configuration files and
database information is deleted.
If masterCatalogId is set to all, all Solr cores are
reset.
Optional: A flag to indicate whether to prepare the basepath and storeid for
building the site content index. If false, the basepath and storeid are
not added to the config column in the SRCHCONFEXT table.
The default value is true.
The name of the DBA user. This parameter is required with the dbauserpwd parameter
to create the workspace indexes.
dbauserpwd
The password of the DBA user. This parameter is required with
the dbauser parameter to create the workspace
indexes.
createAll
Indicates whether to create cores for all available workspaces,
including non-allocated workspaces. The default value is false, where
cores are only created for allocated workspaces.
includeUpdate
Indicates whether the utility applies optional features that are
provided by interim fixes.
For example, features that exist in the
following directories: