Accessing the Search configuration environment

You need to initialize the Search configuration environment to be able to run the SearchCellConfig and SearchService MBean commands.

Before you begin

See Starting the wsadmin client for information about how to start the wsadmin command-line tool.

About this task

Two types of command are provided for administering the Search application:
An MBean used to check out, update, and check in copies of the Search configuration file, search-config.xml. This file is used to control many aspects of Search configuration, such as:
  • The location of the Search index
  • The location of the IBM® LanguageWare® dictionaries used by Search
  • The configuration of the file download and conversion service used by Search when indexing file attachments
The SearchCellConfig MBean also provides the user with a means of checking out and checking in the Search Ajax proxy configuration file, proxy-search-config.xml.

For more information about the syntax of the SearchCellConfig commands and a description of what each command does, see SearchCellConfig commands.

An MBean used to create, retrieve, update, and delete scheduled task definitions of the following Search operations. This includes a facility to trigger one of these operations.
  • Indexing
  • Indexing optimization
This is implemented by scheduling a one-off task that is scheduled to run within 30 seconds of issuing the corresponding SearchService command.

For more information about the syntax of the SearchService commands and a description of what each command does, see SearchService commands.


To initialize the Search configuration environment, complete the following steps.
  1. Start the wsadmin client from one of the following directories on the system on which you installed the Deployment Manager:

    Linux: app_server_root\profiles\dm_profile_root\bin

    Windows: 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.