| Author |
Message |
 Topic: Missing RFHUtil |
Boolean
Replies: 9
Views: 6979
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 31, 2007 10:53 pm Subject: Missing RFHUtil |
Yes, the RFHUtil graphical client is only for Windows as well ...
The Test tool, Jeff - is that a new one or do you mean the GET/PUT options from the menu? |
| Topic: Missing RFHUtil |
Boolean
Replies: 9
Views: 6979
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 30, 2007 2:48 am Subject: Missing RFHUtil |
A big fan of the RFHUtil SupportPac, I have just migrated to LINUX.
Does anyone have a suggestion on how to put/get files to/from MQ in a LINUX world. And then I mean a graphical one like RFHUtil ( ... |
| Topic: DECLARE statement whines when migrated from WMB5 to WMB6 |
Boolean
Replies: 3
Views: 3178
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 30, 2007 2:39 am Subject: DECLARE statement whines when migrated from WMB5 to WMB6 |
That's a much better solution.
Tnx! |
| Topic: DECLARE statement whines when migrated from WMB5 to WMB6 |
Boolean
Replies: 3
Views: 3178
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 30, 2007 12:47 am Subject: DECLARE statement whines when migrated from WMB5 to WMB6 |
One of my colleagues had already solved this one.
Use curly brackets in the reference:
DECLARE InputEquipmentRef REFERENCE TO InputRoot.XMLNS.{NS}:events[1]; |
| Topic: DECLARE statement whines when migrated from WMB5 to WMB6 |
Boolean
Replies: 3
Views: 3178
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 30, 2007 12:04 am Subject: DECLARE statement whines when migrated from WMB5 to WMB6 |
When importing an ESQL flow file built in WBIMB 5.0 (XP) into a WMB 6.0 (Linux) Toolkit I get warnings that a NAMESPACE is not declared.
Declared in module as:
DECLARE NS NAMESPACE 'http://www.bas ... |
| Topic: Stopping order |
Boolean
Replies: 4
Views: 4425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Feb 16, 2007 7:43 am Subject: Stopping order |
So then it's 1. Broker, 2. QM, 3 DB.
Thank's Jeff, I will use your answer in our internal debate. |
| Topic: Stopping order |
Boolean
Replies: 4
Views: 4425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Feb 16, 2007 7:22 am Subject: Stopping order |
Can anyone help me in this issue?
We're having this argument at work - In what order should a broker, a queue manager and the broker database be stopped in order to make it "best practice" ... |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 11:07 pm Subject: TDS message set in WMB 5 |
And that's exactly what I did (following Jeffs former advice). It worked like a charm. Thanks for the good advices. Hope you Hursley guys will enjoy a Ringwood at the Dolphin  |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 7:20 am Subject: TDS message set in WMB 5 |
Ok, so the preferrable solution would be to go for 'unordered' and remove "all elements delimited"?
I'm not using tags for the outgoing data, so it gave me:
Choice Element has more tha ... |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 7:10 am Subject: TDS message set in WMB 5 |
Already tried unorderedSet and:
Composition must not be 'unorderedSet' when Data Element Separation is "AllElementsDelimited". Physical format 'TDS'
Will try 'choice' ASAP |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 6:42 am Subject: TDS message set in WMB 5 |
Invoice:
Min occurs=0
Max occurs= 1
INVEXP:
Min occurs=1
Max occurs= -1
And the same for the other elements |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 6:35 am Subject: TDS message set in WMB 5 |
http://misc.nomethod.net/bolle/VCC240.jpg
Invoice:
Min occurs=0
Max occurs= 1
Invoice Anonymous:
Composition=sequence, Closed
All Elements Delimited
Delimiter = <CR><LF>
INVE ... |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 5:58 am Subject: TDS message set in WMB 5 |
Tried the Validation option with "Content and Value", but no difference and no error message.
Message is happily parsed without the second "INVEXP" row. |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 5:35 am Subject: TDS message set in WMB 5 |
Yes, it's only the INVEXP record (the second one) that's missing.
I will try the "Validation test" - will come back |
| Topic: TDS message set in WMB 5 |
Boolean
Replies: 16
Views: 11903
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 14, 2006 4:17 am Subject: TDS message set in WMB 5 |
1. I'm reading the following message (Input node):
INVEXP ... and more data
INLEXP ... and more data
INLEXP ... and more data
INLEXP ... and more data
INVEXP ... and more data
INLEXP ... and m ... |
