At least one symptom database must be imported and in use for log analysis. You can import a symptom database either from a remote server or from the localhost. An imported database must also be in use.
Two sources for symptom database are identified by default. These need to be imported before use.
If you intend to use other remote symptom databases, identify their locations and then import them.
A symptom database may be imported from any accessible remote host. To import a remote symptom database, the remote host must be running a File Transfer Protocol (FTP) server with anonymous login. Alternatively, the remote host may be running a Hypertext Transfer Protocol (HTTP) server with file transfer enabled. Configure the remote server to access the symptom database file on the server's file system. Derive the Web address (URLs) of the remote symptom database to specify where to obtain a remote symptom database.
To specify where to obtain a remote symptom database, follow these steps:
To specify the symptom databases against which you want to analyze log records, follow these directions.
If you are importing a symptom database for the first time:If you have several symptom databases in use:
Follow these steps while in the Import wizard:
An imported database may be in use or it may not. To enable a symptom database for use, follow these steps:
Related concepts
The Symptom database
The symptom database editor
Determining problems in distributed
applications using the Log and Trace Analyzer
Related tasks
Editing a symptom database
Creating a symptom database
Exporting a symptom database
Importing a log file
Profiling an application
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.