Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4Net/ViPR SRM: How to test the APG WebService SOAP-UI (303743)

Last Updated: 5/29/2020Categories: How toTotal Views: 8020Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

This article aims to provide the procedure to test the APG Web Service SOAP-UI.

To do this procedure you must have a working APG installation (ViPR SRM/Watch4Net) and SOAP UI (The SOAP-UI may be downloaded from this link http://www.soapui.org/).

1- Log into the Watch4Net GUI and create or select a report to call (selecting a smaller report will ensure there will not be a timeout issue).

2- To export the report definition:

Verify you have navigated to the report you would like to call.

Select "Edit Mode" from the top tool bar.

On the top right side of the screen select exports and drop down to "Report Definition".

This will download a report definition XML.

3- Open the XML file, using any text editor and Remove all  xsi:  references, all xmlns tags, and change
all tags to the  xt:  namespaces.

Before:

<?xml version="1.0" encoding="UTF-8"?>
<node xmlns="http://www.watch4net.com/APG/Web/XmlTree1" name="Test ws" order="0" singleNodeId="e93efd9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<property xsi:type="NodeFilter" filterExpression="devtype=='Router'"/>
<property xsi:type="ReportPreferences" duration="l1w" preferredPeriod="3600"/>
<property xsi:type="NodePropertyNodeColumn" name="Device" nodeProperty="name"/>
<property xsi:type="PropertyNodeColumn" name="IP" property="ip"/>
<property xsi:type="PropertyNodeColumn" name="Model" property="model"/>
<property xsi:type="PropertyNodeColumn" name="Location" property="location"/>
<property xsi:type="ValueNodeColumn" name="Availability (%)" majorLevel="99.5" criticalLevel="98.0" filterExpression="name=='Availability' &amp; !(part)" forcePeriod="true" period="86400" useTimeRange="true"/>
<property xsi:type="ValueNodeColumn" name="Current Availability (%)" majorLevel="99.0" criticalLevel="95.0" filterExpression="name=='Availability' &amp; !(part)" timeThreshold="600"/>
<formula formulaId="util.ChildCount">
<result name="devices" default="true" graphable="false"/>
</formula>
<node name="Devices" singleNodeId="cc18ba8f" uid="DEVICE-DETAILS" type="application">
<property xsi:type="NodeExpansion" expandOn="device"/>
<property xsi:type="ReportPreferences" displayMode="3" defaultMode="mix" duration="l1w" preferredPeriod="3600" displayedProperties="devtype ip location devdesc"/>
<property xsi:type="NodePropertyNodeColumn" name="Name" nodeProperty="name"/>
<report-layout hspan=".-80cd7286=3,.-4da6b0d8-a982a5cc=3,.-1962a544-f40408ce=1,.-6bae8933=1,.-1962a544=1,.-9a0502e8-1ccc3c15=1" order=".-4da6b0d8-a982a5cc=6,.-1962a544-f40408ce=2,.-6bae8933=1,.-1962a544=4"/>
</node>
</node>

After:

<?xml version="1.0" encoding="UTF-8"?>
<xt:node name="Test ws" order="0" singleNodeId="e93efd9">
<xt:property type="NodeFilter" filterExpression="devtype=='Router'"/>
<xt:property type="ReportPreferences" duration="l1w" preferredPeriod="3600"/>
<xt:property type="NodePropertyNodeColumn" name="Device" nodeProperty="name"/>
<xt:property type="PropertyNodeColumn" name="IP" property="ip"/>
<xt:property type="PropertyNodeColumn" name="Model" property="model"/>
<xt:property type="PropertyNodeColumn" name="Location" property="location"/>
<xt:property type="ValueNodeColumn" name="Availability (%)" majorLevel="99.5" criticalLevel="98.0" filterExpression="name=='Availability' &amp; !(part)" forcePeriod="true" period="86400" useTimeRange="true"/>
<xt:property type="ValueNodeColumn" name="Current Availability (%)" majorLevel="99.0" criticalLevel="95.0" filterExpression="name=='Availability' &amp; !(part)" timeThreshold="600"/>
<xt:formula formulaId="util.ChildCount">
<xt:result name="devices" default="true" graphable="false"/>
</xt:formula>
<xt:node name="Devices" singleNodeId="cc18ba8f" uid="DEVICE-DETAILS" type="application">
<xt:property type="NodeExpansion" expandOn="device"/>
<xt:property type="ReportPreferences" displayMode="3" defaultMode="mix" duration="l1w" preferredPeriod="3600" displayedProperties="devtype ip location devdesc"/>
<xt:property type="NodePropertyNodeColumn" name="Name" nodeProperty="name"/>
<xt:report-layout hspan=".-80cd7286=3,.-4da6b0d8-a982a5cc=3,.-1962a544-f40408ce=1,.-6bae8933=1,.-1962a544=1,.-9a0502e8-1ccc3c15=1" order=".-4da6b0d8-a982a5cc=6,.-1962a544-f40408ce=2,.-6bae8933=1,.-1962a544=4"/>
</xt:node>
</xt:node>

4- Open SOAPui, and create a new project, and point it to your installation Web Service address: http://your_ip_address:portnumber/APG-WS/wsapi/report?wsdl

5- SOAPui automatically creates a default request called  Request 1 . Open it, and remove everything between <rep:getReport> tags.

6-Paste your previously exported report, but only the <node> tags (don t copy the <?xml tags )

7-  Add authentication, in the Request Properties section. Default username and password are: admin/changeme:

8- Click the Submit button, and see results:

* If you get access denied errors you may need to enable remote access to the Web Service as described in the notes section.

Related Information

* Please Note: note that the default APG Web Service configuration only allows access from localhost and the authentication is enabled. To remove the access restriction, comment the RemoteAddrValve element in APG-WS.xml (located in <Tomcat>/conf/Catalina/localhost/). To disable the authentication,edit web.xml (located in <Tomcat>/webapps/APG-WS/WEB-INF) and comment the corresponding section.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

VMware vSphere Client download

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant