Configuring IBM Db2 Monitoring

Use the following menu options to navigate the SL1 user interface:

To view a pop-out list of menu options, click the menu icon ().
To view a page containing all of the menu options, click the Advanced menu icon ().

The following sections describe how to configure and discover IBM Db2 databases for monitoring by SL1 using the IBM: Db2 PowerPack:

Prerequisites for Monitoring IBM Db2

To configure the SL1 system to monitor IBM Db2 databases using the IBM: Db2 PowerPack, you must first perform the following prerequisites, which are based on your operating system.

After you have configured SL1 to monitor IBM Db2 databases and you have discovered an IBM Db2 server and all associated component devices, make sure that the ports for the IBM Db2 instance are open to the SL1 Data Collector.

Prerequisites for Linux/Unix Users

Create a shell session and SSH into the Db2 database you want to monitor.
Create a new group to monitor by entering the following command:

sudo groupadd <group_name>
Create a new user for the group you created by entering the following command:

sudo useradd -u <user_id> -g <group_name> -m -d /home/<user_name> <user_name>
Set a password for the user you created by entering the following command:

sudo passwd <user_name>
Log in with the instance admin user. For example: su - db2inst1
Run the following commands:

db2 update database manager configuration using SYSMON_GROUP <group_name>

db2stop

db2start
Connect to your database with the following command:

db2 connect to <db_name>
Run the following command to grant the DATAACCESS privilege to the user:

db2 "grant DATAACCESS ON DATABASE TO USER <user_name>"

NOTE: If you do not want to grant DATAACCESS privilege to the user, ScienceLogic provides a Bash and SQL scripts in a .zip file in the PowerPack download folder that grants the user permissions required to monitor Db2 databases.
- The Bash script grants required permissions to monitor Linux Db2 databases. To use the Bash script in the Linux Db2 server:
  - Copy the Bash script named grant_mon_per.sh to the Linux Db2 server.
  - Give the execute permission to the script with: chmod +x grant_mon_per.sh
  - Log in with the instance administrator user, for example: su -db2inst1.
  - Run the script with the following command in the same directory where you copied the script above. Replace the required information before running the command:
  - ./grand_mon_per.sh <DB_NAME> <DB_USER> <mon_user_name>
    - DB_NAME: Database name you want to grant permissions
    - DB_USER: The Db2 instance admin user. For example: su - db2inst1
    - mon_user_name: The new user name that you want to grant the permissions to.
  - Enter the database password of the instance admin user. The required permissions should be configured.
Verify permissions with the following commands:

db2 connect to <db_name> user <user_name> using <user_password>

db2 "select SUBSTR(AUTHORITY,1,30), D_USER, D_GROUP, D_PUBLIC, ROLE_USER, ROLE_GROUP, ROLE_PUBLIC, D_ROLE from table (sysproc.auth_list_authorities_for_authid(CURRENT_USER, 'U'))"

NOTE: Repeat steps 5 - 8 for each Db2 instance.

The user you create will likely need to use KornShell (for Unix systems) or Bash (for Linux systems).

If you are unsure of the shell directory, you can use the command which ksh to determine the KornShell directory, or which bash to determine the Bash directory.

After you have determined shell directory, run the following commands, replacing <shell_directory> with the KornShell or Bash directory:

sudo useradd -u <user_id> -g <group_name> -s <shell_directory> -m -d /home/<user_name> <user_name>

You should not use Shell (sh) as the shell for the user. Using Shell for the user shell could result in shell-related errors appearing in the Device Log.

Prerequisites for Windows Users

NOTE: Before performing the steps for the Windows prerequisites, ensure that you have followed the steps in the Configuring Windows Servers for Monitoring with PowerShellsection of the Monitoring Windows Systems with PowerShell manual.

Windows users will need to create a local user and group for the Db2 database. If you have already done so, proceed to adding the group to the instance database manager.

To create the user and group:

Click Start and select Run.
In the Run window, enter lusrmgr.msc and click OK.
In the Local Users and Groups pane, select the Users folder.

Click the Action menu and select New User.... Enter the new user's information in the New User window and click Create.
In the Local Users and Groups pane, select the Groups folder.
Click the Action menu and select New Group.... Enter the new group's information in the New Group window and click Create.
To add the new user to the group, double-click on the group name.
Click the Add... button under the Members window and enter the username. Click OK.

NOTE: You may need to add the user to the Administrators group in order to use PowerShell remoting if you don't have a PowerShell group/policy in place for non-adminstrative users.

Next, you will need to add the group you created to the instance database manager:

Log in to the Db2 database as the instance admin user.
Open the Db2 admin shell.
Run the following commands:

db2 update database manager configuration using SYSMON_GROUP <group_name>

db2stop

db2start

Next, you will grant the DATAACCESS privilege to the new user:

Log in to the Db2 database as the instance admin user.
Open the Db2 admin shell.
Run the following commands:

db2 connect to <database>

db2 "grant DATAACCESS on database to user <user_name>"

NOTE: If you do not want to grant DATAACCESS privilege to the user, ScienceLogic provides a Bash and SQL scripts in a .zip file in the PowerPack download folder that grants the user permissions required to monitor Db2 databases.

The SQL script grants required permissions to monitor Windows Db2 databases. To use the SQL script in the Windows Db2 server:
- Log in to the Windows Db2 database as the instance admin user.
- Copy the SQL script named grant_mon_per.sql to the Windows Db2 server.
- With a text editor, open the SQL script and replace <mon_user_name> with the user name that you want to grant the permissions to.
- Save your changes and close the script window.
- Open the "DB2 Command window" and at the Db2 command line, navigate to the directory where you copied the SQL script above.
- Connect your database with the following command:
- db2 connect to <db_name>
- Run the query with the following command:
- db2 -vtf grant_mon_per.sql
- The required permissions should be configured.

NOTE: You will need to grant this access to each database.

NOTE: Perform the steps to add the group to the instance database manager and to grant the DATAACCESS privilege for each Db2 instance that you will monitor.

Creating Credentials for IBM Db2

To monitor Db2 databases using SL1, you must create two credentials. These credentials enable SL1 to collect data from your Db2 databases. The types of credentials that are required for monitoring depend on the type of database being monitored:

Linux and Unix users must use an SSH/Key credential and a SOAP/XML credential
Windows users must use a PowerShell credential and a SOAP/XML credential

In addition, if the password has changed for the account with access to the Db2 database, you will need to update the corresponding Database credential.

SL1 will use SSH or PowerShell at the beginning, and then the client provided by IBM. SL1 uses the instance database manager user to connect to the Db2 database.

Creating an SSH/Key Credential (Linux and Unix Users)

Linux and Unix users must create an SSH/Key credential.

NOTE: If you are using an SL1 system prior to version 11.1.0, the new user interface does not include the Duplicate option for sample credential(s). ScienceLogic recommends that you use the classic user interface and the Save As button to create new credentials from sample credentials. This will prevent you from overwriting the sample credential(s).

To create an SSH/Key credential:

Go to the Credentials page (Manage > Credentials).

Locate the DB2 SSH Example credential, click its Actions icon () and select Duplicate. A copy of the credential, called DB2 SSH Example copy appears.
Click the Actions icon () for the DB2 SSH Example copy credential and select Edit. The Edit Credential page appears. Update the following fields:

Supply values in the following fields:

Name. Type a new name for the credential.
All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credential with those specific organizations.
Timeout(ms). Keep the default setting.

Hostname/IP. Type the IP address or hostname of the Db2 database you want to monitor.
Port. Keep the default setting.
Username. Type the username for a user with access to the Db2 database.
Password. Type the password for the account with access to the Db2 database.
Private Key (PEM Format). Optional. Use if required for SSH authentication.

The private key can have a maximum of 64 characters per line. Therefore, you cannot use keys in the OpenSSH format, because that format uses 70 characters per line. When you attempt to save the credential, SL1 will validate that the private key entered is in the correct format. You will be able to save the credential only if the private key is correctly formatted.

NOTE: If you are using a PEM key in the SSH/Key credential, then in your SOAP/XML credential you must fill in the HTTP Auth User and HTTP Auth Password fields with credentials for the same user.

Click the Save & Close button.

NOTE: The credential ID will appear in the Credentials page (Manage > Credentials) after it has been saved. Take note of the ID as you will need it when creating the SOAP/XML credential. If you cannot see the ID column in the Credentials page, click the gear icon () in the upper-left corner of the page and select Id to view the column.

Creating an SSH/Key Credential (Linux and Unix Users) in the SL1 Classic User Interface

Linux and Unix users must create an SSH/Key credential.

To create an SSH/Key credential:

Go to the Credential Management page (System > Manage > Credentials).

Click the wrench icon () for the "DB2 SSH Example" credential. The Credential Editor modal page appears.

Supply values in the following fields:

Credential Name. Type a new name for the credential.

Hostname/IP. Type the IP address or hostname of the Db2 database you want to monitor.
Port. Keep the default setting.
Timeout(ms). Keep the default setting.
Username. Type the username for a user with access to the Db2 database.
Password. Type the password for the account with access to the Db2 database.
Private Key (PEM Format). Optional. Use if required for SSH authentication.

NOTE: If you are using a PEM key in the SSH/Key credential, then in your SOAP/XML credential you must fill in the HTTP Auth User and HTTP Auth Password fields with credentials for the same user.

Click the Save As button.
When the confirmation message appears, click OK.

NOTE: The credential ID will appear at the top of the window after it has been saved. Take note of the ID as you will need it when creating the SOAP/XML credential.

Creating a PowerShell Credential (Windows Users)

Windows users must create a PowerShell credential.

To create a PowerShell credential:

Go to the Credentials page (Manage > Credentials).

Locate the DB2 PowerShell Example credential, click its Actions icon () and select Duplicate. A copy of the credential, called DB2 PowerShell Example copy appears.
Click the Actions icon () for the DB2 PowerShell Example copy credential and select Edit. The Edit Credential page appears. Update the following fields:

Supply values in the following fields:

Name. Type a new name for the credential. Can be any combination of alphanumeric characters.
All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credential with those specific organizations.
Timeout (ms). Type the time, in milliseconds, after which SL1 will stop trying to collect data from the authenticating server. For collection to be successful, SL1 must connect to the authenticating server, execute the PowerShell command, and receive a response within the amount of time specified in this field.
Account Type. Select the type of authentication for the username and password in this credential. Choices are:

Active Directory. On the device, Active Directory will authenticate the username and password in this credential.
Local. Local security on the device will authenticate the username and password in this credential.

Encrypted. Enable if you want SL1 to communicate with the device using an encrypted connection. If enabled, SL1 will communicate with the Windows server using a local user account with authentication of type "Basic Auth". You must then use HTTPS and can use a Microsoft Certificate or a self-signed certificate.

Username. Type the username for a user with access to the Db2 database to be monitored.
Password. Type the password for the user account with access to the Db2 database to be monitored.
Hostname/IP. Type the IP address of the Db2 database from which you want to retrieve data, or enter the variable %D.

Port. Leave as default value.
PowerShell Proxy Hostname/IP. Leave this field blank.
Active Directory Host/IP. Type the AD hostname or IP here if you selected Active Directory under Account Type.
Active Directory Domain. Type the AD domain if you selected Active Directory under Account Type.

Click the Save & Close button.

Creating a PowerShell Credential (Windows Users) in the SL1 Classic User Interface

Windows users must create a PowerShell credential.

To create a PowerShell credential:

Go to the Credential Management page (System > Manage > Credentials).
Click the wrench icon () for the "DB2 Powershell Example" credential. The Credential Editor modal page appears.

Supply values in the following fields:

Profile Name. Type a new name for the credential. Can be any combination of alphanumeric characters.
Account Type. Select the type of authentication for the username and password in this credential. Choices are:

Active Directory. On the device, Active Directory will authenticate the username and password in this credential.
Local. Local security on the device will authenticate the username and password in this credential.

Hostname/IP. Type the IP address of the Db2 database from which you want to retrieve data, or enter the variable %D.
Timeout (ms). Type the time, in milliseconds, after which SL1 will stop trying to collect data from the authenticating server. For collection to be successful, SL1 must connect to the authenticating server, execute the PowerShell command, and receive a response within the amount of time specified in this field.

Username. Type the username for a user with access to the Db2 database to be monitored.
Password. Type the password for the user account with access to the Db2 database to be monitored.

Encrypted. Select whether SL1 will communicate with the device using an encrypted connection. Choices are:

yes. When communicating with the Windows server, SL1 will use a local user account with authentication of type "Basic Auth". You must then use HTTPS and can use a Microsoft Certificate or a self-signed certificate.
no. When communicating with the Windows server, SL1 will not encrypt the connection.

Port. Leave as default value.
PowerShell Proxy Hostname/IP. Leave this field blank.

Click the Save As button.

Creating a SOAP/XML Credential (Linux and Unix Users)

After configuring the SSH/Key credential, you must then create a SOAP/XML credential.

To create the SOAP/XML credential:

Go to the Credentials page (Manage > Credentials).

Locate the DB2 Soap with SSH Example credential, click its Actions icon () and select Duplicate. A copy of the credential, called DB2 Soap with SSH Example copy appears.
Click the Actions icon () for the DB2 Soap with SSH Example copy credential and select Edit. The Edit Credential page appears. Update the following fields:

Update the values in the following fields:

Name. Type a new name for the credential.
All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credential with those specific organizations.

URL. Leave the default value of https://%D.
HTTP Auth User. If you used a PEM key in the SSH/Key credential, type the username for the same user. Otherwise, if you are inserting the database username and password in the SSH/Key credential, leave this field blank.
HTTP Auth Password. If you used a PEM key in the SSH/Key credential, type the password for the same user. Otherwise, if you are inserting the database username and password in the SSH/Key credential, leave this field blank.

NOTE: If the HTTP Auth User and HTTP Auth Password fields are blank, then the Dynamic Applications in the IBM: Db2 PowerPack will use the credentials provided in the SSH/Key credential.

HTTP Headers. Add the following headers by clicking + Add a header:

base_db2_path:<DB2 Installation Path>. For example: base_db2_path:/opt/ibm/db2/V11.5
instance:<Instance Name>:<Port> For example: instance:db2inst1:50000
instance:<Instance Name2>:<Port2> For example: instance:db2inst2:50000
ssh:<SSH Credential ID>

NOTE: In versions of the PowerPack prior to version 103, headers required the "<DB_NAME>" value. This value is no longer needed and can be deleted after you upgrade the PowerPack.

NOTE: You can create a header for each Db2 instance you have.

NOTE: During the discovery process, these headers will either find an existing Database credential that matches the user, password, port, and default database, or it will create a new Database credential.

NOTE: By default, the SOAP/XML credential deletes any white space before and after the colon (:) in the credential headers. If you want to include paths with white spaces in the credential, surround the path with double quotes after the colon. For example: <base_db2_path:"/opt/folder name/program files">

Click the Save & Close button.

Creating a SOAP/XML Credential (Linux and Unix Users) in the SL1 Classic User Interface

After configuring the SSH/Key credential, you must then create a SOAP/XML credential.

To create the SOAP/XML credential:

Go to the Credential Management page (System > Manage > Credentials).

Click the wrench icon () for the "DB2 Soap with SSH Example" credential for Linux/Unix users. The Credential Editor modal page appears.

Update the values in the following fields:

Basic Settings

Profile Name. Type a new name for the credential.

URL. Leave the default value of https://%D.
HTTP Auth User. If you used a PEM key in the SSH/Key credential, type the username for the same user. Otherwise, if you are inserting the database username and password in the SSH/Key credential, leave this field blank.
HTTP Auth Password. If you used a PEM key in the SSH/Key credential, type the password for the same user. Otherwise, if you are inserting the database username and password in the SSH/Key credential, leave this field blank.

NOTE: If the HTTP Auth User and HTTP Auth Password fields are blank, then the Dynamic Applications in the IBM: Db2 PowerPack will use the credentials provided in the SSH/Key credential.

HTTP Headers

HTTP Headers. Add the following headers by clicking + Add a header:

base_db2_path:<DB2 Installation Path>. For example: base_db2_path:/opt/ibm/db2/V11.5
instance:<Instance Name>:<Port> For example: instance:db2inst1:50000
instance:<Instance Name2>:<Port2> For example: instance:db2inst2:50000
ssh:<SSH Credential ID>

NOTE: In versions of the PowerPack prior to version 103, headers required the "<DB_NAME>" value. This value is no longer needed and can be deleted after you upgrade the PowerPack.

NOTE: You can create a header for each Db2 instance you have.

Click the Save As button.

Creating a SOAP/XML Credential for an SSL Certificate (Linux and Unix Users)

After configuring the SSH key, you must create a SOAP/XML credential with an SSL certificate if your Db2 server contains an SSL connection.

To create the SOAP/XML credential:

Go to the Credentials page (Manage > Credentials).
Locate the DB2 Soap SSL with SSH Example credential, click its Actions icon () and select Duplicate. A copy of the credential called DB2 Soap SSL with SSH Example copy appears.
Click the Actions icon () for the DB2 Soap SSL with SSH Example copy credential and select Edit. The Edit Credentials page appears.

Update the values in the following fields:

Name. Type a new name for the credential.
All Organizations.Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credentials with those specific organizations.
URL. Leave the default value of https://%D.
HTTP Auth User. If you used a PEM key in the SSH credential, type the username for the same user. Otherwise, if you are inserting the database username and password in the SSH credential, leave this field blank.
HTTP Auth Password. If you used a PEM key in the SSH credential, type the password for the same user. Otherwise, if you are inserting the database username and password in the SSH credential, leave this field blank.

NOTE: If the HTTP Auth User and the HTTP Auth Password fields are blank, then the Dynamic Applications in the IBM: Db2 PowerPack will use the credentials provided in the SSH key.

HTTP Headers. Add the following headers by clicking + Add a header:
- base_db2_path:<DB2 Insallation Path>.
- For example: base_db2_path:/opt/ibm/db2/v11.5
- instance:<Instance Name>:<SSL Port>
- For example:instance:db2inst1:60000
- instance:<Instance Name2>:<SSL Port2>
- For example: instance:db2inst2:60001
- ssh:<SSH Credential ID>

In versions of the PowerPack prior to version 103, headers required the <DB_NAME> value. This value is no longer needed and an be deleted after you upgrade the PowerPack.

NOTE: You can create a header for each Db2 instance you have.

By default, the SOAP/XML credential deletes any white space before and after the colon (:) in the credential headers. If you want to include paths with white spaces in the credential, surround the path with double quotes after the colon. For example: <base_db2_path:"/opt/folder/name/program files">

CURL options: Edit the following field in this section:
- SSLCERT. Type the certificate path for your SSL certificate.

The certificate path should be a path of the "Collector Unit" where the SSL certificate is located. For example: /tmp/certificate.cer. The permissions for the SSL certificate file should be at least "read" and "write" for the owner, and "read" for the group and others. The permissions for the directory that contains the SSL certificate should be at least "read", "write", and "execute" for the owner, and "read" and "execute" for the group and others.

Use default values for all other fields.
Click Save & Close.

Creating a SOAP/XML Credential for an SSL Certificate (Linux and Unix Users) in the SL1 Classic User Interface

After configuring the SSH key, you must create a SOAP/XML credential with an SSL certificate if your Db2 server contains an SSL connection.

To create the SOAP/XML credential:

Go to the Credential Management page (System>Manage>Credentials).
Click the wrench icon () for the "DB2 Soap SSL with SSH Example" credential for Linux/Unix users. The Credentials Editor modal appears.
Update the values in the following fields:

Basic Settings

Profile Name. Type a new name for the credential.
URL. Leave the default value of https://%D.
HTTP Auth User. If you used a PEM key in the SSH credential, type the username for the same user. Otherwise, if you are inserting the database username and password in the SSH credential, leave this field blank.
HTTP Auth Password. If you used a PEM key in the SSH credential, type the password for the same user. Otherwise, if you are inserting the database username and password in the SSH credential, leave this field blank.

NOTE: If the HTTP Auth User and the HTTP Auth Password fields are blank, then the Dynamic Applications in the IBM: Db2 PowerPack will use the credentials provided in the SSH key.

HTTP Headers. Add the following headers by clicking +Add a header:
- base_db2_path:<DB2 Insallation Path>.
- For example: base_db2_path:/opt/ibm/db2/v11.5
- instance:<Instance Name>:<SSL Port>
- For example:instance:db2inst1:60000
- instance:<Instance Name2>:<SSL Port2>
- For example: instance:db2inst2:60001
- ssh:<SSH Credential ID>

In versions of the PowerPack prior to version 103, headers required the <DB_NAME> value. This value is no longer needed and an be deleted after you upgrade the PowerPack.

NOTE: You can create a header for each Db2 instance you have.

CURL Options.
- SSLCERT. Type the certificate path for your SSL certificate.

Use default values for all other fields.
Click the Save As button.

Creating a SOAP/XML Credential (Windows Users)

After configuring the PowerShell credential, you must then create a SOAP/XML credential.

To create the SOAP/XML credential:

Go to the Credentials page (Manage > Credentials).

Locate the DB2 Soap with PowerShell Example credential, click its Actions icon () and select Duplicate. A copy of the credential, called DB2 Soap with PowerShell Example copy appears.
Click the Actions icon () for the DB2 Soap with PowerShell Example copy credential and select Edit. The Edit Credential page appears. Update the following fields:

Update the values in the following fields:

Name. Type a new name for the credential.
All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credential with those specific organizations.

URL. Leave the default value of https://%D.
HTTP Auth User. If you are inserting the database username and password in the PowerShell credential, leave this field blank.
HTTP Auth Password. If you are inserting the database username and password in the PowerShell credential, leave this field blank.

HTTP Headers. Add the following headers by clicking + Add a header:

instance:<Instance Name>:<Port> For example: instance:db2inst1:50000
instance:<Instance Name2>:<Port2> For example: instance:db2inst2:50000
powershell:<PowerShell Credential ID>

NOTE: You can create a header for each Db2 instance you have.

Click the Save & Close button.

Creating a SOAP/XML Credential (Windows Users) in the SL1 Classic User Interface

After configuring the PowerShell credential, you must then create a SOAP/XML credential.

To create the SOAP/XML credential:

Go to the Credential Management page (System > Manage > Credentials).

Click the wrench icon () for the "DB2 Soap with PowerShell Example" credential for Windows users. The Credential Editor modal page appears.

Update the values in the following fields:

Basic Settings

Profile Name. Type a new name for the credential.

URL. Leave the default value of https://%D.
HTTP Auth User. If ou are inserting the database username and password in the PowerShell credential, leave this field blank.
HTTP Auth Password. If you are inserting the database username and password in the PowerShell credential, leave this field blank.

HTTP Headers

HTTP Headers. Add the following headers by clicking + Add a header:

instance:<Instance Name>:<Port> For example: instance:db2inst1:50000
instance:<Instance Name2>:<Port2> For example: instance:db2inst2:50000
powershell:<PowerShell Credential ID>

NOTE: You can create a header for each Db2 instance you have.

Click the Save As button.

Creating a SOAP/XML Credential for an SSL Certificate (Windows Users)

After configuring the PowerShell credential, you must create a SOAP/XML credential with an SSL certificate if your Db2 server contains an SSL connection.

To create the SOAP/XML credential:

Go to the Credentials page (Manage > Credentials).
Locate the DB2 Soap SSL with PowerShell Example credential, click its Actions icon () and select Duplicate. A copy of the credential called DB2 Soap SSL with PowerShell Example copy appears.
Click the Actions icon () for the DB2 Soap SSL with PowerShell Example copy credential and select Edit. The Edit Credentials page appears.

Update the values in the following fields:
- Name. Type a new name for the credential.
- All Organizations.Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credentials with those specific organizations.
- URL. Leave the default value of https://%D.
- HTTP Auth User. If you are inserting the database username and password in the PowerShell credential, leave this field blank.
- HTTP Auth Password. If you are inserting the database username and password in the PowerShell credential, leave this field blank.
- HTTP Headers. Add the following headers by clicking + Add a header:
  - instance: <Instance Name>:<Port>
  - For example:instance:db2inst1:6000
  - instance:<Instance Name2>:<Port2>
  - For example: instance:db2inst2:6000
  - powershell:<PowerShell Credential ID>

NOTE: You can create a header for each Db2 instance you have.

CURL options: Edit the following field in this section:
- SSLCERT. Type the certificate path for your SSL certificate.

Use default values for all other fields.
Click Save & Close.

Creating a SOAP/XML Credential for an SSL Certificate (Windows Users) in the SL1 Classic User Interface

After configuring the PowerShell credential, you must create a SOAP/XML credential with an SSL certificate if your Db2 server contains an SSL connection.

To create the SOAP/XML credential:

Go to the Credential Management page (System>Manage>Credentials).
Click the wrench icon () for the "DB2 Soap SSL with PowerShell Example" credential for Windows users. The Credentials Editor modal appears.
Update the values in the following fields:

Basic Settings

Profile Name. Type a new name for the credential.
All Organizations.Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credentials with those specific organizations.
URL. Leave the default value of https://%D.
HTTP Auth User. If you are inserting the database username and password in the PowerShell credential, leave this field blank.
HTTP Auth Password. If you are inserting the database username and password in the PowerShell credential, leave this field blank.

HTTP Headers. Add the following headers by clicking +Add a header:
- instance:<Instance Name>:<SSL Port>
- For example:instance:db2inst1:60000
- instance:<Instance Name2>:<SSL Port2>
- For example: instance:db2inst2:60001
- powershell:<PowerShell Credential ID>

NOTE: You can create a header for each Db2 instance you have.

CURL Options.
- SSLCERT. Type the certificate path for your SSL certificate.

Use default values for all other fields.
Click the Save As button.

Updating the Database Credential

If the password has changed for the account with access to the Db2 database, you must also update the corresponding Database credential in SL1. Otherwise, you can skip this section.

To update the Database credential:

Go to the Credentials page (Manage > Credentials).
Search for and locate the credential that includes the name and port of the database with the updated password, then click the credential's Actions icon () and select Edit/Test.
In the Edit Credential page that appears, type the new password in the Password field.
Click Save & Close.

Discovering IBM Db2 Component Devices

To discover an IBM Db2 database:

On the Devices page () or the Discovery Sessions page (Devices > Discovery Sessions), click the Add Devices button. The Select page appears:

Click the Unguided Network Discovery button. Additional information about the requirements for discovery appears in the General Information pane to the right.

Click Select. The Add Devices page appears.
Complete the following fields:

Name. Type a unique name for this discovery session. This name is displayed in the list of discovery sessions on the Discovery Sessions tab.
Description. Optional. Type a short description of the discovery session. You can use the text in this description to search for the discovery session on the Discovery Sessions tab.
Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered devices

Click Next. The Credentials page of the Add Devices wizard appears:

On the Credentials page, locate and select the SOAP/XML credential you created for the Db2 database.

Click Next. The Discovery Session Details page of the Add Devices wizard appears:

Complete the following fields:

List of IPs/Hostnames. Type the IP address of Type the IP address for the Db2 database.
Which collector will monitor these devices?. Required. Select an existing collector to monitor the discovered devices.
Run after save. Select this option to run this discovery session as soon as you save the session.

In the Advanced options section, click the down arrow icon () to complete the following fields:

Discover Non-SNMP. Enable this setting.
Model Devices. Enable this setting.

Click Save and Run if you enabled the Run after save setting, or Save and Close to save the discovery session. The Discovery Sessions page (Devices > Discovery Sessions) displays the new discovery session.
If you selected the Run after save option on this page, the discovery session runs, and the Discovery Logs page displays any relevant log messages. If the discovery session locates and adds any devices, the Discovery Logs page includes a link to the Device Investigator page for the discovered device.

Discovering IBM Db2 Component Devices in the SL1 Classic User Interface

To discover an IBM Db2 database:

Go to the Discovery Control Panel page (System > Manage > Classic Discovery).
In the Discovery Control Panel, click the Create button. The Discovery Session Editor page appears.

In the Discovery Session Editor page, complete the following fields:

Name. Type a name for the discovery session.
IP Address/Hostname Discovery List. Type the IP address for the Db2 database.

Other Credentials. Select the SOAP/XML credential you created for the Db2 database.
Discover Non-SNMP. Select this checkbox.
Model Devices. Select this checkbox.

Optionally, you can enter values in the other fields on this page. For more information about the other fields on this page, see the Discovery & Credentials section.
Click the Save button to save the discovery session and then close the Discovery Session Editor window.
The discovery session you created appears at the top of the Discovery Control Panel page. Click its lightning-bolt icon () to run the discovery session.
The Discovery Session window appears. When the cluster root device(s) are discovered, click the device icon () to view the Device Properties page for each device.

Verifying Discovery and Dynamic Application Alignment

To verify that SL1 has automatically aligned the correct Dynamic Applications during discovery:

After the discovery session has completed, go to the Devices page—or the Device Manager (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface) page in the SL1 classic user interface—and find the device(s) you discovered. When you have located the device, click on its name or click on its edit icon () if you are in the SL1 classic user interface.
Click the Collections tab.
All applicable Dynamic Applications for the Db2 devices are automatically aligned during discovery.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

To verify alignment of the IBM Db2 Dynamic Applications:

After discovery has completed, go to the Discovery Logs page (Devices > Discovery Sessions > click the Actions button for that session > click Show Logs) and click on the IP address of the device. If you are in the SL1 classic user interface, click the device icon for the IBM Db2 device (). From the Device Investigator page for the IBM Db2 device, or the Device Properties page if you are in the SL1 classic user interface, click the Collections tab. The Dynamic Application Collections page appears.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

All applicable Dynamic Applications are automatically aligned to the root device and component devices during discovery:

You should see the following Dynamic Application aligned to the root device:

IBM DB2: Server Discovery

You should see the following Dynamic Application aligned to the Db2 server:

IBM DB2: Instance Discovery

You should see the following Dynamic Application aligned to the Db2 instance:

IBM DB2: Database Discovery
IBM DB2: Diagnostics Log Configuration

You should see some or all of the following Dynamic Applications aligned to the Db2 database:

IBM DB2: Authorizations Configuration
IBM DB2: Buffer Pools Performance
IBM DB2: Database Status
IBM DB2: Indexes Configuration
IBM DB2: Product Configuration
IBM DB2: Subclass Performance
IBM DB2: Summary Performance
IBM DB2: System Utilization Performance
IBM DB2: Tables Performance
IBM DB2: Tablespace Discovery
IBM DB2: Workload Performance
IBM DB2: Installed Products Configuration

You should see the following Dynamic Applications aligned to the Db2 tablespace:

IBM DB2: Tablespace Capacity Performance
IBM DB2: Tablespace Configuration
IBM DB2: Tablespace Container Configuration
IBM DB2: Tablespace Container Performance
IBM DB2: Tablespace Performance

NOTE: The IBM Db2 PowerPack uses db2ilist to discover all Db2 instances, but the Dynamic Applications will be aligned to only the instances specified in the SOAP/XML credential headers.

Viewing IBM Db2 Component Devices

In addition to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface), you can view the IBM Db2 server and all associated component devices in the following places in the user interface:

The Device Investigator Map page (click Map in the Device Investigator page) displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the listed devices reloads the page to make the selected device the primary device:

The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1 in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with an IBM Db2 server, find the IBM Db2 device and click its plus icon (+):

The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for an IBM Db2 server, go to the Component Map page and select the map from the list in the left NavBar. To learn more about the Component Map page, see the section on Maps.