| Author |
Message
|
| vanshulchawla_target |
 Posted: Tue Jul 06, 2010 8:40 pm Post subject: Re Usable Adapters or Subflows |
 |
|
Apprentice
Joined: 19 May 2010
Posts: 25
|
Hi All,
I am doing a POC kinda stuff where we need to create Re Usable Adapters which we can plug in and play in message flows.
Like we have Error handler and Logging Stuff.
Currently i am working on Adapters (subflows):
1. Request Subflow - This will be a plug and play subflow which can be used to take message as XML/MQ, CWF,TDS,SOAP/HTTP,HTTP all in a single shot.I am saving the neccessary headers so that developer need not to change the code in case the type of caller changes.
2. Response Flow - As in request flow, we can get requeste from multiple callers, we will be able to send back response to the corresponding caller from this subflow all at once.
Can any body suggest me that what else we can create and what can be further improvements in these subflows.
Vanshul Chawla |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Jul 06, 2010 9:57 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You don't say what version of broker you are working with.
However if you are working with V7 then you are well on your way.
In V7, there are these wonderful things called 'Patterns'. It comes with a number of pre-defined ones and apparently with the forthcoming Fix Pack (As I heard at Hursley last week) there could well be the ability to define your own ones.
Unfortunately, I expect that for many the revelelance & usefullness of 'patterns' will pass them by. Much like a proper understanding of CCSID's, Unicode, UTF-8 & XML Doc-Type Encoding and how it all works together, but that is another topic entirely.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| vanshulchawla_target |
| Posted: Tue Jul 06, 2010 10:02 pm Post subject: |
|
|
Apprentice
Joined: 19 May 2010
Posts: 25
|
Thanks.
Yes i am working on V 7.0
Actually we worked on a project where initially we were getting XML/MQ but the end party changed their app to give a SAAS provided where we stahted getting some feeds from Webservice also.
So we were forced to change the flow a lot for getting requests and sending back the responses and that correlation stuff.
So though of goung for these adapters.
Please feel free to give further suggestions so that i can create a robust adapter. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jul 07, 2010 12:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
My suggestion is that you make two sets of generic Subflows.
One set for MQ
One set for SOAP.
Each set would comprise of an Imput Subflow and a matching Output/Reply Subflow. With the proper use of promoted properties you can make them very generic.
Then you can easily drop these onto your app specific flow knowing that with the minimum configuration all the I/O to the flow is done and also that you re employing the 'standard error handling'.
That leaves you free to make the logic of your flow work.
The downside is that the flows done this way are generally not quite as efficient as 'hand crafted ones' (done properly naturally) but you really do save time in development.
The other downside is that some people may not configure the 'generic' stuff properly. In that case you may have to resort to the 'dreaded' bar file overrides which are a personal hate of mine but sometimes there is no getting away from them....
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| vanshulchawla_target |
| Posted: Wed Jul 07, 2010 12:44 am Post subject: |
|
|
Apprentice
Joined: 19 May 2010
Posts: 25
|
Thanks. 
Actually i added:
1. Basic error handling
2. HTTP header response related error handling
3. No message available on MQGet related handling
4. SOAP and MQ in same set and used promoted properties for most of the things.
I am going to present the same in my organisation today and lets see what we hear as feedback.
Thanks for your feedback. |
|
| Back to top |
|
|
|
|
