Make sure you run traffic on your BizTalk to visualize all dynamic messaging patterns! AIMS is analyzing the actual traffic and NOT filter properties to visualize the dynamic messaging patterns.
Once the AIMS agent is deployed to your BizTalk, it will be able to map all static connections between components (ports & orchestrations). To successfully group and map dependencies between components using publish subscribe, you need to run traffic on those components!
If you have pubsub components without traffic, these components will typically be placed in the group called "Other nodes". As soon as traffic is run on the components (ports, orchestrations), AIMS will be able to detect their dependencies and place them in the proper group.
For instance, the components below (receive, orchestrations and send ports) are mainly being pubsub components. Finding connections in the admin console is close to mission impossible as the filters may be using payload properties for routing
After running traffic through the components, AIMS will be able to track how the messages are flowing between the different components and lock down the different messaging patterns and dependencies.
The components above are then visualized by AIMS in a "Group" as seen below.
Since this is a live representation of all messaging patterns / processes, it will be updated if you change a pubsub filter or add / delete components.