Resolution:
No. A simple upgrade of an RVCM publisher configuration to RVTX publisher will not provide transactional messaging. What you have instead is the "Immediate messaging" feature provided by RVTX which provides simple store-and-forward delivery of certified messages; the RVTX daemon acts as the certified delivery agent for the publisher. The benefit of this upgrade in quality of service from RVCM to RVTX is that the publisher does not have to be running to deliver the certified message.

Use of RVTX transactional messaging in Adapter SDK based application requires:

A) Repository Configuration of the RVTX session, the RVTX endpoint, and the Transaction Control Pool

B) Bracket for transactional send/receive with begin() and commit() calls


EXAMPLES:
SDK provides 2 examples for both C++ and Java, illustrating how to implement RVTX Transactional messaging with SDK:
/tibco/adapter/sdk/examples/cpp/tx, txdb
/tibco/adapter/sdk/examples/java/tx, txdb

I've configured a RVTX publisher with a RVTX session, which is upgraded from RVCM. Does this mean that the publisher will be able to do transactional messaging?