Configuration and Discovery

This section describes how to configure and discover IBM MQ messaging systems for monitoring by Skylar One using the "IBM: MQ" PowerPack.

Prerequisites for Monitoring IBM MQ

To configure the Skylar One system to monitor IBM MQ messaging systems using the "IBM: MQ" PowerPack, you must first perform the following: 

• Install the IBM MQ PowerShell Snap-in for Monitoring on Windows Servers
• Give all SSH credential users the "mqm" group permission

Installing the IBM MQ PowerShell Snap-In for Monitoring on Windows Servers

NOTE: Users monitoring MQ on Linux servers do not need to perform these steps.

NOTE: On 64-bit versions of Microsoft Windows, both 32-bit and 64-bit versions of Windows PowerShell are installed. Skylar One's collection processes using Windows PowerShell will default to using the version of powershell.exe whose folder exists first in the PATH environment variable. Because this will vary from system to system, these steps ensure the WebSphereMQ.dll file is registered for both Windows PowerShell environments.

1. Download the Windows PowerShell library package (mo74.zip) for IBM MQ.
2. Extract the contents of the zip file to your Windows server, and find the "manual" subfolder from the extracted files (under the mo74_v2.0.1_x86_x64 folder). Create a new folder on your desktop and move the files in the "manual" subfolder to that folder.
3. Register the IBM WebSphere MQ library for use by both 32-bit and 64-bit Windows PowerShell. To do this:

• Start a 32-bit Windows PowerShell console window (this will be the Windows PowerShell (x86) application if running on a 64-bit version of Microsoft Windows) using "Run as adminstrator", run the following:

%WINDIR%\Microsoft.NET\Framework\v4.0.30319\installutil <Directory where WebsphereMQ.dll resides>\WebSphereMQ.dll

 

• Start a 64-bit Windows PowerShell console window (this will be the Windows PowerShell application without (x86) in its program name on a 64-bit version of Microsoft Windows) using "Run as adminstrator" and run the following:

%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\installutil <Directory where WebsphereMQ.dll resides>\WebSphereMQ.dll

 

4. Open your Windows PowerShell console and add the WebSphere MQ for PowerShell snap-in by running the following command:

Add-PSSnapin IBM.PowerShell.WebSphereMQ

Disabling Concurrent SSH Collection

Be advised, concurrent SSH collection is not supported with this PowerPack and should not be enabled. Concurrent SSH collection is disabled by default.

To disable concurrent SSH collection:

• Go to the Process Manager page (System > Settings > Processes).
• Find the "Data Collection: SSH Collector" process and select its wrench icon ().
• Set the Operating State to Disabled.
• Save your change.
• Wait 10 minutes for all collection processes to complete.

Creating a Credential for IBM: MQ Guided Discovery

To allow Skylar One to discover IBM MQ messaging systems with guided discovery, you must first create a IBM: MQ credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

NOTE: This IBM: MQ credential should only be used with IBM: MQ guided discovery.

To configure a credential to access an IBM: MQ system for guided discovery:

1. Go to the Credentials page (Manage > Credentials).
2. Click the Create New button and select Create Ibm mq Credential. The Create Credential modal page appears.
3. Enter values in the following fields:

• Name. Type a 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. This field is required.
• Hostname/IP. Type the Hostname or IP address where the database resides. This field is required.
• Port. Type the Port number associated with the database you want to access with this credential. This field is required.
• Username. Type the username for a user with administrator access to the IBM: MQ messaging system.
• Password. Type the password for the IBM: MQ system account username.

4. Click Save & Close.

Creating a PowerShell Credential for IBM MQ on Windows Systems

To configure Skylar One to monitor IBM MQ messaging systems on Windows systems, you must first create a PowerShell credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

The PowerPack includes an example PowerShell credential that you can edit for your own use.

NOTE: If you are using a Skylar One 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 credential(s). This will prevent you from overwriting the sample credential(s).

To configure a PowerShell credential to access an IBM MQ system:

1. Go to the Credentials page (Manage > Credentials).
2. Locate the IBM MQ PowerShell - Example sample credential, click its Actions icon () and select Duplicate. A copy of the credential, called IBM MQ PowerShell - Example copy appears.
3. Click the Actions icon () for the IBM MQ PowerShell - Example copy credential and select Edit. The Edit Credential modal page appears.
4. Supply values in the following fields:

The following fields reflect fields that appear in generic PowerShell credentials and might not yet appear in the IBM MQ PowerShell - Example copy credential.

• 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). Type the time, in milliseconds, after which Skylar One will stop trying to collect data from the authenticating server. For collection to be successful, Skylar One must connect to the authenticating server, execute the PowerShell command, and receive a response within the amount of time specified in this field.
• Hostname/IP. Keep the default value.
• Port. Leave as default value.
• Username. Type the username for a user with administrator access to the IBM MQ messaging system.
• Password. Type the password for the IBM MQ system account username.
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.

• Use SSL (HTTPS) / Encrypted. Toggle on (blue) if you want Skylar One to communicate with the device using an encrypted connection over HTTPS. If enabled, Skylar One 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.

In Skylar One versions prior to 12.3.7, this field is labeled Encrypted. In versions 12.3.7 and above, it is labeled Use SSL (HTTPS).

In Skylar One versions 11.3.0 and later, a newer Kerberos library is used that allows for message encryption over HTTP. This feature is on by default and may eliminate the need for you to configure an HTTPS certificate depending on your security requirements.

• Validate Certificate (when HTTPS is used). This field is visible when the Use SSL (HTTPS) toggle field is enabled for the connection and enables you to select whether a certificate is validated for the credential. Choices are:
  • Ignore. Skylar One will not validate a certificate for the credential. This is the default setting.
  • Validate. Skylar One will require a validated certificate for the credential. If you select Validate, then the target device must include a non-expired certificate issued from a certificate authority.
• 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.
• Message Encryption Setting. If you selected Active Directory in the Account Type field, select whether Kerberos packages sent over PowerShell Remoting Protocol (PSRP) or Windows Remote Management (WinRM) are encrypted. Choices are:

• Auto. Encryption is enabled if the package supports it; otherwise, encryption is disabled. This is the default setting.
• Never. Messages are never encrypted. If selected, the target device must support this option.
• Always. Messages are always encrypted. If selected, the target device must support this option.

• PowerShell Proxy Hostname/IP. Leave this field blank.

5. Click Save & Close.

Creating a PowerShell Credential for IBM MQ on Windows Systems in the Classic Skylar One User Interface

To configure Skylar One to monitor IBM MQ messaging systems on Windows systems, you must first create a PowerShell credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

The PowerPack includes an example PowerShell credential that you can edit for your own use.

To configure a PowerShell credential to access an IBM MQ system:

1. Go to the Credential Management page (System > Manage > Credentials).
2. Locate the IBM MQ PowerShell - Example credential, then click its wrench icon (). The Edit PowerShell Credential modal page appears.
3. Complete the following fields:

• Credential Name. Type a new name for the credential.
• Hostname/IP. Keep the default value.
• Username. Type the username for a user with administrator access to the IBM MQ messaging system.
• Password. Type the password for the IBM MQ system account username.

4. Click the Save As button.

Creating an SSH/Key Credential for IBM MQ on Linux Systems

To configure Skylar One to monitor IBM MQ messaging systems on Linux systems, you must first create an SSH/Key credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

The PowerPack includes an example SSH/Key credential that you can edit for your own use.

NOTE: If you are using a Skylar One 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 credential(s). This will prevent you from overwriting the sample credential(s).

To configure an SSH/Key credential to access an IBM MQ system:

1. Go to the Credentials page (Manage > Credentials).
2. Locate the IBM MQ SSH - Example sample credential, click its Actions icon () and select Duplicate. A copy of the credential, called IBM MQ SSH - Example copy appears.
3. Click the Actions icon () for the IBM MQ SSH - Example copy credential and select Edit. The Edit Credential modal page appears.

4. Supply values in the following fields:

• Name. Type a new name for the credential.

• Hostname/IP. Keep the default value.

• Username. Type the username for a user with administrator access, and who is a member of the "mgm" group, to the IBM MQ messaging system.
• Password. Type the password for the IBM MQ system account username.

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, Skylar One 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.

5. Click Save & Close.

Creating an SSH/Key Credential for IBM MQ on Linux Systems in the Skylar One Classic User Interface

To configure Skylar One to monitor IBM MQ messaging systems on Linux systems, you must first create an SSH/Key credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

The PowerPack includes an example SSH/Key credential that you can edit for your own use.

To configure an SSH/Key credential to access an IBM MQ system:

1. Go to the Credential Management page (System > Manage > Credentials).
2. Locate the IBM MQ SSH - Example credential, then click its wrench icon (). The Edit SSH/Key Credential modal page appears:
3. Complete the following fields:

• Credential Name. Type a new name for the credential.
• Hostname/IP. Keep the default value.
• Username. Type the username for a user with administrator access, and who is a member of the "mgm" group, to the IBM MQ messaging system.
• Password. Type the password for the IBM MQ system account username.

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, Skylar One 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.

4. Click the Save As button.

Creating a SOAP/XML Credential for IBM MQ on AIX and Linux Systems

To configure Skylar One to monitor IBM MQ messaging systems on your AIX and Linux systems, you must first create a SOAP/XML credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

NOTE: You are only required to create SOAP/XML credential for your Linux system if you want to utilize the Kornshell and sudo commands.

The PowerPack includes an example SOAP/XML credential that you can edit for your own use.

NOTE: If you are using a Skylar One 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 credential(s). This will prevent you from overwriting the sample credential(s).

To configure a SOAP/XML credential to access an IBM MQ system:

1. Go to the Credentials page (Manage > Credentials).
2. Locate the IBM MQ SOAP - Example sample credential, click its Actions icon () and select Duplicate. A copy of the credential, called IBM MQ SOAP - Example copy appears.
3. Click the Actions icon () for the IBM MQ SOAP - Example copy credential and select Edit. The Edit Credential modal page appears.

4. Supply values in the following fields:

• Name. Type a new name for the credential.
• Hostname/IP. Keep the default value.
• HTTP Auth User. Type the username for a user with administrator access to the IBM MQ messaging system.
• HTTP Auth Password. Type the password for the IBM MQ system account username.

HTTP Headers

• HTTP Headers. The following headers can be entered to use KornShell and sudo. Create a separate header for each feature:

• KORNSHELL
• SUDO

5. For all remaining fields, use the default values.
6. Click Save & Close .

Creating a SOAP/XML Credential for IBM MQ on AIX and Linux Systems in the Classic Skylar One User Interface

To configure Skylar One to monitor IBM MQ messaging systems on your AIX and Linux systems, you must first create a SOAP/XML credential. This credential allows the Dynamic Applications in the "IBM: MQ" PowerPack to connect with an IBM MQ system.

The PowerPack includes an example SOAP/XML credential that you can edit for your own use.

To configure a SOAP/XML credential to access an IBM MQ system:

1. Go to the Credential Management page (System > Manage > Credentials).
2. Locate the IBM MQ SOAP - Example credential, then click its wrench icon (). The Edit SOAP/XML Credential modal page appears.
3. Complete the following fields:

Basic Settings

• Profile Name. Type a new name for the credential.
• URL. Keep the default value.
• HTTP Auth User. Type the username for a user with administrator access to the IBM MQ messaging system.
• HTTP Auth Password. Type the password for the IBM MQ system account username.

HTTP Headers

• HTTP Headers. The following headers can be entered to use KornShell and sudo. Create a separate header for each feature:

• KORNSHELL
• SUDO

4. Click the Save As button.

IBM: MQ Guided Discovery

You can use the Guided Discovery Framework process in Skylar Oneto guide you through a variety of existing discovery types in addition to traditional SNMP discovery. This process, which is also called "guided discovery", lets you choose a discovery type based on the type of devices you want to monitor. The Guided Discovery workflow includes a button for IBM: MQ.

To run a Guided Discovery:

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

2. Select the IBM button. Then select the IBM: MQ radio button. Additional information about the requirements for device discovery appears in the General Information pane to the right.

3. Click Select. The Credential Selection page appears.

Only credentials created for guided discovery will display on the Credential Selection page, and you can only use those credentials for guided discovery.

During the guided discovery process, you cannot click Next until the required fields are filled on the page, nor can you skip to future steps. However, you can revisit previous steps that you have already completed.

4. On the Credential Selection page of the guided discovery process, select the IBM: MQ credential that you configured, and then click Next. The Root Device Details page appears.

5. Complete the following fields:

• Root Device Name. Type the name of the root device for the IBM: MQ root device you want to monitor.
• Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered device.
• Collector Group Name. Select an existing collector group to communicate with the discovered device. This field is required.

6. Click Next. Skylar One creates the IBM: MQ root device with the appropriate Device Class assigned to it and aligns the relevant Dynamic Applications. The Final Summary page appears.

7. Click Close.

The results of a guided discovery do not display on the Discovery Sessions page (Devices > Discovery Sessions).

Discovering IBM MQ Component Devices Using Unguided Discovery

To discover an IBM MQ messaging system:

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

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

3. Click Select. The Add Devices page appears.
4. 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.

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

6. On the Credentials page, locate and select the PowerShell, SOAP/XML, or SSH/Key credential you created for the IBM MQ system.

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

8. Complete the following fields:

• List of IPs/Hostnames. Type the IP addresses for the IBM MQ messaging system.

• Which collector will monitor these devices?. Select an existing collector to monitor the discovered devices. Required.
• 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.

9. 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.
10. 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 Component Devices in the Skylar One Classic User Interface

To discover an IBM MQ messaging system:

1. Go to the Discovery Control Panel page (System > Manage > Classic Discovery or System > Manage > Discovery in the classic user interface).
2. In the Discovery Control Panel, click the Create button. The Discovery Session Editor page appears.
3. 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 IBM MQ messaging system.
• Other Credentials. Select the PowerShell or SSH/Key credential you created for the IBM MQ messaging system.
• Discover Non-SNMP. Select this checkbox.
• Model Devices. Select this checkbox.

4. 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.
5. Click the Save button to save the discovery session and then close the Discovery Session Editor window.
6. 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.
7. 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 Skylar One has automatically aligned the correct Dynamic Applications during discovery:

• After discovery has completed, click the device icon for the IBM MQ device (). From the Device Properties page for the IBM MQ device, click the Collections tab. The Dynamic Application Collections page appears.
• All applicable Dynamic Applications for the device 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.

You should see the following Dynamic Applications aligned to the IBM MQ root device:

• IBM: MQ Discovery

You should see the following Dynamic Applications aligned to the IBM MQ server:

• IBM: MQ Queue Manager Discovery

You should see the following Dynamic Applications aligned to the IBM MQ queue managers:

• IBM: MQ Cluster Channel Configuration

NOTE: For Windows users, in the "IBM: MQ Cluster Channel Configuration" Dynamic Application, when a channel is configured with a cluster and that cluster is deleted, the status for that cluster cannot be returned.

NOTE: For Windows users, in the "IBM: MQ Cluster Channel Configuration" Dynamic Application, the "CLUSSDRA" and "CLUSSDRB" are shown as "CLUSSDR".

• IBM: MQ Channel Configuration
• IBM: MQ Queue Discovery

NOTE: For Windows users, the "IBM: MQ Discovery" Dynamic Application currently does not return "Connections", "Parent Queue Manager", or "Start Date" metrics. On some MQ installations, Skylar One may be unable to collect the "Standby Host" property.

• IBM: MQ Queue Manager Configuration

NOTE: For Windows users, the "IBM: MQ Queue Manager Configuration" Dynamic Application currently does not return "Connections", "Parent Queue Manager", or "Start Date" metrics.

You should see the following Dynamic Applications aligned to the IBM MQ queues:

• IBM: MQ Queue Configuration
• IBM: MQ Queue Performance

If the listed Dynamic Applications have not been automatically aligned during discovery, you can align them manually. To do so, perform the following steps:

• Click the Action button and then select Add Dynamic Application. The Dynamic Application Alignment page appears:
• In the Dynamic Applications field, select the Dynamic Application you want to align.
• In the Credentials field, select the appropriate IBM: MQ credential.
• Click the Save button.
• Repeat steps 1-4 for the other unaligned Dynamic Applications.

Configuring the IBM: MQ Queue Discovery Snippet

The "IBM: MQ Queue Discovery" Dynamic Application snippet allows you to customize the list of queue names and types of queues that Skylar One will discover. Up to 20 queue names can be specified, and those names will be discovered under each queue manager where they are found.

For specifying queue types, an integer can be specified as one item in the list, and the allowed values for type are:

1 : Dead letter queue will be discovered

2 : Transmission queues will be discovered

To edit the snippet:

1. Go to the Dynamic Applications Manager page (System > Manage > Applications).
2. Find the "IBM: MQ Queue Discovery" Dynamic Application and click its wrench icon ().
3. In the Dynamic Applications Properties Editor, click the Snippets tab.
4. In the Dynamic Applications Snippet Editor & Registry page, click the wrench icon () of the "Discover-Queues" snippet.
5. The content of the snippet will appear. Add the following text to the snippet to customize the list of queue names and queue types that can be discovered:

QUEUES_TO_DISCOVER = ['<queue name>','<queue name>','<queue type>']

Use commas to separate queue names and queue types.

Configuring the IBM: MQ Error Log Configuration Snippet

By default, only some errors are monitored and alerted in Skylar One. The IDs of the errors supported can be found in the snippet of the "IBM: MQ Error Log Configuration" Dynamic Application. You can add other error messages by adding the alert ID to the ALERT_ID_LIST list in the snippet.

To edit the snippet:

1. Go to the Dynamic Applications Manager page (System > Manage > Applications).
2. Find the "IBM: MQ Error Log Configuration" Dynamic Application and click its wrench icon ().
3. In the Dynamic Applications Properties Editor, click the Snippets tab.
4. In the Dynamic Applications Snippet Editor & Registry page, click the wrench icon () of the "Get-ErrorLogRecords" snippet.
5. The content of the snippet will appear. Add the alert IDs you want added to the ALERT_ID_LIST in the snippet:

Viewing IBM MQ Component Devices

In addition to the Devices page, you can view the IBM MQ system 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 Skylar One 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 a Kubernetes cluster, find the cluster 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. Skylar One automatically updates the Component Map as new component devices are discovered. Skylar One also updates each map with the latest status and event information. To view the map for a Kubernetes cluster, go to Classic Maps > Device Maps > Components, and select the map from the list in the left NavBar. To learn more about the Component Map page, see the section on Views.