You have a small organization with multiple Cisco WCS servers. Management has become
cumbersome and you are planning to deploy Cisco WCS Navigator.
When the Cisco WCS Navigator has been deployed, how are the existing Cisco WCS servers
added to the Cisco WCS Navigator, which software versions are supported, and which protocol(s)
do they use to communicate with Navigator?
A.
Cisco WCS Navigator searches the enterprise intranet to locate the existing Cisco WCS
servers and adds them automatically using SOAP as long as there is only a difference of one
version or less between Cisco WCS and WCS Navigator.
B.
Each existing Cisco WCS server must be added manually and use SOAP/HTTP to
communicate with the Cisco WCS Navigator platform as long as the software versions of Cisco
WCS and Cisco WCS Navigator are the same.
C.
Cisco WCS must be on the same software version as Cisco WCS Navigator and each Cisco
WCS server is added automatically using XML over HTTP.
D.
When Cisco WCS Navigator is added, all the Cisco WCS servers must be added manually,
each system must use the same software release as Navigator, and the Cisco WCS
communicates with Cisco WCS Navigator by using SOAP/XML over HTTPS.
Cisco WCS Navigator uses SOAP/XML over HTTPS to communicate with individual WCSs. Cisco WCS Navigator provides monitoring functionality and reporting capability across
all WCSs. In addition, network-wide searches are available. In Windows and Linux operating systems, Cisco WCS Navigator runs as a service continuously and resumes
running after a reboot.
0
0