Use a SearchCellConfig command to configure the number
of iterations used by the different jobs involved in the social analytics
indexing process.
Before you begin
When using administrative commands, you
must use the IBM® WebSphere® Application Server wsadmin client.
See Starting the wsadmin
client for details.
About this task
The social analytics indexing process includes a number of
jobs. The work for these jobs is divided up based on iterations. To
improve performance, you can configure the number of iterations specified
for a particular job based on the needs of your deployment. For example,
reducing the number of iterations results in faster performance but
is more memory-intensive.For more information about the social
analytics indexing jobs, see Adding scheduled tasks for the
social analytics service.
Procedure
To tune the social analytics indexing process, complete
the following steps.
- Start the wsadmin client from the following
directory of the system on which you installed the Deployment Manager:
app_server_root\profiles\dm_profile_root\bin
where
app_server_root is
the WebSphere Application
Server installation directory and
dm_profile_root is
the Deployment Manager profile directory, typically dmgr01.
You
must start the client from this directory or subsequent commands that
you enter do not execute correctly.
- After the wsadmin command environment
has initialized, enter the following command to initialize the Search
environment and start the Search script interpreter:
execfile("searchAdmin.py")
If prompted to specify a service to connect to, type 1 to pick
the first node in the list. Most commands can run on any node. If
the command writes or reads information to or from a file using a
local file path, you must pick the node where the file is stored.
When
the command is run successfully, the following message displays:
Search Administration initialized
-
Check out the Search cell-level configuration file, search-config.xml,
with the following command:
SearchCellConfig.checkOutConfig("working_dir",
"cellName")
Where:
- working_dir is the temporary directory to which you want to check out the
cell level configuration file. This directory must exist on the server where you are running the
wsadmin client. Use forward slashes to separate directories in the file path,
even if you are using the Microsoft
Windows operating
system.
Note: AIX, and Linux only: The
directory must grant write permissions or the command does not run successfully.
- cellName is the name of the cell that the Search node belongs to. The command
is case-sensitive. If you do not know the cell name, you can determine it by typing the following
command in the wsadmin command processor:
print
AdminControl.getCell()
For
example:
SearchCellConfig.checkOutConfig("c:/search_temp", "SearchServerNode01Cell")
- Use the following command:
- SearchCellConfig.setSandIndexerTuning(String indexer, Int iterations)
Sets the number of iterations used by a specified social analytics
job.
This command takes the following arguments:
- indexer. A string that specifies the name of the social analytics
indexing job. The following values are valid: evidence, graph, manageremployees,
and tags.
- iterations. An integer that specifies the number of iterations
for the specified social analytics indexing job.
For example:
SearchCellConfig.setSandIndexerTuning("manageremployees",200)
SearchCellConfig.setSandIndexerTuning("graph",400)
- Check in the updated search-config.xml configuration
file using the following wsadmin client command:
SearchCellConfig.checkInConfig()
- To exit the wsadmin client, type exit at
the prompt.
-
Stop the server or servers hosting the Search application, and then restart the Search servers.
The next time the scheduled task runs, persisted seedlists are retained after indexing
finishes.