So, screenshots and examples below may no longer be completely accurate.I'm experiencing the same problem: SoapUI freezes when I create a new testcase from a request.įirst I'm going to document the bug and second I'll explain you a possible workaround.ġ.- Create a project (I create a REST project)ģ.- Create a resource, a method and a requestĤ.- Click on the test case, display the popup menu and select "Add to TestCase"Īpparently, the test suite is created (the new test suite item is shown in left navigator panel), but Soap UI freezes GUI doesn't respond and you have to kill it manually. There were changes to the API in N-able N-central 2020.1 to remove deprecated methods, and also some data structures and labels were changed for consistency.API calls no longer working when using T_KeyPair and returns items instead of info or issueĮxample SOAP Call (CustomerAdd) -WSDL url.For more information, see the article below or contact N-able Support for assistance: So, screenshots and examples below may no longer be completely accurate. Look at the 2nd column (Method Name!) and click on the appropriate/desired Method to see details.Click on External API's Javadocs > ServerEI2_PortType.This is described in the documentation as described above. In order to make API calls, you will need to know the Method Name, required fields and their format. Once you click on the green submit button, it will pull all the information about that device, based on what that call should be making.įinding and Reviewing the Documentation of API Methods.To get the applianceid of a device, in N-able N-central UI - click on a device>settings>Local Agent and scroll down till you see Appliance ID. Now since there isn't a way to get the deviceid from a device, we'll stick with the applianceid, but we can get the deviceid from the API call.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |