Web Transaction Test is not working but I can access the internal URL


The Web Transaction test is critical/not working, even though the URL can be reached from the BVE. The URL in question is only accessible within the customer's intranet.

Although the deep web URL transaction tests, once provisioned, run from the DGE or DGE Extension that monitors the device, at the time of creation, the URL is accessed from the Traverse BVE server. localhost or 'intranet' URLs are attempted to be accessed from the Traverse BVE server at creation time.


At the time of test creation, the URL is resolved relative to the Traverse BVE server - and if the URL is accessible only within the customer's intranet - the Traverse BVE server will not resolve to a valid page. To overcome this limitation, you would need to create a script as close to the final one as possible - using a URL that is accessible from the BVE - and then export it to an XML, make edits, and then inject or insert the script back into Traverse which references the intranet URL. From then on, you may create a web URL test on a device and associate it with the script. Below are the steps for the same.

The objective is to be able to add deep web URL transaction scripts from outside the Traverse web interface.

The scripts are executed on the DGE or the DGE Extension (as the case may be) when the tests based on the scripts are executed. However, currently, when the scripts are created from the web interface, the URL specified is accessed from the BVE server (where the Traverse web interface is running). Certain intranet URLs are only accessible from the DGE/DGE Extension, and not from the BVE, making the creation of such deep web URL scripts not possible from the Traverse web interface.

As a workaround you can follow this KB note:

Ensure that you have an existing deep web URL script created from the Traverse web interface (and therefore accessible from the BVE server) similar to the final script you would like to run on the DGE or DGE Extension

* Generate the XML for the existing set of scripts

* Use the XML data as a starting point to create an "insert" input file

* Modify the XML file by replacing/editing existing scripts with the new URL(s) to be monitored.

* Insert the new set of scripts (Note: This does not replace the original set you started with. It adds to the original set)

Detailed steps in the following KB note: https://helpdesk.kaseya.com/hc/en-gb/articles/229045568-How-to-extract-and-insert-Web-Transaction-Test-Scripts- 



Have more questions?

Contact us

Was this article helpful?
1 out of 1 found this helpful

Provide feedback for the Documentation team!

Browse this section