Has anyone come across this use case because currently i could see data in WebServer but not being passed to Application Server/Broker.
Hello @SachinJindal ,
the protocol between Siebel webserver and the Siebel application server is proprietary and it's not supported. That's why you won't see any calls from the webserver down to applications. You can get better insight by defining request attributes for the SWE_* parameters on the webserver level so you can track down the requests. Also, consider using the Siebel extension,, but it will provide you with application-wide metrics, not request-level metrics.
With RUM we had no issues among our customers running Siebel. Our customers don't use comprehensive synthetic scenarios in Siebel, but we did not face any issues so far with simple scenarios. What is the Siebel version you are using?
@SachinJindal you define request attributes for each Siebel SWE parameter you need. The parameters are typically sent using form-encoded data and sometimes as query parameters. Just define both in the request attributes - query parameter and HTTP POST parameter.
There are dozes of the SWE attributes, I find the most useful:
They can be captured on the webserver only. But those requests are 1:1 mapped down to the application server. You won't be able to do any tracing down to the application server and below. But you can still find which calls are not performing as expected and get the values from such requests to be able to troubleshoot them.