Registering and un-registering multiple objects for monitoring
This topic describes how to register / un-register multiple objects for monitoring via the bulk monitoring selection feature.
This feature enables you to register or un-register multiple objects for monitoring in a single operation. Currently, only WebSphere MQ objects are supported.
This section includes:
Accessing the bulk monitoring selection feature
The bulk registration option is accessed from the Available Objects tree in the Object Repository tab by right-clicking on the appropriate object and selecting Bulk Registration for Monitoring, as shown below. The Register Objects for Monitoring dialog box is then displayed.
Object types available for monitoring
Based on the tree node object used to launch the Register Objects for Monitoring dialog box, the type of objects that may be registered or unregistered are pre-configured in the dialog box. The exact type(s) available depend on whether the dialog box was launched from a type or instance node, as described below.
Type node
When launched from a type node, the corresponding type will automatically be pre-set in the dialog box and cannot be changed. This is indicated by the Object Type field being grayed out and disabled.
Queue manager
If launched from a WebSphere MQ Queue Manager type node, the object type will be set to WebSphere MQ Queue Manager (as shown below). When a query is performed, only objects that match this type (i.e. queue managers) will be displayed in the dialog box.
Queue manager child types
If the Register Objects for Monitoring dialog box is accessed from a queue manager child type node, the object type will be pre-set to that type. For instance, if launched from a WebSphere MQ Local Queues type node, that type will be set into the Object Type field, and only local queues that belong to the parent queue manager will be available when a query is performed.
Instance node
If launched from an instance node, the Object Type field will not be automatically set to any specific type. Instead, a list of discoverable child types will be presented for selection by clicking the browse button next to the Object Type field. This will display all the available types; selecting one will constrain all queries to that type. If only a single discoverable child type exists, it will be automatically pre-set to avoid having to manually select it from the list.
Agent
If launched from an agent (host) instance node, the Object Type list will include all discoverable child types, of which WebSphere MQ Queue Manager is the only one pre-set.
Queue Manager
If accessed from a queue manager instance node, the Object Type list will be filled with all discoverable child types of WebSphere MQ Queue Manager.
Note
On z/OS, the objects that are only published for a z/OS queue manager are allowed if discover objects is enabled. Otherwise, the behavior is the same as that available prior to the 8.1 release – a queue manager is registered for monitoring and these extra objects are also registered for monitoring and vice versa when unregistering. Note that the qpreg utility does not register for monitoring the extra objects when the queue manager is registered for monitoring. Instead, each child object must be individually specified when using this tool. As alternatives, use the repomgr tool, policies, or the Register Objects for Monitoring dialog box, as described in the following section.
Working with the Register Objects for Monitoring window
The Object Type determines which types of objects will be displayed when a query is performed. To limit the number of objects that are returned by a query, a regular expression and/or result set size may be specified. The Query button is used to perform the query.
Note
When discovery is disabled, the result set size field is disabled, as that only applies to a direct query of the object repository.
When discovery is off, the query is made against the queue manager. The order of the objects retrieved from the database depends on the database configuration and installation. Therefore, when specifying a result set size, it is recommended to use a value large enough to retrieve all objects that match the regular expression. The JVM size of the Monitor Console may need to be increased if it is not possible to fine tune the query using a sufficiently unique regular expression.
After performing the query, unregistered objects are shown in the top table and registered objects in the lower table. Each table may be filtered independently to find the appropriate objects to be registered or unregistered for monitoring. The arrow buttons may be used to move one or all currently shown objects from one table to the other. Any objects newly selected to be registered for monitoring will be displayed in bold italics with a green border in the lower table. Newly selected objects to be unregistered for monitoring will be shown in italics with a red border in the top table.
When all selections are made, click Apply or OK to register or unregister all configured objects. The Apply button enables you to continue working in the Register Objects for Monitoring dialog box; the OK button closes the Register Objects for Monitoring dialog box after the current register/unregister actions are complete.
Comments
Log in or register to comment.