| Author |
Message
|
| smdavies99 |
 Posted: Tue Jan 26, 2016 11:29 pm Post subject: |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What you describe is typical of an AGGREGATION
There are some good tips here on how to do aggregation in your type of environment (i.e. starting with a webservice call).
As has been said, your current design is flawed. Please re-eamine the Aggregation Sample that comes with the product.
_________________
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 |
|
 |
| fjb_saper |
| Posted: Wed Jan 27, 2016 5:18 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Looks like its more than just aggregation.
First you'd have COLLECTION to COLLECT all responses from a single source, then you'd have AGGREGATION to aggregate the responses from the different sources...
Nice work in perspective... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 27, 2016 5:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mr2kn wrote: |
Have you looked at the samples that come with the product?
- yes, I have looked at it and try with that but no luck |
Which sample?
| mr2kn wrote: |
Have you reviewed where the Environment is available and where it is not?
- yes, reviewed the Environment and values are present and in the log also im able to see in the correct format |
The fact that the debugger shows the Environment tree in an XML-style format doesn't prove that it is XML. And if it is XML, why are you having a problem?
| mr2kn wrote: |
Have you reviewed the features of IIB to determine if there's some way you can share data between message flows?
- yes, IIB can share the data between msgflow through environment, so that it cannot lost the data |
Post the link from the InfoCenter where it says you can share data between message flows rather than between nodes in a single message flow.
| mr2kn wrote: |
Have you worked with a more senior developer to review your requirements and come up with a working plan to implement?
- yes, we are also working same but no luck |
The best your senior developer came up with was the Environment? They didn't mention IIB's inbuilt abilities to handle your design situation?
Are they an IIB Senior Developer, or a senior developer in some other technology? The latter may not be that much help.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 27, 2016 7:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Let's be a little more straight forward.
- Your XML structures are coming out wrong because you are not putting them under an XMLNSC parser in the Environment tree.
- Your intended use of the Environment to share data across more than one message flow, or even across more than one instance of the same message flow will not work
- You need to spend much more of your own time reviewing the samples, reading the documentation, and running experiments.
- You need to redesign your solution.
At some point, if you keep asking for direct assistance with the above, you will find that we get less cooperative, or even simply don't respond. We have jobs, too.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| mr2kn |
| Posted: Mon Feb 01, 2016 7:34 am Post subject: |
|
|
Apprentice
Joined: 26 Jan 2016
Posts: 46
|
got the solution and displaying as I required, and thank you for the support and giving the response,
I put the code like this and worked
DECLARE envRefShared SHARED ROW;
CREATE LASTCHILD OF Environment.Variables DOMAIN('XMLNSC') Name 'envRefShared';
SET Environment.Variables.envRefShared = THE(SELECT ITEM R FROM envRefSharedEB AS R);
in the response im able to see it
<Status success="false">
<StatusDetails code="6666"> |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 7:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mr2kn wrote: |
got the solution and displaying as I required, and thank you for the support and giving the response,
I put the code like this and worked
DECLARE envRefShared SHARED ROW;
CREATE LASTCHILD OF Environment.Variables DOMAIN('XMLNSC') Name 'envRefShared';
SET Environment.Variables.envRefShared = THE(SELECT ITEM R FROM envRefSharedEB AS R);
in the response im able to see it
<Status success="false">
<StatusDetails code="6666"> |
Well that's fixed the attribute problem.
How's the sharing data between flows using the Environment tree going?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mr2kn |
| Posted: Mon Feb 01, 2016 8:12 am Post subject: |
|
|
Apprentice
Joined: 26 Jan 2016
Posts: 46
|
| I used the global cache to share data between message flows |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 8:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mr2kn wrote: |
| I used the global cache to share data between message flows |
So why use the Environment tree at all?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
