<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Mapping from WSDL operation names to NaElement names in the Core SDK in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Mapping-from-WSDL-operation-names-to-NaElement-names-in-the-Core-SDK/m-p/116229#M1810</link>
    <description>&lt;P&gt;Well, it would seem that I've asnwered my own question. This&amp;nbsp;&lt;A href="http://mysupport.netapp.com/documentation/docweb/index.html?productID=62158&amp;amp;language=en-US" target="_blank"&gt;http://mysupport.netapp.com/documentation/docweb/index.html?productID=62158&amp;amp;language=en-US&lt;/A&gt; takes you to SDK documentation for the manageability API which includes the API documentation itself. I think I expected that it woudl be part of the SDK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, nothing to see, move along.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Feb 2016 03:55:33 GMT</pubDate>
    <dc:creator>seafoodbuffet</dc:creator>
    <dc:date>2016-02-24T03:55:33Z</dc:date>
    <item>
      <title>Mapping from WSDL operation names to NaElement names in the Core SDK</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Mapping-from-WSDL-operation-names-to-NaElement-names-in-the-Core-SDK/m-p/116227#M1809</link>
      <description>&lt;P&gt;Or this question might be written as "how do I figure out what are the valid Api's that I can call?"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm completely new with the NetApp API but I've read through the SDK documentation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's a simple example, looking at the DFM WSDL, I see that there's an operation called DfmAbout. However, all of the SDK sample code (regardless of language) create the NaServer and pass it an NaElement named "dfm-about". Are all operations patterned like that? e.g.&amp;nbsp;DatasetUpdateProtectionStatus would be datasetup-update-protection-status?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other than reading the WSDL, is there a better/different way to get a list of all of the api names?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:58:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Mapping-from-WSDL-operation-names-to-NaElement-names-in-the-Core-SDK/m-p/116227#M1809</guid>
      <dc:creator>seafoodbuffet</dc:creator>
      <dc:date>2025-06-04T21:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Mapping from WSDL operation names to NaElement names in the Core SDK</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Mapping-from-WSDL-operation-names-to-NaElement-names-in-the-Core-SDK/m-p/116229#M1810</link>
      <description>&lt;P&gt;Well, it would seem that I've asnwered my own question. This&amp;nbsp;&lt;A href="http://mysupport.netapp.com/documentation/docweb/index.html?productID=62158&amp;amp;language=en-US" target="_blank"&gt;http://mysupport.netapp.com/documentation/docweb/index.html?productID=62158&amp;amp;language=en-US&lt;/A&gt; takes you to SDK documentation for the manageability API which includes the API documentation itself. I think I expected that it woudl be part of the SDK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, nothing to see, move along.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2016 03:55:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Mapping-from-WSDL-operation-names-to-NaElement-names-in-the-Core-SDK/m-p/116229#M1810</guid>
      <dc:creator>seafoodbuffet</dc:creator>
      <dc:date>2016-02-24T03:55:33Z</dc:date>
    </item>
  </channel>
</rss>

