Component Monitor
Use
You can use the component monitor to identify wrongly configured objects of the following technical components:
- Filters
- Repository managers
- Repository services
- Global services
You can use the component monitor to manually trigger an attempt to start a repository manager that has failed to start in case the automatic retry to start failed repository managers was disabled. For more information, see: Deactivating Repositories if Not Available
The status of an object is displayed using a colored symbol. The color indicates whether objects are incorrectly configured. A message text helps you to find errors and correct the configuration of the objects in question.
Features
On the left-hand side of the iView, a tree that contains the various components is displayed. If you select a component, all objects within the component are displayed in a list on the right-hand side of the iView.
Entries in the Component Monitor
| Entry | Description |
|---|---|
|
Name |
Name of the component/object. |
|
Status |
Status of the component/object. There are the following statuses: Running: The object is running without errors. Startup failed: The object could not be started, for example, because a remote server could not be reached, or due to memory problems. Stopped: The object was stopped. |
|
Changed |
Time at which the configuration of the object was last changed. |
|
Startup Error |
Description of the error that occurred when the object was started. |
|
Configuration Error |
Description of the error that occurs in the configuration of the object. An error may already exist in the initial configuration, or it may have arisen after the configuration was changed. |
|
Next Automatic Restart |
Time at which the system automatically restarts the object. The components are automatically restarted to reactivate repositories that could not be started because the remote server couldn't be reached, for example. The file system, Web, and WebDav repository managers currently support this function. |
|
Start |
Triggers an attempt to start the repository manager This option is relevant for repository managers only. This option is only available in case the automatic retry to start failed repository managers is disabled and there is a repository manager that has failed to start. |
Differently colored symbols display the status of an object.
Symbols and Statuses
| Symbol | Status |
|---|---|
|
Green circle |
The configuration of the object has no errors. The object is able to function properly. |
|
Yellow triangle |
The configuration of the object has errors. The object is running using the last valid configuration. |
|
Red square |
The object is not available. This may be due to configuration errors or because the object could not be started for other reasons (for example, due to an unavailable remote server). |
A message text gives you more information about the error.
Activities
To call up the component monitor, choose System Administration → Support → Knowledge Management → Component Monitor.
If a component has objects that are either wrongly configured or that couldn't be started, a yellow or red symbol is already displayed in the tree view. Open the components affected, and read the error messages for any objects with errors. You correct errors by calling up the configuration of the object (for example, repository manager) and correcting the errors there.
Example
The following message is displayed beneath the Repository Manager component:
runtime > Repository Managers
| Name | Status | Changed |
|---|---|---|
|
dbfs |
startup failed |
01.08.03 11:37:47 |
|
Configuration Error: folder 'C:/share_dbfs' does not exist |
The dbfsrepository manager could not be started because the C:/share_dbfsdirectory could not be found.
Check the configuration of the repository manager, and make sure that you specified a valid path. If necessary, correct the path specification.