These messages would then be picked up by the console service inside the Docker container. To make things easier for myself, I just built a shortcut into the app to send messages from a local run console into the remote MSMQ queue. It will read from one queue on a remote machine somewhere, and forward the message to another queue on a remote machine. The app is very simple, with a MSMQ reader and a MSMQ writer. To fit in with most of the existing solutions, it must be full. In order to test MSMQ and how it would be used from a container, I decided to write a quick and small “dummy” console app. Ensure that the queues you want to connect to had Everyone and ANONYMOUS LOGON added with FullControl. For the service inside the Docker container to connect to the remote MSMQ, certain permissions need to be set. But as with everyone, time is always a factor. Don’t get me wrong, I would gladly rewrite some of the applications and remove MSMQ all together, splitting applications up into more manageable micro-services. Since it was announced that MSMQ will be available in Windows containers, at least this wouldn’t be required. Up until last year, to move these applications into Docker containers meant rewriting or at least rewriting the messaging that’s used. There are a lot of applications that use MSMQ for messaging between processes and services. Download sample with Dockerfile - 856.4 KB.
0 Comments
Leave a Reply. |