Some of the content described in this article is available in meshIQ Manage versions 12.1 and later.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier
Version 12.x and Later
This article describes the properties available in the Node Properties dialog in Manage. Use these settings to configure identity, communication, discovery, statistics, and advanced behavior for an agent-managed node.
To view the node properties, the node must be in Unmanaged state.
In the Node widget, select the required node.
-
Click the Selected menu and choose Manage.
If the node shows a red icon, it means the node is now Unmanaged.
In this state, the Properties option becomes available in the Selected menu.
Click Selected > Properties... to open the Node Properties dialog.
-
To run the node again, select Manage from the Selected menu.
The node icon changes to green, which means the node is now in Managed state.
In Managed state, the Properties option is not available.
See the table below for a description of each tab and its fields.
| Field | Description |
|---|---|
| Identity Tab | |
| Name | Specifies the name of the node as defined in meshIQ Manage. |
| Host Name | Specifies the network name of the physical workstation where the agent is installed. |
| Use DNS | Select this checkbox to use Domain Naming Service (DNS) instead of the node’s IP address. |
| IP Address | Specifies the IP address of the MQ, EMS, Kafka, Solace or ACE/IIB node. |
| Listening Port | Specifies the agent listening port number associated with this IP address. |
| Platform | Displays the operating system platform of the node (for example, Java, UNIX, Linux, or Windows). |
| Description | Optional field used to provide additional information about the node or agent. |
| Node Type | The default Node Type is M6-WMQ Agent-managed MQ Node. Other Node Types are EMS Node, Kafka Node, Solace Node, RabbitMQ Node and ACE/IIB Node. Starting from version 11.2.4, you can also add an ActiveMQ Node. |
| Communication Policy Tab | |
| Heartbeat (min.) | Specifies the heartbeat interval, in minutes, at which the agent sends status updates. Default: 1 minute. |
| Update interval (sec.) | Specifies how often the Workgroup Server updates information about MQ objects (queue managers, queues, channels, and so on). Default: 30 seconds. |
| Request timeout (sec.) | Specifies how long the Workgroup Server waits for a response from the agent before timing out. Default: 90 seconds. |
| Command limit | Specifies the maximum number of commands the Workgroup Server can send to the agent without acknowledgment. A value of 0 indicates no limit. Default: 5000. |
| Send registration to GM period (sec.) | Specifies how frequently the agent sends a registration (“I’m alive”) message to the Workgroup Server. Default: 0. |
| DNS name to create fully qualified host name | Specifies the domain name used to generate a fully qualified host name (FQDN). |
| Discovery Policy Tab | |
| Queue managers or Managers | Applies to: IBM MQ, EMS, ACE/IIB, Solace, RabbitMQ, ActiveMQ) Specifies which queue managers or EMS managers the Workgroup Server automatically discovers. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). Example: LONDON*. |
| Model queues |
Applies to MQ and ACE/IIB nodes. Specifies which model queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Namelists |
Applies to MQ and ACE/IIB nodes. Specifies which namelists are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Local queues | Applies to MQ, ACE/IIB, EMS nodes. Specifies which local queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Remote queues |
Applies to MQ and ACE/IIB nodes. Specifies which remote queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Authentication Information |
Applies to MQ and ACE/IIB nodes. Specifies which authentication information is to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Alias queues |
Applies to MQ and ACE/IIB nodes. Specifies which alias queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Client connections |
Applies to MQ and ACE/IIB nodes. Specifies which client connections are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Services |
Applies to MQ and ACE/IIB nodes. Specifies which services are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Channels |
Applies to MQ, ACE/IIB, EMS nodes. Specifies which channels are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Cluster queue managers |
Applies to MQ and ACE/IIB nodes. Specifies which cluster queue managers are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Clusters | Applies to Kafka nodes. Specifies which clusters are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Subscriptions |
Applies to MQ and ACE/IIB nodes. Specifies which subscriptions are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Processes |
Applies to MQ and ACE/IIB nodes. Specifies which processes are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Listeners |
Applies to MQ and ACE/IIB nodes. Specifies which listeners are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Topics |
Applies to MQ, ACE/IIB, EMS, Kafka nodes. Specifies which topics are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Discovery period (min.) | Specifies how often the agent performs scheduled object discovery and reports changes to the Workgroup Server. However, discovery may also be triggered by the refresh mechanism, which can cause discovery to occur more frequently than this setting. Default: 720 minutes. |
| Enable special name list discovery (-N) | Enables special discovery mode for z/OS systems when large object sets exceed 64KB response size limits. Default: Disabled. |
| Force full discovery for initial discovery (-f) | Forces a complete discovery when the agent starts, instead of discovering only modified objects. Default: OFF. |
|
Statistics Tab The fields in this tab are read-only. The values are collected from the running agent and cannot be modified in the UI. | |
| Node type | Displays the configured node type. |
| Software version | Displays the installed meshIQ MQ, EMS, Kafka, or ACE/IIB software version. |
| Status | Displays the node status (Active or Unknown). |
| System information | Displays OS name and version details. |
| CPU count | Displays the number of licensed CPUs. |
| Authorization |
Displays whether alternate authorization checking (+u) is enabled. When enabled, the node uses the permits.ini file for object-level authorization. Applicable only to IBM MQ nodes. Default: Disabled.
|
| Event counter | Displays the number of workgroup events generated. |
| Last action | Displays the last command executed against this node (for example, EXCMD_UNMANAGE_MQNODE). |
| Last event time | Displays the timestamp of the most recent recorded event. |
| Last updated | Displays when the node view was last refreshed. |
| Time since last update | Displays how long it has been since the node was active. |
|
Advanced Tab The fields in this tab are read-only. The values are collected from the running agent and cannot be modified in the UI. | |
| Convert user id to upper case | Converts the user ID to uppercase before passing it to the M6-WMQ agent for authorization checks. |
| Buffer size (KB) | Specifies total per-socket buffer space reserved for sending and receiving data. |
| Reuse address | Enables socket reuse even when the port is in the TIME_WAIT state. |
| TCP no delay | Disables the Nagle algorithm for send coalescing. |
| Number of TCP/IP bind retries | Specifies the maximum number of attempts to bind the socket to the IP address. |
| TCP buffering queue limit | Specifies the maximum number of items permitted in the TCP buffering queue. |
| Max. wait time for socket r/w event (msec) | Specifies the maximum wait time for a socket read/write event. |
________________________________________________________________________________________________________________
Version 11.3 and Earlier
This article describes the properties available in the Node Properties dialog in Manage. Use these settings to configure identity, communication, discovery, statistics, and advanced behavior for an agent-managed node.
Starting from version 11.2.4, users can add an ActiveMQ Node.
To view the node properties, the node must be in Unmanaged state.
In the Node viewlet, select the required node.
-
Click the Selected menu and choose Manage.
If the node shows a red icon, it means the node is now Unmanaged.
In this state, the Properties option becomes available in the Selected menu.
Click Selected > Properties to open the Node Properties dialog.
-
To run the node again, select Manage from the Selected menu.
The node icon changes to green, which means the node is now in Managed state.
In Managed state, the Properties option is not available.
See the table below for a description of each tab and its fields.
| Field | Description |
|---|---|
| Identity Tab | |
| Name | Specifies the name of the node as defined in meshIQ Manage. |
| Host Name | Specifies the network name of the physical workstation where the agent is installed. |
| Use DNS | Select this checkbox to use Domain Naming Service (DNS) instead of the node’s IP address. |
| IP Address | Specifies the IP address of the MQ, EMS, Kafka, Solace or ACE/IIB node. |
| Listening Port | Specifies the agent listening port number associated with this IP address. |
| Platform | Displays the operating system platform of the node (for example, Java, UNIX, Linux, or Windows). |
| Description | Optional field used to provide additional information about the node or agent. |
| Node Type | The default Node Type is M6-WMQ Agent-managed MQ Node. Other Node Types are EMS Node, Kafka Node, Solace Node, RabbitMQ Node and ACE/IIB Node. Starting from version 11.2.4, you can also add an ActiveMQ Node. |
| Communication Policy Tab | |
| Heartbeat (min.) | Specifies the heartbeat interval, in minutes, at which the agent sends status updates. Default: 1 minute. |
| Update interval (sec.) | Specifies how often the Workgroup Server updates information about MQ objects (queue managers, queues, channels, and so on). Default: 30 seconds. |
| Request timeout (sec.) | Specifies how long the Workgroup Server waits for a response from the agent before timing out. Default: 90 seconds. |
| Command limit | Specifies the maximum number of commands the Workgroup Server can send to the agent without acknowledgment. A value of 0 indicates no limit. Default: 5000. |
| Send registration to GM period (sec.) | Specifies how frequently the agent sends a registration (“I’m alive”) message to the Workgroup Server. Default: 0. |
| DNS name to create fully qualified host name | Specifies the domain name used to generate a fully qualified host name (FQDN). |
| Discovery Policy Tab | |
| Queue managers or Managers | Applies to: IBM MQ, EMS, ACE/IIB, Solace, RabbitMQ, ActiveMQ) Specifies which queue managers or EMS managers the Workgroup Server automatically discovers. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). Example: LONDON*. |
| Model queues |
Applies to MQ and ACE/IIB nodes. Specifies which model queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Namelists |
Applies to MQ and ACE/IIB nodes. Specifies which namelists are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Local queues | Applies to MQ, ACE/IIB, EMS nodes. Specifies which local queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Remote queues |
Applies to MQ and ACE/IIB nodes. Specifies which remote queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Authentication Information |
Applies to MQ and ACE/IIB nodes. Specifies which authentication information is to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Alias queues |
Applies to MQ and ACE/IIB nodes. Specifies which alias queues are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Client connections |
Applies to MQ and ACE/IIB nodes. Specifies which client connections are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Services |
Applies to MQ and ACE/IIB nodes. Specifies which services are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Channels |
Applies to MQ, ACE/IIB, EMS nodes. Specifies which channels are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Cluster queue managers |
Applies to MQ and ACE/IIB nodes. Specifies which cluster queue managers are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Clusters | Applies to Kafka nodes. Specifies which clusters are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Subscriptions |
Applies to MQ and ACE/IIB nodes. Specifies which subscriptions are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Processes |
Applies to MQ and ACE/IIB nodes. Specifies which processes are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Listeners |
Applies to MQ and ACE/IIB nodes. Specifies which listeners are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Topics |
Applies to MQ, ACE/IIB, EMS, Kafka nodes. Specifies which topics are to be automatically discovered by the workgroup server. This field accepts simple wildcards, meaning that characters can be followed by an asterisk (*). |
| Discovery period (min.) | Specifies how often the agent performs scheduled object discovery and reports changes to the Workgroup Server. However, discovery may also be triggered by the refresh mechanism, which can cause discovery to occur more frequently than this setting. Default: 720 minutes. |
| Enable special name list discovery (-N) | Enables special discovery mode for z/OS systems when large object sets exceed 64KB response size limits. Default: Disabled. |
| Force full discovery for initial discovery (-f) | Forces a complete discovery when the agent starts, instead of discovering only modified objects. Default: OFF. |
|
Statistics Tab The fields in this tab are read-only. The values are collected from the running agent and cannot be modified in the UI. | |
| Node type | Displays the configured node type. |
| Software version | Displays the installed meshIQ MQ, EMS, Kafka, or ACE/IIB software version. |
| Status | Displays the node status (Active or Unknown). |
| System information | Displays OS name and version details. |
| CPU count | Displays the number of licensed CPUs. |
| Authorization |
Displays whether alternate authorization checking (+u) is enabled. When enabled, the node uses the permits.ini file for object-level authorization. Applicable only to IBM MQ nodes. Default: Disabled.
|
| Event counter | Displays the number of workgroup events generated. |
| Last action | Displays the last command executed against this node (for example, EXCMD_UNMANAGE_MQNODE). |
| Last event time | Displays the timestamp of the most recent recorded event. |
| Last updated | Displays when the node view was last refreshed. |
| Time since last update | Displays how long it has been since the node was active. |
|
Advanced Tab The fields in this tab are read-only. The values are collected from the running agent and cannot be modified in the UI. | |
| Convert user id to upper case | Converts the user ID to uppercase before passing it to the M6-WMQ agent for authorization checks. |
| Buffer size (KB) | Specifies total per-socket buffer space reserved for sending and receiving data. |
| Reuse address | Enables socket reuse even when the port is in the TIME_WAIT state. |
| TCP no delay | Disables the Nagle algorithm for send coalescing. |
| Number of TCP/IP bind retries | Specifies the maximum number of attempts to bind the socket to the IP address. |
| TCP buffering queue limit | Specifies the maximum number of items permitted in the TCP buffering queue. |
| Max. wait time for socket r/w event (msec) | Specifies the maximum wait time for a socket read/write event. |