| Author |
Message
|
| grtABHIJEET |
 Posted: Wed Jun 12, 2013 4:04 am Post subject: Share variable between two message flow |
 |
|
Newbie
Joined: 12 Jun 2013
Posts: 4
|
Hi guys
I very new to broker development.I want to share single var to two different message
In my single EG i have deployed two flows
Flow One
MQ Ip --> Compute Node1 ----> Filter1 ----> MQ Output
In above Compute Node1 I am defining setting
OutputLocalEnvironment.Variables.RequestType
Flow Two
MQ Ip --> Compute Node2 ----> JCN ----> Filter2 ---> MQ Output
I want to use RequestType which is define in Compute Node1 of first meassage flow
in filter2 of second message flow
M i doing correct way ????
Please rectify me is there any better solution for this
I search forum but not getting proper solution for this |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jun 12, 2013 4:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You really probably don't want to do this. You're too new to Broker to be doing this kind of design. You need to rethink what you're trying to do in terms of existing patterns that are documented in the Samples - collection, aggregation, etc.
Also, you can't access ESQL shared variables from Java.
Also, this question should have been asked in the Broker forum. |
|
| Back to top |
|
|
| grtABHIJEET |
| Posted: Wed Jun 12, 2013 4:42 am Post subject: Share variable between two message flow |
|
|
Newbie
Joined: 12 Jun 2013
Posts: 4
|
Thx ton for your reply
For more clear view
In second flow I am calling third party application as service and getting response in JCN. After getting response I need to forward this response to particular Output node (after filter2 there are two O/P Node for true n false)
selection criteria for filter2 is request type which lost after computenode1 in flow1
like CreateModify become Create in compute1
So I need this specific "CreateModify" request type in second flow |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 12, 2013 4:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Throw away the notion of using two flows.
Why are you using two flows?
Every flow is entirely separate from every other flow. Every Input node creates an entirely separate thread from every other Input node.
You do not have the experience necessary to complete the task you have, given the design you are trying to use.
Make a new design. Start over. Simplify. Use the Samples that come with the product that provide patterns you can follow.
If someone at your local site is telling you to do this using the design you have, stop asking US for help and start asking THEM. |
|
| Back to top |
|
|
| grtABHIJEET |
| Posted: Wed Jun 12, 2013 5:00 am Post subject: |
|
|
Newbie
Joined: 12 Jun 2013
Posts: 4
|
What rude way to reply..............
Its ok in this case to merge two flow in single flow as this flows are in sequence as flow1 and flow2
what if i want var in fourth or fifth flow. ????
But still I want to know what is best way to share var across flow.
Experience does not come avoiding problem OR making shortcut |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 12, 2013 5:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There is no best way to share information across two flows.
There are several different ways, all with different advantages and disadvantages.
The simplest way to share information between two flows is to include it in the message received by the second flow.
If you remotely considered that option, you did not mention it nor provide any reasons why you chose not to use it. If you remotely considered any other options, you did not mention them nor provide any reason why you chose not to do them.
You merely insisted that we tell you how to do something that is probably a bad idea, particularly given your own statement of lack of experience.
It's not rude to tell someone that they should not step in front of a speeding taxicab. |
|
| Back to top |
|
|
| grtABHIJEET |
| Posted: Wed Jun 12, 2013 5:18 am Post subject: |
|
|
Newbie
Joined: 12 Jun 2013
Posts: 4
|
* please do not use * its grt 
That means there are way to share variable across flow
Can you share one of the way from several different ways
Its for my understanding |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 12, 2013 6:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| grtABHIJEET wrote: |
* please do not use * its grt
That means there are way to share variable across flow
Can you share one of the way from several different ways
Its for my understanding |
It's certainly possible for me to share this.
I choose not to provide any other mechanisms than I already have, because again with the level of skill and understanding that you have demonstrated, it will lead you to step in front of a speeding taxi cab.
I repeat.
Redesign your flow. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 12, 2013 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| grtABHIJEET wrote: |
| Experience does not come avoiding problem OR making shortcut |
Nor does experience come from jumping out in front of a speeding taxicab because you want to become a stuntman one day. All that comes from that are shattered dreams and shattered bones. Experience comes from jumping out in front of a skateboard and working your way up to taxicabs. During which process experience will teach you when you jump up, when you roll and when you jump backwards out of the way covering your head (messengers on bikes).
Explain why you can't use the information in a single flow, with reference to why the samples provided that apparently fit your use case and why they in fact do not. Explain what it is about your requirement that leads you to consider this suicidally complex solution to an apparently simple issue.
With these facts we will be able to better advise you on which is the least dangerous method for you to use. My most worthy associate is not talking about avoiding the issue or taking a shortcut; he's talking about doing the flow design right.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
