Architecture > CMS Architecture Considerations

CMS Architecture Considerations

Size of my enterprise: Its all numbers. You need to have an idea of how many servers and network devices you have. Micro Focus CMS (UCMDB and UD) product versions have different capacity boundaries. For example, current CMS (version 10.32) with Oracle Database 12g can handle 150 million CIs and relationships.

Integration points: CMS is often the central point of focus in any reference architecture. Identifying critical integration points will help to design the architecture.

Network layout: For each customer, the network segments are different. You will see different network topology adopted and preached, and will see one of the below structures in your network:

  • IP segmentation based on geo-clustering (for example, country-specific segmentation).
  • IP segmentation based on data center location. Some architectures where spanning is enabled will allow the same IP segments across data centers.
  • PCI, DMZ, and other secure segments.
  • Non-routable islands where IP routing is not allowed.

Network latency: Discovery is network driven. Understanding the latencies across network segments will help to plan the probe location.

Capacity and sizing: Availability, number of users, data center locations, recovery strategy.

Integration scope: Identify integration points for CMS data.