The Cockpit is a database server monitoring tool that provides an up-to-date view of the availability, capacity, and performance of your database server. Use a browser to access it. It also provides information for the SAP DB Control Center.
The Cockpit issues alerts when it detects conditions that could indicate possible problems in your system. There are predefined alerts for conditions such as high CPU use, a high number of database server connections, and lengthy blocked connections and operations. From the Cockpit, you control the threshold values for the alerts, and email notification settings. Alerts exist while the conditions that create the alert are true; when these conditions are no longer present, the alert disappears.
Use the Cockpit to view the users who are connected to a database server, and to display both database server and database properties. You can perform simple administration tasks such as starting backups and dropping connections.
The Cockpit runs on the same database server that it monitors. It is designed to run continuously in the background so that you can connect to it when needed. But, you can also easily start and stop it to investigate issues.
Start the Cockpit when you start your database server, so that it is always available when you need to view the current state of the database server.
Connect to the Cockpit by using the credentials of a user from one of the databases running on the database server. This user must have the COCKPIT_ROLE user-defined role. In newly created databases, only the administrator rights are granted to the database administrator, so you must grant this user-defined role to any user that needs to connect to the Cockpit. To perform tasks using the Cockpit, you need the associated roles or privileges. For example, to back up a database, you must also have the BACKUP DATABASE system privilege for that database.
For information about the browsers that the Cockpit supports, see SAP SQL Anywhere Components by Platform.
When you start the Cockpit, you must decide whether you want to preserve your settings and alert histories between sessions.
The Cockpit application uses an embedded database, referred to as the Cockpit database. This database stores the configuration settings, such as alert thresholds, and alert histories. The Cockpit database can be a permanent database, for which you specify a file name and path, or a temporary database. A temporary Cockpit database is deleted when the Cockpit stops. When the Cockpit database is a permanent database any changes you make within the Cockpit are automatically saved to the file. You can
When you start the Cockpit, you choose whether to use a permanent database or a temporary database. If you choose to use a temporary database, you can switch to using a permanent database from the Cockpit by opening MONITORING page, clicking Configure Alerts, and then clicking Switch to a permanent Cockpit database.
The CockpitDB database server property lists the set of Cockpit options currently being used by the database server, as well as the Temp parameter. When Temp is set to yes, the Cockpit database is a temporary database.
You can view the CockpitDB database server property by opening the HOME page, clicking Show Details and locating the property in the properties table.