ADK Tagging not working
I'm attempting to use the ADK sample MultiAppDotNet.exe to test ADK tagging. The pure paths don't link up for some reason. I have both Server.run and Client.run as active and starting pure paths. The client knows it's waiting for a sync invocation to finish, but it just seems to timeout. I've linked to images that show the purepath transition: http://imgur.com/a/0BFv7
DT 5.6 current fixpack.
Hi Michael,
Can you attach the system profile you are using or a session with the server and client PurePath? Did you define custom entry points for the server by any chance (asking since the screenshot shows a Server.run PurePath that would precede all the client activity)...
Best, Roman
Your comment pointed me in the correct direction. I had Server.run as active and start a PurePath. This prevented the pure paths from linking up. Setting that to active, and adding multiply as active solved my problem. I'm surprised it's not possible to have a method participate in it's own pure path within it's process, and a remote path independently.
Another side question: If I have a client calling to the server for a long running operation, and the server calls back to the client to report progress, can I call linkClientPurePath on the server and setTag on the client to track those calls in the same purepath as well?
Thanks for your help!
Mike
As you discovered each method can only be part of one PurePath, not mutiple and wherever the first PurePath is started is where the data is correlated.
Correct, for the scenario with client -> server -> client you will need to use the ADK twice. To make things less confusing lets call the scenario A -> B -> A.
You would use the ADK and say A is the client and B the server first, then you would use the ADK a second time with B the client and A the server. That gets you a PurePath that shows the communication correctly.
Best, Roman
