*Content migrated from LinkedIn Group- Enterasys OneFabric Connect Central
By: Salvador Ferrer, Director, Solutions Architecture
Web Services in NetSight are structured in three actual WebServices. Actually there is a bit more happening under the hood. A few more 'undocumented' features that we will be exposing in future releases of NetSight as we define the strategic direction of the product. These are weeks of heavy brainstorming.
But back to what we have today, you can find the full set of methods and variables here:
Summarizing, NetSight Webservices are structured in three different webservices:
-NAC webservices whose base url is https://:8443/axis/services/NACWebService and its wsdl can be accessed in https://:8443/axis/services/NACWebService?wsdl. It is primarily concerned with NAC operations, manipulating the NAC tables in NetSight's database. Adding devices to end system groups, creating users in NAC local database, adding switches under NAC control, accessing end system information in different formats, etc.
-NetSight Device webservices whose base url is https://:8443/axis/services/NACWebService and the wsdl can be accessed in https://:8443/axis/services/NACWebService?wsdl. This one is concerned with manipulation of the device database in NetSight. Adding a device to NetSight, deleting it, creating authentication profiles in NetSight, etc...
-NAC Configuration Webservices in https://:8443/axis/services/NACConfigurationWebService and wsdl in https://:8443/axis/services/NACConfigurationWebService?wsdl. This is web service for complex operations. It is currently used by the fabric configurator in DCM but can be used in standalone configurations. The methods it provides allow to add switches to NAC and create NAC configurations. It can create a nac rule with an associated policy manager role and vlan for endsystems in that rule optionally synchronizing that config with VMware if DCM is installed.
I will go into more detail about the most interesting methods in future posts.