How to associate an XA Resource Manager with a Corba Native Client?

Question

Hello,
how is a Corba Native (C++) Client associated with an XA Resource Manager? I can't find it in the documentation.
I believe I understand how it works in a Tuxedo native client: buildclient needs "-r <rmname>" and tpinit() needs to include the group name (ubbconfig group with TMS_ORA and OPENINFO).
buildobjclient does not seem have anything like the "-r" option, and the bootstrap object does not seem to have any way to specify a group.
We have a Corba client that updates the database, enqueues into /Q and invokes a transactional Corba service. All three need to be in the same transaction. I am stuck on how to get an XA DB connection.
Thanks...
Roger
PS: The proper solution is to make the client's functionality a service and have the client invoke the service. But that causes other complications.

Answer 1

I got part of the answer from a different thread.
Native clients do not need a TMS_* to start a transaction. On commit/rollback they consult the Global Transaction Table (GTT) to find a TMS_* that is involved in the transaction and delegate the commit/rollback to one of those TMS_*.
For remote clients (using IIOP) the ISH handles the request from the remote client and deals with transaction management.
Roger