In this article we share an example of a company with multiple CA Automation Point Servers and administrators who are creating multiple shared PPQs with the same name within one PPQ network. This design led to problems with their PPQs and automation, so this document shares a design best practice that will prevent this PPQ problem when followed.
Why CA Automation Point allows define two shared PPQs with the same name on the same PPQ network?
CA Automation Point r11.4.x or r11.5.x
CA Automation Point does not enforce any rules about how you design your PPQs in a peer-to-peer, shared network, son it's possible to create multiple shared PPQs with the same name if a process has not read from, written to, or LISTed the new PPQ remotely, from another system in your PPQ network because the other machines are simply not aware of the new PPQ yet. However, once multiple PPQs with the same name exist in the PPQ network, then the product will get confused when an ADDRESS PPQ command is executed against this PPQ name.
To avoid potential problems that stem from confusion about multiple shared PPQs with the same name, we advise you to identify which Server will host the PPQ, based upon the recommendations in our Design Guidelines section in the product documentation. Once this decision has been made, you should only try to create new shared PPQs on the designated server. CA Automation Point will not allow you to create multiple shared PPQs on the same server.
You can review the PPQ Design Guide following this link located in our website: CA Technologies Documentation