According to how an Application (cmdb_ci_appl and subclasses) is defined, it represents a specific application running on a specific server. It should run on multiple servers. Rather, you should have an application running on each server. For example:
APP01@LVNAPP01 == Runs on ==> LVNAPP01
APP01@ROMAPP01== Runs on ==> ROMAPP01
APP01@PARAPP01== Runs on ==> PARAPP01
There are two common scenarios where you would have this pattern: in one case you are looking to represent an Application resource that is running on multiple nodes of a Server cluster; in the other case you are running the same Application on multiple servers that are each part of different instances of the overall Business Application, i.e. separate Application Services. In each case, there would be a separate Application CI for each Server, as the Application represents a distinct running process and software installation. How this looks in the Dependency Map will be different depending on which scenario you are looking at.
As for creating an Incident against the Application, typically a user isn't going to be selecting the application directly, but rather, would focus on the Application Service that depends on the specific Application(s); the CI would only be set to the Application either as a result of application monitoring / event management which would automate the incident creation based on where the issue was detected, or based on further analysis by the support team who is working the incident as they get closer to refining the root causes of the incident. However, if the user does select the specific application, they would see only the specific server it is running on. If they wanted to see the Application Service which contains multiple Applications running on multiple Servers, they can refocus the dependency map on the Application Service node.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
