In this Global Customer Support (GCS) video created by @Rett_Hean_GCS, you will learn how to trace offline mobile applications. These techniques are useful when debugging your mobile applications and diagnosing sync related issues.
To see our complete collection of videos, refer to this Support Video search link, which picks up all new Support Videos as they are posted.
Did you find this content helpful?
Want to help us improve this content?
Hi. In a multi node (cluster) environment, will the Tracer show requests from mobile clients that hit a different node than the one on which Tracer has been executed? Thanks.
This is a good question. No it will not. But you might catch yourself with approach 1 anyways, since the list of available requestors to remotely trace would be missing the requestor you are looking for. Also, those familiar with SMA would also inherently be aware of what node they chose once they found the requestor of interest.
But approach 2 is where one could easily make this mistake. So in a multi-node environment, in order for approach 2 to work, you will want to temporarily bring down nodes so you can be certain which node will be hit. In some cases, this might not be feasible, but in many cases it can be, especially for testing.
This is all with the understanding that the tracer utility cannot cross node trace. I am not aware of any enhancements which have added that capability, but I'd be happy if someone surprised and corrected me :)
