| Author |
Message |
 Topic: DP - Can't set service variable via xslt |
dyson
Replies: 0
Views: 6255
|
 Forum: WebSphere DataPower Posted: Fri Mar 07, 2014 2:35 pm Subject: DP - Can't set service variable via xslt |
The goal : to send a soap message from a multi-protocol gateway to a ws-proxy via loopback.
Problem: I keep getting xmlmgr (default): illegal character 'S' at line 1 of http://127.0.0.1:2601/Emai ... |
| Topic: MRM in V8.0.1 |
dyson
Replies: 3
Views: 2793
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jul 10, 2013 10:05 pm Subject: MRM in V8.0.1 |
I'm converting an XML message to text fixed-space message using the MRM domain in wmb V8.
I know I'm being lazy here and supposed to use DFLD but I was pressed for time and wanted to get this work ... |
| Topic: ESQL - converting variables into literals |
dyson
Replies: 14
Views: 10510
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 19, 2013 10:04 am Subject: Rules engine |
You are correct I am trying to build a very simple rules engine. And you may be correct that my approach is wrong.
Little background:
Instead of publishing the same message to multiple destinat ... |
| Topic: ESQL - converting variables into literals |
dyson
Replies: 14
Views: 10510
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 18, 2013 5:53 pm Subject: ESQL - converting variables into literals |
Hi,
I'm looking for a way to convert variables into literals e.g.
set x = 'InputRoot.XMLNSC.*:Transaction.*:TranID';
set y = '<>';
set z = '1234567';
IF {x} { ... |
| Topic: XML - setting a wildcard attribute from an extension |
dyson
Replies: 6
Views: 4395
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 25, 2013 8:10 am Subject: XML - setting a wildcard attribute from an extension |
| Perfect, thank you! |
| Topic: XML - setting a wildcard attribute from an extension |
dyson
Replies: 6
Views: 4395
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Apr 24, 2013 5:42 pm Subject: XML - setting a wildcard attribute from an extension |
e.g. The Total element has a wildcard attribute which I'm trying to set.
SET TRANSACTION.*:Total=5.99;
SET TRANSACTION.*:Total.(XMLNSC.Attribute)*:Element.*:TotalType='Gr ... |
| Topic: MQ content filtering using messages with default namespace |
dyson
Replies: 4
Views: 4774
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Dec 06, 2012 10:07 am Subject: MQ content filtering using messages with default namespace |
Using WMB 6.1, publishing a topic via the publication node.
I've tried qualifying all fields with namespaces but the rfhutil write fails when a colon is used ':'. |
| Topic: MQ content filtering using messages with default namespace |
dyson
Replies: 4
Views: 4774
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 05, 2012 3:05 pm Subject: MQ content filtering using messages with default namespace |
I'm publishing an xlm message to a couple MQ queues and I'm struggling to setup a subscription with a content filter via rfhutil.
I can get it to work with and with out namespces in the message, ... |
| Topic: Message Set design - is there a way to ignore new fields? |
dyson
Replies: 19
Views: 10940
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 24, 2012 2:13 pm Subject: Message Set design - is there a way to ignore new fields? |
| If so, you can alter the structure of the sequence containing the choice to include a variable length optional field at the end (call it FILLER or something). The unmodelled records will then be consu ... |
| Topic: Message Set design - is there a way to ignore new fields? |
dyson
Replies: 19
Views: 10940
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 24, 2012 9:12 am Subject: Message Set design - is there a way to ignore new fields? |
| No they add it right in the middle someplace. My consolation is that it's restricted to two specific areas in the message set. I will look at the reg exp option, thanks! |
| Topic: Message Set design - is there a way to ignore new fields? |
dyson
Replies: 19
Views: 10940
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 24, 2012 8:55 am Subject: Message Set design - is there a way to ignore new fields? |
it's still the most expensive of the parsing options and is a lot of trouble for a short term problem that would yield to good change control!
This might be one of the times where it's worth the pric ... |
| Topic: Message Set design - is there a way to ignore new fields? |
dyson
Replies: 19
Views: 10940
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 23, 2012 5:02 pm Subject: Message Set design - is there a way to ignore new fields? |
| This is short term solution we have plans to change to xml at the source. By techniques are you referring to wildcards? |
| Topic: Message Set design - is there a way to ignore new fields? |
dyson
Replies: 19
Views: 10940
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 23, 2012 4:48 pm Subject: Message Set design - is there a way to ignore new fields? |
| I have a message set that converts from binary to the xml tree. It fails whenever a new record/field is added to the incoming binary. I was looking for a way to modify the message set that would al ... |
| Topic: Debugging the XSL Transform Node |
dyson
Replies: 20
Views: 16230
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 02, 2012 12:12 pm Subject: Debugging the XSL Transform Node |
| yup that's what I did using XMLSpy ... debugging as we speak, thanks again. |
| Topic: Debugging the XSL Transform Node |
dyson
Replies: 20
Views: 16230
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 02, 2012 8:46 am Subject: Debugging the XSL Transform Node |
| My bad I should have mentioned that in my scenario the binary is first converted into the broker xml tree via a message set then run thru the xsl. |
