We had a similar requirement and trialed an approach with some limited sucess but never deployed into production.
We had to install a seperate agent into the client JVM but this did not automatically detect the business transactions for us as in our application there is no automated boundary triggers the controller could detect. We had to instead manually configure the transactions for the Client Tier by setting up a custom POJO transaction on the areas of the application that we were looking to monitor.
We were then advised that a transaction could only be detected after repeated executions and did find that it was reporting back into the controller and was able to collate with a matching transaction on the middle tier
We're not unfortunately in the position where we could have added annotations to all of our transactions and application is structured in such a way that a standard naming convention wouldnt have been possible to retrofit into the existing app.
Since our user base far exceeds our licence count we scaled back on these plans for the time being but will be looking for.
We were also not quite prepared to allow our client machines direct access to the network the controller lives on.
