The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This guide describes how to install, migrate data from HCM 1.0, and uninstall HCM Dashboard and HCM Mediation. This chapter describes the Hosted Collaboration Mediation (HCM) software.
HCM is intended for use in a Managed Service Provider's (MSP) Network Operations Center (NOC). HCM consists the following two components:
HCM Dashboard provides a single pane view of assurance data in the hosted environment and provides various summaries and reports. HCM Dashboard acts as a bridge among customer-specific implementations of the following domain managers, in a virtualized environment:
•Cisco Unified Operations Manager (CUOM)
•VMware vCenter
•Cisco Fabric Manager Server (FMS)
•Cisco Unified Computing System Manager (UCSM)
HCM Dashboard aggregates data from multiple instances of these domain managers, so that when you log into HCM Dashboard, you can view aggregated customer data in a single window. HCM Dashboard comprises a set of Administration and Dashboard portlets and a Diagnostics portlet.
The Dashboard portlets enable you to aggregate data from each virtualized instance of CUOM, vCenter, FMS, and UCSM.
The Administration portlets enable you to cross-launch to the web pages of the individual instances of CUOM, vCenter, FMS, and UCSM for customer-centric views.
The portlets leverage the existing APIs and make API calls to retrieve information from domain managers. HCM Dashboard supports a VMWare-based deployment and can be installed and operated alongside other portal servers or applications.
See Chapter 2, "Installing, Migrating, and Uninstalling HCM Dashboard" for:
•HCM Dashboard Server Requirements
•HCM Dashboard Pre-Installation Steps
•Installing and Starting HCM Dashboard in a Non-Cluster Setup
•Installing HCM Dashboard in a Cluster Setup
•HCM Dashboard Post-Installation Tasks
•Migrating HCM Dashboard Data from Windows to Linux
The HCM Mediation layer component uses the TM Forum Shared Information/Data Model (SID) as the foundation data model. HCM Mediation implements the SID as its common model to create and maintain the data interoperability layer in Hosted Communications Services. It provides SID-based normalized API to the underlying domain managers.
HCM 1.1 Mediation layer supports the VOSS connectors.
See Chapter 3, "Installing, Migrating, and Uninstalling HCM Mediation" for:
•HCM Mediation Server Requirements
•Installing and Starting HCM Mediation
•HCM Mediation Post-Installation Tasks
•Migrating HCM Mediation Data from HCM 1.0 to HCM 1.1