in my opinion you can use any interpretation you want. It sounds a bit weird, but it shows the real situation.
BMC shows some best practice examples i.e. in 176785_CMDB7.6.04_DataModelingGuide. However you are not forced to accept it in 100%. You even may change the data structure per your particular needs.
The needs the organization has is the main point of CMDB planning. You are not expected to put every information (CI) and relation in the database. How to show application in your model is directly connected with all contexts it is required to be used.
If you show the IPEndpoint of application's server it is up to you. Consider if price for maintaining this information is relatively not to high comparing to importance of this information. You could resign from showing IPEndpoint and for example implement new relation attributes when connecting 2 servers directly. Morover you could revise requirements and resign from it at all. If in the future the information becomes very important it is possible to expand model and reconcile existing structure with additional information.
Best what you can do when planning the model is to keep trying maintain it small as justifiable.
Looking forward for discussion about my thoughts.
It appears that your figure is representing two verticals; Apache web server and JBoss application server. These are typically two distinct infrastructure elements that are managed seperately.
The Web server serves pages for viewing in a Web browser, while an application server provides methods that client applications can call. In other words, a web server exclusively handles HTTP requests, whereas an application server serves business logic to application programs through any number of protocols.
In my current project, ADDM is discovering runtime software instances of SoftwareServers, ApplicationSystems and ApplicationServices. These make up my infrastructure layer, along with ComputerSystems, Products, OS,... This is "given" or discovered data automatically provided.
These combine to link with the BMC_Applications in the next higher logical CMDB layer. The application CI's and these links are not automated and need to be defined and then applied to ADDM. For example, the Atrium application is dependent on a web server, app server and db server.
The next layer, technical service, is required to show technical functionality delivered by IT, e.g. CMDB or ITSM. Other apps like ARS or ADDM could link to the same tech service. Finally, the Business Service is defining the customer interface, as experienced, along with support for incidents and requests.