| Author |
Message |
 Topic: MQOutput node, ESQL, remote QM |
sudaltsov
Replies: 2
Views: 4608
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 05, 2024 12:04 pm Subject: MQOutput node, ESQL, remote QM |
Hello everybody. When we used local QMs to put the messages, this code worked for us:
set OutputLocalEnvironment.Destination.MQ.DestinationData.queueName = 'QName';
Now we want to put our messages ... |
| Topic: versions in bar file |
sudaltsov
Replies: 2
Views: 5158
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon May 20, 2024 1:31 pm Subject: versions in bar file |
| I assume that you are trying to link the BAR file to the version of code that it was built from. The best way to do that is to link the entire BAR file to a git commit id.I want to know exactly the re ... |
| Topic: versions in bar file |
sudaltsov
Replies: 2
Views: 5158
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 15, 2024 2:37 am Subject: versions in bar file |
Hi folks
It is obvious how to make the msgflow and esql file versions visible in the bar files: there is special property in msgflow, there is $MQSI_VERSION$ in esql.
How about xsd, wsdl files? ... |
| Topic: Is fte:filespec case sensitive? |
sudaltsov
Replies: 1
Views: 23082
|
Forum: IBM MQ File Transfer Edition Posted: Tue Mar 26, 2024 9:08 am Subject: Is fte:filespec case sensitive? |
In fteAnt fte:filespec has srcfilespec parameter described as
"Specifies the source of the file operation. The value of this attribute can include a wildcard." But is it case sensitive or n ... |
| Topic: MQMD header and FTEOutput node |
sudaltsov
Replies: 4
Views: 6853
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 11, 2023 3:17 am Subject: MQMD header and FTEOutput node |
| I know nothing about the FTEOutput node, but I do know that when calling the MQ API to put a message, the contents of the MQMD UserIdentifier are ignored and over-written by the context of the applica ... |
| Topic: MQMD header and FTEOutput node |
sudaltsov
Replies: 4
Views: 6853
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 07, 2023 10:17 am Subject: Re: MQMD header and FTEOutput node |
| More explanation, please.The MQFTE transfers seem to ignore that setting - it is still using the account specified in the MQFTE bridge agent configuration, not the account that we put into OutputRoot. ... |
| Topic: MQMD header and FTEOutput node |
sudaltsov
Replies: 4
Views: 6853
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 07, 2023 6:46 am Subject: MQMD header and FTEOutput node |
| Is there any way to setup MQMD headers (I am interested in User Id) to be used by FTEOutput node? In the documentation, I see nothing relevant. And trying to set OutputRoot.MQMD.UserIdentifier does no ... |
| Topic: SOAPRequest using POST |
sudaltsov
Replies: 4
Views: 3687
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 24, 2021 2:10 am Subject: SOAPRequest using POST |
| Thank you! All is good then |
| Topic: SOAPRequest using POST |
sudaltsov
Replies: 4
Views: 3687
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 24, 2021 12:59 am Subject: SOAPRequest using POST |
| Thank you! But I am using gateway mode, no wsdl |
| Topic: SOAPRequest using POST |
sudaltsov
Replies: 4
Views: 3687
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Aug 23, 2021 11:52 am Subject: SOAPRequest using POST |
Hello all
Is it possible to use SOAPRequest node with POST method? I could not find where I can specify the HTTP method of the request. Am I blind?
Or should I just fallback to HTTPRequest (it has ... |
| Topic: Bad chars : reason to fail |
sudaltsov
Replies: 14
Views: 9810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 09, 2021 7:47 am Subject: Re: Bad chars : reason to fail |
| That's probably the easiest way to force a conversion exception, then. The parse timing shouldn't matter for ASBITSTREAM() though, since it reads the whole message anyway; on-demand parsing should wo ... |
| Topic: Bad chars : reason to fail |
sudaltsov
Replies: 14
Views: 9810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 08, 2021 7:38 am Subject: Re: Bad chars : reason to fail |
So, it does fail then; just not soon enough? Please post the complete error message.
It fails later trying to insert that data into database that cannot handle those characters. I would like to ha ... |
| Topic: Bad chars : reason to fail |
sudaltsov
Replies: 14
Views: 9810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 08, 2021 7:34 am Subject: Bad chars : reason to fail |
| What format is your input message, and what domain are you using in the FileInput node?FileInput is using MRM domain, Text format |
| Topic: Bad chars : reason to fail |
sudaltsov
Replies: 14
Views: 9810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 03, 2021 2:44 am Subject: Bad chars : reason to fail |
That is what I think too. I just wanted to spare a bit of esql code but that is not so critical.
hi...have you tried using Parsing-->Immediate/Complete at the FileInput with ccsid as 367
Of cou ... |
| Topic: Bad chars : reason to fail |
sudaltsov
Replies: 14
Views: 9810
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 03, 2021 2:29 am Subject: Bad chars : reason to fail |
hi...yes, don't think there is way to force a failure at the FileInput node itself butThat is what I think too. I just wanted to spare a bit of esql code but that is not so critical. |
