LOL Not sure if it’s such a gem. Much of the communication between the components is well known and public knowledge.
Now, one reason why you typically don’t see a diagram like this is because the communication between the products can vary greatly depending on what you use them for. If you try to capture everything, you will end up with a spider web that is just confusing. If you try to capture just the communication that is common across all, you will end up with a diagram that is too simplistic and adds no value.
But hey, let’s give it a shot! Why not? Google Drawing is not the best tool for the job, but it’s likely that everyone here has a Google account by now, right? I created a draft drawing here with some basic lines of communication. Let’s see if we can build on it or at least spark an interesting conversation.
Percio
#webMethods-Architecture#Integration-Server-and-ESB#webMethods#webMethods-General