Hi Team,
Looking forward for some help. We have developed lot of virtual services and requests do come from different channel for consumption. When certain test fails consumer come and ask if lisa can capture both request and response when it hits SV. I would like to know if there is way to capture them (e.g soap calls) that actually comes/sent and can be made available to consumers at console. Apologies I haven't done deep search on communities as its urgent if it is already answered.
The Console Inspection View in 7.5 is similar to Portal's Inspection View in 9.x and higher. The major difference is the UX. However, both seem likely to fall a bit short of your needs.
I believe some type of customization is necessary.
Off the wall idea? Maybe or maybe not...
This may be a stretch, but what if you created a front-end virtual service that performs what amounts to live invocation? Your consumers call this front-end service. The front-end passes the request to the virtual service back-end. When the response comes back from the virtual service, the request and response are logged to a consumer accessible file share using some type of directory and file naming standard for the R/R pairs.
I don't know if it is feasible to choke all of the services through a single endpoint since I do not know what kind of transaction volumes and response time characteristics you have.
If you are running a functional VSE with a reasonable amount of concurrent input requests, this might create throughput issues which could result in HTTP timeouts.
Logic would need to be added to setup the virtual service endpoint and port -- probably based on analysis of the incoming operation and/or URI information, create a bogus VSI response, send the lisa_vse_request body to the endpoint, and fill in the lisa_vse_response with the response from the downstream service. After the responder step, write the R/R pair to the appropriate directory on the file system. You may also need to marshal the response headers into the lisa_vse_response Meta Data prior to sending the response to the consumer. Rather than a Live Invocation step, you would likely use a REST or WS Execution XML step.
You could get fancy and set up an interface on the front-end that that allows you to enable and disable writing the R/R pairs so transactions are only logged when the "log step" is enabled.
Short of modifying the individual services, the above may or may not be an alternative to consider.
Perhaps, others have ideas....