Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal DiscoveryContent Pack 28.00 (CP28)

Use > Discovery Modules > Middleware > Messaging Servers > Microsoft MQ (Message Queue) Discovery > How to Discover Microsoft MQ

How to Discover Microsoft MQ

The Microsoft Message Queue (MS MQ) discovery process enables you to discover MS MQ topology running with Active Directory, as well as the end configuration of all MS MQ servers.

There are two discovery flows, detailed as follows:

Run the discovery by LDAP
1. Run the Range IPs by ICMP job, or the Range IPs by nmap job, to discover the MS MQ system IP addresses.
2. Run the TCP Ports job to discover the LDAP ports on the MS MQ system.
3. Run the Active Directory Connection by LDAP job to detect which LDAP credentials are needed for discovery for the Microsoft Message Queue Topology by LDAP job.
4. Run the Microsoft Message Queue Topology by LDAP job to discover the Active Directory topology (forest, site-link).
Run the discovery by NTCMD or UDA or PowerCmd
1. Run the Range IPs by ICMP job, or the Range IPs by nmap job to discover the MS MQ system IP addresses.
2. Run the Host Connection by Shell job to detect which Shell credentials are needed for discovery for the Host Applications by Shell job.
3. Run the Host Applications by Shell job. At this stage, UCMDB contains information about the MS MQ Manager and machine with the domain controller, on condition that the server (the physical machine on which the MS MQ is installed) is a member of the domain.
4. Run the Microsoft Message Queue Topology by NTCMD or UDA or PowerCmd job to discover the server side topology (queues, triggers, rules).

Note Because information is retrieved from configuration files in three short registry branches only, and each file is less than 2 KB, system performance should not be affected.

For details on how DFM discovers MQ topology, see Microsoft MQ Topology Discovery Methodology.

For details on running jobs, refer to "Module/Job-Based Discovery" in the Data Flow Management section of the UCMDB Help.

Send Help Center feedback