An infrastructure diagram illustrates how
an application is organized into different zones of security and how
the different application components communicate across those zones.
About this task
Although you can model your infrastructure in a variety of
formats, this style of diagram is commonly used to show a high-level
view of how an application and its architecture is organized.
Procedure
- In a topology, add location units to represent the different
zones of security and other areas or organization for the application.
- Select all of the units, right-click one of them, and then
click .
- Optional: Color-code the location units as
necessary to indicate different levels of security. To
change the color of a unit, right-click the unit and then click and the color for the unit.
- Add units to the locations to represent the computer systems
and other components of the infrastructure in each location. At
this level of abstraction, the topology normally includes the units
that are used in logical or operational modeling. You can use node
units to represent a high-level, abstract concept of a computer system,
or you can use more specific units to indicate particular servers
or systems.
- Using application communication constraint links, link
the infrastructure units to indicate how they communicate. Errors on the constraint links indicate that the locations
must be able to communicate if the infrastructure components within
the locations communicate.
- Create network communication constraint links between each
of the locations that must communicate. When the units
are snapped together, as in this diagram, the constraint links are
shown by dashed lines on the borders between the adjacent locations.
- Add components or deployment units to the nodes to represent
the components of the application.
- Link the components or deployment units with application
communication constraint links to indicate how the components of the
application communicate.