Hello All!
In my earlier posts I have covered two topics which includes JMS Emulator, which emulates any target system and is capable of handling any systems in parallel and Dynamic Web Service which call act as a facade layer for calling any Web service. You can refer the individual posts if you want.
Now, the current assignment that I work in and most of other assignments, we often come across using a middle ware which acts as a transmission medium to cope with different interfacing needs firstly and to mitigate point of failures.
In current assignment of mine, it’s called OSB. System1 transmits a message via JMS protocol and needs to get the result from a target system which support HTTP WS protocol and respond to the System1 with a response.
Now in order to have the two systems tested without middle ware, I thought of merging my previous two implementation with a soft layer.
So my new architecture combining these two framework looks like below:
As you can see, System 1 first interacts via JMS Emulator Framework, the Framework directs to common MDB which in some cases can interact with emulated response from Common Proxy Message Layer or can integrate with Facade Web service Framework to get the response from a Web service.
The same pattern can be applied vice versa as well. I will write a different post on that topic.
I will soon upload the design details and complete logic for you all!
Excellent post. I’m fwcing some of tthese issues as well..
Heree is my weblog this post