Skip Headers
Oracle® Fusion Middleware Autonomy Search Integration Sample Guide for Oracle WebLogic Portal
10g Release 3 (10.3.2)

Part Number E15073-02
Go to Documentation Home
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
View PDF

8 Managing Autonomy Search in Production

After you have deployed your portal, you can manage your search services.

This chapter includes the following sections:

8.1 Using the Autonomy Service Dashboard

The Autonomy Service Dashboard allows you to access the Autonomy DiSH server, which monitors the performance of Autonomy's search services.

You can also monitor services using Autonomy's ACI interface. For more information about monitoring search services, see the Autonomy DiSH documentation.

8.2 Re-Indexing WLP Repository Content

You can re-index WLP repository content at any time. For example, you may need to re-index WLP content if your indexes get corrupted (power outage, hardware problems, and so on).

WebLogic Portal provides a script that you can use to re-index WLP repository content. You can either use command line arguments or a .properties file to indicate the content you want to index.


Oracle WebLogic Server must be running when re-indexing content.

To re-index content, do the following:

  1. From any managed server in your cluster, navigate to the index_cm_data.cmd/sh script. It is located in the <WLPORTAL_HOME>/content-mgmt/bin directory.


    You can view help for re-indexing content by typing index_cm_data -help.
  2. Optionally, if using the file, modify the properties file to match the parameters of your configuration. Example 8-1 provides an example of the file.

  3. Run the script. Table 8-1 provides a complete listing of the command line arguments and their descriptions. If no arguments are set, the is assumed and used. See Example 8-2 for an example of a file. If using command line arguments, see Example 8-3 for an example.

Example 8-1 Example of Using the File


Example 8-2 Sample File

# Set verbose to true if you want to view any error messages.
#Use username and passowrd that is used to access the portal application.
#Use the t3 protocol to refer to the WebLogic Server URL
#Indicate the name of the repository
repository=Shared Content Repository
#Indicate the name of the portal application
#Optionally, indicate which content types you want to index.
#Indicate the repository path of the content you want to index.
path=/Shared Content Repository

Example 8-3 Example of Using Command Line Arguments:

C:\myhome\wlportal_10.3\content-mgmt\bin\index_cm_data -verbose -user weblogic
-password weblogic -url t3://localhost:7001 -repository myRepo -application
myPortalApp -path \myRepo

Table 8-1 Command Line Arguments for the cm_index_data Script

Argument Description


Set verbose to true to view error messages.


The user name.


The user password.


The URL of the WebLogic Server. For example, when running the CM_INDEX_DATA script for the local machine, this URL should be: t3://localhost:7001.

Note that you should use the T3 protocol, not HTTP.


Name of the repository you want to index.


Name of the portal application that uses the repository.


Optional. Indicate which content type you want to index.


The path of the repository or repository folders you want to index. For example, if you want to index the entire repository use path=/RepositoryName. If you want to index a particular folder within the repository, use path=/RepositoryName/FolderName.