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.
Cisco Fabric Manager Web Services provide application programming interfaces (APIs) that expose Fabric Manager core software functionalities as remote procedure calls to third-party vendors. Software developers can use the APIs to design computer applications that interact with the Fabric Manager Server over the network.
Using Fabric Manager you can monitor MDS switch events, performance, and inventory, and you can perform administrative tasks. Applications can access Fabric Manager Web Services through many protocols and data formats such as HTTP, HTTPS, XML, SOAP and WSDL.
Fabric Manager Web Services provide cross-platform operations. Web Services can interact with .NET applications, C++ applications, and applications written in other programming languages, and Web Services must adhere to accepted conventions to make services interoperable with other applications. For this reason, Fabric Manager Web Services must follow the Java API for XML Web Services (JAX-WS) specification. Fabric Manager Web Services relies on JBoss Web Service (JBoss WS) as a service endpoint engine and as an entry point into the JAX-WS programming model. The framework also allows Fabric Manager Web Services to become an integral part of the Fabric Manager Server run-time environment.