| Author |
Message |
 Topic: MRM to XMLNSC migration |
pawel_janowski
Replies: 12
Views: 6582
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 07, 2012 9:26 am Subject: MRM to XMLNSC migration |
I did this like this:
OutputRoot.XMLNSC.outbody.header.field1 = InputRoot.XMLNSC.(XML.Element)
You might want to consider using a field type different to XML.Element. Something that starts with ... |
| Topic: MRM to XMLNSC migration |
pawel_janowski
Replies: 12
Views: 6582
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 07, 2012 7:20 am Subject: MRM to XMLNSC migration |
I ask if I can do this in situation when I don't know what I've got on input, but I know that the message on input contains "header".
Start
Thanx.
I did this like this:
OutputRo ... |
| Topic: MRM to XMLNSC migration |
pawel_janowski
Replies: 12
Views: 6582
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 07, 2012 7:14 am Subject: MRM to XMLNSC migration |
So if the input document looks like <xml>
<root>
<header>
<field1>data</field1>
<field2>data</field2>
<header/>
<b ... |
| Topic: MRM to XMLNSC migration |
pawel_janowski
Replies: 12
Views: 6582
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 07, 2012 6:59 am Subject: MRM to XMLNSC migration |
Hi!
We are trying to migrate from MRM to XMLNCS. In the MRM domain, the name of the root element of the input message isn't stated explicitly so I can refer to the content of the XML message (its ele ... |
| Topic: Parsing input as TDS |
pawel_janowski
Replies: 6
Views: 3845
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Nov 10, 2010 4:34 am Subject: Parsing input as TDS |
OK. So my problem identification and more details as needed:
1) The problem - there is no difference between segment and field separators - they are of the same form, so parsing the segment broker ... |
| Topic: Parsing input as TDS |
pawel_janowski
Replies: 6
Views: 3845
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 09, 2010 6:47 am Subject: Parsing input as TDS |
Hi!
I've got the problem with parsing input messages of the following format:
- each message consist of one or more segments and each segment starts with segment indicator of form @5000, with assign ... |
| Topic: Accessing node properties from ESQL |
pawel_janowski
Replies: 13
Views: 16226
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 09, 2010 6:40 am Subject: Accessing node properties from ESQL |
The MQOutput node will populate WrittenDestination after it is invoked.
Regardless of whether or not it is promoted, there is no mechanism in ESQL to inquire about properties of even the Compute no ... |
| Topic: Accessing node properties from ESQL |
pawel_janowski
Replies: 13
Views: 16226
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 09, 2010 5:01 am Subject: Accessing node properties from ESQL |
Do you want to know what it is BEFORE you invoke the node, or AFTER?
Well, truly - I promote the property 'Queue Name' of the Output Node to the subflow and set the desired value at the subflow lev ... |
| Topic: Accessing node properties from ESQL |
pawel_janowski
Replies: 13
Views: 16226
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 09, 2010 4:38 am Subject: Re: Accessing node properties from ESQL |
Yes to both.
For the ESQL Solution, it uses the OutputLocalEnvironment folder.
This is how you implement distribution lists.
The info about how to setup the data is in the docs/infocentre.
Sea ... |
| Topic: Accessing node properties from ESQL |
pawel_janowski
Replies: 13
Views: 16226
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 09, 2010 2:40 am Subject: Accessing node properties from ESQL |
Hello!
Is it possible to get the Queue Name defined as a Output Node property from the ESQL Code f Compute Node within the same message flow?
Or maybe it is possible to get the value of the propert ... |
| Topic: Problem with starting broker after update |
pawel_janowski
Replies: 1
Views: 1573
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 06, 2009 2:15 am Subject: Problem with starting broker after update |
Hi once again!
I discovered the problem - very stupid: the trace for odbc was turned on and the output file reached o 2GB. Sorry for post.
Regards,
Pawel Janowski |
| Topic: Problem with starting broker after update |
pawel_janowski
Replies: 1
Views: 1573
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 06, 2009 1:42 am Subject: Problem with starting broker after update |
Hi everybody!
I decided to apply FP03 to my WMB installation. After successful completion of the installation I tried to start the broker and obtained sth like this:
/opt/ibm/mqsi/6.1/bin/mqsistar ... |
| Topic: Actual message length |
pawel_janowski
Replies: 7
Views: 4576
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 20, 2009 6:32 am Subject: Actual message length |
Thanks!
Regards, |
| Topic: Actual message length |
pawel_janowski
Replies: 7
Views: 4576
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 20, 2009 5:58 am Subject: Re: Actual message length |
Why? Of what use or value is this information? What do you mean by "the whole size" against "the size of the MRM" which is the entire message read in?
Well, inside the messa ... |
| Topic: Actual message length |
pawel_janowski
Replies: 7
Views: 4576
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 20, 2009 5:42 am Subject: Re: Actual message length |
Why? Of what use or value is this information? What do you mean by "the whole size" against "the size of the MRM" which is the entire message read in?
Well, inside the messa ... |
