Licensing
Spycer must have the SOAP license enabled.
Configuring and starting Spycer web services (SOAP) API
1. As root user, use a text editor (gedit, nano, vim, etc.) to edit the configuration file found here: /etc/opt/DVS/Spycer/WebService.conf
2. Change the line "Enabled=0" to "Enabled=1"
[Server]
AbsPath=/opt/DVS/Spycer/bin/SpycerWebService
Enabled=1
Username=
Port=8080
IP=127.0.0.1
KeepAlive=true
. . .
3. From the command prompt, enter: service spycerwebservice start
4. To test if service is running, enter the IP address of the Spycer server plus port 8080 into a browser address field. For example:
192.168.1.10:8080
5. The browser should return the Spycer SOAP envelope XML, similar to below:
<SOAP-ENV: Envelope>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
. . .
6. If problem see the web service log at /home/[user]/.DVS/Spycer/log
Gathering the most up-to-date web services definition list (WSDL)
One of the best ways to get the most recent list of definitions available to you when using Spycer webservices you can install whichever version of Spycer is needed, request a temp webservices license (submit a ticket to support@dvsus.com), and query Spycer for its list.
Another quick test is to append the URL with either /?info or /?WSDL:
http://172.24.255.220:8080/?info or http://172.24.255.220:8080/?WSDL
DVS Spycer Webservice Server endpoint=http://172.24.255.220:8080/?info client agent IP=172.24.255.67 Spycer Version=3.1.0.22
See the attached HTML file. It shows all the available commands and responses. The two .txt files need to be renamed with a .xml extension. They are SOAP test cases that can be imported into a SOAP client such as soapUI.
4 Comments