In the gitHub there is a link for GitHub - CA-PM/Interface-Connections
Can you explain what this does?
I believe, per that URL, it resolves the following problem:
"Fixed OpenAPI queries which were missing /pc and were causing auto-complete and list existing connection to fail"
With that in place querying interfaces and their connections via OpenAPI should no longer cause auto-complete or a list of existing connections to fail.
jason_normandin is that correct or is there more to that GitHub posting than meets the eye?
the app is used for the Weathermap app. It sets the ConnectsTo custom attribute on an interface.
Hi @jason normadin
i still get error using GitHub - CA-PM/Interface-Connections, here capture :
Please let me know why my devices not appear.
what is the error you are facing?
What do you mean by "SW" - this should be the name of the target device this interface connects to. As mentioned above, the ConnectsTo relationships are used to plot the lines between devices on the weathermap. If you are missing devices on your map, this is different topic, and I would suggest to review Tech Tip: Troubleshoot CA PC App
I want to create the line between my devices, here capture my weathermap :
I already create custom attribute & device alias, but my devices can't appear on interface connection context.
Ok, so your devices display correctly on the map. For the connection, you should have
Oke Thx LUTZ HOLZBECHER
The problem is, i cannot setting my interfaces connectsTo. I was followed the instruction but still failure after click save.
How did you log in to CA PC? Please note that non-admin users need to be authorized for DA REST calls like the ConnectsTo setting in this app: CA PC Apps and User Authorization
I used admin user. ConnectsTo text box cannot lookup my devices. I think auto complete interface connection app doesn't work properly on my machine.
Do you have zip file interface connection app? i used this one GitHub - CA-PM/Interface-Connections, doesn't work for me.
In this case I would recommend to set the custom attribute with REST client according to Create Custom Attributes - CA Performance Management - 3.5 - CA Technologies Documentation , e.g.
<PortCustomAttributes version='1.0.0'> <ConnectsTo>target device name</ConnectsTo></PortCustomAttributes>
Thank You for your advice, my problem solved now.
just curious about what was the problem and how did you solve it?
I followed your advice about custom attribute port using rest.