| Author |
Message |
 Topic: Build HTTP POST using x-www-form-urlencoded w/XML as param |
johkar
Replies: 0
Views: 4034
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 25, 2017 8:29 am Subject: Build HTTP POST using x-www-form-urlencoded w/XML as param |
| I need to build a HTTP POST request in ESQL which will pass several parameters in the Body, one of which will be a large XML document passed as a String for the value. By large I mean from .2 up to 25 ... |
| Topic: FileInput Node - File lock |
johkar
Replies: 3
Views: 4847
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jul 11, 2017 5:43 am Subject: FileInput Node - File lock |
| Sounds good. I just wanted to make sure I wasn't missing some documentation. Thanks. |
| Topic: FileInput Node - File lock |
johkar
Replies: 3
Views: 4847
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jul 10, 2017 5:53 pm Subject: FileInput Node - File lock |
| I'm trying to understand when the FileInput node will start processing a file and am not finding definitive documentation. Is it upon the transferring agent to maintain a file lock until the file is ... |
| Topic: Unable to configure SOAP nodes - Broker Toolkit 8.0.0.4 |
johkar
Replies: 11
Views: 10746
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 20, 2017 1:15 pm Subject: Unable to configure SOAP nodes - Broker Toolkit 8.0.0.4 |
In frustration (our replacement PCs have been delayed), I uninstalled and reinstalled the Toolkit. This didn't resolve the issue.
However, what does seem to have resolved the issue (or is a workar ... |
| Topic: REST API not validating incoming JSON |
johkar
Replies: 7
Views: 7330
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 22, 2017 5:02 am Subject: REST API not validating incoming JSON |
https://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc28400_.htm
In general, you cannot validate JSON. There is a thing called JSON schema, but it is not properly st ... |
| Topic: REST API not validating incoming JSON |
johkar
Replies: 7
Views: 7330
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 21, 2017 12:05 pm Subject: Re: REST API not validating incoming JSON |
Any pointers on what I should try?
Is the node set to both complete parsing and validation for Content & Value?
The flow for REST APIs in IIB10 is dynamically generated so there is nothing t ... |
| Topic: REST API not validating incoming JSON |
johkar
Replies: 7
Views: 7330
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 21, 2017 11:42 am Subject: REST API not validating incoming JSON |
IIB 10
10.0.0.6
I'm working on a REST API and I created my yaml file in http://editor.swagger.io/#!/ and it validates.
* There are no errors in the workspace after the Swagger file was imported ... |
| Topic: Route Node error in Filter Pattern in IIB 10 |
johkar
Replies: 4
Views: 4575
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 21, 2017 11:07 am Subject: Route Node error in Filter Pattern in IIB 10 |
Why are there duplicate elements?
Which elements is it complaining about as being duplicate?
Does XSL20 have a namespace with it?
There are no duplicate elements; there is only one entry in ... |
| Topic: Route Node error in Filter Pattern in IIB 10 |
johkar
Replies: 4
Views: 4575
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 21, 2017 10:50 am Subject: Re: Route Node error in Filter Pattern in IIB 10 |
We have a custom XSL node which implements the Saxon parser.
I've got to ask - why a custom node? What's insufficient about the built in facilities??
Turning to your problem, have you considere ... |
| Topic: Route Node error in Filter Pattern in IIB 10 |
johkar
Replies: 4
Views: 4575
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 21, 2017 9:33 am Subject: Route Node error in Filter Pattern in IIB 10 |
We just upgraded to 10.0.0.6 Toolkit from 8.0.0.6. I have a few flows that use a Route Node in which I now get an error in my workspace:
"The $LocalEnvironment/XSL20/Params/Method = 'printPre ... |
| Topic: How to set Timestamp multiple times in ESQL |
johkar
Replies: 15
Views: 20673
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Dec 04, 2016 7:40 pm Subject: How to set Timestamp multiple times in ESQL |
| Thanks adubya and smdavies99. I searched a bit and found the below link which I think outlines what I need to do. I'll need to consult with a teammate who is a Java developer but think we can get it ... |
| Topic: How to set Timestamp multiple times in ESQL |
johkar
Replies: 15
Views: 20673
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Dec 04, 2016 9:44 am Subject: How to set Timestamp multiple times in ESQL |
| The documentation for the ESQL keyword CURRENT_TIMESTAMP and CURRENT_TIME functions say that it retains the same value in the node/flow. I have a need within ESQL to set an updated timestamp from wit ... |
| Topic: AdditionalInstances for One Flow with 2 JMSInputs |
johkar
Replies: 6
Views: 5593
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 27, 2015 12:46 pm Subject: AdditionalInstances for One Flow with 2 JMSInputs |
| I think we will need some additional, but we are still evaluating. Message size can vary a lot, say from 300K to 25 MB with some higher. Pretty typical to be several MB. |
| Topic: AdditionalInstances for One Flow with 2 JMSInputs |
johkar
Replies: 6
Views: 5593
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 27, 2015 9:42 am Subject: AdditionalInstances for One Flow with 2 JMSInputs |
| Correct, I'd do not want JMSInput1 and JMSInput2 to block each other during heavy load. So if I'm following you correctly I'd set the 6 instances (or whatever number we end up at) on each input node ... |
| Topic: AdditionalInstances for One Flow with 2 JMSInputs |
johkar
Replies: 6
Views: 5593
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 27, 2015 9:19 am Subject: AdditionalInstances for One Flow with 2 JMSInputs |
| Thanks for the reply. I think that makes sense, I should set one or the other and in my case it probably makes more sense on the JMSInput nodes. |
