Building on my ‘has anyone ever used’ this feature of the NT 4.0 option pack‘, I thought it’d be interesting to build a simple MSMQ deployment. Â MSMQ is another technology I never saw deployed, as everyone was instead far more interested in MTS. Â So I thought I’d take a stab at MSMQ.
The only deployment guide I can find is here.
And I have to say, that it looks and feels a *LOT* of what became Active Directory.
So let’s look at a few things through the guide.
Top features of MSMQ are:
- Connectionless messaging. With store-and-forward message queuing, applications are not affected by network fluctuations and do not have to establish sessions. Because MSMQ uses a sessionless model at the application level, the sender and receiver do not need to support the same protocol. MSMQ supports Internet Protocol (IP) and Internet Packet eXchange (IPX).
- Network traffic prioritization. Message prioritization allows urgent or important traffic to preempt less important traffic so you can guarantee adequate response time for critical applications at the expense of less important applications.
- Guaranteed delivery. Messages can be logged to a disk-based queue to provide guaranteed delivery.
Which for 1997 technology sounds pretty great! Â But obviously what is the cost? Â To deploy MSMQ you *NEED* the following:
- Install a PEC (Primary Enterprise Controller).
- Install a PSC (Primary Site Controller) at each additional site
- Define site links and costs
- Install MSMQ dependent clients and independent clients
Optionally you can install for greater redundancy and speed..
- Install a BSC (Backup Site Controller) at each site, if required
- Install MSMQ routing servers, if required
- Install the connectors and transports, if required
As you may guess MSMQ needs a server infrastructure of it’s own. Â I thought for my limited experiment, I would use a simple two site network, comprising of a Windows NT 4.0 PDC, a Windows NT 4.0 BDC and two Windows NT 4.0 workstations.
As MSMQ stores it’s topology database in SQL Server 6.5 service pack 3, I found out the hard way that It will not install correctly with SQL Server 7. Â Nor will itÂ work with sp1, and it’ll bomb with 2. Â It must be SP3. Â I’ve also found it works best with the ‘restricted’ cut down version specifically for MSMQ. Â Which is on CD2 of the Enterprise edition of Windows NT 4.0 (I stuck a copy here). Â Basically it’s 6.5 slip-streamed to SP3, with no books (don’t’ try to install the books!). Â However I found it works best on the PDC, and installing it on a BDC you should set the SQL services to login as local system for the installation, then set them for a domain account. Â I also had to change the security model to “Windows NT Integrated”. Â I’m not sure if that is 100% a requirement, but the installer demanded it.
With that out of the way, I ran setup from the option pack, selecting MSMQ.
And the install proceeds as normal installing the base components of IIS 4.0.
Then we get to decide what kind of Server this Server will become. Â The first server I installed this on was the PDC, so I made it the PEC. Â It installed without any further incident.
I installed the option pack on the BDC, which was located in a different network, and set it up as the PSC. Â I then installed the workstation option pack on both of my workstations making them independent clients, and assigning them to their closest PEC/PSC.
As you can see the Enterprise view of MSMQ looks a LOT like the AD Sites and Computers view. Â No doubt MSMQ was on the way to Cairo.. Although I’ve always thought Exchange would have been better served by SQL, having directory services being hosted on SQL would have made life a bit easier for doing backups and restores, making it less of a black box. Â However the prospect of managing all those SQL servers.. I guess there is always trade offs.
This is a small ‘demo’ application where MSMQ can pass messages between a shared paintbrush application. Â Very cool stuff. Â And no doubt a missed opportunity to run something fun and subversive. Â Although I was always the network admin so I never had to hide my traffic.
I’ve setup MSMQ in 2000 & 2003 networks, and it is not only far more simpler to deploy, but it relies on Active Directory to figure out it’s topology, and nominated MSMQ servers to forward traffic between sites. Â I’m more surprised that AD doesn’t rely on MSMQ, but rather it seems it uses common technology.