In upstream and downstream relationships, anything that happens downstream can have an
adverse affect on upstream configuration items.
In our example relationship, if the virtual server sannnm-01 crashes, the database
instances and the web server upstream are adversely affected. Likewise, if the web server
fails, the web site hosted on it goes down. The CI record for the virtualized Windows
server sannnm-01 with its
upstream and downstream relationships is shown below. The downstream relationships show that
this server is virtualized by VMware running on a Windows
server named sandb01. Our
upstream relationships show a MySQL instance, a SQL instance, and a web server running on
sannnm-01. Farther upstream, a web site is hosted on the web server.
When you delete a CI from the CMDB, ServiceNow also deletes all
relationships with that CI.
Deleting a CI affects references to the CI in Incidents, Problems and Changes. In some
situation, it might be preferable to block a CI by setting the
install_status or hardware_status attributes to
retired, without deleting the CI.
ADM dependencies: example with JBoss and Apache
In this example, the three JBoss application servers on three different physical machines
have a TCP connection to the local Apache application on www.online1.com. Additionally,
there are five Apache web servers using the local JBoss application.