Depending upon which components are installed, <install_directory>/bin might contain some or all of the scripts below. The operational scripts are appropriate for use during normal operations of Sentinel. The troubleshooting scripts should only be used when troubleshooting an issue.
For most scripts that require arguments, running the scripts without arguments provides details about the arguments and usage of the script.
The scripts below can be used during the normal operation of Sentinel.
Table 14-1 Operational Scripts
|
Script File |
Description |
|---|---|
|
adv_change_passwd.sh |
Resets the encrypted Advisor password stored in the Advisor configuration files. |
|
advisor.sh |
Starts the Internet download and processing of Advisor feed data. This script is scheduled to run automatically when Advisor is installed. |
|
BackupIncidentData.sh |
Used to back up incident-related data before running the delete incident utilities. For more information, contact Novell Support. |
|
Clean_Database.sh |
Used to delete incidents or Identity information from the database. |
|
control_center.sh |
Launches the Sentinel Control Center graphical user interface. |
|
dbconfig |
Configures the database connection settings stored in the DAS container XML files. For more information, see |
|
runadvisor_client.sh |
Launches the client to download Advisor data. |
|
sdm |
Launches the Sentinel Data Manager application. For more information, see Section 13.0, Sentinel Data Manager. |
|
sentinel.sh |
Starts or stops the Sentinel server. For more information, see Section 14.2, Starting and Stopping a Sentinel Server. |
|
setadvenv.sh |
Used by the Advisor scripts to set some local environment variables. |
|
setenv.sh |
Used by many of the Sentinel scripts to set some local environment variables. |
|
softwarekey.sh |
Resets the Sentinel license key. For more information, see Section 14.8, Updating Your License Key. |
|
solution_designer.sh |
Starts the Solution Designer application. |
|
uninstallcron.sh |
Removes the Advisor feed download and processing scheduled jobs. This script is run automatically by the uninstaller. |
|
versionreader.sh |
Displays the version information stored in a Sentinel jar file. For more information, see Section 14.4.2, Sentinel .jar Version Information. |
|
AnalyzePartitions.sh |
Analyzes only the event partitions |
|
javac |
|
|
Agentengine |
|
|
Install cron.sh |
|
|
Physicalmemory.sh |
|
|
setmemory.sh |
|
|
wrapper |
The scripts in this section are useful when you are troubleshooting an issue you are experiencing. They provide finer -grained control of certain components in Sentinel, allowing you to drill down to the root cause of the issue.
NOTE:These scripts should not be used during normal operation of Sentinel. They are intended for troubleshooting purposes.
Table 14-2 Troubleshooting Scripts
|
Script File |
Description |
|---|---|
|
start_broker.sh |
Starts the message bus component of the communication server. This script is useful if you are having problems starting the message bus. This script is automatically run by the installer. For more information, see Starting the Communication Server in Console Mode. |
|
stop_broker.sh |
Stops the message bus component of the communication server. For more information, see Stopping the Communication Server in Console Mode. |
|
|
These scripts start the communication server on the command line in console mode. The scripts are useful for debugging the communication server without requiring you to run the rest of Sentinel server.
NOTE:During normal operations, you should not use these scripts. Instead, follow the procedures in Section 14.2.1, Starting a Sentinel Server.
Log in as the Sentinel Administrator operating system user.
Go to:
<install_directory>/bin
Enter:
./start_broker.sh
These scripts stop the communication server on the command line in console mode. The scripts are useful for troubleshooting the communication server without forcing you to stop the rest of Sentinel server.
NOTE:During normal operations, you should not use these scripts. Instead, follow the procedures in Section 14.2.2, Stopping a Sentinel Server.
Log in as the Sentinel Administrator operating system user.
Go to:
<install_directory>/bin
Enter:
./stop_broker.sh