![]() ![]() ![]() ![]() ![]() ![]() |
After you have deployed your portal, you can manage your search services.
Note: | The Autonomy documentation is included in your WebLogic Portal installation directory at: //WebLogic_Home /cm/thirdparty/autonomy-wlp10/common/docs/*.* |
This chapter includes the following sections:
You can either use 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.
You can re-index BEA content at any time. For example, you may need to re-index BEA 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 BEA content. You can either use command line arguments or a .properties
file to indicate the content you want to index.
This section includes the following topics:
The indexing script requires access to the following JAR file: p13n_app.jar
. This JAR file is located in the p13n-app-lib.ear
file. Before re-indexing content, you need to extract the p13n_app.jar
from the p13n-app-lib.ear
. After extracting the file, you also need to add its location to your classpath. You can delete this JAR
file after you are finished using the indexing script.
p13n-app-lib.ear
file. For example, c:\bea\wlserver_10.0\portal\lib\modules\p13n_app.ear
. p13N_app.jar
file from the p13n-app-lib.ear
to the //
WebLogic_Home
/common/p13n/lib
directory. p13n_app.jar
to the classpath on the system where you intend to use the cm_index_data
script.To re-index content, do the following:
Tip: | You can view help for re-indexing content by typing index_cm_data -help . |
cm_indexer.properties
file, modify the properties file to match the parameters of your configuration. Listing 5-2 provides an example of the cm_indexer.properties
file.cm_indexer.properties
is assumed and used. See Listing 5-2 for an example of a cm_indexer.properties file. If using command line arguments, see Listing 5-3 for an example. C:\bea\weblogic100\cm\bin\index_cm_data
# Set verbose to true if you want to view any error messages.
verbose=true
#Use username and passowrd that is used to access the portal application.
user=weblogic
password=weblogic
#Use the t3 protocol to refer to the WebLogic Server URL
url=t3://localhost:7001
#Indicate the name of the repository
repository=Shared Content Repository
#Indicate the name of the portal application
application=portalApp
#Optionally, indicate which content types you want to index.
type=
#Indicate the repository path of the content you want to index.
path=/Shared Content Repository
C:\bea1204\weblogic100\cm\bin\index_cm_data -verbose -user weblogic -password weblogic -url t3://localhost:7001 -repository myRepo -application myPortalApp -path \myRepo
![]() ![]() ![]() |