Is the plan to create this environment and move it through test and then production and then get new machines to serve as development? Not an unreasonable approach, but you might consider keeping these boxes as development and then buy and build new machines for test and prod. That way, you’ll create and debug your deployment processes too.
Do you have a defined need for TN or is it just a case of “would like to?” I would caution against using it simply because it exists. There should be a specific need that you’re addressing.
As Mark mentioned, this may be more work than it is worth. You should make sure you understand what IS clustering does and does not do. Then if you have a need that only IS clustering can address, then you’ll at least have some justification for using it.
Be careful. The “guaranteed delivery” feature is very specific in what it does and doesn’t do. Broker assures that the event will get to IS, but after that, it doesn’t do anything. If your IS service that processes the document from Broker isn’t designed correctly, you can still drop things. My point isn’t to necessarily dissuade from using Broker (though IMO it’s rarely needed) but that you make sure you understand exactly what the components do and do not do so that you make more-informed decisions.
#webMethods#webMethods-General#Integration-Server-and-ESB#webMethods-Architecture