• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (1)

1 localhost commented Permalink

Bobby,

 
Thanks for the post, this is a cool new feature, but there are a few things it is worth noting. 1. It has always been possible to connect an MDB to an SIBus in a different cell, it could be achieved by creating a core group bridge. This is not an ideal solution but it is there. This new feature is still really important though since it makes things much easier. 2. If the MDB is connecting to a bus defined in the local cell you do not need the server/cluster the MDB is in to be a bus member, you also do not need to specify provider endpoints. In fact the WebSphere Process Server Golden topology advices placing the MDBs in a different cluster from the messaging engines. This behaviour is documented in the v7 infocenter (link below). 3. This new feature is useful if you have two core groups in a single cell. An MDB running in a server that is part of one core group cannot communicate with a bus whose members are in a different core group, unless you use the provider endpoints feature. 4. When the provider end points are used the bus name property of the activation specification is not ignored, as is suggested by your post. The provider endpoints are consulted in order to find the bus named in the activation specification. 5. You can send messages to a bus in a different cell, and you have always been able to do this, you just configure the connection factory with the appropriate bus name and provider endpoints. You do not need a foreign bus. 6. The term foreign bus only really applies when you connect two or more buses (or queue managers) together. It is foreign because it is not the bus to which the JMS Connection is connected. The term foreign does not apply just because the bus is defined to a different cell.
 
References:
 
WebSphere Process Server Golden Toplogy: http://www.ibm.com/developerworks/websphere/library/techarticles/0803_chilanti/0803_chilanti.html How a message-driven bean connects in a cluster (v7 infocenter): http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.iseries.doc/concepts/cjn_mdb_endpt_overview.html
 
Thanks Alasdair

Add a Comment Add a Comment