| Author |
Message |
 Topic: Accessing xml elements |
marquies
Replies: 19
Views: 16810
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 11, 2016 1:25 am Subject: Accessing xml elements |
Thanks Maurito for the advice.
I tried it myself but couldn't succeed hence posted it on the forum. |
| Topic: Accessing xml elements |
marquies
Replies: 19
Views: 16810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 11, 2016 12:04 am Subject: Accessing xml elements |
Hi All,
In this same example i.e.
<Message>
<A>
<B>
<AdditionalFlds>
<Field name="f1">abc</Field>
<Field name="f2">def< ... |
| Topic: Ignore blank space elements in DFDL parser |
marquies
Replies: 8
Views: 3571
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 25, 2016 1:13 am Subject: Ignore blank space elements in DFDL parser |
Thanks Timber.
Yes, I agree with you. But I want to tell the DFDL parser to delete the optional element, if it is a blank space, instead of treating it as NULL. Is it possible? |
| Topic: Ignore blank space elements in DFDL parser |
marquies
Replies: 8
Views: 3571
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 22, 2016 6:43 am Subject: Ignore blank space elements in DFDL parser |
Ok, no issues. I'll try to search for the same here.
Thanks. |
| Topic: Ignore blank space elements in DFDL parser |
marquies
Replies: 8
Views: 3571
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 22, 2016 6:38 am Subject: Ignore blank space elements in DFDL parser |
Thanks mqjeff.
Can you please help me on how to achieve it? i.e. how and what properties to be set..
Links or notes or any material briefing on the same will be helpful.
Thank you. |
| Topic: Ignore blank space elements in DFDL parser |
marquies
Replies: 8
Views: 3571
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 22, 2016 6:14 am Subject: Ignore blank space elements in DFDL parser |
Hello Everyone.
Request your inputs on my following query:
Is it possible to ignore blank value elements in DFDL parsing that are optional in nature and having data type string i.e. The DFDL par ... |
| Topic: Need Swift MT 102 and Swift MT 200 message sets or XSD |
marquies
Replies: 1
Views: 2470
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Nov 17, 2013 11:20 pm Subject: Need Swift MT 102 and Swift MT 200 message sets or XSD |
Hi Everyone,
Can somebody please help me out with the Swift MT 102 and Swift MT 200 message sets or XSD for parsing the respective messages.
Thanks in advance. |
| Topic: Remove Default Namespace in message broker |
marquies
Replies: 2
Views: 3322
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 19, 2013 7:00 am Subject: Remove Default Namespace in message broker |
Current output:
<out3:RequestPayload xmlns:out="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.03" xmlns:out3="pac813_head111" xmlns:out2="urn:iso:std:iso:20022:tech:xsd:he ... |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 4:13 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
Is it? But I'm able to deploy the same msgflow into a Windows Broker v7.0.0.3.
Facing this issue only whiling deploying the msgflow into an AIX Broker v7.0.0.3. |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 2:32 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
I executed the command "mqsichangebroker <broker> -f all"
The o/p of the mqsiservice <broker> is now
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepa ... |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 2:28 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
Zpat, it didn't work. Getting the same error as above while deploying the flow with an emailoutputnode into the broker.
Any other suggestion? |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 1:51 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
| Hi Zpat, Can I execute the command "mqsichangebroker MB7BROKER -f 7.0.0.3" and then try delpoying the flow with the emailoutputnode? Because I observe that the Broker Runtime version is 7.0. ... |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 1:33 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
The above output for for mqsiservice -v
Please find below the output of mqsiservice <broker>
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=I ... |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 1:30 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
BIP8996I: Version: 7003
BIP8997I: Product: Web ... |
| Topic: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
marquies
Replies: 10
Views: 5348
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 23, 2012 12:22 am Subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
Begin running task [Deploying [SMTP.msgflow] to execution group [Mail]]
BIP2087E: Broker SANGAM_WMB was unable to process the internal configuration message.
The entire internal configuration m ... |
