| Author |
Message |
 Topic: Problem verifying signature with WMB7 |
jborella
Replies: 0
Views: 5169
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jan 13, 2014 5:02 am Subject: Problem verifying signature with WMB7 |
I have a SOAP Input node receiving some data. I put the data on a queue and send a reply to the SOAP client whether all went well, using a SOAP Reply Node.
The data exchanged with the client are to ... |
| Topic: Problem with JMS MessageSelector and native MQ. |
jborella
Replies: 1
Views: 3118
|
Forum: IBM MQ Java / JMS Posted: Mon Aug 05, 2013 2:20 am Subject: Problem with JMS MessageSelector and native MQ. |
After two days of working and posting this, I found a solution. According to http://www-01.ibm.com/support/docview.wss?uid=swg21569646 it works if write:
MessageConsumer consumer = session.createC ... |
| Topic: Problem with JMS MessageSelector and native MQ. |
jborella
Replies: 1
Views: 3118
|
Forum: IBM MQ Java / JMS Posted: Mon Aug 05, 2013 1:09 am Subject: Problem with JMS MessageSelector and native MQ. |
| I want to be able to use JMS for programming a Java Client to communicate with a native MQ application in a request/reply scenario. The native MQ application doesn't support RFH2 headers. Unfortunatel ... |
| Topic: BrokerDataSource in WMB v7 |
jborella
Replies: 10
Views: 4961
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 07, 2011 4:19 am Subject: Re: BrokerDataSource in WMB v7 |
You should be testing all of your Broker artifacts continuously. I don't understand why you (or your boss) thinks that system and software does not need to be tested.
I totally agree with You, but un ... |
| Topic: BrokerDataSource in WMB v7 |
jborella
Replies: 10
Views: 4961
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 07, 2011 4:09 am Subject: BrokerDataSource in WMB v7 |
You should be able to create a new ESQL file that defines this variable at the schema level, and add this to the bar file.
"BrokerDataSource" is just a name, after all.
Thanks for the su ... |
| Topic: BrokerDataSource in WMB v7 |
jborella
Replies: 10
Views: 4961
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 07, 2011 4:08 am Subject: BrokerDataSource in WMB v7 |
However the DB2 supplied with WMB 6 is not licensed for business data in the first place.
We are running against a MS SQL server (soon 2008), so there aren't any licensing issues.
Can you define B ... |
| Topic: BrokerDataSource in WMB v7 |
jborella
Replies: 10
Views: 4961
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 03, 2011 4:23 am Subject: Re: BrokerDataSource in WMB v7 |
reading some config, which is stored in the broker database
Why? 
Some extra tables has been added with some routing information. Maybe its bad design, but now it's there and the chal ... |
| Topic: BrokerDataSource in WMB v7 |
jborella
Replies: 10
Views: 4961
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 03, 2011 2:04 am Subject: BrokerDataSource in WMB v7 |
| Our company is planning to upgrade from WMB v6 to v7. We would like to upgrade the environment and then deploy the bar files unchanged from v6. Changing the bar files would require extensive testing, ... |
| Topic: converiting special characters using ESQL and CCSID |
jborella
Replies: 8
Views: 11530
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 03, 2011 1:30 am Subject: converiting special characters using ESQL and CCSID |
I used below esql.But it didnt work
SET Formattedvalue = REPLACE(Formattedvalue,'¼','a');
Have You tried debugging Your flow?
1. You need to verify, that the data are read and understood as cc ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 01, 2010 1:04 am Subject: Problem parsing XML with FileInputNode. |
Glad you got it working. Thank you for being a good citizen and posting the solution.
You are welcome. I always find it frustrating myself, when a thread isn't closed with some kind of solution or co ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 23, 2010 12:34 am Subject: Problem parsing XML with FileInputNode. |
As expected I got a reply from IBM stating:
"The CCSID is mandatory property on File Input node and defaults to broker system default value. FileInput node uses stream based parser which inter ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 02, 2010 1:31 am Subject: Problem parsing XML with FileInputNode. |
| I mean that the MQInput node takes the encoding from the transport ( the MQMD header ) and not from the XML declaration. The FileInput node also takes the encoding from the 'transport' ( I understand ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 02, 2010 12:56 am Subject: Problem parsing XML with FileInputNode. |
If I have understood this correctly:
- the XML has an XML declaration which accurately describes the encoding of the XML document.
- the FileInput node is not reading the XML declaration to determi ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 01, 2010 6:09 am Subject: Re: Problem parsing XML with FileInput node |
| In my humble experience it is often these external systems that are sending incorrect XML formatted messages. Many of these external suppliers have absolutely no idea of the XML Standards & Rules ... |
| Topic: Problem parsing XML with FileInputNode. |
jborella
Replies: 21
Views: 11794
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 01, 2010 5:50 am Subject: Re: Problem parsing XML with FileInput node |
| is it your assertion that for file based XML documents arriving in WMB without encoding information that WMB should assume UTF-8 irrespective of the default CCSID specified on the FileInput node or th ... |
