| Author |
Message |
 Topic: XML Parsing Output Error |
SKAT
Replies: 5
Views: 3210
|
 Forum: General Discussion Posted: Thu Nov 03, 2005 7:56 am Subject: XML Parsing Output Error |
Yes, there is another MQRFH2 header , see below
(0x01000000):MQRFH2 = (
(0x03000000):Version = 2
(0x03000000):Format = 'MQ ... |
| Topic: XML Parsing Output Error |
SKAT
Replies: 5
Views: 3210
|
Forum: General Discussion Posted: Thu Nov 03, 2005 6:12 am Subject: XML Parsing Output Error |
No, it is using 1208/273 which is UTF-8
Find the header received in trace node
(0x01000000):Properties = (
(0x03000000):MessageSet = 'HKVHDF4002001'
& ... |
| Topic: XML Parsing Output Error |
SKAT
Replies: 5
Views: 3210
|
Forum: General Discussion Posted: Thu Nov 03, 2005 6:02 am Subject: XML Parsing Output Error |
Hi folks,
has anybody an idea why the char Ö becomes Ö when parsed to my MQNode Output.
Trace node just after my eqsl and before output queue
(0x01000010):XML = (
... |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 9:01 am Subject: Basic XMLNS question |
Here is my XMLNS trace
(0x01000010):XMLNS = (
(0x05000018):XML = (
(0x ... |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 8:49 am Subject: Basic XMLNS question |
try
set nsRaqDataRef = InputBody."Q1:ImageFile"."Q1:Image";
Still compilation warning on this |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 8:26 am Subject: Basic XMLNS question |
Hi again,
i have tried the XMLNS version and still no success.
The BLOB version has not helped either.
Looking at the input message
<?xml version="1.0" encoding="UTF-8" ... |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 6:31 am Subject: Basic XMLNS question |
Hi,
both responses were positive.
What I have lernt is that the receiving MQInput Node does not actually care about the namespace of the incoming message. I have therefore used XML messageset i ... |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 3:53 am Subject: Basic XMLNS question |
Hi
thanks for your speedy reply.
I have tried your suggestion in two ways
First without using a message set to parse the message.
Both messages (yours and mine) parsed as BLOB
When using a me ... |
| Topic: Basic XMLNS question |
SKAT
Replies: 12
Views: 6615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2005 3:04 am Subject: Basic XMLNS question |
Hi guys,
I have the following question on XmlNs Message Set
Incoming message to my MQInput looks like this
<?xml version="1.0" encoding="UTF-8"?>
<Q1:ImageFi ... |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 11:07 am Subject: Datasource problem |
| All the DB setup was done by someone else. Unfortunately no more available. How can I find out on the BROKER machine what has been configured for the DB |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 11:00 am Subject: Datasource problem |
Schema is DB2ADMIN.
If only I know where the WBIMBADM was taken from.
I will try around and give u some more details
Thanks again for the efforts
Regards
Skat |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 10:46 am Subject: Datasource problem |
When I first tested it with the Database Schema, it brought out the same error, that the name DB2ADMIN.BIG_HEADER is undefined
I have removed the Schema and use only
INSERT INTO Database.BIG_H ... |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 10:36 am Subject: Datasource problem |
You are right Jeff, the Broker has the token. The error is gone but I'm still not through.
Look at this
2005-08-16 21:20:26.832714 5141 RecoverableException BIP2519E: Error executing SQL ... |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 10:12 am Subject: Datasource problem |
Hang on, I have something like this on Broker log
Aug 16 19:46:19 fieai1es MQSIv500[454784]: (MBDE002.Test_Dev)[1]BIP2201I: Execution Group started: process '454784'; thread '1'; additional informa ... |
| Topic: Datasource problem |
SKAT
Replies: 16
Views: 9005
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 16, 2005 10:01 am Subject: Datasource problem |
| Yes I have wbiadmin account with all rights on the DB and the ODBC connection test is also successful on the control panel. |
