...
Add the fileEventListener.jar file to the system.properties.classpath property in your localsettings settings properties file. For example:
...
- Ensure that the traffic files you want to monitor are being saved in the local directory specified in the File Event Listener's Local Directory to Monitor field. This should be the same directory used in the Data Learning tool's Source Traffic> Directory to Scan for Traffic Files field.
- Add a Data Learning tool as an "outgoing response" output to a responder within the .pva that's associated with the virtual asset using the File Event Listener.
- Configure that Data Learning tool to identify the new traffic and add the new data to the desired Data Repository. See the Data Learning Tooldocumentation for details.
(Optional) By default, the Data Learning tool will execute any time that a file is added, modified, or deleted. If you want it to execute only in one of these cases, configure the responder's Request Body correlation accordingly. For example, the following responder is configured to respond only when the File Event Listener detects a new file in the specified directory.
The listener can trigger three types of events:
fileCreate,fileDelete,fileModify. The following example shows how these events are formatted:Code Block <fileeventlistenerEvents> <fileCreate>path_to_new_file</fileCreate> <fileDelete>path_to_deleted_file</fileDelete> ... </fileeventlistenerEvents>
Info title A Detailed Use Case on Using the File Listener along with the Data Learning Tool For a detailed use case of how to use the File Listener along with the Data Learning tool, see the Data Learning Tool documentation, which explains how to set up an environment that achieves the following objective:
If a virtual asset doesn't know how to respond to a given request, record that request (and its corresponding response from the live service) and add this data to the Data Repository. The next time the virtual asset receives that same request, the appropriate response will be returned.
Third-party Content
This extension does not include any items that have been sourced from third parties. Additional license details are available in this plugin's licenses folder.