PurePath Behavior When Crossing System Profiles
Hello,
Here is the scenario:
We have two system profiles:
SystemProfile - Shipping Application
SystemProfile - My Application
If a PurePath is created in "My Application" and makes a web request to "Shipping Application" should it create a PurePath in the "Shipping Application" System Profile?
In our current "My Application", I can see that the PurePath indeed follows the trace into the "Shipping Application", however I would also expect to see a PurePath in the "Shipping Application". This is not currently happening. Could this be a support issue?
Is there a way to get the data to show up in both profiles? We have it set up this way due to security concerns. People with access to "Shipping Application" cannot be allowed to have access to "My Application".
Hi David,
The behavior that you're seeing is not unexpected. The "rule" for monitored instances is that if there is a call from one instance to another and those instances are being monitored on the same dT server, then they have to be in the same system profile. Otherwise, the behavior is often exactly what you see here: the PP started in Profile A will "steal" the PP that you expect to start in Profile B. That may not always happen, but it very likely will. The bottom line is that the installation you have here is not a supported one, so the behavior is undefined.
One solution to this if you want to get your desired behavior is to monitor the Shipping Application on a different dT server. Then you would see the outbound web request from My Application, and you would see a corresponding PP start in Shipping Application. Unfortunately you can't set it up so that you see the data showing up in both profiles.
Hope this helps,
Rob
