| Author |
Message
|
| Abhinay185127 |
 Posted: Thu Jul 04, 2013 2:32 am Post subject: Parsing Exceptions Logging and sending back to calling servi |
 |
|
Acolyte
Joined: 20 May 2013
Posts: 58
|
Hi
Needed some pointers on the following scenario.
I have a requirement in which if an exception occurs inside WMB(parsing exception etc) then i have to log it to the exception handler subflow as well as send it back to the calling webservice with appropriate error message.
The problem is as soon as a parsing exception occurs it moves to the catch terminal of the SOAP Input node. From the catch terminal i have connected the exception handler subflow . I can't add any nodes in between say a flow order through which i could have logged in the exception handler subflow as well as sent back to calling web service. Strictly no nodes in between as the requirement is such.
Is there any other way to achieve the scenario. Is it possible that before the parsing error moving to the input we hold it in between and then process it.  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 04, 2013 2:57 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps whoever drafted the requirement is wrong?
Why
| Quote: |
Strictly no nodes in between as the requirement is such.
|
I am sure there are a few people here who would love to know why this is a requirement?
What happens if what you want can't be done without adding a node or two?
Are you going back to the originator and explaining to them why the conditions they have laid down are wrong?
_________________
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 |
|
|
| lancelotlinc |
| Posted: Thu Jul 04, 2013 3:11 am Post subject: Re: Parsing Exceptions Logging and sending back to calling s |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Abhinay185127 wrote: |
| I can't add any nodes in between say a flow order through which i could have logged in the exception handler subflow as well as sent back to calling web service. Strictly no nodes in between as the requirement is such. |
Let me guess ... your manager came up with this requirement. Please explain why he/she will not let you add nodes? What's the point?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Abhinay185127 |
| Posted: Thu Jul 04, 2013 3:23 am Post subject: |
|
|
Acolyte
Joined: 20 May 2013
Posts: 58
|
Because as per standard it is that the catch terminal of input will just be connected to exception handler subflow.
This is how they want to catch exceptions. They don't want any other terminal or node to be connected to the exception handler subflow. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Jul 04, 2013 3:24 am Post subject: Re: Parsing Exceptions Logging and sending back to calling s |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Abhinay185127 wrote: |
From the catch terminal i have connected the exception handler subflow . I can't add any nodes in between say a flow order through which i could have logged in the exception handler subflow as well as sent back to calling web service. Strictly no nodes in between as the requirement is such.
Is there any other way to achieve the scenario. |
One easy way is to remove the exception handler subflow so that there is no restriction and do what ever you want in that path, 
How can a requirement be in a such a way that it should not be done in a regular way? Is it some sort of puzzle? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jul 04, 2013 3:24 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Abhinay185127 wrote: |
Because as per standard it is that the catch terminal of input will just be connected to exception handler subflow.
This is how they want to catch exceptions. They don't want any other terminal or node to be connected to the exception handler subflow. |
Who is 'they'? This requirement is bogus.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Abhinay185127 |
| Posted: Thu Jul 04, 2013 3:35 am Post subject: |
|
|
Acolyte
Joined: 20 May 2013
Posts: 58
|
In that case i'll try explaining them that it is not possible and we should go for another approach. They signifies my managers  |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jul 04, 2013 6:01 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Abhinay185127 wrote: |
| They signifies my managers |
How many message flows are in production written by your managers?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Abhinay185127 |
| Posted: Thu Jul 04, 2013 8:52 pm Post subject: |
|
|
Acolyte
Joined: 20 May 2013
Posts: 58
|
This is the first time we are going with WMB as middleware for the application we are developing.
So there are no flows in production as of now.
I am working on all the flows and my managers only give the requirements |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jul 04, 2013 9:06 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
"You are not allowed to use <xyz> node." is not a valid business requirement.
"Your flow must process n-number of transactions per second." is an example of a good business requirement.
"Your flow must transform data from format A to format B." is another valid business requirement.
People lacking technical skill should not impose unreasonable or poorly thought out dictates on those writing the code.
Presumably you have been to the required nine days of Message Broker developer training, or know how to read the InfoCentre, or have previous experience developing WMB functionality, so you should have a basic idea of how to write message flows, what nodes to use, and how to manipulate the Logical Message Tree.
Message flow nodes are not mutually exclusive. In your case, just because you used a Flow Order node does not preclude you from using any other node after it. The developer makes intelligent decisions on which nodes to use, how many nodes to use, based on his/her desire to code a flow a certain way. A common argument by some low-information voters is that you should choose between Java and ESQL and only code in that language. This is a bogus idea. Good WMB developers sometimes use both Java and ESQL in the same flow for specific reasons. It's not one or the other, its both. There are times when a JCN makes absolutely perfect sense. There are other times when an ESQL Compute node is ideal. If your manager says you cannot use a JCN, ask him or her why. If your manager has prejudicial thoughts against a JCN, what about a .NET-Compute node? Or a PHP-Compute node? Don't just blindly accept what your manager says - stand up for yourself. Find out the logic behind the dictates. Is your manager's logic appropriate or justified with technical merit? Its only a job. There are many more WMB jobs than there are good WMB developers. Don't be afraid, be brave. Tactful, but brave. There are 194 nodes in the WMB pallette. Which of these 194 nodes are you prohibited from using? Why?
There are bigger fish to fry in the WMB development process than some petty little argument from a manager who has no flows in production against using certain nodes. Do you have a source code control system in place? Do you have a logging facility in place? Do you use Trace nodes in your flows before and after every major node to help you design and implement functionality? Has your WMB runtime been setup with the necessary truststore and keystore? Do you organize your main flow for upstream interaction and your subflows for downstream interaction? Do you use scripts to build your bars? Do you have BFOs (bar file overrides) for each environment? Have you been to the wonderful training offered by IBM on the WMB product? Tell your manager rather than some silly argument about you are not allowed to use a certain node, why not send you to the official training class so you can actually learn the product owner's way to write message flows? Remember, your company does not own message broker. They only licensed it. That license entitles your company to support. Only if your trained.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
