Exchange record, replay & more
- Recording exchanges
- Prerequisites
- Run manager UI
- How to make exchanges to record
- Replay & validation using the service registry
- Either run the v0.4 demo or later
- Or build and run manually the service registry (see Setting up the service registry) + the node server (see Setting up the discovery by browsing tool)
Just browse to http://localhost:8084 to access the "run manager" UI. From there, you can create and delete "runs" which are simply a ordered set of HTTP requests, recorded on demand.
Usually, the process would be:
- Type the name of a new run, and start it
- Make some exchanges to let them be recorded
- Stop the run (it will be saved automatically)
When a run is recording, exchanges are captured from two sources:
- From every application configured to use the HTTP monitoring proxy (example: Pure Air Flowers sample)
- From Nuxeo, thanks to a servlet filter (all HTTP requests are captured)
In order to make a feature such as the scheduled validation, a useful set of exchanges to record would be the REST requests that led to the discovery of services. In order to do that, simply use, for instance, the Discovery by Browsing to find some services.
Once you have recorded a run, it is possible to use it to trigger a run-based validation.
- Open the service registry
- Browse to the EasySOA tab (on the top menu), and choose "Validation"
- Confirm to run the validation and make the report appear.
