Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2015.1
Deploying GermainUX Monitoring for IBM WebSphere MQ: Local and Remote Options Deploy GermainUX monitoring to collect queue health and performance metrics from IBM WebSphere MQ. GermainUX supports local and SSH-based MQ monitoring.

Deployment Options

Choose MQ monitoring method

Configure Network Access

Limit MQ connectivity

Configure Monitoring Credentials

Use minimal MQ permissions

Validate SSH Access

Confirm remote MQ access

​
Deployment Options

​
Local Monitoring

Use local monitoring when the GermainUX monitoring component can execute the required monitoring operations directly on the IBM WebSphere MQ server. GermainUX Engine → IBM WebSphere MQ Local monitoring does not require an SSH connection to the monitored server.

​
Remote Monitoring

Use remote monitoring when the GermainUX Engine is deployed separately from the IBM WebSphere MQ server.
GermainUX EngineSSHIBM WebSphere MQ Server
The Engine connects to the MQ server through SSH and retrieves the configured MQ monitoring information.

​
Prerequisites

Before deployment, identify:
  • IBM WebSphere MQ server
  • MQ environment
  • Queue managers to monitor
  • Queues to monitor
  • Monitoring method
  • GermainUX Engine
  • Required credentials
  • Network requirements
For remote monitoring, also confirm:
  • SSH is enabled.
  • MQ server is reachable from the Engine.
  • Required SSH port is accessible.
  • Monitoring credentials are available.
  • Monitoring account has the required permissions.

​
Deploy or Select a GermainUX Engine

Select an existing GermainUX Engine or deploy an Engine that can access the MQ environment. For local monitoring, the monitoring component must have local access to the MQ server. For remote monitoring, the Engine must be able to establish an SSH connection to the MQ server.

​
Configure Network Access

For remote monitoring, confirm:
  • DNS resolution
  • Network routing
  • Firewall access
  • SSH port access
Restrict connectivity to only the systems and ports required for monitoring.

​
Configure Monitoring Credentials

Use an account with the minimum permissions required to retrieve the MQ monitoring information. For remote monitoring, verify that the account can:
  • Connect through SSH
  • Access the required MQ environment
  • Execute the operations required by the MQ monitor
Do not grant unnecessary administrative privileges.

​
Identify the Queue Managers and Queues

Before configuring GermainUX, identify which MQ resources require monitoring. Prioritize queues that support:
  • Critical applications
  • Business transactions
  • Integrations
  • Customer-facing services
  • Time-sensitive processing
Also identify the normal operating behavior of each queue. This information will be useful when configuring SLAs and Rules.

​
Validate Local Access

For local monitoring, verify:
1

GermainUX monitoring component is operational

2

MQ environment is accessible

3

Monitoring account has the required permissions

4

Required MQ monitoring information can be retrieved

​
Validate SSH Access

For remote monitoring, verify:
1

Engine is online

2

MQ server hostname resolves

3

SSH port is reachable

4

Authentication succeeds

5

Monitoring account has the required permissions

6

MQ environment is accessible after connection

Once access has been validated, continue with Configure Monitoring for IBM WebSphere MQ.

​
Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your WebSphere environment. Contact GermainUX Support.

​
Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE LLC.