| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| service.setMaintainSession(true) for Message Broker ?? |
« View previous topic :: View next topic » |
| Author |
Message
|
| ilabmq |
 Posted: Wed Sep 08, 2010 12:11 pm Post subject: service.setMaintainSession(true) for Message Broker ?? |
 |
|
Newbie
Joined: 02 Sep 2010
Posts: 8
|
in Axis the statefull conversation is maintained via cookies using service.setMaintainSession(true); Does Message Broker allow anything similar?
So far the closest I can find is preserving cookies from HttpInput via setting flag in HTTPRequest and HTTPReply which is not the same as maintaining the multi-call transaction' state.
Without this ability the broker can not replace the old stubs because the WS-Addressing might not be adopted by the provider.
 |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Sep 09, 2010 6:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Hi ilabmq,
The short answer is no. Message Broker is a high-performance messaging engine. IBM has a really nice page that maps the SOA service concepts to Message Broker.
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamsoa.doc/kd4ugmst109.htm
Here is a discussion on SOAP limitations within Broker:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamsoa.doc/kd4ugmst115.htm#limit
Session state is a function of the transport layer. Limitations of the HTTP Transport protocol: If you use two different execution groups, one for the HTTP request flow and one for the HTTP response flow, the correlation between message flow instances cannot be maintained. In this case, only the request message flow instance is monitored.
The ability to monitor services by the remote hostname or IP address form of Requester Identity is supported only for WebSphere Message Broker Version 6.1.0.2 or later. In WebSphere Message Broker Version 6.0.0.5, there is no requester identity or remote hostname and IP address available in the WebSphere Message Broker HTTP transport protocol.
For a server side message flow, if the correlation information between the request and response expires, the response flow fails to find the context for the request flow. In this case the response message is ignored, and the message metric and content information for the response is not written to the log files.
What it boils down to, is you must code for this in your code and message flows in order to preserve state. One way to do this is by storing session state in a database.
Without going into a much longer discussion and work out the actual design, this is the best I can do. Good luck.
Lance
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
