besides to add the TLOG, in the invocation from the client side is something else that it has to be done? I mean in a normal tuxedo client / servervice with transaction in the client we add tpbegin to initiated a transaction , in the case that we are working with SALT and we set a tuxedo service as a WS , the client that invoke tuxedo has to do some work or add something to advice that is initiated a transaction or the same at the end has to tell that is commit or rollback or abort?
Typically your web service client needs to be operating in some sort of transaction management system that can act as a coordinator. This could be a JEE server or Microsoft WCF environment. In any case, the normal process would be for the client to start a transaction in whatever environment it is running, call the Tuxedo service that has been exposed as a web service, and then commit or rollback the transaction.
Oracle Tuxedo Chief Architect