Run PTSpy on Remote Server
We’ve written about using PTSpy to capture Publisher events before, but a lot of times network switches don’t allow UDP messages (the kind generated by this logging subsystem) to go to other machines, even on the same subnet. So even if you can add a message sender for, say, Collab, to a PTSpy instance running on a portal box, there’s still a chance it might not actually capture logging messages.
What most switches DO allow, however, is traffic to mapped drives and file shares. So, what to do if you run PTSpy on a portal machine, add a message sender from another machine, and don’t see traffic? Run PTSpy locally on THAT system. And, even if you didn’t install the portal (which means you don’t get PTSpy in your start menu), you don’t even have to install anything.
Just RDP into the Collab server (or Publisher or Analytics or whatever), start Windows Explorer, and connect to \\SERVER-NAME\SHARE-NAME$\bea\alui\ptlogging\6.1\bin\. Then just double-click PTSpy.exe.
You might have to add the message sender again, but you’re much more likely to be able to capture events this way than trying to run PTSpy on a remote machine and capture them from there.
