Hello Stig,
everything is doing well, thanks. And I start shipping APM 10.5.1 to the field some week ago. Hopefully, I finished the job until June.
The map is a nice useless view (sorry), the map can't handle all the resources. See my previous post, https://communities.ca.com/thread/241773193.
So, the first thing to think about is that Experience Cards are only based on the nodes in the map that represent the entry-points of the application - think of it as the end user.
But, yes this is the Problem.
One idea would be to just create a Card based on agentDomain - no filters.
This Card would contain all the domains in the universe, and also pick up new domain-values as they are added to the system. With only one click - you'll have the Experience Cards for each Domain.
Cards based on "agentDomain" are the only useful way I found to use the Cards.
I do the click many times, to add resources to the Cards. But the problem is, I can add available Domain entries only.
For example, I add a new Domain entry to the domains.xml, I can't create a corresponding Card as long as no agent is assigned to the entry.
Second, you will only have attributes assigned to the above node types available to define your Experience Card.
I have a look to the APM Rest API documentation, but I can't find a useful sample to update some attributes on the one hand, on the other, it seems to me, it is necessary to reassign the attributes all the time something was changed or a application is moved.
For example, I assign attributes to JVM jm001, jvm002 and jvm003. The Card is useful as long as the JVMs are running on system A, but if we moved the JVMs to system B the Card is useless. This is the reason I used "agentDomain" only.
I'm able to retrieve some Information via the Rest API only, but I take a look to the PATCH command.
With regards,
Lutz