Administration functions are carried out locally using the MSMQAdm utility, a console utility that configures MSMQ. MSMQAdm is script-driven, so routine tasks can be automated. MSMQAdm is an independent client that is not part of any ___domain and all relevant administration information is stored on the device itself.
Tasks administered through MSMQAdm include the following:
- Browsing local queues
- Purging messages
- Deleting individual messages
- Stopping and starting MSMQ service
- Connecting and disconnecting from the network
The following command line parameters have been added to MSMQAdm.
| Parameter | Description |
|---|---|
| -s | Silent; no output is produced. Cannot be used with scripting. |
| -f <filename> | Output goes to specified file. Cannot be used with scripting. |
Base Directory
The base directory contains the following:
- The local and outgoing queues
- Message data
- MSMQ internal queues
One file is contained in each queue.
At startup, MSMQ creates a machine journal queue and a dead-letter queue, if they are not already present. These queues have a local queue manager GUID as part of their names.
The following file types are associated with GUIDs.
| Extensions | File type |
|---|---|
| Oq | Outgoing messages that were sent to queues on different machines. |
| Iq | Local queues and messages residing in these queues. |
| Jq | Journal counterparts to local queues. |
File names are prefixed with the machine name and "public" token for public queues. The exception is the naming convention for local queues, which are prefixed with the "$localhost$" token and cannot be public.
See Also
MSMQ Application Development | Summary of Supported MSMQ Functions | Installable File Systems | Using the MSMQAdm Utility | Backup | Uninstallation | Application Installation of MSMQ | Installation Options | Debugging MSMQ Installations | MSMQ Security | MSMQ Samples
Send Feedback on this topic to the authors