| Author |
Message |
 Topic: LDAP Query - IIB |
dsteinmann
Replies: 6
Views: 8815
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 26, 2019 12:33 pm Subject: LDAP Query - IIB |
I recently had to implement an LDAP query and did it like this:
package bar.foo.app;
import java.util.ArrayList;
import java.util.Hashtable;
import java.util.List;
import javax.naming.Conte ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Nov 25, 2018 11:42 pm Subject: Reconstruct MQ message from Monitoring Event |
So your MQMD gets parsed fine.
Not only the MQMD, also the RFH2 as I wrote earlier:DataInputStream dis = new DataInputStream(getClass().getResourceAsStream("/mq-msg.bin" ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Nov 25, 2018 1:02 pm Subject: Reconstruct MQ message from Monitoring Event |
Maybe you misunderstood me. Following works fine:DataInputStream dis = new DataInputStream(getClass().getResourceAsStream("/mq-msg.bin"));
MQMD mqmd = new MQMD( ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Nov 25, 2018 6:06 am Subject: Reconstruct MQ message from Monitoring Event |
You are using a DataInputStream to create your header list...
DataInput is an interface, which the class DataInputStream implements. Here a snippet from the JDK implementation:
public class DataIn ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Nov 23, 2018 2:30 pm Subject: Reconstruct MQ message from Monitoring Event |
Yes, the MQData was a good starting point, thank you!
The following method allGood() processes successfully my message 
But the not so nice thing is that I hard-coded the headers. It would fa ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Nov 22, 2018 10:35 pm Subject: Reconstruct MQ message from Monitoring Event |
There should be a way.
I know, it seems such a simple problem. I looked through the whole InputStream in = getClass().getResourceAsStream("/test-mq-messge.bin");
byte[& ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Nov 22, 2018 2:19 am Subject: Reconstruct MQ message from Monitoring Event |
Sure it is possible but it will be damn hard if you don't have the CCSID and format saved to the DB as well.
The Monitoring Event contains the whole MQ message (including MQMD, RFH2). This is why for ... |
| Topic: Reconstruct MQ message from Monitoring Event |
dsteinmann
Replies: 13
Views: 8913
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Nov 21, 2018 10:51 pm Subject: Reconstruct MQ message from Monitoring Event |
| I configured Monitoring Event on a flow with MQ Input node and set the "include bitstream data in payload". I have another flow with an MQ Input node that reads those Monitoring Events from ... |
| Topic: Why do statistics show a lot of time in Label node |
dsteinmann
Replies: 0
Views: 1979
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 28, 2017 2:53 am Subject: Why do statistics show a lot of time in Label node |
During performance tests I looked at the Statistics in the Web UI of my flow (IIB 10.0.0.7 on Windows).
There I see a considerable amount of time in the Label node:
Average Elapsed Average CPU
... |
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Dec 10, 2015 3:27 am Subject: POST multipart/form-data with HTTPRequestNode |
Ok, I did the test again. Here is the ESQL code:
DECLARE CONTENT BLOB ASBITSTREAM(InputRoot.XMLNSC, InputProperties.Encoding, InputProperties.CodedCharSetId);
SET OutputRoot.Properties.Cod ... |
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Dec 10, 2015 2:38 am Subject: POST multipart/form-data with HTTPRequestNode |
That probably will work, and if it does, then you are a lot closer to working out why.
As I wrote previously ("The length or characters used in the boundary string have no influence"), ... |
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 09, 2015 1:52 pm Subject: POST multipart/form-data with HTTPRequestNode |
I don't add this additional CRLF (see top of my post for complete code):
SET OutputRoot.Properties.ContentType = 'multipart/form-data; boundary=----------------------12a063b587462211';
|
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 09, 2015 8:38 am Subject: POST multipart/form-data with HTTPRequestNode |
Now that you have posted twice why not try to post the url/links again.
Good point!
Here is the problem message on the wire created by the MIME domain with the two empty lines between HTTP hea ... |
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 09, 2015 4:10 am Subject: POST multipart/form-data with HTTPRequestNode |
| Sorry, I could not post how the HTTP Request looks on the wire (captured with Wireshark), because the forum did not allow me to enter URLs/links. |
| Topic: POST multipart/form-data with HTTPRequestNode |
dsteinmann
Replies: 10
Views: 16163
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Dec 09, 2015 4:08 am Subject: POST multipart/form-data with HTTPRequestNode |
The flow creates a MIME multipart/form-data message and send it via HTTPRequestNode. Problem is that the target server does not accept the request complaining about wrong boundaries.
The message is ... |
