| Author |
Message |
 Topic: sending 'n' no of attachmnts (MTOM )along with SOAP request |
satheesh.k
Replies: 15
Views: 12770
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Nov 05, 2014 4:53 am Subject: sending 'n' no of attachmnts (MTOM )along with SOAP request |
| In the soap UI properties set the Disablemultiparts = 'false' then u can send multi attachements where this property by default is true |
| Topic: sending 'n' no of attachmnts (MTOM )along with SOAP request |
satheesh.k
Replies: 15
Views: 12770
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Nov 05, 2014 4:52 am Subject: sending 'n' no of attachmnts (MTOM )along with SOAP request |
| In the sopa UI properties set the Disablemultiparts = 'false' then u can send mutli attachements |
| Topic: Process id getting killed and reload the execution group |
satheesh.k
Replies: 1
Views: 1672
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Aug 05, 2014 10:09 pm Subject: Process id getting killed and reload the execution group |
Hi All,
I am working on a TCPIP Calll.
In this flow i will be hitting the TCPIP repeatedly until the required output is received but after certain hits my execution group is restarting before.
... |
| Topic: CLOSING TICPIPRECEIVE NODE CONNECTIONS |
satheesh.k
Replies: 0
Views: 1299
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 27, 2014 5:29 am Subject: CLOSING TICPIPRECEIVE NODE CONNECTIONS |
Hi All,
As per the infocenter we can close the TCPIPReceive Close connection in either of the follwing cases give below
On the Advanced tab, set the properties that determine how the data stream ... |
| Topic: CLOSING TCPIP CONNECTION DURING EXCEPTION |
satheesh.k
Replies: 0
Views: 1087
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 27, 2014 2:38 am Subject: CLOSING TCPIP CONNECTION DURING EXCEPTION |
Hi All,
Currently we are using the TCPIP Client receive node with close connection as after data received.
AND USING THE MRM LAYOUT.
How can we close this connection when there is a exception ... |
| Topic: JMS CCSID from 1208 t0 1051 |
satheesh.k
Replies: 0
Views: 1637
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 27, 2014 12:47 am Subject: JMS CCSID from 1208 t0 1051 |
Hi All,
I am new in configuring and using the JMS NODES.
I have been trying to set the CCSID to 1051 in the JMS Transport and the payload to jms_text and i was able to send to the queue but the ch ... |
| Topic: Expected 6 digit correlation id in the BLOB Format |
satheesh.k
Replies: 8
Views: 6460
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Jan 18, 2014 10:26 pm Subject: Expected 6 digit correlation id in the BLOB Format |
Hi fjb_saper,
Thanks for the response, it was the same case of what you have responsed.
But i have appended the value with the '0' padding and the consumer is receiving it with this '0' padding. ... |
| Topic: Expected 6 digit correlation id in the BLOB Format |
satheesh.k
Replies: 8
Views: 6460
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jan 15, 2014 10:28 pm Subject: Expected 6 digit correlation id in the BLOB Format |
Hi Victor,
The consumer is sending a 6 digit correlation id as JMS correlation id and we receive it in BLOB and they expect only that 6 digits as the correlation id and we are setting this value i ... |
| Topic: Replying 6 digit correlation id to JMSCorrelationID |
satheesh.k
Replies: 2
Views: 3105
|
Forum: General Discussion Posted: Wed Jan 15, 2014 5:08 am Subject: Replying 6 digit correlation id to JMSCorrelationID |
Hi All,
Consumer is sending 6 digit correlation id which will receive in the BLOB format but expecting it in the 6 digit character.
The consumer is using the Jms application and sending only t ... |
| Topic: Expected 6 digit correlation id in the BLOB Format |
satheesh.k
Replies: 8
Views: 6460
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jan 15, 2014 5:04 am Subject: Expected 6 digit correlation id in the BLOB Format |
Hi All,
Consumer is sending 6 digit correlation id which will receive in the BLOB format but expecting it in the 6 digit character.
The consumer is using the Jms application and sending only the ... |
