!--a11y-->
Configuring Systems for Remote Monitoring
Using Remote Database Connections (DB2 UDB for UNIX and Windows) 
You use this procedure to configure systems that are to be monitored using remote database connections.
· The system(s) you intend to monitor must have a database release that is compatible with the database release of your local database.
· The user for the database connection must have sufficient database permissions. For more information, see Maintenance Actions in the DBA Cockpit.
...
1. Call the DBA Cockpit.
2.
Choose
Configuration.
A list of all
systems available is displayed with a
Stop,
Go
or
Attention icon showing the current status of this
system.

When you start the DBA Cockpit for the first time, the local system is automatically added to the list of all systems available. At least one system entry is displayed.
3.
Choose
Add.
The Configuration: System Administration – Add System Entry screen appears.
4. In the System field, specify the name of the system you want to monitor.

This name is a unique ID and does not need to be the SAP system ID.
You can choose any name except the SAP system ID of the local system, which is reserved for the local system entry.
5. On the Connection Data tab, choose Remote Database and specify the name of the database connection.
If the database connection was already defined using transaction DBCO, all parameters are automatically displayed.
If the database connection does not yet exist, you have to specify parameters, such as database system, user name, password and whether or not you want the database connection to be permanent.
You can specify the number of database connections by setting the following parameters:
¡ Connection Maximum
By setting this parameter, you limit the number of database connections, which are currently held by the system. The system makes sure that you cannot exceed this limit.
¡ Connection Optimum
By setting this parameter, you specify a more flexible limit that can be exceeded. For example, it is temporarily possible to exceed the set limit of database connections but as soon as connections are no longer used, the system releases them automatically until the set limit of optimum connections is reached.

The schema of the specified user is used as schema for monitoring a system remotely. Therefore, you have to specify the SAP connect user and not <sid>adm. Make sure that you grant the SAP connect user the appropriate permissions. For more information, see Maintenance Actions in the DBA Cockpit.
6.
Confirm your entries by
choosing
Add.
The database will now be automatically cataloged.

When a remote connection is defined, the system automatically catalogs the database. Changing an already existing database connection can result in a re-catalogization of the database with the new parameters. To avoid having to restart the database engine to activate the changes, we recommend that you disable DB2’s caching of database directory entries before you change the connection parameters. To do so, set database manager parameter DIR_CACHEto NO.
...
1. Perform steps 1 and 2 as described above under Adding a System.
2. Select a system.
3.
Choose
Edit.
The Configuration: System Administration – Change System Entry screen appears.
4. Enter your changes in the corresponding fields.
5. Save your changes.
...
1. Perform steps 1 to 2 as described above under Adding a System.
2. Select a system.
3.
Choose
Delete.
